ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:46:21-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/6264Python shell doesn't know that it has an active connection.2019-03-05T10:46:21-05:00Kitware RobotPython shell doesn't know that it has an active connection.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6264). Further discussion may take place here.**
---
This is a bug/feature/annoyance from a user. It would be nice to have it f...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6264). Further discussion may take place here.**
---
This is a bug/feature/annoyance from a user. It would be nice to have it fixed for 3.4.
I am trying to update the python scripting work we did to use the
servermanager interface. I am using the mac builds of paraview 3.2.1
which I downloaded from the public download page at kitware (both the
mac style app and the tgz.)
Another problem I am having is that when I open the python shell
form the gui, it doesn't know it has an active connection. That is,
after setting the paths with an import command and importing the servermanager module,
I try
Print servermanager.ActiveConnection
And it prints None. I can see the builtin server in the pipeline manager
in the client window when this happens. I can start another connection,
Connection = servermanager.Connect()
And it appears in the pipeline browser and I get another display window
in the gui.
import command is:
import sys
sys.path.apend('/usr/local/paraview3/paraview-3.2.1-Darwin-i386/lib/para
view-3.2',
'/usr/local/paraview3/paraview-3.2.1-Darwin-i386/lib/paraview-3.2/paravi
ew')
https://gitlab.kitware.com/paraview/paraview/-/issues/6263Servermanager module not in default path2019-03-05T10:46:21-05:00Kitware RobotServermanager module not in default path**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6263). Further discussion may take place here.**
---
The following bug/annoyance/feature is from a user. It would be nice to ge...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6263). Further discussion may take place here.**
---
The following bug/annoyance/feature is from a user. It would be nice to get it fixed for 3.4.
I am trying to update the python scripting work we did to use the
servermanager interface. I am using the mac builds of paraview 3.2.1
which I downloaded from the public download page at kitware (both the
mac style app and the tgz.)
One annoying thing is that the location of the servermanager module
is not in the default path known by paraview. If I run pvpython or the
python shell from the GUI, in both cases I have to
import sys
sys.path.apend('/usr/local/paraview3/paraview-3.2.1-Darwin-i386/lib/para
view-3.2',
'/usr/local/paraview3/paraview-3.2.1-Darwin-i386/lib/paraview-3.2/paravi
ew')
It would also be nice to have the current working directory in the path
as well, at least for pvpython.
https://gitlab.kitware.com/paraview/paraview/-/issues/6262Selection Inspector cannot display Cell Label GlobalElementId2019-03-05T10:46:21-05:00Kitware RobotSelection Inspector cannot display Cell Label GlobalElementId**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6262). Further discussion may take place here.**
---
ParaView 3.2.1, XP.
Open can.exo.
Make Selection Inspector visible.
Sele...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6262). Further discussion may take place here.**
---
ParaView 3.2.1, XP.
Open can.exo.
Make Selection Inspector visible.
Select Cells On - rubber band select some cells.
On the Selection Inspector/Display Style/ Cell Label, check Visible. Label Mode: GlobalElementId.
Lots of output messages, from vtkLabeledDataMapper.cxx, line 289 "Deed input data to render labels".
This functionality/bug fix is needed by a user. Should be fixed for 3.4.
https://gitlab.kitware.com/paraview/paraview/-/issues/6246Extract selection through has errors when animating.2019-03-05T10:46:21-05:00Kitware RobotExtract selection through has errors when animating.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6246). Further discussion may take place here.**
---
ParaView 3.2.1, XP
* can.exo.
* Select Cells THROUGH (Not ON - On works...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6246). Further discussion may take place here.**
---
ParaView 3.2.1, XP
* can.exo.
* Select Cells THROUGH (Not ON - On works) on the back of the can.
* Filters/ Data Analysis/ Extract Selection
* Copy Active Selection - Apply.
* Animate. Notice that the cells will disappear.
Ken - think this is a Priority of High? I wanted medium-high.https://gitlab.kitware.com/paraview/paraview/-/issues/6245Hologram needs Rescale to Data Range button2019-03-05T10:46:21-05:00Kitware RobotHologram needs Rescale to Data Range button**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6245). Further discussion may take place here.**
---
ParaView 3.2.1, on XP.
* Open can.exo.
* Split horizontal.
* Histogram...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6245). Further discussion may take place here.**
---
ParaView 3.2.1, on XP.
* Open can.exo.
* Split horizontal.
* Histogram filter. Select DISPL as the scalar.
* Animate.
* The bars stay colored blue, except the right most one.
* Display tab/ select Use Points. Display goes multi-colored.
* Display tab/ Turn off use points. Display stays multi-colored
The histogram filter needs a Rescale to Data Range button on the Display tab.https://gitlab.kitware.com/paraview/paraview/-/issues/6240Global IDs not read as vtkIdType from vtkXMLUnstructuredGridReader2019-03-05T10:46:21-05:00Kitware RobotGlobal IDs not read as vtkIdType from vtkXMLUnstructuredGridReader**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6240). Further discussion may take place here.**
---
When reading a VTK XML Unstructured Grid file with Global IDs set, ParaView...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6240). Further discussion may take place here.**
---
When reading a VTK XML Unstructured Grid file with Global IDs set, ParaView recognizes that there are Global Ids set (the Use Global Ids check box becomes available in both the Plot Point Over Time and the Selection Inspector), but they not valid -- e.g. they are listed as "int" rather than "idtype" in the Information tab.
When points are selected, the Selection Inspector shows the Index for the points, but if you check Use Global Ids the list goes blank. In the Selection Inspector if you then try to uncheck Use Global Ids, ParaView crashes.https://gitlab.kitware.com/paraview/paraview/-/issues/6239Rescale to Data Range in bar chart/histogram2019-03-05T10:46:21-05:00Kitware RobotRescale to Data Range in bar chart/histogram**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6239). Further discussion may take place here.**
---
When displaying a histogram in a bar chart type of view, you should have fu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6239). Further discussion may take place here.**
---
When displaying a histogram in a bar chart type of view, you should have full control of the coloring used for the bars (which is based on the scalar of the histogram). This includes a button for Rescale to Data Range much like there is for 3D views.https://gitlab.kitware.com/paraview/paraview/-/issues/6235clicking on the "Time" bar of the Animation view crashes ParaView (binary dis...2019-03-05T10:46:21-05:00Kitware Robotclicking on the "Time" bar of the Animation view crashes ParaView (binary distribution of ParaView 3.2, winXP)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6235). Further discussion may take place here.**
---
Configuration : winXP SP2, binary distribution of ParaView 3.2
Start Par...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6235). Further discussion may take place here.**
---
Configuration : winXP SP2, binary distribution of ParaView 3.2
Start ParaView3, open the Animation View, left click on the "Time" bar (see the red dot on Time_bug.jpg)https://gitlab.kitware.com/paraview/paraview/-/issues/6233Data that has a VERY small scale doesn't display and resize properly.2019-03-05T10:46:21-05:00Kitware RobotData that has a VERY small scale doesn't display and resize properly.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6233). Further discussion may take place here.**
---
Note - this must be done exactly as below to see bug.
Source/ Sphere/ Ap...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6233). Further discussion may take place here.**
---
Note - this must be done exactly as below to see bug.
Source/ Sphere/ Apply.
TransformFilter.
Scale X=1e-5, Y=1e-5, Z=1e-5. Apply.
Hit Reset. Object never appears. Center cross gets very small. The lower left XYZ arrows get big.
Hit Reset. Object never appears. Center cross goes away.
Scale X=1e-4, Y=1e-4, Z=1e-4. Apply.
Hit Reset. Sphere is still gone.
Change eye focus to the SphereSource. Sphere is gone.
Hit Reset. Sphere is visible. (Sometimes the screen goes white, and it takes a second reset.)
Hit Reset. Sphere is visible.
Change eye focus to the Transform. Sphere is back.
This occurs with exodus files also (and I suspect, everything).
I am marking it as severe (major), but not seen (low priority).
https://gitlab.kitware.com/paraview/paraview/-/issues/6232(MARS-high) Crash on Edit Scalar Range2019-03-05T10:46:21-05:00Kitware Robot(MARS-high) Crash on Edit Scalar Range**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6232). Further discussion may take place here.**
---
We were running client/server and had a CTH reader->CellToPoint->Calculator...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6232). Further discussion may take place here.**
---
We were running client/server and had a CTH reader->CellToPoint->Calculator->3xContour. When we hit Edit Scalar range for the second time, the paraview client segfaulted.
This happens with exodus data as wellhttps://gitlab.kitware.com/paraview/paraview/-/issues/6228Exodus reader needs to be able to handle 2d cylindrical axisymmetric coordina...2019-03-05T10:46:21-05:00Kitware RobotExodus reader needs to be able to handle 2d cylindrical axisymmetric coordinates.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6228). Further discussion may take place here.**
---
My user explains the problem as follows:
> ALEGRA can also run in cyli...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6228). Further discussion may take place here.**
---
My user explains the problem as follows:
> ALEGRA can also run in cylindrical axisymmetric (r-z) coordinates. If
> you find that there are 2 coordinate dimensions, could you look for
> trailing {R,Z} in addition to {X,Y}? For whatever reason, we sometimes
> write r-z vector components DISPLX, DISPLY and e.g. B_R, B_Z in the same exodus > file.
https://gitlab.kitware.com/paraview/paraview/-/issues/6227Exodus reader not applying displacements to meshes for 2d data.2019-03-05T10:46:21-05:00Kitware RobotExodus reader not applying displacements to meshes for 2d data.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6227). Further discussion may take place here.**
---
To quote my user and Dave's reply,
> It seems that with the new reader, ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6227). Further discussion may take place here.**
---
To quote my user and Dave's reply,
> It seems that with the new reader, the displacements are not applied
> to the mesh when that option is selected. This happens for 2D data
> (quad4 elements) but not for 3D hex8 elements, which are displaced
> appropriately. Was there any change in the logic detecting the
> displacement variable in the new reader?
Yes, the way patterns in variable names are detected and turned from a set of scalars into a single vector has changed. I can see what's wrong and should have a fix later this afternoon; it would still be nice to have a sample file to test with, though. Alan should be bugging you about that and about the priority of the problem.
> The displacement variable is called DISPL{X,Y,Z} by ALEGRA, but the
> velocity has an underscore, VELOCITY_{X,Y,Z}.
As far as the reader is concerned, only the first 3 characters and the last one character of the variable name are examined when searching for displacement vectors. In general, a set of consecutively stored variables with the same name that differ only by a trailing X, Y, and Z are turned into vectors. I'll fix that so that Z is not required when the coordinate dimension is 2.
https://gitlab.kitware.com/paraview/paraview/-/issues/6218(MARS-low) arrow keys control camera rotation/translation2019-03-05T10:46:21-05:00Kitware Robot(MARS-low) arrow keys control camera rotation/translation**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6218). Further discussion may take place here.**
---
We'd like the ability to use the arrow keys to rotate or translate the came...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6218). Further discussion may take place here.**
---
We'd like the ability to use the arrow keys to rotate or translate the camera in fixed intervalshttps://gitlab.kitware.com/paraview/paraview/-/issues/6217(MARS-low) Add tickmarks to scalar bar widget2019-03-05T10:46:21-05:00Kitware Robot(MARS-low) Add tickmarks to scalar bar widget**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6217). Further discussion may take place here.**
---
The scalar bar widget should have tick marks that indicate whether it's sho...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6217). Further discussion may take place here.**
---
The scalar bar widget should have tick marks that indicate whether it's showing a linear or log-scalehttps://gitlab.kitware.com/paraview/paraview/-/issues/6213(MARS-normal) Fix lighting when scaling by a negative factor2019-03-05T10:46:21-05:00Kitware Robot(MARS-normal) Fix lighting when scaling by a negative factor**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6213). Further discussion may take place here.**
---
When an actor is scaled by a negative value, the normals look wrong. Some p...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6213). Further discussion may take place here.**
---
When an actor is scaled by a negative value, the normals look wrong. Some polygons are front-facing and others are back-facing leading to lighting issues.https://gitlab.kitware.com/paraview/paraview/-/issues/6210(MARS-high) CTH Reader should combine X,Y, and Z velocity into a vector2019-03-05T10:46:21-05:00Kitware Robot(MARS-high) CTH Reader should combine X,Y, and Z velocity into a vector**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6210). Further discussion may take place here.**
---
If X, Y, and Z velocity are enabled (or X and Y), the 3 (or 2) values shoul...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6210). Further discussion may take place here.**
---
If X, Y, and Z velocity are enabled (or X and Y), the 3 (or 2) values should be made into a vector.https://gitlab.kitware.com/paraview/paraview/-/issues/6209Automatic updates2019-03-05T10:46:21-05:00Kitware RobotAutomatic updates**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6209). Further discussion may take place here.**
---
It would be nice if ParaView provided automatic updates. That is, it would...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6209). Further discussion may take place here.**
---
It would be nice if ParaView provided automatic updates. That is, it would periodically check to see if a new stable version of ParaView is available and allow the user to download it (perhaps by simply taking them to the download web site).https://gitlab.kitware.com/paraview/paraview/-/issues/6208Cannot select scalar to vary radius of tube filter2019-03-05T10:46:21-05:00Kitware RobotCannot select scalar to vary radius of tube filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6208). Further discussion may take place here.**
---
The tube filter has a "Vary radius" option that allows you to vary the radi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6208). Further discussion may take place here.**
---
The tube filter has a "Vary radius" option that allows you to vary the radius of the tube based on a scalar or vector. However, you are not able to select the scalar or vector to use. Instead, the active scalar or vector is taken.
The tube filter should allow you to select the scalar or vector. Ideally, it would also automatically select scalars or vectors based on what variable the user selected.https://gitlab.kitware.com/paraview/paraview/-/issues/6189Triangle strips + color by cell in image data causes crashes2019-03-05T10:46:28-05:00Kitware RobotTriangle strips + color by cell in image data causes crashes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6189). Further discussion may take place here.**
---
Try the following:
* Set triangle strips on
* Load attached data
* Col...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6189). Further discussion may take place here.**
---
Try the following:
* Set triangle strips on
* Load attached data
* Color by rasterData
= crash
Here is part of the stack trace:
0 GLEngine 0x52e395f9 glColor4ubv_Comp + 52
1 libGL.dylib 0x92b27e10 glColor4ubv + 83
2 libvtkRendering.pv3.3.dylib 0x2493767b vtkOpenGLPainterDeviceAdapter::SendAttribute(int, int, int, void const*, unsigned long) + 3171 (vtkOpenGLPainterDeviceAdapter.cxx:358)
3 libvtkRendering.pv3.3.dylib 0x2490037f vtkStandardPolyDataPainter::DrawCells(int, vtkCellArray*, int, vtkShaderDeviceAdapter*, vtkRenderer*, int, int) + 1131 (vtkStandardPolyDataPainter.cxx:310)
4 libvtkRendering.pv3.3.dylib 0x249015dc vtkStandardPolyDataPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 1212 (vtkStandardPolyDataPainter.cxx:235)
5 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
6 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
7 libvtkRendering.pv3.3.dylib 0x248c3374 vtkPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 72 (vtkPainter.cxx:217)
8 libvtkRendering.pv3.3.dylib 0x248d336c vtkPrimitivePainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 2250 (vtkPrimitivePainter.cxx:276)
9 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
10 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
11 libvtkRendering.pv3.3.dylib 0x24870b53 vtkChooserPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 937 (vtkChooserPainter.cxx:349)
12 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
13 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
14 libvtkRendering.pv3.3.dylib 0x248c3374 vtkPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 72 (vtkPainter.cxx:217)
15 libvtkRendering.pv3.3.dylib 0x2495122b vtkOpenGLRepresentationPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 253 (vtkOpenGLRepresentationPainter.cxx:79)
16 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
17 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
18 libvtkRendering.pv3.3.dylib 0x248c3374 vtkPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 72 (vtkPainter.cxx:217)
19 libvtkRendering.pv3.3.dylib 0x249363e5 vtkOpenGLLightingPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 601 (vtkOpenGLLightingPainter.cxx:139)
20 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
21 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
22 libvtkRendering.pv3.3.dylib 0x248c3374 vtkPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 72 (vtkPainter.cxx:217)
23 libvtkRendering.pv3.3.dylib 0x2492b1f3 vtkOpenGLCoincidentTopologyResolutionPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 221 (vtkOpenGLCoincidentTopologyResolutionPainter.cxx:77)
24 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
25 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
26 libvtkRendering.pv3.3.dylib 0x248c3374 vtkPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 72 (vtkPainter.cxx:217)
27 libvtkRendering.pv3.3.dylib 0x2492b99b vtkOpenGLDisplayListPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 681 (vtkOpenGLDisplayListPainter.cxx:134)
28 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
29 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
30 libvtkRendering.pv3.3.dylib 0x248c3374 vtkPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 72 (vtkPainter.cxx:217)
31 libvtkRendering.pv3.3.dylib 0x2492ae82 vtkOpenGLClipPlanesPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 900 (vtkOpenGLClipPlanesPainter.cxx:108)
32 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
33 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
34 libvtkRendering.pv3.3.dylib 0x248c3374 vtkPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 72 (vtkPainter.cxx:217)
35 libvtkRendering.pv3.3.dylib 0x24951c3a vtkOpenGLScalarsToColorsPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 732 (vtkOpenGLScalarsToColorsPainter.cxx:171)
36 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
37 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
38 libvtkRendering.pv3.3.dylib 0x248c3374 vtkPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long) + 72 (vtkPainter.cxx:217)
39 libvtkRendering.pv3.3.dylib 0x248c3301 vtkPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 239 (vtkPainter.cxx:206)
40 libvtkRendering.pv3.3.dylib 0x248cece3 vtkPolyDataPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 425 (vtkPolyDataPainter.cxx:63)
41 libvtkRendering.pv3.3.dylib 0x24874382 vtkDefaultPainter::Render(vtkRenderer*, vtkActor*, unsigned long) + 100 (vtkDefaultPainter.cxx:181)
42 libvtkRendering.pv3.3.dylib 0x248c4b29 vtkPainterPolyDataMapper::RenderPiece(vtkRenderer*, vtkActor*) + 1181 (vtkPainterPolyDataMapper.cxx:274)
43 libvtkRendering.pv3.3.dylib 0x248ce1e5 vtkPolyDataMapper::Render(vtkRenderer*, vtkActor*) + 599 (vtkPolyDataMapper.cxx:69)
https://gitlab.kitware.com/paraview/paraview/-/issues/6182Selection inspector breaks easily2019-03-05T10:46:28-05:00Kitware RobotSelection inspector breaks easily**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6182). Further discussion may take place here.**
---
This happens on the trunk, XP.
Open can.exo.
Display/ Representation/ Sur...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6182). Further discussion may take place here.**
---
This happens on the trunk, XP.
Open can.exo.
Display/ Representation/ Surface with edges.
Select Points On icon.
Rubber band select a point.
View/ Selection Inspector.
At the bottom, Display Style, Point Label, select Visible.
Select Points On icon.
Rubber band select an area on the can, but NOT containing a point.
an output dialog comes up that cannot be closed. It says "vtkLabeledDataMapper () Could not find label array (vtkOriginalPointIds) in input".
This window should either grumble once or not at all.
I did find a workaround - you just ignore the window, and select again. But it is confusing.