ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-11-09T17:16:45-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/20963texture warnings on save/ load state2021-11-09T17:16:45-05:00W. Alan Scotttexture warnings on save/ load stateWe have an unacceptable number of texture warnings when saving then loading state. Here is how to replicate:
* nightly 5.9.1-1808-gdb1698b0d4, MacOS, builtin server.
* Reset to Default Settings
* File/ Open/ Examples/ can.exo. Apply.
*...We have an unacceptable number of texture warnings when saving then loading state. Here is how to replicate:
* nightly 5.9.1-1808-gdb1698b0d4, MacOS, builtin server.
* Reset to Default Settings
* File/ Open/ Examples/ can.exo. Apply.
* File/ Save State.
* Reset Session.
* File Load State.
We get the following, maybe 100 or so times:
ERROR: In /opt/glr/paraview/paraview-ci/source-paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 668
vtkPVCompositeDataPipeline (0x6000011d42a0): Input port 0 of algorithm vtkOpenGLTexture(0x7fc60792ff00) has 0 connections but is not optional.
ERROR: In /opt/glr/paraview/paraview-ci/source-paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 668
vtkPVCompositeDataPipeline (0x600001191c00): Input port 0 of algorithm vtkOpenGLTexture(0x7fc624061790) has 0 connections but is not optional.
ERROR: In /opt/glr/paraview/paraview-ci/source-paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 668
vtkPVCompositeDataPipeline (0x6000011d4000): Input port 0 of algorithm vtkOpenGLTexture(0x7fc607937f30) has 0 connections but is not optional.
Really should be fixed in 5.10.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/22259Texture with `.jpeg` extension generates error2023-09-12T21:32:46-04:00Francois MazenTexture with `.jpeg` extension generates errorThe `.jpeg` extension is not supported by ParaView for a texture, whereas the file is the same as with `.jpg` extension.
To reproduce with ParaView 5.11.1:
- Load a dataset with texture coordinates (for example [this one](https://skfb.l...The `.jpeg` extension is not supported by ParaView for a texture, whereas the file is the same as with `.jpg` extension.
To reproduce with ParaView 5.11.1:
- Load a dataset with texture coordinates (for example [this one](https://skfb.ly/CXO6))
- In the Display properties tab click the Texture combo box and select "Load..."
- select the `All files (*)` filter and load a file with a jpeg extension
- Error:
```
ERROR: In vtkNetworkImageSource.cxx, line 147
vtkNetworkImageSource (0x23f6c470): Unknown texture file extension: /home/francois/Documents/Demos_HPC/mining/mining_quarry/textures/Material_0_baseColor.jpeg
ERROR: In vtkOpenGLTexture.cxx, line 206
vtkOpenGLTexture (0x16f69240): No scalar values found for texture input!
```
(the second error is then repeated in a loop and it fills the Output Messages dialog)https://gitlab.kitware.com/paraview/paraview/-/issues/19462texturemaptocylinder always removes seam (5.6.x)2020-01-15T21:20:38-05:00Paul Ferrelltexturemaptocylinder always removes seam (5.6.x) - Create a cylinder.
- Increase it's resolution to something less blocky (20 works)
- Apply a the 'texturemaptocylinder' filter with an appropriate image. (An earth map works well).
- Uncheck 'prevent seam'.
The image will display ... - Create a cylinder.
- Increase it's resolution to something less blocky (20 works)
- Apply a the 'texturemaptocylinder' filter with an appropriate image. (An earth map works well).
- Uncheck 'prevent seam'.
The image will display on half the cylinder, and then repeat on the other half inverted as should only happen with seam prevention.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/14608TextureMaPToPlane doesn't seem to work with slice.2023-08-01T11:29:33-04:00Kitware RobotTextureMaPToPlane doesn't seem to work with slice.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14608). Further discussion may take place here.**
---
TextureMapToPlane doesn't work on slices. This should be fixed.
Local se...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14608). Further discussion may take place here.**
---
TextureMapToPlane doesn't work on slices. This should be fixed.
Local server, Linux, 4.1.0.
Wavelet. Apply.
Slice. Z Normal. Apply.
TextureMapToPlane. Apply.
Now, texture by a picture. I used frame 4 of the can.0004.png movie.
You never see a texture appear. This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/15416TextureMapToSphere problem2020-05-25T19:44:37-04:00Kitware RobotTextureMapToSphere problem**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15416). Further discussion may take place here.**
---
I have a "ghost wrapped image" at the seam when I apply a texture to a sph...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15416). Further discussion may take place here.**
---
I have a "ghost wrapped image" at the seam when I apply a texture to a sphere source.
The option "Present Seam" solves this but makes the texture mirrored.https://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/10405TextureMapToSphere is not multiple server aware2020-01-07T22:55:40-05:00Kitware RobotTextureMapToSphere is not multiple server aware**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10405). Further discussion may take place here.**
---
I have a user that wants to map the world to a sphere.
ParaView 3.6.2, XP...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10405). Further discussion may take place here.**
---
I have a user that wants to map the world to a sphere.
ParaView 3.6.2, XP, 4 remote servers.
* Sources/ SuperQuadric. Theta resolution == 128. Phi Resolution = 128.
* Turn off Toroidal.
* Apply.
* Filters/ Alphabetical/ TextureMapToSphere.
* Turn off Prevent Seam.
* Color by Texture Coords.
* Notice that the colors have zones, but should actually smoothly wrap around the sphere.
https://gitlab.kitware.com/paraview/paraview/-/issues/19461TextureMapToSphere is not multiple server aware (again), 5.6.x2020-02-04T11:30:57-05:00Paul FerrellTextureMapToSphere is not multiple server aware (again), 5.6.xThere seems to be a regression of #10405. The steps in that ticket ca be followed to reproduce. Everything looks fine on the client alone, but when using pvserver with more than one proc/node, each node applies the texture starting from ...There seems to be a regression of #10405. The steps in that ticket ca be followed to reproduce. Everything looks fine on the client alone, but when using pvserver with more than one proc/node, each node applies the texture starting from the same offset to it's portion of the sphere.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/10391TextureMapToSphere is wrong or needs more options2019-03-05T10:40:11-05:00Kitware RobotTextureMapToSphere is wrong or needs more options**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10391). Further discussion may take place here.**
---
I have a user that wants to map the world to a sphere.
ParaView 3.6.2, XP...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10391). Further discussion may take place here.**
---
I have a user that wants to map the world to a sphere.
ParaView 3.6.2, XP, local server.
Sources/ Sphere. Theta resolution == 128. Phi Resolution = 128.
Filters/ Alphabetical/ TextureMapToSphere.
Use the world map, found at http://www.oera.net/How2/PlanetTexs/EarthMap_2500x1250.jpg. (Enter this on the Display tab)
Notice that u of the u,v pair, goes from 0-1, then 1-0. Shouldn't it go from 0-1 (i.e., u==0 at degrees == 0, u == 0.5 at degrees == 180, and u = 1.0 at degrees = 360)? Either this is a bug, or a feature that should be added.
https://gitlab.kitware.com/paraview/paraview/-/issues/10406TextureMapToSphere prevent seam is wrong2019-03-05T10:40:11-05:00Kitware RobotTextureMapToSphere prevent seam is wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10406). Further discussion may take place here.**
---
As per Greenfield, our TextureMapToSphere "Prevent Seam" is wrong. What i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10406). Further discussion may take place here.**
---
As per Greenfield, our TextureMapToSphere "Prevent Seam" is wrong. What it tries to do is draw the texture on the sphere twice. What it should do is draw the texture on the sphere, then CONTINUE to draw it one more time around. That way, if there are minor holes, the second draw of the texture will catch it.
A good test texture is here: Use the world map, found at http://www.oera.net/How2/PlanetTexs/EarthMap_2500x1250.jpghttps://gitlab.kitware.com/paraview/paraview/-/issues/19066Textures are unsupported in pvcrs mode2019-09-17T03:17:33-04:00Mathieu Westphal (Kitware)Textures are unsupported in pvcrs modeLoading a texture in pvcrs mode always results in a segfault :
Steps to reproduce :
* run pvrenderserver
* run pvdataserver
* run ParaView, connect to render and data server
* Background -> Image -> Load -> any png file -> ass...Loading a texture in pvcrs mode always results in a segfault :
Steps to reproduce :
* run pvrenderserver
* run pvdataserver
* run ParaView, connect to render and data server
* Background -> Image -> Load -> any png file -> assert
`pvdataserver: /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyProperty.cxx:242: bool vtkSIProxyProperty::IsValidNull(vtkTypeUInt32): Assertion "SIProxy shouldn't be null otherwise it's a Proxy location issue in the XML" && siProxy != 0' failed.`
The backtrace is as follows :
```
Thread 1 "pvdataserver" received signal SIGABRT, Aborted.
0x00007ffff7e0582f in raise () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007ffff7e0582f in raise () from /usr/lib/libc.so.6
#1 0x00007ffff7df0672 in abort () from /usr/lib/libc.so.6
#2 0x00007ffff7df0548 in __assert_fail_base.cold.0 () from /usr/lib/libc.so.6
#3 0x00007ffff7dfddb6 in __assert_fail () from /usr/lib/libc.so.6
#4 0x00007ffff6659607 in vtkSIProxyProperty::IsValidNull (this=0x555556576ce0, globalId=8844)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyProperty.cxx:241
#5 0x00007ffff665903d in vtkSIProxyProperty::Push (this=0x555556576ce0, message=0x7fffffffd7c0, offset=0)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyProperty.cxx:178
#6 0x00007ffff6640de9 in vtkSIProxy::Push (this=0x55555645f450, message=0x7fffffffd7c0)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx:153
#7 0x00007ffff660d09e in vtkPVSessionCore::PushStateInternal (this=0x55555573bf40, message=0x7fffffffd7c0)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:465
#8 0x00007ffff660d335 in vtkPVSessionCore::PushState (this=0x55555573bf40, message=0x7fffffffd7c0)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:504
#9 0x00007ffff660a05d in vtkPVSessionBase::PushState (this=0x555555752150, msg=0x7fffffffd7c0)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:140
#10 0x00007ffff661b006 in vtkPVSessionServer::OnClientServerMessageRMI (this=0x555555752150, message=0x55555657b440, message_length=47)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkPVSessionServer.cxx:550
#11 0x00007ffff6619fa8 in (anonymous namespace)::RMICallback (localArg=0x555555752150, remoteArg=0x55555657b440, remoteArgLength=47)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ServerImplementation/Core/vtkPVSessionServer.cxx:56
#12 0x00007ffff4b363ac in vtkMultiProcessController::ProcessRMI (this=0x555555814b20, remoteProcessId=1, arg=0x55555657b440, argLength=47, rmiTag=55625)
at /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Parallel/Core/vtkMultiProcessController.cxx:767
#13 0x00007ffff4b35fa5 in vtkMultiProcessController::ProcessRMIs (this=0x555555814b20, reportErrors=0, dont_loop=1)
at /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Parallel/Core/vtkMultiProcessController.cxx:715
#14 0x00007ffff6522b1c in vtkTCPNetworkAccessManager::ProcessEventsInternal (this=0x5555557499a0, timeout_msecs=0, do_processing=true)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx:288
#15 0x00007ffff6522622 in vtkTCPNetworkAccessManager::ProcessEvents (this=0x5555557499a0, timeout_msecs=0)
at /home/glow/work/paraview/paraviewSecondary/paraview/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx:188
#16 0x00005555555565ec in RealMain (argc=1, argv=0x7fffffffe9f8, type=vtkProcessModule::PROCESS_DATA_SERVER)
at /home/glow/work/paraview/paraviewSecondary/paraview/CommandLineExecutables/pvserver_common.h:89
#17 0x00005555555566c2 in main (argc=1, argv=0x7fffffffe9f8) at /home/glow/work/paraview/paraviewSecondary/paraview/CommandLineExecutables/pvdataserver.cxx:21
```https://gitlab.kitware.com/paraview/paraview/-/issues/13640The "Show" button should not be enable when no data is available for the scal...2018-08-23T15:16:46-04:00Kitware RobotThe "Show" button should not be enable when no data is available for the scalarbar**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13640). Further discussion may take place here.**
---
To reproduce the bug do:
> Create Cone source + Apply
> Then in the pr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13640). Further discussion may take place here.**
---
To reproduce the bug do:
> Create Cone source + Apply
> Then in the property panel, click on the "Show" button in order to show the scalar bar.
If you notice, in the toolbar, the same button is disable but not here... This lead to an error message.https://gitlab.kitware.com/paraview/paraview/-/issues/7091The attached ensight file causes an infinite loop2019-03-05T10:45:01-05:00Kitware RobotThe attached ensight file causes an infinite loop**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=7091). Further discussion may take place here.**
---
This file causes the ensight reader to into infinite loop. Note that this f...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=7091). Further discussion may take place here.**
---
This file causes the ensight reader to into infinite loop. Note that this file is wrong: it says it has 1 time step but it lists a few time values.https://gitlab.kitware.com/paraview/paraview/-/issues/4867The camera should be reset if a lookmark is loaded in a view with no displays...2019-03-05T10:49:15-05:00Kitware RobotThe camera should be reset if a lookmark is loaded in a view with no displays visible**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4867). Further discussion may take place here.**
---
...but only if we're not using the lookmark state's camera settings.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4867). Further discussion may take place here.**
---
...but only if we're not using the lookmark state's camera settings.https://gitlab.kitware.com/paraview/paraview/-/issues/19245The cell data to point data and point data to cell data filters should pass f...2019-08-15T22:30:28-04:00Andrew BauerThe cell data to point data and point data to cell data filters should pass field dataThe cell data to point data and point data to cell data filters should pass field data
Steps to reproduce:
1. Load [pointdatawithfielddata.vti](/uploads/f0473e3dd7a9d4d02d9d28aa37097d6d/pointdatawithfielddata.vti)
2. Use the `Point Data...The cell data to point data and point data to cell data filters should pass field data
Steps to reproduce:
1. Load [pointdatawithfielddata.vti](/uploads/f0473e3dd7a9d4d02d9d28aa37097d6d/pointdatawithfielddata.vti)
2. Use the `Point Data to Cell Data` filter
3. The `dog` field data array is no longer available to the output of the `Point Data to Cell Data` filter
A VTK fix is at https://gitlab.kitware.com/vtk/vtk/merge_requests/5844
@cory.quammen @utkarsh.ayachit could we get this into ParaView 5.7? I consider this a bug.5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/11709The close button does not terminate the paraview process during animation.2019-03-05T10:38:23-05:00Kitware RobotThe close button does not terminate the paraview process during animation.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11709). Further discussion may take place here.**
---
When I pressed the close button at the top-right of the window while anima...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11709). Further discussion may take place here.**
---
When I pressed the close button at the top-right of the window while animation
was playing, the gui application was terminated but its process was still
running.
If paraview was playing an animation loop when the button was pressed,
the process continued running until I killed it manually.
When I used the‘EXIT’in the Edit menu, both the gui application and
the process were terminated normally.
This problem occurred on both linux and windows.https://gitlab.kitware.com/paraview/paraview/-/issues/9563The CMake file for StreamingParaview doesn't work with DESTDIR under Linux in...2019-03-05T10:41:30-05:00Kitware RobotThe CMake file for StreamingParaview doesn't work with DESTDIR under Linux in copying the QT libraries**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9563). Further discussion may take place here.**
---
Do a "make install" with "DESTDIR" set and you will get many tar "Cannot ch...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9563). Further discussion may take place here.**
---
Do a "make install" with "DESTDIR" set and you will get many tar "Cannot chdir: No such file or directory" error messages when it tries to copy the various QT libraries over for StreamingParaview. The problem is in the following code in Applications/StreamingParaView/CMakeLists.txt which doesn't take DESTDIR into account
IF(NOT Q_WS_MAC)
FOREACH(qtlib ${QTLIBLIST})
IF (NOT WIN32)
#INSTALL(FILES ${QT_${qtlib}_LIBRARY_RELEASE} DESTINATION ${PV_INSTALL_LIB_DIR})
GET_FILENAME_COMPONENT(QT_LIB_DIR_tmp ${QT_${qtlib}_LIBRARY_RELEASE} PATH)
GET_FILENAME_COMPONENT(QT_LIB_NAME_tmp ${QT_${qtlib}_LIBRARY_RELEASE} NAME)
FILE(GLOB QT_LIB_LIST RELATIVE ${QT_LIB_DIR_tmp} "${QT_${qtlib}_LIBRARY_RELEASE}*")
INSTALL(CODE "
MESSAGE(STATUS \"Installing \${CMAKE_INSTALL_PREFIX}/${PV_INSTALL_LIB_DIR}/${QT_LIB_NAME_tmp}\")
EXECUTE_PROCESS (WORKING_DIRECTORY ${QT_LIB_DIR_tmp}
COMMAND tar c ${QT_LIB_LIST}
COMMAND tar -xC \${CMAKE_INSTALL_PREFIX}/${PV_INSTALL_LIB_DIR})
" COMPONENT Runtime)
ELSE (NOT WIN32)
GET_FILENAME_COMPONENT(QT_DLL_PATH_tmp ${QT_QMAKE_EXECUTABLE} PATH)
INSTALL(FILES ${QT_DLL_PATH_tmp}/${qtlib}4.dll DESTINATION ${PV_INSTALL_BIN_DIR} COMPONENT Runtime)
ENDIF (NOT WIN32)
ENDFOREACH(qtlib)
ENDIF(NOT Q_WS_MAC)
Note that the installation is not killed though, so you have to capture the output if you wish to see this error. Actually, I'm not sure I understand why we want a personal copy of these libraries in this case in the first place. Why not just use them as is?https://gitlab.kitware.com/paraview/paraview/-/issues/4900The color preset preview does not look right when using wrapped HSV2019-03-05T10:49:08-05:00Kitware RobotThe color preset preview does not look right when using wrapped HSV**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4900). Further discussion may take place here.**
---
The color preset dialog shows a preview of the color gradient. The preview ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4900). Further discussion may take place here.**
---
The color preset dialog shows a preview of the color gradient. The preview does not look right when using wrapped hsv space. The preview is identical to hsv space.https://gitlab.kitware.com/paraview/paraview/-/issues/17955The coprocess API is a bit clunky2021-03-29T20:24:51-04:00olesenThe coprocess API is a bit clunky@acbauer
There are a number of places where things could be made a little smoother, but I don't know what can be changed without totally breaking the API (your discretion).
They mostly basic handling:
- seems silly to pass all of string...@acbauer
There are a number of places where things could be made a little smoother, but I don't know what can be changed without totally breaking the API (your discretion).
They mostly basic handling:
- seems silly to pass all of string as `const char*` when the internals convert them back to a string for the mapping
- where appropriate, we could have some non-void return values - to reduce duplicate calling
Here's a small wish-list to start:
- vtkCPDataDescription
/// Add names for grids produced by the simulation. This allocates a new
/// vtkCPInputDataDescription for that grid, if a grid by that name does not
/// already exist.
/// NOTE currently no guard against null or empty values
/// \return pointer to new or existing input description
vtkCPInputDataDescription* AddInput(const char* gridName);
vtkCPInputDataDescription* AddInput(const std::string& gridName);
/// Returns true if the grid is necessary, given the grid's name.
bool GetIfGridIsNecessary(const char*) CONST;
bool GetIfGridIsNecessary(const std::string& gridName) CONST;
/// Returns true if any of the grids is necessary.
bool GetIfAnyGridNecessary() CONST;
I used CONST to highlight a few places where const methods might be possible.
After the changes, it only saves a few lines, but IMO is considerably less ugly.
Eg,
Simply
vtkNew<vtkCPDataDescription> descrip;
vtkCPInputDataDescription* cpInput = descrip->AddInput("input");
Or
const std::string inputName = "input";
vtkNew<vtkCPDataDescription> descrip;
vtkCPInputDataDescription* cpInput = descrip->AddInput(inputName);
Instead of this
const std::string inputName = "input";
vtkNew<vtkCPDataDescription> descrip;
descrip->AddInput(inputName.c_str());
vtkCPInputDataDescription* cpInput = descrip->GetInputDescriptionByName(inputName.c_str());https://gitlab.kitware.com/paraview/paraview/-/issues/14032The CoProcessingTestInput test is not working properly2018-08-08T22:26:35-04:00Kitware RobotThe CoProcessingTestInput test is not working properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14032). Further discussion may take place here.**
---
The test should currently be failing but isn't because it just gives a war...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14032). Further discussion may take place here.**
---
The test should currently be failing but isn't because it just gives a warning that something is wrong.