ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-02-03T12:02:19-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/19592Error when compiling pqRenderViewSelectionReaction.cxx with ParaView 5.8.0-RC12020-02-03T12:02:19-05:00Joseph G. HennesseyError when compiling pqRenderViewSelectionReaction.cxx with ParaView 5.8.0-RC1When compiling Qt/ApplicationComponents/pqRenderViewSelectionReaction.cxx using the ParaView superbuild for ParaView 5.8.0-RC1 and using the default version of Qt 5.9.2 compiled by the superbuild with gcc 4.8.5 on RHEL 7.7 the following ...When compiling Qt/ApplicationComponents/pqRenderViewSelectionReaction.cxx using the ParaView superbuild for ParaView 5.8.0-RC1 and using the default version of Qt 5.9.2 compiled by the superbuild with gcc 4.8.5 on RHEL 7.7 the following error occurs
```
/home/joeh/PV/Build_5.8.0-RC1_mesa/superbuild/paraview/src/Qt/ApplicationComponents/pqRenderViewSelectionReaction.cxx: In member function 'void pqRenderViewSelectionReaction::setRepresentation(pqDataRepresentation*)':
/home/joeh/PV/Build_5.8.0-RC1_mesa/superbuild/paraview/src/Qt/ApplicationComponents/pqRenderViewSelectionReaction.cxx:290:10: error: no matching function for call to 'pqRenderViewSelectionReaction::connect(QPointer<pqDataRepresentation>&, void (pqDataRepresentation::*)(), pqRenderViewSelectionReaction* const, pqRenderViewSelectionReaction::setRepresentation(pqDataRepresentation*)::__lambda0)'
});
^
```
The relevant lines were changed by
Commit aea5c5aa
authored 1 month ago by Michael Migliore
Add selection by array
Thanks,
Joe Hennessey5.8 (Winter 2020)Michael MiglioreMichael Migliorehttps://gitlab.kitware.com/paraview/paraview/-/issues/19591Error when compiling ParaView 5.8.0-RC1 with pqChooseColorPresetReaction.cxx2020-01-31T19:53:33-05:00Joseph G. HennesseyError when compiling ParaView 5.8.0-RC1 with pqChooseColorPresetReaction.cxxWhen compiling Qt/ApplicationComponents/pqChooseColorPresetReaction.cxx using the ParaView superbuild for ParaView 5.8.0-RC1
and using the default version of Qt 5.9.2 compiled by the superbuild with gcc 4.8.5 on RHEL 7.7 the following er...When compiling Qt/ApplicationComponents/pqChooseColorPresetReaction.cxx using the ParaView superbuild for ParaView 5.8.0-RC1
and using the default version of Qt 5.9.2 compiled by the superbuild with gcc 4.8.5 on RHEL 7.7 the following error occurs
```
[ 99%] Building CXX object Qt/ApplicationComponents/CMakeFiles/pqApplicationComponents.dir/pqCustomShortcutBehavior.cxx.o
/home/joeh/PV/Build_5.8.0-RC1_mesa/superbuild/paraview/src/Qt/ApplicationComponents/pqChooseColorPresetReaction.cxx: In member function 'bool pqChooseColorPresetReaction::choosePreset(const char*)':
/home/joeh/PV/Build_5.8.0-RC1_mesa/superbuild/paraview/src/Qt/ApplicationComponents/pqChooseColorPresetReaction.cxx:156:53: error: no matching function for call to 'pqChooseColorPresetReaction::connect(QPointer<pqPresetDialog>&, void (pqPresetDialog::*)(const vtkJson::Value&), pqChooseColorPresetReaction* const, void (pqChooseColorPresetReaction::*)())'
&pqChooseColorPresetReaction::applyCurrentPreset);
```
The relevant lines where last changed by this commit
Commit a7872caf
authored 1 month ago by Ben Boeckel's avatar Ben Boeckel
qt: hook up mangled signal name with a function pointer
Thanks,
Joe Hennessey5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19589Please add ability for superquadrics to run in parallel2021-11-15T17:41:17-05:00W. Alan ScottPlease add ability for superquadrics to run in parallelPlease add the ability for Sources/ superquadrics to run on multiple ranks.Please add the ability for Sources/ superquadrics to run on multiple ranks.Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/19588Spreadsheet displays incorrect values for field data in Paraview 5.72020-01-31T20:12:44-05:00Loïc BertheSpreadsheet displays incorrect values for field data in Paraview 5.7With Paraview 5.7, the spreadsheet displays incorrects values for field data.
Here is a test file showing the problem : [test_FieldData.xdmf](/uploads/7a2920380e0993b106f369ee1a4fb7f5/test_FieldData.xdmf).
You will find below two scr...With Paraview 5.7, the spreadsheet displays incorrects values for field data.
Here is a test file showing the problem : [test_FieldData.xdmf](/uploads/7a2920380e0993b106f369ee1a4fb7f5/test_FieldData.xdmf).
You will find below two screenshots of the spreadsheet in Paraview 5.5 and paraview 5.7 :
![Test_paraview-5.5](/uploads/75652da3fc0446d233d8656ebfcd6935/Test_paraview-5.5.png)
--> Paraview 5.5 displays field data correctly
![Test_paraview-5.7](/uploads/bc43876fc769ba34c8bc96ecf2ec0102/Test_paraview-5.7.png)
--> Paraview 5.7 displays incorrects values
Best regards,
Loïc5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19587Missing SVG for the "Select by array" feature2020-01-24T05:38:35-05:00Michael MiglioreMissing SVG for the "Select by array" featureSVG icons have been created [in this MR](https://gitlab.kitware.com/paraview/paraview/merge_requests/3792) and they look great.
I have added a new feature [here](https://gitlab.kitware.com/paraview/paraview/merge_requests/3768) but the...SVG icons have been created [in this MR](https://gitlab.kitware.com/paraview/paraview/merge_requests/3792) and they look great.
I have added a new feature [here](https://gitlab.kitware.com/paraview/paraview/merge_requests/3768) but the icons are still low quality png files.
We might need to update this for 5.8 release.
@cory.quammen5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19586Internal error on wiki page2020-01-17T13:47:04-05:00Jean M. FavreInternal error on wiki pageI have difficulty porting external plugins [which work in pv5.7] to pv5.8 and search the wiki for documentation. I was taken to this page which causes an internal error
https://www.paraview.org/Wiki/ParaView/Plugin_HowToI have difficulty porting external plugins [which work in pv5.7] to pv5.8 and search the wiki for documentation. I was taken to this page which causes an internal error
https://www.paraview.org/Wiki/ParaView/Plugin_HowTohttps://gitlab.kitware.com/paraview/paraview/-/issues/19585texturemaptosphere hangs in parallel2020-04-12T18:43:31-04:00W. Alan Scotttexturemaptosphere hangs in parallelI am getting a hang with texturemaptosphere. Here is how to replicate:
* 5.8.0-RC1, Linux, remote server (I have 32 ranks).
* Sources/ Superquadric. Theta Resolution == 128, Phi Resolution == 128. Turn off Toroidal. Apply.
* TextureM...I am getting a hang with texturemaptosphere. Here is how to replicate:
* 5.8.0-RC1, Linux, remote server (I have 32 ranks).
* Sources/ Superquadric. Theta Resolution == 128, Phi Resolution == 128. Turn off Toroidal. Apply.
* TextureMapToSphere. Apply.
It will never come back.5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19584Hover Cells On and Hover Points On is backwards2020-05-22T20:28:46-04:00W. Alan ScottHover Cells On and Hover Points On is backwardsHover Cells On and Hover Points On is backwards. All of the rest of the selection icons have the Cells on the left, points on the right.
Please make Hover Cells On left of Hover Points On.Hover Cells On and Hover Points On is backwards. All of the rest of the selection icons have the Cells on the left, points on the right.
Please make Hover Cells On left of Hover Points On.Michael MiglioreMichael Migliorehttps://gitlab.kitware.com/paraview/paraview/-/issues/19583Interactive Select Cell Data On and Interactive Select Point Data On icons ar...2020-05-22T20:29:49-04:00W. Alan ScottInteractive Select Cell Data On and Interactive Select Point Data On icons are backwardsThe Interactive Select Cell Data On and Interactive Select Point Data on icons and functionality are backwards. Everything on these icons have cells on the left, points on the right. Interactive Select * reverses this.
Please place In...The Interactive Select Cell Data On and Interactive Select Point Data on icons and functionality are backwards. Everything on these icons have cells on the left, points on the right. Interactive Select * reverses this.
Please place Interactive Select Cell Data On to the left of Interactive Select Point Data On.
By the way, what do these icons do? I couldn't get them to work.Michael MiglioreMichael Migliorehttps://gitlab.kitware.com/paraview/paraview/-/issues/19582Add ability for mandlebrot to become an image stack2020-01-22T13:59:30-05:00W. Alan ScottAdd ability for mandlebrot to become an image stackPlease add the ability for the Sources/ Mandlebrot to become an image stack. Say I want 200 stacks on top of each other, so I can then contour/ volume render/ slice/ dice/ mince etc.Please add the ability for the Sources/ Mandlebrot to become an image stack. Say I want 200 stacks on top of each other, so I can then contour/ volume render/ slice/ dice/ mince etc.https://gitlab.kitware.com/paraview/paraview/-/issues/19581ParaView 5.8.0-RC1: build failure on MSVC 20172020-01-31T19:55:45-05:00Cory Quammencory.quammen@kitware.comParaView 5.8.0-RC1: build failure on MSVC 2017Building with `ninja` and Visual Studio 2017, I get a build error:
```
[10834/11965] Building CXX object Remoting\Views\CMakeFiles\RemotingViews.dir\vtkSMTransferFunctionPresets.cxx.obj
FAILED: Remoting/Views/CMakeFiles/RemotingViews.di...Building with `ninja` and Visual Studio 2017, I get a build error:
```
[10834/11965] Building CXX object Remoting\Views\CMakeFiles\RemotingViews.dir\vtkSMTransferFunctionPresets.cxx.obj
FAILED: Remoting/Views/CMakeFiles/RemotingViews.dir/vtkSMTransferFunctionPresets.cxx.obj
C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1416~1.270\bin\Hostx64\x64\cl.exe /nologo /TP -DPROTOBUF_USE_DLLS -DRemotingViews_EXPORTS -DVTK_MODULE_ENABLE_ParaView_icet=0 -DVTK_MODULE_ENABLE_ParaView_nvpipe=0 -DVTK_MODULE_ENABLE_VTK_AcceleratorsVTKm=1 -DVTK_MODULE_ENABLE_VTK_FiltersOpenTURNS=0 -DVTK_MODULE_ENABLE_VTK_ParallelMPI=0 -DVTK_MODULE_ENABLE_VTK_RenderingRayTracing=0 -DVTK_MODULE_ENABLE_VTK_vtkm=1 -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -DvtkDomainsChemistry_AUTOINIT_INCLUDE=\"C:/build/paraview-debug/CMakeFiles/vtkModuleAutoInit_006c125fb83ec547e364ce4bbccaaa20.h\" -DvtkRenderingContext2D_AUTOINIT_INCLUDE=\"C:/build/paraview-debug/CMakeFiles/vtkModuleAutoInit_006c125fb83ec547e364ce4bbccaaa20.h\" -DvtkRenderingCore_AUTOINIT_INCLUDE=\"C:/build/paraview-debug/CMakeFiles/vtkModuleAutoInit_006c125fb83ec547e364ce4bbccaaa20.h\" -IRemoting\Views -IC:\source\paraview-debug\Remoting\Views -IRemoting\Core -IC:\source\paraview-debug\Remoting\Core -IRemoting\ClientServerStream -IC:\source\paraview-debug\Remoting\ClientServerStream -IVTK\Common\Core -IC:\source\paraview-debug\VTK\Common\Core -IVTKExtensions\Core -IC:\source\paraview-debug\VTKExtensions\Core -IVTK\Common\DataModel -IC:\source\paraview-debug\VTK\Common\DataModel -IVTK\Common\Math -IC:\source\paraview-debug\VTK\Common\Math -IVTK\Common\Transforms -IC:\source\paraview-debug\VTK\Common\Transforms -IVTK\Common\ExecutionModel -IC:\source\paraview-debug\VTK\Common\ExecutionModel -IVTK\IO\XML -IC:\source\paraview-debug\VTK\IO\XML -IVTK\IO\XMLParser -IC:\source\paraview-debug\VTK\IO\XMLParser -IVTK\Common\Misc -IC:\source\paraview-debug\VTK\Common\Misc -IVTK\Parallel\Core -IC:\source\paraview-debug\VTK\Parallel\Core -IRemoting\ServerManager -IC:\source\paraview-debug\Remoting\ServerManager -IC:\source\paraview-debug\ThirdParty\protobuf\vtkprotobuf\src -IVTK\ThirdParty\jsoncpp\vtkjsoncpp -IC:\source\paraview-debug\VTK\ThirdParty\jsoncpp\vtkjsoncpp -IVTK\ThirdParty\jsoncpp\vtkjsoncpp\json -IVTK\Charts\Core -IC:\source\paraview-debug\VTK\Charts\Core -IVTK\Filters\General -IC:\source\paraview-debug\VTK\Filters\General -IVTK\Filters\Core -IC:\source\paraview-debug\VTK\Filters\Core -IVTK\Rendering\Context2D -IC:\source\paraview-debug\VTK\Rendering\Context2D -IVTK\Rendering\Core -IC:\source\paraview-debug\VTK\Rendering\Core -IVTK\Rendering\Annotation -IC:\source\paraview-debug\VTK\Rendering\Annotation -IVTK\Rendering\Parallel -IC:\source\paraview-debug\VTK\Rendering\Parallel -IVTK\Rendering\OpenGL2 -IC:\source\paraview-debug\VTK\Rendering\OpenGL2 -IVTK\ThirdParty\glew\vtkglew -IC:\source\paraview-debug\VTK\ThirdParty\glew\vtkglew -IVTK\Views\Context2D -IC:\source\paraview-debug\VTK\Views\Context2D -IVTK\Views\Core -IC:\source\paraview-debug\VTK\Views\Core -IVTK\Interaction\Widgets -IC:\source\paraview-debug\VTK\Interaction\Widgets -IVTK\Filters\Sources -IC:\source\paraview-debug\VTK\Filters\Sources -IVTKExtensions\Extraction -IC:\source\paraview-debug\VTKExtensions\Extraction -IVTK\Filters\Extraction -IC:\source\paraview-debug\VTK\Filters\Extraction -IVTKExtensions\FiltersRendering -IC:\source\paraview-debug\VTKExtensions\FiltersRendering -IVTKExtensions\InteractionStyle -IC:\source\paraview-debug\VTKExtensions\InteractionStyle -IVTK\Interaction\Style -IC:\source\paraview-debug\VTK\Interaction\Style -IVTKExtensions\Misc -IC:\source\paraview-debug\VTKExtensions\Misc -IVTK\Common\Color -IC:\source\paraview-debug\VTK\Common\Color -IVTK\Common\System -IC:\source\paraview-debug\VTK\Common\System -IVTK\Domains\ChemistryOpenGL2 -IC:\source\paraview-debug\VTK\Domains\ChemistryOpenGL2 -IVTK\Domains\Chemistry -IC:\source\paraview-debug\VTK\Domains\Chemistry -IVTK\IO\Legacy -IC:\source\paraview-debug\VTK\IO\Legacy -IVTK\IO\Core -IC:\source\paraview-debug\VTK\IO\Core -IVTK\Filters\Modeling -IC:\source\paraview-debug\VTK\Filters\Modeling -IVTK\Filters\Parallel -IC:\source\paraview-debug\VTK\Filters\Parallel -IVTK\Filters\Geometry -IC:\source\paraview-debug\VTK\Filters\Geometry -IVTK\Filters\Texture -IC:\source\paraview-debug\VTK\Filters\Texture -IVTK\IO\Image -IC:\source\paraview-debug\VTK\IO\Image -IVTK\Rendering\ContextOpenGL2 -IC:\source\paraview-debug\VTK\Rendering\ContextOpenGL2 -IVTK\Rendering\FreeType -IC:\source\paraview-debug\VTK\Rendering\FreeType -IVTK\ThirdParty\freetype\vtkfreetype -IC:\source\paraview-debug\VTK\ThirdParty\freetype\vtkfreetype -IVTK\ThirdParty\zlib\vtkzlib -IC:\source\paraview-debug\VTK\ThirdParty\zlib\vtkzlib -IVTK\Rendering\Label -IC:\source\paraview-debug\VTK\Rendering\Label -IVTK\Rendering\VolumeAMR -IC:\source\paraview-debug\VTK\Rendering\VolumeAMR -IVTK\Imaging\Core -IC:\source\paraview-debug\VTK\Imaging\Core -IVTK\Rendering\Volume -IC:\source\paraview-debug\VTK\Rendering\Volume -IVTK\Rendering\VolumeOpenGL2 -IC:\source\paraview-debug\VTK\Rendering\VolumeOpenGL2 -IVTK\Imaging\Math -IC:\source\paraview-debug\VTK\Imaging\Math -IVTK\Accelerators\Vtkm -IC:\source\paraview-debug\VTK\Accelerators\Vtkm -IVTK\ThirdParty\vtkm\vtkvtkm -IC:\source\paraview-debug\VTK\ThirdParty\vtkm\vtkvtkm -IC:\source\paraview-debug\VTK\ThirdParty\vtkm\vtkvtkm\vtk-m -IVTK\ThirdParty\vtkm\vtkvtkm\vtk-m\include -IC:\source\paraview-debug\VTK\ThirdParty\vtkm\vtkvtkm\vtk-m\vtkm\thirdparty\taotuple -IC:\source\paraview-debug\VTK\ThirdParty\vtkm\vtkvtkm\vtk-m\vtkm\thirdparty\optionparser -IC:\source\paraview-debug\VTK\ThirdParty\vtkm\vtkvtkm\vtk-m\vtkm\thirdparty\diy -IC:\source\paraview-debug\VTK\ThirdParty\vtkm\vtkvtkm\vtk-m\vtkm\thirdparty\lcl\vtkmlcl -IVTK\Utilities\KWIML -IC:\source\paraview-debug\VTK\Utilities\KWIML -IVTK\Utilities\KWSys -IC:\source\paraview-debug\VTK\Utilities\KWSys -IThirdParty\protobuf -IC:\source\paraview-debug\ThirdParty\protobuf -IVTK\ThirdParty\jsoncpp -IC:\source\paraview-debug\VTK\ThirdParty\jsoncpp -IVTK\ThirdParty\glew -IC:\source\paraview-debug\VTK\ThirdParty\glew -IVTK\ThirdParty\freetype -IC:\source\paraview-debug\VTK\ThirdParty\freetype -IVTK\ThirdParty\zlib -IC:\source\paraview-debug\VTK\ThirdParty\zlib -IVTK\ThirdParty\vtkm -IC:\source\paraview-debug\VTK\ThirdParty\vtkm /DWIN32 /D_WINDOWS /W4 /GR /EHsc /bigobj /MDd /Zi /Ob0 /Od /RTC1 /Gy /bigobj /showIncludes /FoRemoting\Views\CMakeFiles\RemotingViews.dir\vtkSMTransferFunctionPresets.cxx.obj /FdRemoting\Views\CMakeFiles\RemotingViews.dir\ /FS -c C:\source\paraview-debug\Remoting\Views\vtkSMTransferFunctionPresets.cxx
C:\source\paraview-debug\VTK\ThirdParty\jsoncpp\vtkjsoncpp/json/json.h(617): warning C4275: non dll-interface class 'std::exception' used as base for dll-interface class 'vtkJson::Exception'
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\vcruntime_exception.h(44): note: see declaration of 'std::exception'
C:\source\paraview-debug\VTK\ThirdParty\jsoncpp\vtkjsoncpp/json/json.h(617): note: see declaration of 'vtkJson::Exception'
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\xmemory(217): error C2678: binary '*': no operator found which takes a left-hand operand of type 'const _Iter' (or there is no acceptable conversion)
with
[
_Iter=vtkJson::Value::iterator
]
C:\source\paraview-debug\VTK\ThirdParty\jsoncpp\vtkjsoncpp/json/json.h(1509): note: could be 'vtkJson::ValueIterator::reference vtkJson::ValueIterator::operator *(void)'
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\xmemory(217): note: while trying to match the argument list '(const _Iter)'
with
[
_Iter=vtkJson::Value::iterator
]
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\vector(1823): note: see reference to function template instantiation '_FwdIt *std::_Uninitialized_copy<_Iter,vtkJson::Value*,std::allocator<_Ty>>(const _InIt,const _InIt,_FwdIt,_Alloc &)' being compiled
with
[
_FwdIt=vtkJson::Value *,
_Iter=vtkJson::Value::iterator,
_Ty=vtkJson::Value,
_InIt=vtkJson::Value::iterator,
_Alloc=std::allocator<vtkJson::Value>
]
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\vector(1161): note: see reference to function template instantiation 'vtkJson::Value *std::vector<vtkJson::Value,std::allocator<_Ty>>::_Ucopy<_Iter>(_Iter,_Iter,vtkJson::Value *)' being compiled
with
[
_Ty=vtkJson::Value,
_Iter=vtkJson::Value::iterator
]
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\vector(1161): note: see reference to function template instantiation 'vtkJson::Value *std::vector<vtkJson::Value,std::allocator<_Ty>>::_Ucopy<_Iter>(_Iter,_Iter,vtkJson::Value *)' being compiled
with
[
_Ty=vtkJson::Value,
_Iter=vtkJson::Value::iterator
]
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\vector(1261): note: see reference to function template instantiation 'void std::vector<vtkJson::Value,std::allocator<_Ty>>::_Insert_range<_Iter>(std::_Vector_const_iterator<std::_Vector_val<std::_Simple_types<_Ty>>>,_Iter,_Iter,std::forward_iterator_tag)' being compiled
with
[
_Ty=vtkJson::Value,
_Iter=vtkJson::Value::iterator
]
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\vector(1261): note: see reference to function template instantiation 'void std::vector<vtkJson::Value,std::allocator<_Ty>>::_Insert_range<_Iter>(std::_Vector_const_iterator<std::_Vector_val<std::_Simple_types<_Ty>>>,_Iter,_Iter,std::forward_iterator_tag)' being compiled
with
[
_Ty=vtkJson::Value,
_Iter=vtkJson::Value::iterator
]
C:\source\paraview-debug\Remoting\Views\vtkSMTransferFunctionPresets.cxx(198): note: see reference to function template instantiation 'std::_Vector_iterator<std::_Vector_val<std::_Simple_types<_Ty>>> std::vector<_Ty,std::allocator<_Ty>>::insert<vtkJson::Value::iterator,void>(std::_Vector_const_iterator<std::_Vector_val<std::_Simple_types<_Ty>>>,_Iter,_Iter)' being compiled
with
[
_Ty=vtkJson::Value,
_Iter=vtkJson::Value::iterator
]
C:\source\paraview-debug\Remoting\Views\vtkSMTransferFunctionPresets.cxx(198): note: see reference to function template instantiation 'std::_Vector_iterator<std::_Vector_val<std::_Simple_types<_Ty>>> std::vector<_Ty,std::allocator<_Ty>>::insert<vtkJson::Value::iterator,void>(std::_Vector_const_iterator<std::_Vector_val<std::_Simple_types<_Ty>>>,_Iter,_Iter)' being compiled
with
[
_Ty=vtkJson::Value,
_Iter=vtkJson::Value::iterator
]
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\xmemory(217): error C2100: illegal indirection
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\xmemory(217): error C2062: type 'unknown-type' unexpected
[10864/11965] Building CXX object Remoting\Views\CMakeFiles\RemotingViews.dir\vtkSMTransferFunctionProxy.cxx.obj
C:\source\paraview-debug\VTK\ThirdParty\jsoncpp\vtkjsoncpp/json/json.h(617): warning C4275: non dll-interface class 'std::exception' used as base for dll-interface class 'vtkJson::Exception'
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\vcruntime_exception.h(44): note: see declaration of 'std::exception'
C:\source\paraview-debug\VTK\ThirdParty\jsoncpp\vtkjsoncpp/json/json.h(617): note: see declaration of 'vtkJson::Exception'
```5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19580paraview.simple.GetOpenGLInformation() fails2020-04-12T18:19:25-04:00Cory Quammencory.quammen@kitware.comparaview.simple.GetOpenGLInformation() failsFrom @jfavre:
in 5.7, I use
```python
info = GetOpenGLInformation(location=servermanager.vtkSMSession.RENDER_SERVER)
print("Vendor: %s" % info.GetVendor())
print("Version: %s" % info.GetVersion())
print("Renderer: %s" % info.GetRen...From @jfavre:
in 5.7, I use
```python
info = GetOpenGLInformation(location=servermanager.vtkSMSession.RENDER_SERVER)
print("Vendor: %s" % info.GetVendor())
print("Version: %s" % info.GetVersion())
print("Renderer: %s" % info.GetRenderer())
```
in my regression test to verify that I am connected to the GPU.
This no longer works in 5.8. I get this error:
```python
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/local/apps/ParaView/5.8/lib/python3.7/site-packages/paraview/simple.py", line 2109, in GetOpenGLInformation
openGLInfo = servermanager.vtkPVServerImplementationRendering.vtkPVClientServerCoreRendering.vtkPVOpenGLInformation()
```5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19579CMake configure CATALYST edition can't find ParaView::RemotingViews2020-02-04T20:03:27-05:00Ethan StamCMake configure CATALYST edition can't find ParaView::RemotingViewsOn MacOS 10.14.6, ParaView master branch, cmake version 3.12.4
I selected CATALYST as the build edition, and I am got this error when configuring:
```
CMake Error at CMakeLists.txt:331 (message):
The following modules were requested...On MacOS 10.14.6, ParaView master branch, cmake version 3.12.4
I selected CATALYST as the build edition, and I am got this error when configuring:
```
CMake Error at CMakeLists.txt:331 (message):
The following modules were requested or required, but not found:
ParaView::RemotingViews;ParaView::RemotingViews;ParaView::RemotingViews;ParaView::RemotingViews;ParaView::RemotingViews;ParaView::RemotingViews;ParaView::RemotingVie
ws;ParaView::RemotingViews.
```5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19578Preview menu item is grayed out2020-01-31T21:22:54-05:00W. Alan ScottPreview menu item is grayed outPreview is grayed out. Here is how to replicate:
* 5.8.0-RC1, Linux, builtin server.
* Sources/ Fast Uniform Grid. Apply. (Just to make sure it isn't that there is no object.) (I did make the source Solid)
* View/ Preview is grayed ...Preview is grayed out. Here is how to replicate:
* 5.8.0-RC1, Linux, builtin server.
* Sources/ Fast Uniform Grid. Apply. (Just to make sure it isn't that there is no object.) (I did make the source Solid)
* View/ Preview is grayed out! This is a bug.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19577Split Views icons are backwards!2020-01-15T14:39:11-05:00W. Alan ScottSplit Views icons are backwards!Split Views are backwards! The left split icon should be horizontal (as the help bubble says), but the icon is for vertical.
5.8.0-RC1, Linux.Split Views are backwards! The left split icon should be horizontal (as the help bubble says), but the icon is for vertical.
5.8.0-RC1, Linux.5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19575Split vertical and horizontal icons are switched2020-01-31T21:23:45-05:00Dan LipsaSplit vertical and horizontal icons are switchedOn the latest ParaView master (SHA 836601d1e80b56b297869fea5e9b7a5baf662174) split horizontal button splits the views vertically and vice-versa. Probably the connections are switched.On the latest ParaView master (SHA 836601d1e80b56b297869fea5e9b7a5baf662174) split horizontal button splits the views vertically and vice-versa. Probably the connections are switched.5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19574"Hover points on" and "Hover cells on" and interactive selection not updated...2023-11-16T18:36:18-05:00Florian Maurin"Hover points on" and "Hover cells on" and interactive selection not updated when switching geometriesTo reproduce the bug:
* Open the two geometries attached
[triangle_stress_1.vtu](/uploads/b5f48ba74765219f3305b3c36d60dd53/triangle_stress_1.vtu)
[triangle_stress_2.vtu](/uploads/3db1aa4ac89cc8b18a4fe64623b72e43/triangle_stress_2.vtu)
* ...To reproduce the bug:
* Open the two geometries attached
[triangle_stress_1.vtu](/uploads/b5f48ba74765219f3305b3c36d60dd53/triangle_stress_1.vtu)
[triangle_stress_2.vtu](/uploads/3db1aa4ac89cc8b18a4fe64623b72e43/triangle_stress_2.vtu)
* Select the first one (triangle_stress_1)
* Clic on "Hover points on", move the mouse to an edge of the triangle. The indicated stress should be 1.
* Select the second file (triangle_stress_2), and deselect the first file (the order of the operation is here important).
* Move the mouse to an edge. The indicated stress is 1, whereas it should be 2!
See the picture below, where the scale indicates a stress of 2 (the expected value), whereas the stress reported by "Hover points on" is 1.
If the order of the operation is deselect the first file, and then select the second one, the correct stress is reported in "Hover points on".
My Paraview version is the development one that was on master Yesterday, so just before it was forked to 5.8 RC1.
This issue seams to be related to this one https://gitlab.kitware.com/paraview/paraview/issues/19177 and https://gitlab.kitware.com/paraview/paraview/issues/18313 .
![HoverPointsOnBug](/uploads/fa3917be6412ea4f0f12e77363fdf904/HoverPointsOnBug.png)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/19573Wrong case for names in Catalyst script.2020-06-02T07:32:44-04:00W. Alan ScottWrong case for names in Catalyst script.Case of letters in the middle of script names is being changed to lowercase, thus killing our scripts. This is with the Catalyst Script exporter.
Here is how to replicate.
* 5.8.0-RC1, remote server (should break with builtin, but wil...Case of letters in the middle of script names is being changed to lowercase, thus killing our scripts. This is with the Catalyst Script exporter.
Here is how to replicate.
* 5.8.0-RC1, remote server (should break with builtin, but will be slower), Linux.
* Open Watney HiFire CGNS dataset. Only for speed, only open block blk-3 grid. Turn on no variables.
* Surface.
* Extract Subset With Seed.
* Place the cursor on the inside, concave section. "p". Now, your point is floating in space. For me, I need to move the Z in the possitive direction. I assume this is true. I moved 0.1 positive, now the seed is inside the dataset. Apply.
* View/ Export Inspector. Down where it says Data Extracts, we want Extract Subset With Seed. CSW Writer. Select the box right of there.
* Catalyst. Export Catalyst Script. Save it somewhere.
We will have a line that says:
extractSubsetWithSeed1 = ExtractSubsetWithSeed(Input=sparcvolumecgns144)
Then, we have a line that says:
cSVWriter1 = servermanager.writers.CSVWriter(Input=extractsubsetwithseed1)
Notice that the case of the first letter of Subset, With, and Seed has gone from upper to lower case.
This is a bug and is impacting Watney.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19572VCR Controls Broken with Temporal Collection XDMF File2020-01-15T11:43:13-05:00Joel KuleszaVCR Controls Broken with Temporal Collection XDMF File# Summary
**When a temporal-collection XDMF (version 2) file is loaded by ParaView, the "VCR Controls" at the top to navigate through time steps are disabled.**
However, the "Time Inspector," available from the "View" menu can be use...# Summary
**When a temporal-collection XDMF (version 2) file is loaded by ParaView, the "VCR Controls" at the top to navigate through time steps are disabled.**
However, the "Time Inspector," available from the "View" menu can be used to navigate through the time steps. Further, when "Save Animation..." is selected from the "File" menu, all of the frames export as expected (see attached screenshots).
Note: the LLNL VisIt utility can correctly load and display the attached test case.
Issue observed with ParaView 5.7.0 on macOS 10.14.6.
# Steps to Reproduce
1. Launch ParaView 5.7.0
2. File -> Open -> `vcr_breaker.xdmf`
3. Select `XDMF Reader` from the `Open Dataset` dialog. Click OK.
4. Click `Apply` to view the data set.
5. Change to the "Surface" representation of the `myquantity` array.
6. Rescale to data range over all timesteps to observe changes as time is traversed.
7. **Note that the VCR controls are unavailable.**
8. View -> Time Inspector.
9. **Note that the right-hand arrow buttons to navigate time step by index functions and permits traversing through time.**
CC: @patchett2002
[vcr_breaker.xdmf](/uploads/7b1192f25799f31cf6476a81cd0e2629/vcr_breaker.xdmf)
![testanim_0](/uploads/17fc2a24a9ab5b0ad31b753197181266/testanim_0.png)
![testanim_1](/uploads/6e3d6e14d8ae0438088ffbfb0fbe132b/testanim_1.png)
![testanim_2](/uploads/7da4f30be12fadb5d05c2f8faac93d48/testanim_2.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19569create infrastructure to provide longer term maintenance for older releases2022-12-20T15:08:51-05:00David E. DeMarlecreate infrastructure to provide longer term maintenance for older releasesWe should make it straightforward to backport important fixes to previously released versions of paraview and occasionally produce new patch releases. Institutional deployments of ParaView will benefit from this for example as they can q...We should make it straightforward to backport important fixes to previously released versions of paraview and occasionally produce new patch releases. Institutional deployments of ParaView will benefit from this for example as they can quickly overcome whatever features they come across rather than having to wait for the next release, which may have its own problems.
At a minimum we need public release-X branches and tags as well as a way to build one-off binaries for all three platforms. Ideally though ParaView's code review and merge, tagging, documentation and binary release processes will be extended to make it routine. Binary releases will likely require maintaining Linux, Mac and Windows systems (VMs/Docker Images or whatnot) that are consistent with the original build environment.