ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:45:34-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/6791Detection of optional arrays2019-03-05T10:45:34-05:00Kitware RobotDetection of optional arrays**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6791). Further discussion may take place here.**
---
In my example, the first input array is required and the second one is opti...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6791). Further discussion may take place here.**
---
In my example, the first input array is required and the second one is optional,
which I set using the optional="0" and optional="1" tag for "InputArrayDomain"
(I used the XML file for vtkRibbonFilter as a template).
Now in vtkRibbonFilter.cxx there is the following code:
inNormals = this->GetInputArrayToProcess(1,inputVector);
if ( !inNormals || this->UseDefaultNormal )
This suggests that inNormals is set to NULL when there is no such array,
but in my tests this is not the case, instead it points to the first array in
these cases.
https://gitlab.kitware.com/paraview/paraview/-/issues/6787Comparative views timestep value range different than [0,1] creates wrong int...2019-03-05T10:45:34-05:00Kitware RobotComparative views timestep value range different than [0,1] creates wrong intermediate time values**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6787). Further discussion may take place here.**
---
When using data collection with a range of timestep values that is differen...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6787). Further discussion may take place here.**
---
When using data collection with a range of timestep values that is different than [0, 1], the multiple views are not generated at the correct intermediate timesteps.
example: timerange [0, 0.1] gives 4 frames at time 0, 0.1, 0.1, 0.1
timerange [10, 60] gives 4 frames at time 10, 10, 10, 10https://gitlab.kitware.com/paraview/paraview/-/issues/6786Compartative views last frame is not set at the last timestep value2019-03-05T10:45:34-05:00Kitware RobotCompartative views last frame is not set at the last timestep value**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6786). Further discussion may take place here.**
---
Because of an incorrect computation of the time increment to use in generat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6786). Further discussion may take place here.**
---
Because of an incorrect computation of the time increment to use in generating the multi-views in comparative viewing, the last frame does not coincide with the last timestep value.
A suggested change is to edit on line 565 of ./Servers/ServerManager/vtkSMComparativeViewProxy.cxx
changing the computation of the increment from
double increment = (this->TimeRange[1] - this->TimeRange[0])/
(this->Dimensions[0]*this->Dimensions[1]);
to
double increment = (this->TimeRange[1] - this->TimeRange[0])/
(this->Dimensions[0]*this->Dimensions[1] - 1.0);
https://gitlab.kitware.com/paraview/paraview/-/issues/6785Comparative views cameras are not linked if parallel projection is ON2019-03-05T10:45:34-05:00Kitware RobotComparative views cameras are not linked if parallel projection is ON**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6785). Further discussion may take place here.**
---
when using comparative views, the cameras are not in synch.
tried with P...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6785). Further discussion may take place here.**
---
when using comparative views, the cameras are not in synch.
tried with ParaView3 cvs version of April 10, 2008https://gitlab.kitware.com/paraview/paraview/-/issues/6783Cannot convert frustum selection to id selection2019-03-05T10:45:34-05:00Kitware RobotCannot convert frustum selection to id selection**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6783). Further discussion may take place here.**
---
Create a Wavelet source and perform a select cells through operation. In t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6783). Further discussion may take place here.**
---
Create a Wavelet source and perform a select cells through operation. In the selection inspector, change the selection type from Frustum to either IDs or Global IDs. The selection disappears. The selection should be converted to IDs (which was the behavior in 3.2.1).https://gitlab.kitware.com/paraview/paraview/-/issues/6782Show frustum option not working for selection2019-03-05T10:45:34-05:00Kitware RobotShow frustum option not working for selection**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6782). Further discussion may take place here.**
---
Create a Wavelet source and then select some region with select cells throu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6782). Further discussion may take place here.**
---
Create a Wavelet source and then select some region with select cells through. Now go to the selection inspector and turn on "Show Frustum". I see no frustum regardless of viewing angle.https://gitlab.kitware.com/paraview/paraview/-/issues/6781Extract Selections filter missing2019-03-05T10:45:35-05:00Kitware RobotExtract Selections filter missing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6781). Further discussion may take place here.**
---
What happened to the extract selections filter? It's missing from the CVS ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6781). Further discussion may take place here.**
---
What happened to the extract selections filter? It's missing from the CVS trunk.https://gitlab.kitware.com/paraview/paraview/-/issues/6780Cannot extract blocks from exodus file2019-03-05T10:45:35-05:00Kitware RobotCannot extract blocks from exodus file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6780). Further discussion may take place here.**
---
Load in any exodus file (disk_out_ref or can). Both the Extract Level and ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6780). Further discussion may take place here.**
---
Load in any exodus file (disk_out_ref or can). Both the Extract Level and Extract Datasets filters are disabled.https://gitlab.kitware.com/paraview/paraview/-/issues/6779Cannot save Exodus as anything2019-03-05T10:45:35-05:00Kitware RobotCannot save Exodus as anything**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6779). Further discussion may take place here.**
---
Open an exodus file (like disk_out_ref or can). Then try to save the data....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6779). Further discussion may take place here.**
---
Open an exodus file (like disk_out_ref or can). Then try to save the data. ParaView gives no choice for the file type and raises an error if you try to select a file to save to.https://gitlab.kitware.com/paraview/paraview/-/issues/6774default colourmap is saved, default legend text colour is not2019-03-05T10:45:35-05:00Kitware Robotdefault colourmap is saved, default legend text colour is not**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6774). Further discussion may take place here.**
---
Tried on the Paraview 3.3 cvs of 07/04/08.
Change legend text colour. Pr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6774). Further discussion may take place here.**
---
Tried on the Paraview 3.3 cvs of 07/04/08.
Change legend text colour. Press 'Make Default'. Exit&restart. Legend colour not restored.
(the colour map is correctly restored)https://gitlab.kitware.com/paraview/paraview/-/issues/6773Use Broadcast to propagate commands from root sever node to other server nodes2019-03-05T10:45:35-05:00Kitware RobotUse Broadcast to propagate commands from root sever node to other server nodes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6773). Further discussion may take place here.**
---
As we all know, the PV client connects to node 0 of servers and sends comma...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6773). Further discussion may take place here.**
---
As we all know, the PV client connects to node 0 of servers and sends commands to that node. That node propagates commands to the other server nodes (as appropriate).
This is implemented using the ProcessRMIs method in vtkMultiProcessController. This means that each node waits in a MPI_Recv from any command. Node 0 then iteratively sends a message to each of the other nodes.
This is not a very efficient way to broadcast messages. Instead, everyone should use the Broadcast method to propagate the requests. (Broadcast is now part of vtkMultiProcessController.)https://gitlab.kitware.com/paraview/paraview/-/issues/6770ParaView does not read exodus data with many blocks well2019-03-05T10:45:35-05:00Kitware RobotParaView does not read exodus data with many blocks well**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6770). Further discussion may take place here.**
---
When ParaView tries to read in a dataset with a large number of blocks, it ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6770). Further discussion may take place here.**
---
When ParaView tries to read in a dataset with a large number of blocks, it acts very, very badly. I have a dataset of 1500 blocks, the whole dataset which is only 17 MBytes in size. paraviewInternals sucks up about 1.2 GBytes of memory reading in this data.
I have a user that would really like this fixed. He does not have any other workarounds, since EnSight also fails.
Setting to high, since there are no workarounds.
File is many.e.https://gitlab.kitware.com/paraview/paraview/-/issues/6769Allow view options to be registered via plugin2019-03-05T10:45:35-05:00Kitware RobotAllow view options to be registered via plugin**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6769). Further discussion may take place here.**
---
pqActiveViewOptionsManager provides API to register "handlers" for displayi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6769). Further discussion may take place here.**
---
pqActiveViewOptionsManager provides API to register "handlers" for displaying options for a view. This mechanism seems perfect for custom view plugins to register their own options, however the manager is only accessible through pqMainWindowCore, which - as far as I can tell - can't be accessed by a plugin.
https://gitlab.kitware.com/paraview/paraview/-/issues/6768Select any array as texture coordinates2019-03-05T10:45:35-05:00Kitware RobotSelect any array as texture coordinates**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6768). Further discussion may take place here.**
---
Right now, you can only use an array for texture coordinates if it is assig...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6768). Further discussion may take place here.**
---
Right now, you can only use an array for texture coordinates if it is assigned as the active texture coordinates in the data structure. Furthermore, there is no direct way to set the active texture coordinates.
A better approach (I think) is to be able to select any array to use as the texture coordinates.https://gitlab.kitware.com/paraview/paraview/-/issues/6767Plot over time should work for composite data sets2019-03-05T10:45:35-05:00Kitware RobotPlot over time should work for composite data sets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6767). Further discussion may take place here.**
---
The plot over time filter should work with composite type data sets. This ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6767). Further discussion may take place here.**
---
The plot over time filter should work with composite type data sets. This includes using either global ids or local VTK structure ids. It should also support pipeline iteration and fast path for plotting.https://gitlab.kitware.com/paraview/paraview/-/issues/6766Clipping range does not take 3D widgets into account.2019-03-05T10:45:41-05:00Kitware RobotClipping range does not take 3D widgets into account.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6766). Further discussion may take place here.**
---
The clipping range calculation does not take the 3D widgets into account. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6766). Further discussion may take place here.**
---
The clipping range calculation does not take the 3D widgets into account. If the 3D widget extends beyond the range of the visible data, it is sometimes clipped by near and/or far planes. To replicate, do the following:
1. Create a sphere source.
2. Apply the cut filter with the default values.
3. Rotate everything around (with the 3D widget still visible) so that you are looking directly onto the clip plane.
At this point, the front and back part of the widget are clipped off. The attached image shows the results of the clipping.https://gitlab.kitware.com/paraview/paraview/-/issues/6734Installation of Paraview2019-03-05T10:45:41-05:00Kitware RobotInstallation of Paraview**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6734). Further discussion may take place here.**
---
Install fails when it reaches this point because "C:\Q" is not being treate...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6734). Further discussion may take place here.**
---
Install fails when it reaches this point because "C:\Q" is not being treated as C:/Q. See the output below:
1>-- Installing: C:/Program Files/ParaView/bin/QTASSISTANTCLIENT4.dll
1>CMake Error: Invalid escape sequence \Q
1>Syntax error in cmake code at
1>C:/Users/amaclean/Code/Kitware/build/ParaView/Applications/Client/cmake_install.cmake:82:
1>syntax error, unexpected cal_ERROR, expecting $end (4), when parsing string "C:\Qt\qt-win-opensource-src-4.3.4\bin/assistant.exe"
1>-- Installing: C:/Program Files/ParaView/bin/assistant.exe
1>-- Installing: C:/Program Files/ParaView/bin/pvTestDriver.exe
1>Project : error PRJ0019: A tool returned an error code from "Performing Post-Build Event..."https://gitlab.kitware.com/paraview/paraview/-/issues/6732After Creating a new folder in a file dialog box, the file list goes back to ...2019-03-05T10:45:41-05:00Kitware RobotAfter Creating a new folder in a file dialog box, the file list goes back to where ever paraview was launched from.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6732). Further discussion may take place here.**
---
After applying the patch from <http://public.kitware.com/Bug/view.php?id=67...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6732). Further discussion may take place here.**
---
After applying the patch from <http://public.kitware.com/Bug/view.php?id=6731>, launch ParaView.
Go to "File->Open"
Navigate to another directory
Create a new folder
Give the folder a name (Optional)
press the return/enter key on the keyboard to accept the folder name
The file list changes _back_ to the default file list of where paraview was launched from although the new folder was created in the original location.
I tried to track this down but couldn't find what was causing the problem.https://gitlab.kitware.com/paraview/paraview/-/issues/6731Using the "Create New Folder" button in the File Dialog does nothing2019-03-05T10:45:41-05:00Kitware RobotUsing the "Create New Folder" button in the File Dialog does nothing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6731). Further discussion may take place here.**
---
Launch ParaView 3
Go to "File->Open"
Click the icon to "Create a new Fold...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6731). Further discussion may take place here.**
---
Launch ParaView 3
Go to "File->Open"
Click the icon to "Create a new Folder"
Nothing happenshttps://gitlab.kitware.com/paraview/paraview/-/issues/6728Tooltips for object inspector2019-03-05T10:45:41-05:00Kitware RobotTooltips for object inspector**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6728). Further discussion may take place here.**
---
Qt tooltips for e.g. filter plugin widgets did nicely work in ParaView2 but...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6728). Further discussion may take place here.**
---
Qt tooltips for e.g. filter plugin widgets did nicely work in ParaView2 but don't work anymore in ParaView3.