ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:52:50-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/3439SNL: Bad path in linking commands on Mac2019-03-05T10:52:50-05:00Kitware RobotSNL: Bad path in linking commands on Mac**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3439). Further discussion may take place here.**
---
This applies to a cvs checkout.
I discovered this bug because my own per...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3439). Further discussion may take place here.**
---
This applies to a cvs checkout.
I discovered this bug because my own personal script for launching paraview kept disappearing. I have paraview built in ~/util/src/ParaView-datestring-build. I have a script in ~/util/bin that launches a particular build of paraview. When I build a new paraview, my script disappeared.
I've tracked it down to the linking command. The actual link command cds into GUI/Client and then builds the executable at ../../bin. Before the link command executes, the previous binary is removed. But it uses the same path without cd'ing
first and ends up trying delete the binary somewhere outside of the build directory. Yikes!
And hence, my poor little script which happens to be at ../../bin gets killed.
This problem showed up between 5/4 and 6/23.
Below are the linking commands.
Linking CXX executable ../../bin/paraview
/Users/wkoegle/util/bin/cmake -E remove -f ../../bin/paraview
cd /Users/wkoegle/util/src/ParaView/GUI/Client && c++ -Wno-deprecated -noprebind -g -fPIC "CMakeFiles/paraview.dir/ParaView.o" -o ../../bin/paraview -Lhttps://gitlab.kitware.com/paraview/paraview/-/issues/3394SNL: Automatic reload of Exodus files2019-03-05T10:53:03-05:00Kitware RobotSNL: Automatic reload of Exodus files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3394). Further discussion may take place here.**
---
It would be nice if you could reload the exodus file you're currently viewi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3394). Further discussion may take place here.**
---
It would be nice if you could reload the exodus file you're currently viewing, while staying in Paraview.
It would be ideal if this could be automated (if Paraview would check if the exodus file had been updated every x seconds).https://gitlab.kitware.com/paraview/paraview/-/issues/3072SNL: Arbitrary surface 'probing'2019-03-05T10:53:31-05:00Kitware RobotSNL: Arbitrary surface 'probing'**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3072). Further discussion may take place here.**
---
We would like the ability to probe an arbitrary surface with the probe. The...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3072). Further discussion may take place here.**
---
We would like the ability to probe an arbitrary surface with the probe. The easiest thing to do is have the cutplane intersection with the dataset define the vtkPolyData that will be used for the probing data.https://gitlab.kitware.com/paraview/paraview/-/issues/1551SNL: Annotation Improvements2019-03-05T10:54:23-05:00Kitware RobotSNL: Annotation Improvements**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=1551). Further discussion may take place here.**
---
It would be nice to be able to select font size and hide annotations and la...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=1551). Further discussion may take place here.**
---
It would be nice to be able to select font size and hide annotations and labels. For example the node numbers displayed by pick can cover most of the neighboring cells for high resolution displays and closely spaced nodes. If the user could change size or hide this display, they could see to pick adjacent nodes.https://gitlab.kitware.com/paraview/paraview/-/issues/4136SNL: Allow PT in interactive volume render.2019-03-05T10:51:29-05:00Kitware RobotSNL: Allow PT in interactive volume render.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4136). Further discussion may take place here.**
---
The PT volume renderer is sometimes faster than the HAVS volume renderer. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4136). Further discussion may take place here.**
---
The PT volume renderer is sometimes faster than the HAVS volume renderer. That is probably the case when the user selects PT over HAVS.
The logic for the interactive rendrer should select PT if the data is small enough and PT is the still renderer.https://gitlab.kitware.com/paraview/paraview/-/issues/2699SNL: Add vtkSNL Gradient filter to ParaView GUI2019-03-05T10:53:57-05:00Kitware RobotSNL: Add vtkSNL Gradient filter to ParaView GUI**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2699). Further discussion may take place here.**
---
Please add the vtkGradientFilter in vtkSNL to ParaView's GUI.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2699). Further discussion may take place here.**
---
Please add the vtkGradientFilter in vtkSNL to ParaView's GUI.https://gitlab.kitware.com/paraview/paraview/-/issues/2791SNL: Add Material/Shader support to ParaView2019-03-05T10:53:51-05:00Kitware RobotSNL: Add Material/Shader support to ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2791). Further discussion may take place here.**
---
Allow users to apply library and possibly repository materials through Para...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2791). Further discussion may take place here.**
---
Allow users to apply library and possibly repository materials through ParaView's 'Display' gui tab.https://gitlab.kitware.com/paraview/paraview/-/issues/4391SNL: 2.6: Fatal crash: servers bad X server connection.2019-03-05T10:50:56-05:00Kitware RobotSNL: 2.6: Fatal crash: servers bad X server connection.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4391). Further discussion may take place here.**
---
When running ParaView 2.6, Client/Server on a server that doesn't have a gr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4391). Further discussion may take place here.**
---
When running ParaView 2.6, Client/Server on a server that doesn't have a grapics card, I get the following error:
Process id: 0 >> ERROR: In /projects/viz/paraview/src/ParaView/2.6/ParaView/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 497
vtkXOpenGLRenderWindow (0xcec7e00): bad X server connection. DISPLAY=:0
Process id: 0 >> ERROR: In /projects/viz/paraview/src/ParaView/2.6/ParaView/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 319
vtkXOpenGLRenderWindow (0xcec7e00): bad X server connection. DISPLAY=:0
This is probably the same error as reported on an e-mail listed as PV2.6 Crashes. I am including that e-mail here:
I'm using the released PV2.6 and seeing some strange crashes.
I'm using the Windows Version you guys compiled for the pvclient, and running the PVServer on a linux Cluster. I compiled the server myself with OSMesa ( 6.4.2) & MPI (OpenMPI 1.1.1-1)support, and i'm running it on multiple processors (the number doesn't matter). When I compiled it, I seeded CMake with the following cache:
BUILD_DOCUMENTATION:BOOL=OFF
BUILD_EXAMPLES:BOOL=OFF
BUILD_SHARED_LIBS:BOOL=ON
BUILD_TESTING:BOOL=OFF
CMAKE_BUILD_TYPE:STRING=Release
CMAKE_CXX_COMPILER:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/bin/mpicxx
CMAKE_C_COMPILER:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/bin/mpicc
CMAKE_INSTALL_PREFIX:PATH=/viz/home/rhand/local/pv-2.4
//Path to a file.
MPI_INCLUDE_PATH:PATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1 /include
MPI_LIBRARY:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/lib64/libmpi.so
OPENGL_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OPENGL_gl_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libVTKMesaGL.so
OPENGL_glu_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libVTKMesaGLU.so
OPENGL_xmesa_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OSMESA_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OSMESA_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libOSVTKMesa.so
VTK_OPENGL_HAS_OSMESA:BOOL=ON
VTK_USE_64BIT_IDS:BOOL=ON
VTK_USE_MPI:BOOL=ON
VTK_USE_RPATH:BOOL=OFF
Problem #1:
If I load an ImageData dataset (VTI) and then attempt to use the Clip filter on it, it crashes every time. Also, I get no ghost cells so when I extract an isosurface the process boundaries are clearly visible. I place the Clip Filter at roughly 45-degrees (eyeballed, not much precision) so that it gives me the lower-left half of the data, and when it crashes I get a trace like the following:
Connected to client
Process id: 0 >> ERROR: In /viz/home/rhand/src/pv- 2.6/comp/PV/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 497
vtkXOpenGLRenderWindow (0x5362f50): bad X server connection. DISPLAY=Process id: 0 >> ERROR: In /viz/home/rhand/src/pv- 2.6/comp/PV/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 319
Signal:11 info.si_errno:0(Success) si_code:1(SEGV_MAPERR)
Failing at addr:0x10
[0] func:/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/lib64/libopal.so.0 [0x2a9bf15dd5]
[1] func:/lib64/tls/libpthread.so.0 [0x3dd910c430]
[2] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow13CreateAWindowEv+0x216) [0x2a984e13f6]
[3] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow16WindowInitializeEv+0x12) [0x2a984e21d2]
[4] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow5StartEv+0xd) [0x2a984e249d]
[5] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow14DoStereoRenderEv+0x10) [0x2a98452160]
[6] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow10DoFDRenderEv+0x36b) [0x2a984520fb]
[7] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow10DoAARenderEv+0x46b) [0x2a98451d3b]
[8] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow6RenderEv+0x149) [0x2a98451439]
[9] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow6RenderEv+0x1c) [0x2a984e437c]
[10] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN25vtkOpenGLExtensionManager20ReadOpenGLExtensionsEv+0xc0) [0x2a984ab450]
[11] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN25vtkOpenGLExtensionManager6UpdateEv+0x52) [0x2a984aac12]
[12] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN32vtkPVOpenGLExtensionsInformation14CopyFromObjectEP9vtkObject+0xf9) [0x2a955b0bf9]
[13] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN17vtkSelfConnection17GatherInformationEjP16vtkPVInformation17vtkClientServerID+0x83) [0x2a955dc163]
[14] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN20vtkMPISelfConnection17GatherInformationEjP16vtkPVInformation17vtkClientServerID+0x64) [0x2a9559e684]
[15] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN19vtkClientConnection15SendInformationER21vtkClientServerStream+0x1d5) [0x2a9558ff65]
[16] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_Z39vtkClientConnectionGatherInformationRMIPvS_ii+0x48) [0x2a955900b8]
[17] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkParallel.so.pv2.6(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x9e) [0x2a9707ef6e]
[18] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkParallel.so.pv2.6(_ZN25vtkMultiProcessController11ProcessRMIsEii+0xa0) [0x2a9707f3b0]
[19] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN19vtkRemoteConnection20ProcessCommunicationEv+0x14) [0x2a955d9fb4]
[20] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN33vtkProcessModuleConnectionManager18MonitorConnectionsEm+0x2d9) [0x2a955d81d9]
[21] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN16vtkProcessModule11StartServerEm+0x76) [0x2a955cb676]
[22] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN16vtkProcessModule5StartEiPPc+0x24d) [0x2a955ce8cd]
[23] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVFilters.so(_ZN9vtkPVMain3RunEP12vtkPVOptions+0x7b) [0x2a95857b7b]
[24] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/pvserver-real(main+0xc2) [0x402482]
[25] func:/lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x3dd881c3fb]
[26] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/pvserver-real(__gxx_personality_v0+0x5a) [0x40232a]
*** End of error message ***
If I load the same ImageData Dataset & apply the D3 filter, then attempt to use the Clip filter, it works. I have alot of rendering artifacts (I think due to the Structured->Unstructured conversion) and it takes ALOT of memory, but it works.https://gitlab.kitware.com/paraview/paraview/-/issues/2966SNL: "Split Parts" filter request2019-03-05T10:53:44-05:00Kitware RobotSNL: "Split Parts" filter request**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2966). Further discussion may take place here.**
---
Not sure how difficult this is. Our users would like to be able to 'fan out...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2966). Further discussion may take place here.**
---
Not sure how difficult this is. Our users would like to be able to 'fan out' parts based on part ids in their datasetshttps://gitlab.kitware.com/paraview/paraview/-/issues/3479SNL: We need to be able to color blocks differently2019-03-05T10:52:50-05:00Kitware RobotSNL: We need to be able to color blocks differently**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3479). Further discussion may take place here.**
---
We need to be able to color blocks differently - using a different color ma...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3479). Further discussion may take place here.**
---
We need to be able to color blocks differently - using a different color map per block. For instance, if a user wants to select block number 30, and turn it red while leaving the rest of an object colored by tempurature. Or, a user may want ALL blocks blue, except for wanting block number 3000 to be red.https://gitlab.kitware.com/paraview/paraview/-/issues/4476SNL: Cube axes doesn't go away2019-03-05T10:50:36-05:00Kitware RobotSNL: Cube axes doesn't go away**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4476). Further discussion may take place here.**
---
The cube axes doesn't go away properly, after the filter that created it is...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4476). Further discussion may take place here.**
---
The cube axes doesn't go away properly, after the filter that created it is deleted.
* Run ParaView 2.6, XP.
* Open Can.
* clip can
* Turn on Cube Axes.
* Delete the clip.
The cube axes will still be visible, and possibly in the wrong location.https://gitlab.kitware.com/paraview/paraview/-/issues/12606Snapshot resolution can't be set via script2020-05-04T22:22:34-04:00Kitware RobotSnapshot resolution can't be set via script**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12606). Further discussion may take place here.**
---
There is no way to set or change the snapshot resolution/quality in python...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12606). Further discussion may take place here.**
---
There is no way to set or change the snapshot resolution/quality in python scripts. WriteImage() has no such options. There is no documentation on
it either.
'Recording script' gives nothing during 'save snapshot' dialog manipulation.
https://gitlab.kitware.com/paraview/paraview/-/issues/7799Snap to timesteps should only snap to timesteps of visibile objects2019-03-05T10:43:55-05:00Kitware RobotSnap to timesteps should only snap to timesteps of visibile objects**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=7799). Further discussion may take place here.**
---
An annoying "feature" of snap to timesteps animation is that it will snap t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=7799). Further discussion may take place here.**
---
An annoying "feature" of snap to timesteps animation is that it will snap to timesteps of objects that no one is looking at. This is problematic when, say, someone loads in data and then uses the temporal shift scale filter to change the time range. You really only want to snap to the timesteps after the temporal shift scale, but ParaView also snaps to timesteps of the original data, which may even be outside the range of the desired time.
To observe, load the blow file series (found FileSeries directory of the ParaView data), warp by vector, and add a temporal shift scale with shift and scale both 10. Play the animation. You will see that the first part of the animation does nothing because it is playing timesteps from the original data set that are outside of the range of the desired time.https://gitlab.kitware.com/paraview/paraview/-/issues/4486Snap to TimeSteps by default2019-03-05T10:50:36-05:00Kitware RobotSnap to TimeSteps by default**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4486). Further discussion may take place here.**
---
If a user loads a data set with discrete time steps, then the animation pla...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4486). Further discussion may take place here.**
---
If a user loads a data set with discrete time steps, then the animation play mode should default to Snap to TimeSteps (or maybe that should just be the default on program startup). We have lots of users who will expect PV to animate through all the time steps in their data, and they may be very upset if that is not the case.https://gitlab.kitware.com/paraview/paraview/-/issues/9577Snap to point for spline2019-03-05T10:41:23-05:00Kitware RobotSnap to point for spline**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9577). Further discussion may take place here.**
---
It would be good if the spline source points could be snapped to the neares...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9577). Further discussion may take place here.**
---
It would be good if the spline source points could be snapped to the nearest mesh point when holding down a key and moving.https://gitlab.kitware.com/paraview/paraview/-/issues/4485Snap to each and every time step2019-03-05T10:50:36-05:00Kitware RobotSnap to each and every time step**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4485). Further discussion may take place here.**
---
When the "Snap to TimeSteps" option is selected for the animation play mode...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4485). Further discussion may take place here.**
---
When the "Snap to TimeSteps" option is selected for the animation play mode, it does not actually snap to all of the time steps. Instead, you still need to enter the number of frames. Presumably the animator is snapping to the time steps, but it does not visit each one exactly once.
When the "Snap to TimeSteps" option is selected, the "No. Of Frames" option should be greyed out, and the animation should visit every time step defined in the data.https://gitlab.kitware.com/paraview/paraview/-/issues/22138smTestDriver: add documentation for features supported2023-05-11T08:55:48-04:00Ben BoeckelsmTestDriver: add documentation for features supportedThe following discussion from !6253 should be addressed:
- [ ] @cory.quammen started a [discussion](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6253#note_1358574): (+1 comment)
> This seems like a reasonable chan...The following discussion from !6253 should be addressed:
- [ ] @cory.quammen started a [discussion](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6253#note_1358574): (+1 comment)
> This seems like a reasonable change to me. There isn't a clear place for documentation for this environment variables (or the previously existing environment variable), so I suggest just merging as is as it adds a useful feature and the lack of documentation does not make anything worse.
---
`smTestDriver` has all kinds of hidden knobs that we should document. Somewhere.https://gitlab.kitware.com/paraview/paraview/-/issues/18726smTestDriver doesn't allow for nprocs at runtime2020-12-16T17:34:44-05:00Ben BoeckelsmTestDriver doesn't allow for nprocs at runtimeCurrently, `smTestDriver` hard-codes the number of processors to use for MPI tests at runtime. It should support taking a command line flag to change this.
Cc: @utkarsh.ayachitCurrently, `smTestDriver` hard-codes the number of processors to use for MPI tests at runtime. It should support taking a command line flag to change this.
Cc: @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/22306smTestDriver crashes when QT_QPA_PLATFORMTHEME variable is set2023-09-22T03:23:21-04:00Louis GombertsmTestDriver crashes when QT_QPA_PLATFORMTHEME variable is setSteps to reproduce on Linux :
- install a Qt theme
- set environment variable `$QT_QPA_PLATFORMTHEME`, either manually or through qt5ct
- run a rendering test (eg `ctest -R pv.PythonShellRunScript`)
Running the test manually using `...Steps to reproduce on Linux :
- install a Qt theme
- set environment variable `$QT_QPA_PLATFORMTHEME`, either manually or through qt5ct
- run a rendering test (eg `ctest -R pv.PythonShellRunScript`)
Running the test manually using `paraview` executable works fine, but not using `smTestDriver` executable or `ctest`.https://gitlab.kitware.com/paraview/paraview/-/issues/16126Smarter spreadsheet column widths2019-01-04T20:09:35-05:00Kitware RobotSmarter spreadsheet column widths**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16126). Further discussion may take place here.**
---
Please make the spreadsheet view have smarter column widths. An example w...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16126). Further discussion may take place here.**
---
Please make the spreadsheet view have smarter column widths. An example where this fails is with can.exo. Do the following:
* Linux, 5.0.1, local server.
* Open can.exo. All vars on. Apply.
* Split screen horizontal. spreadsheet view. Turn on visibility.
Notice that the Points X, Y, Z doesn't show up properly.
5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachit