ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-08-23T15:16:54-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/13422Quad Slice View2018-08-23T15:16:54-04:00Kitware RobotQuad Slice View**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13422). Further discussion may take place here.**
---
- Create new custom composite representation for that view
- Add support ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13422). Further discussion may take place here.**
---
- Create new custom composite representation for that view
- Add support for slice representation
- Add plane origin widgethttps://gitlab.kitware.com/paraview/paraview/-/issues/13423expose vtkStreaklineFilter::SetDisableResetCache() in paraview2018-08-23T15:16:54-04:00Kitware Robotexpose vtkStreaklineFilter::SetDisableResetCache() in paraview**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13423). Further discussion may take place here.**
---
Need to expose vtkStreaklineFilter::SetDisableResetCache() in paraview for...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13423). Further discussion may take place here.**
---
Need to expose vtkStreaklineFilter::SetDisableResetCache() in paraview for coprocessing.https://gitlab.kitware.com/paraview/paraview/-/issues/13425Bad camera manipulation when only showing text source2018-08-23T15:16:54-04:00Kitware RobotBad camera manipulation when only showing text source**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13425). Further discussion may take place here.**
---
If you create a text source in a 3D view without anything else visible, yo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13425). Further discussion may take place here.**
---
If you create a text source in a 3D view without anything else visible, you get a confusing warning pointless warning message. To replicate, do the following:
1. Start a fresh instance of ParaView.
2. Create a Text source.
3. Apply.
At this point you will get a warning message like this:
Warning: In /Users/kmorel/src/ParaView/VTK/Rendering/Core/vtkRenderer.cxx, line 1035
vtkOpenGLRenderer (0x11b6f2a10): Resetting view-up since view plane normal is parallel
The camera also gets set to some strange interaction mode.https://gitlab.kitware.com/paraview/paraview/-/issues/13426TextEdit boxes in Animation View get too small2018-08-23T15:16:54-04:00Kitware RobotTextEdit boxes in Animation View get too small**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13426). Further discussion may take place here.**
---
If the Animation View window is not large enough, the TextEdit widgets for...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13426). Further discussion may take place here.**
---
If the Animation View window is not large enough, the TextEdit widgets for Time, Start Time, and End Time become so thin as to be unusable. Attached is a screen capture of these widgets from my Mac build when the Animation View is brought up with the default window layout.
So, the first part of the fix would be to set the minimum width of these boxes to be at least one character wide.
The second part of the fix would be to make a bit more room for these widgets. The No. Frames SpinBox is at least twice as wide as I imagine most applications will ever need. Also, the lock buttons could be changed to square tool buttons like that used for the "advanced" button in the Properties panel. That would serve the double purpose of making the widgets more narrow and to better indicate their toggle behavior.https://gitlab.kitware.com/paraview/paraview/-/issues/13427Plugins in PV_PLUGIN_PATH not loading correctly.2018-08-23T15:16:54-04:00Kitware RobotPlugins in PV_PLUGIN_PATH not loading correctly.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13427). Further discussion may take place here.**
---
Refer to thread:
http://markmail.org/thread/4i3x5kbqqzmajgzy
**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13427). Further discussion may take place here.**
---
Refer to thread:
http://markmail.org/thread/4i3x5kbqqzmajgzy
https://gitlab.kitware.com/paraview/paraview/-/issues/13428Teach Memory inspector panel about limits2018-08-23T15:16:54-04:00Kitware RobotTeach Memory inspector panel about limits**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13428). Further discussion may take place here.**
---
Update memory inspector panel so that process and jobs memory limits are r...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13428). Further discussion may take place here.**
---
Update memory inspector panel so that process and jobs memory limits are reported correctly.https://gitlab.kitware.com/paraview/paraview/-/issues/13429Slice filter always traingulates2018-08-23T15:16:54-04:00Kitware RobotSlice filter always traingulates**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13429). Further discussion may take place here.**
---
Slice filter always traingulates irrespective of the input cell structure.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13429). Further discussion may take place here.**
---
Slice filter always traingulates irrespective of the input cell structure.https://gitlab.kitware.com/paraview/paraview/-/issues/13430Exodus Reader uses cell counts when naming blocks2018-08-23T15:16:54-04:00Kitware RobotExodus Reader uses cell counts when naming blocks**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13430). Further discussion may take place here.**
---
Exodus Reader uses cell counts when naming blocks. This is a problem since...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13430). Further discussion may take place here.**
---
Exodus Reader uses cell counts when naming blocks. This is a problem since if the number of cells in blocks change over time, the block names become invalid and raise errors.
WHen fixing this, case must be take to handle backwards compatibility for XML state files and Python state files.https://gitlab.kitware.com/paraview/paraview/-/issues/13431Exodus Panel makes the apply button "green"2018-08-23T15:16:54-04:00Kitware RobotExodus Panel makes the apply button "green"**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13431). Further discussion may take place here.**
---
Steps:
1> Open can.ex2, Apply
2> Click on "builtin" in the pipeline brow...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13431). Further discussion may take place here.**
---
Steps:
1> Open can.ex2, Apply
2> Click on "builtin" in the pipeline browser
3> Click on "can.ex2" in the pipeline browser
==> the apply button goes green!https://gitlab.kitware.com/paraview/paraview/-/issues/13432Checkboxes should not use two columns2018-08-23T15:16:54-04:00Kitware RobotCheckboxes should not use two columns**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13432). Further discussion may take place here.**
---
One of the main reasons why several of the panels get cluttered is that th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13432). Further discussion may take place here.**
---
One of the main reasons why several of the panels get cluttered is that the check-boxes have labels on the left side, while in the past check-boxes used the check-box label which showed up on the right side and we would assign the check box item the entire row.https://gitlab.kitware.com/paraview/paraview/-/issues/13433Find data help crashes behind firewalls2018-08-23T15:16:54-04:00Kitware RobotFind data help crashes behind firewalls**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13433). Further discussion may take place here.**
---
ParaView is dying a really horrible death when you try to get help in the ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13433). Further discussion may take place here.**
---
ParaView is dying a really horrible death when you try to get help in the find data dialog, when you are behind a firewall. I did the following:
* ParaView trunk, Linux, local server.
* Sphere source.
* Edit/ Find Data
* Select the ? at the end of the ID ... is ... line
And got the following:
lanMachine:bin$ ./paraview_4.0.0-alpha
Cannot resolve 'dbus_get_version' in your libdbus-1.
Abort
By the way, once you have done this once, you have to get rid of your .config/ParaView/*.ini file to keep from having a seg fault anytime you try to go to the find data dialog box.
https://gitlab.kitware.com/paraview/paraview/-/issues/13434Find data dialog doesn't work2018-08-23T15:16:54-04:00Kitware RobotFind data dialog doesn't work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13434). Further discussion may take place here.**
---
I may be missing something, but it seems that the find data dialog just se...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13434). Further discussion may take place here.**
---
I may be missing something, but it seems that the find data dialog just selects everything.
* Windows, local server, master (from a week or so ago).
* Open Can.exo. All vars on, apply.
* Edit/ find data. Find: Cell, from can.ex2. GlobalElementId is 100. Run Selection Query.
<<Everything is selected. this is a bug.>>
Note - this also happens when trying to select EQPS >= 1.5
A message is output:
Traceback (most recent call last):
File "<string>", line 3, in <module>
File "D:\alan\paraviewMasterVisual\bld2\ParaView3\bin\site-packages\paraview\extract_selection.py", line 19, in <module>
from paraview.vtk import dataset_adapter
File "D:\alan\paraviewMasterVisual\bld2\ParaView3\bin\site-packages\paraview\vtk\__init__.py", line 1, in <module>
from vtkCommonComputationalGeometryPython import *
ImportError: No module named vtkCommonComputationalGeometryPython
https://gitlab.kitware.com/paraview/paraview/-/issues/13435:Spatial bounds of multiblock datasets2018-08-23T15:16:54-04:00Kitware Robot:Spatial bounds of multiblock datasets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13435). Further discussion may take place here.**
---
multiblock datasets that contain a mixture of 3d data and tables always in...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13435). Further discussion may take place here.**
---
multiblock datasets that contain a mixture of 3d data and tables always include (0,0,0) in the spatial bounds which seems to be returned from the table.
https://gitlab.kitware.com/paraview/paraview/-/issues/13437"invalid drawable" error when opening color scale editor2018-08-23T15:16:54-04:00Kitware Robot"invalid drawable" error when opening color scale editor**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13437). Further discussion may take place here.**
---
On the latest build of ParaView on my Mac, whenever I open up the Color Sc...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13437). Further discussion may take place here.**
---
On the latest build of ParaView on my Mac, whenever I open up the Color Scale Editor, I get an "invalid drawable" error in the console (but not in the ParaView output window). There might be something screwy going on with the Qt widget states.https://gitlab.kitware.com/paraview/paraview/-/issues/13438Advanced toggle on the color scale editor2018-08-23T15:16:54-04:00Kitware RobotAdvanced toggle on the color scale editor**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13438). Further discussion may take place here.**
---
This week I thought there was something wrong with my ParaView build when ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13438). Further discussion may take place here.**
---
This week I thought there was something wrong with my ParaView build when I brought up the Color Scale Editor and saw that most of the widgets were missing. I brought this up during the ParaView meeting today and learned that there is an advanced toggle to get the full controls. I see it now, but if I had not been told who knows how long before I would have discovered it.
I recommend making the advanced toggle consistent with that on the properties panel. Place the widget in the upper right of the dialog (rather than the lower left) and use the same square toggle button with the gear icon.https://gitlab.kitware.com/paraview/paraview/-/issues/13439Finer control over Lock Interactive Render2018-08-23T15:16:54-04:00Kitware RobotFiner control over Lock Interactive Render**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13439). Further discussion may take place here.**
---
Currently, the Lock Interactive Render control is fixed to allow you to se...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13439). Further discussion may take place here.**
---
Currently, the Lock Interactive Render control is fixed to allow you to set only integer seconds. Often even one second feels like too long to wait. I suggest allowing you to set the Lock Interactive Render time by units of 100 ms.https://gitlab.kitware.com/paraview/paraview/-/issues/13440ExodusII: Time steps wrongly ordered2018-08-23T15:16:54-04:00Kitware RobotExodusII: Time steps wrongly ordered**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13440). Further discussion may take place here.**
---
Exodus files that contain several states associated with time steps typica...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13440). Further discussion may take place here.**
---
Exodus files that contain several states associated with time steps typically store those in ascending order in the file. It may happen though that "time" really represents another scalar parameter quantity which is allowed to decrease from one step to another. The file found at http://win.ua.ac.be/~nschloe/other/solution.e is an example.
What ParaView does for those files is reorder the states found in the file by time instead of taking the order in which they are stored. This leads to unwanted behavior with observing the data.
VTK has the ability of reading individual, int-indexed time steps, cf. http://www.vtk.org/doc/nightly/html/classvtkExodusIIReader.html#a37e8d6c7118877de07fa140b5d5eb8c3.
The suggestion would be to remove the code that explicitly orders the time steps by their time value, and display the states in the natural int-indexed order that is stored in the file.https://gitlab.kitware.com/paraview/paraview/-/issues/13441sqtk-tetsing -- SciberquestToolKit plugin ctests, bug fixes, and updates2018-08-23T15:16:54-04:00Kitware Robotsqtk-tetsing -- SciberquestToolKit plugin ctests, bug fixes, and updates**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13441). Further discussion may take place here.**
---
Added ctests to the SciberQuestToolKit plugin. Fixed writer bug that came ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13441). Further discussion may take place here.**
---
Added ctests to the SciberQuestToolKit plugin. Fixed writer bug that came about as a result of vtk 6 changes. Added ftle filter. Added support to ftle for periodic boundary conditions. Updated logging facility.
The git branch is called "sqtk-testing".
https://gitlab.kitware.com/paraview/paraview/-/issues/13445support CTH coprocessing adaptor2018-08-23T15:16:54-04:00Kitware Robotsupport CTH coprocessing adaptor**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13445). Further discussion may take place here.**
---
Add code to support CTH as a coprocessing target**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13445). Further discussion may take place here.**
---
Add code to support CTH as a coprocessing targethttps://gitlab.kitware.com/paraview/paraview/-/issues/13446some symbols not exported in windows compilation (xdmf)2018-08-23T15:16:54-04:00Kitware Robotsome symbols not exported in windows compilation (xdmf)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13446). Further discussion may take place here.**
---
I have a plugin, it compile perfectly in Linux and Mac, but not in windows...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13446). Further discussion may take place here.**
---
I have a plugin, it compile perfectly in Linux and Mac, but not in windows7 (visual C++ 2008).
Paraview 3.14.1 git version (using superbuild)
Reason:
Symbols are not exposed in the windows library.
errors:
...
...
Build started: Project: PXDMFReader, Configuration: Release|Win32
Linking...
Creating library C:\Users\utilisateur\ParaView\builds\ParaView-build\bin\Release\PXDMFReader.lib and object C:\Users\utilisateur\ParaView\builds\ParaView-build\bin\Release\PXDMFReader.exp
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: __thiscall vtkXdmfDocument::~vtkXdmfDocument(void)" (??1vtkXdmfDocument@@QAE@XZ) referenced in function "public: void * __thiscall vtkXdmfDocument::`scalar deleting destructor'(unsigned int)" (??_GvtkXdmfDocument@@QAEPAXI@Z)
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: int __thiscall vtkXdmfDomain::GetVTKDataType(class XdmfGrid *)" (?GetVTKDataType@vtkXdmfDomain@@QAEHPAVXdmfGrid@@@Z) referenced in function "public: virtual int __thiscall vtkPXDMFDocument::ReadOutputType(void)" (?ReadOutputType@vtkPXDMFDocument@@UAEHXZ)
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: class XdmfGrid * __thiscall vtkXdmfDomain::GetGrid(__int64)" (?GetGrid@vtkXdmfDomain@@QAEPAVXdmfGrid@@_J@Z) referenced in function "public: virtual int __thiscall vtkPXDMFDocument::ReadOutputType(void)" (?ReadOutputType@vtkPXDMFDocument@@UAEHXZ)
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: __thiscall vtkXdmfDocument::vtkXdmfDocument(void)" (??0vtkXdmfDocument@@QAE@XZ) referenced in function "protected: __thiscall vtkPXDMFDocument::vtkPXDMFDocument(void)" (??0vtkPXDMFDocument@@IAE@XZ)
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: bool __thiscall vtkXdmfDocument::SetActiveDomain(int)" (?SetActiveDomain@vtkXdmfDocument@@QAE_NH@Z) referenced in function "public: virtual class vtkXdmfDomain * __thiscall vtkPXDMFDocument::PrepareDocument(void)" (?PrepareDocument@vtkPXDMFDocument@@UAEPAVvtkXdmfDomain@@XZ)
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: bool __thiscall vtkXdmfDocument::SetActiveDomain(char const *)" (?SetActiveDomain@vtkXdmfDocument@@QAE_NPBD@Z) referenced in function "public: virtual class vtkXdmfDomain * __thiscall vtkPXDMFDocument::PrepareDocument(void)" (?PrepareDocument@vtkPXDMFDocument@@UAEPAVvtkXdmfDomain@@XZ)
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: bool __thiscall vtkXdmfDocument::Parse(char const *)" (?Parse@vtkXdmfDocument@@QAE_NPBD@Z) referenced in function "public: virtual class vtkXdmfDomain * __thiscall vtkPXDMFDocument::PrepareDocument(void)" (?PrepareDocument@vtkPXDMFDocument@@UAEPAVvtkXdmfDomain@@XZ)
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: __thiscall vtkXdmfHeavyData::~vtkXdmfHeavyData(void)" (??1vtkXdmfHeavyData@@QAE@XZ) referenced in function "public: class vtkDataObject * __thiscall vtkPXDMFDocument::GenerateOutput(class vtkInformation *,class vtkInformationVector * *,class vtkInformationVector *)" (?GenerateOutput@vtkPXDMFDocument@@QAEPAVvtkDataObject@@PAVvtkInformation@@PAPAVvtkInformationVector@@PAV4@@Z)
vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: class vtkDataObject * __thiscall vtkXdmfHeavyData::ReadData(class XdmfGrid *)" (?ReadData@vtkXdmfHeavyData@@QAEPAVvtkDataObject@@PAVXdmfGrid@@@Z) referenced in function "public: class vtkDataObject * __thiscall vtkPXDMFDocument::GenerateOutput(class vtkInformation *,class vtkInformationVector
* *,class vtkInformationVector *)" (?GenerateOutput@vtkPXDMFDocument@@QAEPAVvtkDataObject@@PAVvtkInformation@@PAPAVvtkInformationVector@@PAV4@@Z) vtkPXDMFDocument.obj : error LNK2019: unresolved external symbol "public: __thiscall vtkXdmfHeavyData::vtkXdmfHeavyData(class vtkXdmfDomain *,class vtkAlgorithm *)" (??0vtkXdmfHeavyData@@QAE@PAVvtkXdmfDomain@@PAVvtkAlgorithm@@@Z) referenced in function "public: class vtkDataObject * __thiscall vtkPXDMFDocument::GenerateOutput(class vtkInformation *,class vtkInformationVector * *,class vtkInformationVector *)" (?GenerateOutput@vtkPXDMFDocument@@QAEPAVvtkDataObject@@PAVvtkInformation@@PAPAVvtkInformationVector@@PAV4@@Z)
C:\Users\utilisateur\ParaView\builds\ParaView-build\bin\Release\PXDMFReader.dll : fatal error LNK1120: 10 unresolved externals
Build log was saved at "file://c:\Users\utilisateur\ParaView\builds\ParaView-build\Plugins\ParaviewPXDMFReader\PXDMFReader.dir\Release\BuildLog.htm"
PXDMFReader - 11 error(s), 0 warning(s)
Fermeture de la commande avec le code 1.
...
...
THE SOLUTION:
Add VTK_EXPORT to some classes.
THE PATCH:
diff --git a/vtk/vtkXdmfHeavyData.h b/vtk/vtkXdmfHeavyData.h
index 7995329..0b3413f 100644
--- a/vtk/vtkXdmfHeavyData.h
+++ b/vtk/vtkXdmfHeavyData.h
@@ -35,7 +35,7 @@ class vtkAlgorithm;
// vtkXdmfHeavyData helps in reading heavy data from Xdmf and putting that into
// vtkDataObject subclasses.
-class vtkXdmfHeavyData
+class VTK_EXPORT vtkXdmfHeavyData
{
vtkXdmfDomain* Domain;
XdmfDataItem DataItem;
diff --git a/vtk/vtkXdmfReaderInternal.h b/vtk/vtkXdmfReaderInternal.h
index 2d7c7e9..3adb9be 100644
--- a/vtk/vtkXdmfReaderInternal.h
+++ b/vtk/vtkXdmfReaderInternal.h
@@ -51,8 +51,8 @@
#include <algorithm>
#include <vtksys/ios/sstream>
-class vtkXdmfDomain;
-class vtkXdmfDocument
+class VTK_EXPORT vtkXdmfDomain;
+class VTK_EXPORT vtkXdmfDocument
{
public:
//---------------------------------------------------------------------------
@@ -173,7 +173,7 @@ public:
};
//***************************************************************************
-class vtkXdmfDomain
+class VTK_EXPORT vtkXdmfDomain
{
private:
XdmfInt64 NumberOfGrids;