ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-01-03T03:44:50-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22434OBJ Loader does not open time series correctly2024-01-03T03:44:50-05:00Micha PfeifferOBJ Loader does not open time series correctlyLoading a time series of .obj files does not work for me.
The .obj files are correctly collapsed as a group in the file dialogue, but after loading only the first file seems to really be opened.
The files are named correctly (surface_f1...Loading a time series of .obj files does not work for me.
The .obj files are correctly collapsed as a group in the file dialogue, but after loading only the first file seems to really be opened.
The files are named correctly (surface_f1.obj, surface_f2.obj ...) and the same process works fine with .vtu files and .stl files.
Similar bug report (where the only workaround was to convert to .vtk):
https://discourse.paraview.org/t/how-to-open-a-group-of-obj-files/8672/8
Paraview version: 5.12.0-RC1
Ubuntu version: 20.04https://gitlab.kitware.com/paraview/paraview/-/issues/22433ExtractBlock is not able to extract block with identical names2024-01-03T03:49:18-05:00farensheepExtractBlock is not able to extract block with identical namesExtractBlock let user select block to extract but if the block of the same name, all blocks will be extracted.
Steps to reproduce:
- Open [samename.vtm](/uploads/01846bd1dbca718df398eb463e1053ed/samename.tgz), Apply
- Filters -> Extr...ExtractBlock let user select block to extract but if the block of the same name, all blocks will be extracted.
Steps to reproduce:
- Open [samename.vtm](/uploads/01846bd1dbca718df398eb463e1053ed/samename.tgz), Apply
- Filters -> ExtractBlock
- Select a single block, apply
- All blocks are extracted
================= Original issue below:
Hi,
I am trying to use paraview to process the results of the Fire Dynamics Simulator (FDS). Recently, a new reader has been implemented in paraview and I am trying to use it.
I set a simple case of a convective heat transfer with slides defined by FDS. When I try to process the results the reader can see the different temperature slices but I can’t select only one, they are all selected, even though I click on only one “STRUCTURE_TEMPERATURE” (see image).
It seems that the name of the blocks from the smv are all the same.
See the discussion : https://discourse.paraview.org/t/fdsreader-vtkpartitioneddatasetcollection/13599
Could it be possible to change the name, maybe including the coordinate of the slide ?https://gitlab.kitware.com/paraview/paraview/-/issues/22427CI: Flaky tests on fedora runner2024-01-04T07:41:47-05:00Nicolas VuailleCI: Flaky tests on fedora runnerOn `[fedora35_shared_mpi_python_qt_vtkmoverride]` and `[fedora35_shared_mpi_python_qt]`, the following tests fails with different output, but since the exact same build on master. (12/08/2023: https://open.cdash.org/viewTest.php?buildid=...On `[fedora35_shared_mpi_python_qt_vtkmoverride]` and `[fedora35_shared_mpi_python_qt]`, the following tests fails with different output, but since the exact same build on master. (12/08/2023: https://open.cdash.org/viewTest.php?buildid=9212439)
* [ ] pqCoreKeySequences
* `FAIL! : KeySequencesTester::basic() 'QTest::qWaitForWindowActive(window)' returned FALSE. ()`
* [ ] pqWidgetspqTextEditTest
* Timeout
* [ ] pv.ComputeArrayMagnitudeSetting
* `critical: Components property value is: X. Expecting: Magnitude.`
* [ ] (pv|pvcs|pvcrs)TestPythonView
* baseline: black screen
* [ ] pv.TooltipCopy
* `critical: property value is: . Expecting: MeshQuality1`
* [ ] (pvcs|pvcrs)ShaderReplacements
* baseline: scalars instead of solid color
Needs investigations.
CI exclusion: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6630https://gitlab.kitware.com/paraview/paraview/-/issues/22425Add ability for linear cell extrusion to extrude on point normals2023-12-20T20:59:44-05:00W. Alan ScottAdd ability for linear cell extrusion to extrude on point normalsThe Linear Cell Extrusion filter will extrude a 2d surface based on some variable. Please add the following two features.
* Ability to extrude based on object units, not a variable. See example below - we want to not depend on a variabl...The Linear Cell Extrusion filter will extrude a 2d surface based on some variable. Please add the following two features.
* Ability to extrude based on object units, not a variable. See example below - we want to not depend on a variable such as object_id.
* Ability to extrude based on point normals, not cell normals. Again see example below.
Example.
* 5.12.0-RC1, MacOS, builtin server.
* Open disk_out_ref.exo. Apply.
* Extract Surface. Apply.
* Linear Cell Extrusion. As we want a variable with a 1 in it, select object_id. Scale factor 1. Apply.
What we want is the image below, with the ridge tops touching. I believe this can be done again by finding the cell normal (which is obviously being used for this filter), deriving the normals at the points, and extruding the serface along these point normals.
![Screenshot_2023-12-20_at_6.56.51_PM](/uploads/0dcaed8be2d973b46315587537d4f5c9/Screenshot_2023-12-20_at_6.56.51_PM.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22423Link to python error when compiling ParaView with -DPARAVIEW_BUILD_TESTING=ON...2024-01-02T04:43:04-05:00guillaume PeillexLink to python error when compiling ParaView with -DPARAVIEW_BUILD_TESTING=ON -DPARAVIEW_BUILD_WITH_KITS=ONHi all,
I’m facing a link problem when i try to build `ParaView` when the option `PARAVIEW_BUILD_TESTING` and `PARAVIEW_BUILD_WITH_KITS` to on.
When it is `OFF`, `ParaView` build successfully.
The errors arise when compiling some of the...Hi all,
I’m facing a link problem when i try to build `ParaView` when the option `PARAVIEW_BUILD_TESTING` and `PARAVIEW_BUILD_WITH_KITS` to on.
When it is `OFF`, `ParaView` build successfully.
The errors arise when compiling some of the test modules of the `VTKExtensions` such as `IOCGNS`.
The error message is the following:
```
FAILED: bin/vtkPVVTKExtensionsIOCGNSWriterCxxTests
: && /usr/bin/c++ -O2 -g -DNDEBUG -Wl,-lc -Wl,-lc VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/vtkPVVTKExtensionsIOCGNSWriterCxxTests.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPartitionedDataSetCollection2.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestStructuredGrid.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestUnstructuredGrid.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPartitionedDataSet.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPartitionedDataSetCollection.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPolydata.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestPolyhedral.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestCellAndPointData.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestMultiBlockDataSet.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestMappedUnstructuredGrid.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestTimeWriting.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestRectilinearGrid.cxx.o VTKExtensions/IOCGNS/Testing/Cxx/CMakeFiles/vtkPVVTKExtensionsIOCGNSWriterCxxTests.dir/TestImageData.cxx.o -o bin/vtkPVVTKExtensionsIOCGNSWriterCxxTests -Wl,-rpath,/opt/paraview_build/lib:/usr/lib/x86_64-linux-gnu/openmpi/lib:/usr/lib/x86_64-linux-gnu/hdf5/serial lib/libvtkTestingDataModel-pv5.12.so.5.12 lib/libvtkIOIOSS-pv5.12.so.5.12 lib/libvtkPVCoreKit-pv5.12.so.5.12 /usr/lib/x86_64-linux-gnu/libexpat.so lib/libvtkParallel-pv5.12.so.5.12 lib/libvtkIO-pv5.12.so.5.12 lib/libvtkFilters-pv5.12.so.5.12 lib/libvtkverdict-pv5.12.so.5.12 /usr/lib/x86_64-linux-gnu/libpugixml.so.1.13 lib/libvtkCommon-pv5.12.so.5.12 lib/libvtksys-pv5.12.so.5.12 lib/libvtktoken-pv5.12.so.5.12 lib/libvtkloguru-pv5.12.so.5.12 lib/libvtkkissfft-pv5.12.so.5.12 /usr/lib/x86_64-linux-gnu/libdouble-conversion.so /usr/lib/x86_64-linux-gnu/liblz4.so /usr/lib/x86_64-linux-gnu/liblzma.so /usr/lib/x86_64-linux-gnu/libz.so lib/libvtkcgns-pv5.12.so.5.12 lib/libvtkfmt-pv5.12.so.5.12 /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5_hl.so -ldl -Wl,-rpath-link,/opt/paraview_build/lib:/usr/lib/x86_64-linux-gnu/hdf5/serial && :
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyUnicode_InternFromString'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyDict_DelItemString'
/usr/bin/ld: /opt/paraview_build/lib/libvtkPythonInterpreter-pv5.12.so.1: undefined reference to `_Py_Dealloc'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyByteArray_AsString'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyLong_FromLong'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyExc_KeyError'
/usr/bin/ld: /opt/paraview_build/lib/libvtkPythonInterpreter-pv5.12.so.1: undefined reference to `PyStatus_Exception'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyExc_NotImplementedError'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyByteArray_Type'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyNumber_Absolute'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyDescr_NewClassMethod'
/usr/bin/ld: /opt/paraview_build/lib/libvtkPythonInterpreter-pv5.12.so.1: undefined reference to `PyType_IsSubtype'
/usr/bin/ld: /opt/paraview_build/lib/libvtkWrappingPythonCore3.11-pv5.12.so.1: undefined reference to `PyErr_Fetch'
/usr/bin/ld: /opt/paraview_build/lib/libvtkPythonInterpreter-pv5.12.so.1: undefined reference to `Py_PreInitialize'
...
collect2: error: ld returned 1 exit status
```
I have made a reproducer through the following Dockerfile
[Dockerfile](/uploads/cd4ef7bc6793b20df0da3406460cfe9e/Dockerfile)
When built, run the container and in the `/opt/paraview_build` just run `cmake --build ..`
I found a hack to workaround. It is to add a dependency to `ParaView::RemotingApplication` in the `TEST_DEPENDS` section of the vtk.module files involved.
See https://discourse.paraview.org/t/link-to-python-error-when-compiling-paraview-with-dparaview-build-testing-on/13524https://gitlab.kitware.com/paraview/paraview/-/issues/22422namometer scale objects arent painted correctly2023-12-18T12:13:10-05:00W. Alan Scottnamometer scale objects arent painted correctlyParaView is not painting very, very small objects correctly. This is impacting users that run physics codes that are creating datasets in nanometers, using meters as their units. Here is how to replicate:
* 5.12.0-RC1, Windows, builtin...ParaView is not painting very, very small objects correctly. This is impacting users that run physics codes that are creating datasets in nanometers, using meters as their units. Here is how to replicate:
* 5.12.0-RC1, Windows, builtin server
* Wavelet. Apply. RTData. Surface.
* Transform filter. Scale by 1e-9, 1e-9, 1e-9. Apply.
* Reset.
The object will look black and white. If you use mouse controls to zoom out, all of a sudden Wavelet gets painted correctly.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22421Molecule representation: crash when creating new view with ParaView 5.12-RC12024-03-07T20:23:59-05:00Francois MazenMolecule representation: crash when creating new view with ParaView 5.12-RC1The second output of the PDB Reader has to be a Molecule representation. When I create a new 3D render view and try to show the second output (forcing molecule representation), then ParaView crashes.
To reproduce with ParaView 5.12-RC1:...The second output of the PDB Reader has to be a Molecule representation. When I create a new 3D render view and try to show the second output (forcing molecule representation), then ParaView crashes.
To reproduce with ParaView 5.12-RC1:
- Open the file 3GQP.pdb available here: https://data.kitware.com/#item/5afd92b68d777f15ebe1aad4
- Click apply, the "Output-1" is displayed with Molecule representation in the 3D render view
- Create a new view (new layout or split current view)
- Click "Render View" for the view type
- Click on the eye of the "Output-1" item in the pipeline browser
- Crash in `pqColorMapEditor::renderViews` because the `representation` variable is null
ParaView 5.11.0 does not crash and the new render view switch to Molecule representation as expected.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22418Cannot color VTU cells as glyphs by scalar2023-12-11T10:42:58-05:00Randy HeilandCannot color VTU cells as glyphs by scalarUsing PV 5.11.2, I’m unable to color cells as glyphs with a scalar array. In the attached .vtu file, I want to display the cells as 3D glyphs, colored by the “cell_id” array. It seems to only do what I want if I add a "CellDataToPointDat...Using PV 5.11.2, I’m unable to color cells as glyphs with a scalar array. In the attached .vtu file, I want to display the cells as 3D glyphs, colored by the “cell_id” array. It seems to only do what I want if I add a "CellDataToPointData" filter
[vtu_2cells.vtu](/uploads/c336c67f40d973c8d6eeaa0e389cb8a0/vtu_2cells.vtu)
[Screenshot_2023-12-11_at_10.20.18_AM](/uploads/e3d2bced384587f5f969a165af98947e/Screenshot_2023-12-11_at_10.20.18_AM.png)[Screenshot_2023-12-11_at_10.24.31_AM](/uploads/f168c3a2642ff6306ac8e1195008b7da/Screenshot_2023-12-11_at_10.24.31_AM.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22417Time Manager - end time controls don't stay located correctly.2023-12-07T21:12:38-05:00W. Alan ScottTime Manager - end time controls don't stay located correctly.The time manager end time controls don't stay located properly. Here is how to replicate this issue.
* 5.12.0-RC1, Linux, builtin server. To see this, you may need to delete your configuration files, or run paraview -dr.
* Make ParaVi...The time manager end time controls don't stay located properly. Here is how to replicate this issue.
* 5.12.0-RC1, Linux, builtin server. To see this, you may need to delete your configuration files, or run paraview -dr.
* Make ParaView non full screen. We want a few inches of space between ParaView and the edges of the desktop.
* File/ Open/ Examples/ can.exo. Apply.
* View/ Time Manager.
* Grab the lower right corner of ParaView, and make ParaView bigger and smaller. Look at the right side of the Time Manager/ Time Source. It looks fine.
* The maximum time is editable. Double click it.
* Grab the lower right corner of ParaView. Make ParaView wider. The maximum time entry isn't being adjusted in the X axis.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22416Time Manager - Animation - Follow Path is not editable2024-01-15T08:42:15-05:00W. Alan ScottTime Manager - Animation - Follow Path is not editableThe Time Manager, Animation, Follow Path is not editable. Here is how to replicate:
* 5.12.0-RC1, Linux, builtin server
* File/ open/ examples/ can.exo. Apply.
* View/ Time Manager.
* Animations/ Camera/ Follow Path. Blue +.
* Click the...The Time Manager, Animation, Follow Path is not editable. Here is how to replicate:
* 5.12.0-RC1, Linux, builtin server
* File/ open/ examples/ can.exo. Apply.
* View/ Time Manager.
* Animations/ Camera/ Follow Path. Blue +.
* Click the track. Click the "path". (Side issue, this is not obvious that you need to do this. A comment somewhere would be nice.). Camera Position.
Issue 1) I have no mouse control whatsoever of the control points. This is a feature loss. Please add it back. Next, please add the normal - enhanced mouse controls - X, Y, Z.
Issue 2) The control points are set for the can in it's intial position. It should be for the camera when the Follow Path is created. You can see this by using the steps above, but:
* After reading in the can, move the camera.
* After creating the path, click "play".5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22415Time Manager Animations needs to be clarified2023-12-07T20:48:07-05:00W. Alan ScottTime Manager Animations needs to be clarifiedThe Time Manager Animations needs clarification. Do the following:
* 5.12.0-RC1, Linux, builtin server.
* File/ Open/ Examples/ can.exo. Apply
* View/ Time Manager.
Now, we want to create an animation track.
* Animations/ Camera/ Fo...The Time Manager Animations needs clarification. Do the following:
* 5.12.0-RC1, Linux, builtin server.
* File/ Open/ Examples/ can.exo. Apply
* View/ Time Manager.
Now, we want to create an animation track.
* Animations/ Camera/ Follow Path. Click the magic blue +.
I now don't know what type of Camera control I have made. My first suggestion would be to add the words right on the track - "Follow Path Animation. Click here to customize". If that doesn't work, add another line below Camera - Renderview1.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22414paraview without python using external VTK with python results in errors2023-12-12T13:07:44-05:00Dan Lipsaparaview without python using external VTK with python results in errors```
Using 'QtHelp' without 'QtWebEngine' will ignore embedded javascript and *.js files for documentation
Enabled modules: VTK(172), ParaView(42 + 5)
Configuring done (4.0s)
CMake Error at /home/local/KHQ/dan.lipsa/projects/vtk/external_...```
Using 'QtHelp' without 'QtWebEngine' will ignore embedded javascript and *.js files for documentation
Enabled modules: VTK(172), ParaView(42 + 5)
Configuring done (4.0s)
CMake Error at /home/local/KHQ/dan.lipsa/projects/vtk/external_vtk/build/install/lib/cmake/vtk-9.3/VTK-targets.cmake:1308 (set_target_properties):
The link interface of target "VTK::Python" contains:
Python3::Module
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
/home/local/KHQ/dan.lipsa/projects/vtk/external_vtk/build/install/lib/cmake/vtk-9.3/vtk-config.cmake:149 (include)
CMakeLists.txt:65 (find_package)
CMake Error at /home/local/KHQ/dan.lipsa/projects/vtk/external_vtk/build/install/lib/cmake/vtk-9.3/VTK-targets.cmake:1342 (set_target_properties):
The link interface of target "VTK::PythonUsed" contains:
Python3::Python
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
/home/local/KHQ/dan.lipsa/projects/vtk/external_vtk/build/install/lib/cmake/vtk-9.3/vtk-config.cmake:149 (include)
CMakeLists.txt:65 (find_package)
Generating done (1.7s)
```https://gitlab.kitware.com/paraview/paraview/-/issues/22413GmshIO plugin assumes signed char which breaks on ARM2023-12-14T06:00:34-05:00Drew ParsonsGmshIO plugin assumes signed char which breaks on ARMAt https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/GmshIO/IO/gmshCommon.h#L9
the GmshIO plugin sets
```
enum class GmshPrimitive : char
{
Unsupported = -1,
...
}
```
So a value of `-1` is being set to type `char`. ...At https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/GmshIO/IO/gmshCommon.h#L9
the GmshIO plugin sets
```
enum class GmshPrimitive : char
{
Unsupported = -1,
...
}
```
So a value of `-1` is being set to type `char`. This assumes that char is signed, which apparently is not always the case.
For instance on ARM (arm64) architecture, paraview 5.11.2 fails to build with GmshIO enabled, giving an error
```
[ 26%] Building CXX object VTK/Filters/Core/CMakeFiles/FiltersCore.dir/vtkMassProperties.cxx.o
/usr/bin/c++ -o vtkMassProperties.cxx.o -c vtkMassProperties.cxx
In file included from Plugins/GmshIO/IO/vtkGmshReader.cxx:16:
Plugins/GmshIO/IO/gmshCommon.h:9:18: error: enumerator value ‘-1’ is outside the range of underlying type ‘char’
9 | Unsupported = -1,
| ^
```
A full build log can be found at https://buildd.debian.org/status/fetch.php?pkg=paraview&arch=arm64&ver=5.11.2%2Bdfsg-3&stamp=1701895041&raw=0
At https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/GmshIO/IO/vtkGmshWriter.cxx#L55 `GmshPrimitive` is used in association with VTKCellType as `unsigned char`,
```
static const std::unordered_map<unsigned char, GmshPrimitive> TRANSLATE_CELLS_TYPE;
```
But vtkCellType.h does define `VTK_EMPTY_CELL = 0`, so it probably would not work well to set `GmshPrimitive::Unsupported` to 0 instead of -1.
The value (and sign) is used at https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/GmshIO/IO/vtkGmshWriter.cxx#L140 but handled alongside explicit `unsigned char`,
```
for (unsigned char currentType = 1; currentType < GmshWriterInternal::MAX_TAG; ++currentType)
{
std::vector<std::size_t>& indexes = idxPerType[currentType];
if (indexes.empty())
{
continue;
}
char gmshType =
static_cast<char>(GmshWriterInternal::TRANSLATE_CELLS_TYPE.find(currentType)->second);
// If this type is not natively supported, it will be transleted in either lines or triangles
if (gmshType < 0)
{
continue;
}
...
```
So `unsigned char` is explicitly used here for `currentType`, while an unsupported type is handled via a negative value in `gmshType`.
Should the GmshPrimitive enum in gmshCommon.h, and `gmshType` in vtkGmshWriter.cxx, and elsewhere, be declared explicitly as type `signed char` instead of `char`? I gather that just using `int` itself would not be appropriate.https://gitlab.kitware.com/paraview/paraview/-/issues/22410vtkblockcolors disappears after using volume rendering2023-12-05T12:03:58-05:00W. Alan Scottvtkblockcolors disappears after using volume renderingThe option to paint by vtkblockcolors disappears after using volume rendering. Here is how to replicate.
* 5.12.0-RC1, builtin, Windows
* Read can.exo. Apply.
* Paint by id
* Volume.
* Surface.
vtkBlockColors is no longer available to...The option to paint by vtkblockcolors disappears after using volume rendering. Here is how to replicate.
* 5.12.0-RC1, builtin, Windows
* Read can.exo. Apply.
* Paint by id
* Volume.
* Surface.
vtkBlockColors is no longer available to paint with. This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/22409ParaView 5.12.0-RC1: when saving stereo pair images, left eye is unchanged fr...2023-12-05T06:43:41-05:00Cory Quammencory.quammen@kitware.comParaView 5.12.0-RC1: when saving stereo pair images, left eye is unchanged from non-stereo imageVersion: ParaView 5.12.0-RC1
Configuration: builtin server
Steps to reproduce bug:
* Start ParaView
* Add **Box** source.
* From toolbar click Apply isometric view
* File -> Save Screenshot. Give the file a name, e.g., "stereo.png"
* In...Version: ParaView 5.12.0-RC1
Configuration: builtin server
Steps to reproduce bug:
* Start ParaView
* Add **Box** source.
* From toolbar click Apply isometric view
* File -> Save Screenshot. Give the file a name, e.g., "stereo.png"
* In the Save Screenshot Options dialog, set **Stereo Mode** to "Both Eyes". Click OK.
* File -> Save Screenshot. Give the file a name, e.g., "nostereo.png"
* In the Save Screenshot Options dialog, make sure **Stereo Mode** is set to "No change". Click OK.
* In an image viewer, compare stereo_left.png to nostereo.png. They are the same. I expect them to be different.
Note: leaving the left eye unmodified and applying an eye separation to only the right eye may be the actual design.https://gitlab.kitware.com/paraview/paraview/-/issues/22408pvserver: make it so render windows in Windows do not need to always be on top2023-12-04T15:56:43-05:00Cory Quammencory.quammen@kitware.compvserver: make it so render windows in Windows do not need to always be on top5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22407Feature: add ability to specify which representations are included in camera ...2023-12-04T15:53:39-05:00Cory Quammencory.quammen@kitware.comFeature: add ability to specify which representations are included in camera Reset actionAdd a way, only in Python is okay, to reset the view to ensure a select list of representations is centered in the view.Add a way, only in Python is okay, to reset the view to ensure a select list of representations is centered in the view.https://gitlab.kitware.com/paraview/paraview/-/issues/22406CAVEInteraction: let roles be listed in order declared in Python interactor s...2023-12-04T15:43:02-05:00Cory Quammencory.quammen@kitware.comCAVEInteraction: let roles be listed in order declared in Python interactor script and not alphabetized5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22405CAVEInteraction: in Python interactor, object/attribute pulldowns should be b...2023-12-04T14:56:19-05:00Cory Quammencory.quammen@kitware.comCAVEInteraction: in Python interactor, object/attribute pulldowns should be blankAccess to all proxies and their properties is already available within the script.Access to all proxies and their properties is already available within the script.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22402ResetSession() breaks GetLayout()2024-03-27T08:01:49-04:00baloeResetSession() breaks GetLayout()running the following through `pvbatch`
```python
from paraview.simple import *
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
ResetSession()
renderView1 = GetActiveViewOrCreate('RenderView')
la...running the following through `pvbatch`
```python
from paraview.simple import *
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
ResetSession()
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
```
prints
```
<paraview.servermanager.ViewLayout object at 0x7f841067ffd0>
None
```
I am expecting another Viewlayout reference instead of that None in the second line.
This renders `ResetSession()` useless for me right now, and I have needed `ResetSession()` in the past to mitigate memory leakage issues when iterating over time steps. So I think it is a feature worth having just in case.