VTK issueshttps://gitlab.kitware.com/vtk/vtk/-/issues2016-08-12T06:39:46-04:00https://gitlab.kitware.com/vtk/vtk/-/issues/4069wxVTKRenderWindowInteractor mouse capturing logic breaks with multiple clicks2016-08-12T06:39:46-04:00Kitware RobotwxVTKRenderWindowInteractor mouse capturing logic breaks with multiple clicks**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4069). Further discussion may take place here.**
---
There's a problem in the mouse capturing logic of wxVTKRWI that you can trigger ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4069). Further discussion may take place here.**
---
There's a problem in the mouse capturing logic of wxVTKRWI that you can trigger with the following steps (easy to test with e.g. the wxVTKRenderWindowInteractor.py in Wrapping/Python/vtk/wx itself)
1) Press left mouse button to cause the object to rotate
2) While keeping the left mouse button pressed, press the right button. This will activate "continuous rotation"
3) Release both buttons
This will cause the mouse to remain captured to the render window. Even if you left click on the scene again, the rotation correctly stops, but the mouse remains captured.
It was very easy to fix this: instead of having a boolean flag _own_mouse for indicating whether it window has captured the mouse, make it a counter. So initialize it to zero, and when you CaptureMouse(), increase it by one and when you ReleaseMouse() , decrease it by one.https://gitlab.kitware.com/vtk/vtk/-/issues/4066The left-handed axes are not left-handed.2016-08-12T06:39:45-04:00Kitware RobotThe left-handed axes are not left-handed.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4066). Further discussion may take place here.**
---
In /Widgets/Testing/Cxx/TestOrientationMarkerWidget.cxx line 510.
This should b...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4066). Further discussion may take place here.**
---
In /Widgets/Testing/Cxx/TestOrientationMarkerWidget.cxx line 510.
This should be: transform->RotateY(180);
You need a reflection along one of the axes in order to change the handedness. A rotation of 90 will not do it but a rotation of 180 will.
You could also use transform->Scale(1,1,-1) but the colours will be all black. It seems that orientation of the normals is changed if this is done. (I think.)https://gitlab.kitware.com/vtk/vtk/-/issues/4058RepeatingTimer breaks TrackBall interaction2016-08-12T06:39:42-04:00Kitware RobotRepeatingTimer breaks TrackBall interaction**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4058). Further discussion may take place here.**
---
I just added a repeating timer to a Cone5 example and after a mouse interaction ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4058). Further discussion may take place here.**
---
I just added a repeating timer to a Cone5 example and after a mouse interaction IF THE MOUSE BUTTON IS NOT RELEASED there is some residual movement dependend on the frequency of the timer. Code is attached.https://gitlab.kitware.com/vtk/vtk/-/issues/4045Textures are unnecessarily reloaded2016-08-12T06:39:39-04:00Kitware RobotTextures are unnecessarily reloaded**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4045). Further discussion may take place here.**
---
vtkOpenGLTexture checks the MTime of it's associated RenderWindow when deciding ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4045). Further discussion may take place here.**
---
vtkOpenGLTexture checks the MTime of it's associated RenderWindow when deciding whether to reload a texture. The MTime gets updated on every mouse button and keyboard event, causing the texture to be reloaded every time. This may not be noticeable with small textures, but it becomes noticeable with either remove X rendering, or when using huge textures (I actually modified vtkOpenGLTexture and vtkPrimitivePainter to support 3D textures), as there is a slight delay whenever a mouse button is pushed or released, the mousewheel is used, or a key is pressed.
The mappers and painters don't check the MTime on the RenderWindow, they only check whether it's the same one they used previously. If there is any change in the state of RenderWindow which warrants a texture reload, I suggest checking for it explicitly, instead of reloading the texture over and over again for no good reason.https://gitlab.kitware.com/vtk/vtk/-/issues/4044STYLE: cout should be removed.2016-08-12T06:39:38-04:00Kitware RobotSTYLE: cout should be removed.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4044). Further discussion may take place here.**
---
//-------------------------------------------------------------------------
voi...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4044). Further discussion may take place here.**
---
//-------------------------------------------------------------------------
void vtkSeedWidget::DeleteAction(vtkAbstractWidget *w)
{
cout << "Delete action\n";
...
...https://gitlab.kitware.com/vtk/vtk/-/issues/4043win32 offscreen breaks ParaView3 GUI2016-08-12T06:39:38-04:00Kitware Robotwin32 offscreen breaks ParaView3 GUI**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4043). Further discussion may take place here.**
---
Trying to save an animation on Windows in ParaView3 causes problems.
With the...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4043). Further discussion may take place here.**
---
Trying to save an animation on Windows in ParaView3 causes problems.
With the first animation frame,
DestroyWindow() is called on a window that VTK didn't own in the first place.
From then on, VTK creates a new window that isn't embedded in the GUI anymore.
If it makes a difference, my virtualization environment doesn't have the extensions that are being queried to support hardware offscreen rendering. It appears that in either case, DestroyWindow() is called.https://gitlab.kitware.com/vtk/vtk/-/issues/4042Unable to allocate ... elements of size 8 bytes.2016-08-12T06:39:37-04:00Kitware RobotUnable to allocate ... elements of size 8 bytes.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4042). Further discussion may take place here.**
---
during the execution of my applications I obtain a segmentation fault, here belo...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4042). Further discussion may take place here.**
---
during the execution of my applications I obtain a segmentation fault, here below you are the error message:
ERROR: In /debian/stage/vtk-5.0.1/Common/vtkDataArrayTemplate.txx, line 255
vtkDoubleArray (0xd5e6068): Unable to allocate 100663290 elements of size 8 bytes.
.... see the attached file for a more detailed report
I'm using the vtk-5.0.1 version provided by debian, this error does not appends with vtk-4
Any suggestion?
thanks for any help.
A.https://gitlab.kitware.com/vtk/vtk/-/issues/4041bug in both vtkPlot3DReader.cxx and vtkMultiBlockPLOT3DReader.cxx2016-08-12T06:39:37-04:00Kitware Robotbug in both vtkPlot3DReader.cxx and vtkMultiBlockPLOT3DReader.cxx**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4041). Further discussion may take place here.**
---
There appears to be a bug in both vtkPlot3DReader.cxx and
vtkMultiBlockPLOT3DRe...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4041). Further discussion may take place here.**
---
There appears to be a bug in both vtkPlot3DReader.cxx and
vtkMultiBlockPLOT3DReader.cxx
The function "ReadQHeader" (in both files) does not properly
handle 2D geometries.
int vtkPLOT3DReader::ReadQHeader(FILE* fp)
{
int numGrid = this->GetNumberOfOutputsInternal(fp, 0);
vtkDebugMacro("Q number of grids: " << numGrid);
if ( numGrid == 0 )
{
return VTK_ERROR;
}
this->SkipByteCount(fp);
for(int i=0; i<numGrid; i++)
{
int ni, nj, nk;
this->ReadIntBlock(fp, 1, &ni);
this->ReadIntBlock(fp, 1, &nj);
this->ReadIntBlock(fp, 1, &nk);
The above incorrectly attempts to read "nk" whether the
data is 2D or 3D. The above should be changed to test
for the 2D case :
for(i=0; i<numGrid; i++)
{
int ni, nj, nk;
this->ReadIntBlock(fp, 1, &ni);
this->ReadIntBlock(fp, 1, &nj);
if (!this->TwoDimensionalGeometry)
{
this->ReadIntBlock(fp, 1, &nk);
}
else
{
nk = 1;
}
This is how it is correctly handled in the function
"ReadGeometryHeader".https://gitlab.kitware.com/vtk/vtk/-/issues/4024vtkInteractorStyle and vtkInteractorStyleImage can't be overidden in Java.2016-08-12T06:39:31-04:00Kitware RobotvtkInteractorStyle and vtkInteractorStyleImage can't be overidden in Java.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4024). Further discussion may take place here.**
---
My overrides of OnLeftButtonDown/Up() handlers don't get called in any of the tw...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4024). Further discussion may take place here.**
---
My overrides of OnLeftButtonDown/Up() handlers don't get called in any of the two classes in Java. There's no compile-/run-time error either.
The overrides get called without any problems in C++, though!
This is completely stopping me from proceeding ahead since September end! Using approximately 2006 Sep end snapshot of VTK.https://gitlab.kitware.com/vtk/vtk/-/issues/4019vtkCellDerivatives dereferences NULL pointer and crashes2016-08-12T06:39:29-04:00Kitware RobotvtkCellDerivatives dereferences NULL pointer and crashes**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4019). Further discussion may take place here.**
---
When I first tried to compute the vorticity of a velocity vector field using the...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4019). Further discussion may take place here.**
---
When I first tried to compute the vorticity of a velocity vector field using the vtkCellDerivatives filter, I got a segfault. If I'm reading <paraview_source>/VTK/Graphics/vtkCellDerivatives.cxx correctly, the block of code on lines 77-94 allocates storage for the computed vorticity vector field (outVectors) only if there is an input scalar array, even if VectorMode is set to COMPUTE_VORTICITY. So if I give the filter a vector field without a scalar field and ask for vorticity, it tries to write vorticity into the outVectors object, which is NULL, and it crashes. (line 193)https://gitlab.kitware.com/vtk/vtk/-/issues/4010installation of python modules ignores DESTDIR2016-08-12T06:39:26-04:00Kitware Robotinstallation of python modules ignores DESTDIR**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4010). Further discussion may take place here.**
---
When running 'make DESTDIR=&lt;...&gt; install', the python modules are installe...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4010). Further discussion may take place here.**
---
When running 'make DESTDIR=<...> install', the python modules are installed by setup.py, but PythonInstall.cmake runs a straight install into CMAKE_INSTALL_PREFIX. The rest of VTK is correctly installed relative to DESTDIR.https://gitlab.kitware.com/vtk/vtk/-/issues/4001vtk uses deprecated functions in its Carbon support, must remove2016-08-12T06:39:23-04:00Kitware Robotvtk uses deprecated functions in its Carbon support, must remove**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4001). Further discussion may take place here.**
---
vtk uses several deprecated APIs in vtkCarbonRenderWindow.cxx. They are:
New...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4001). Further discussion may take place here.**
---
vtk uses several deprecated APIs in vtkCarbonRenderWindow.cxx. They are:
NewRgn(), DiffRgn(), EqualRgn(), DisposeRgn()
This generates warnings on several build machines, such as:
http://www.vtk.org/Testing/Sites/atlantis.kitware/Darwin-i386-Xcode-Debug/20061030-0845-Experimental/BuildWarning.html
But this issue is bigger than simple compiler warnings.
These functions are deprecated, which means that they will eventually be removed from the OS.
Because of my NDA with Apple I cannot really say more, except that I suggest vtk stop using any and all deprecated APIs. :)https://gitlab.kitware.com/vtk/vtk/-/issues/4000Infinite loop in vtkGraphDFSIterator2016-08-12T06:39:23-04:00Kitware RobotInfinite loop in vtkGraphDFSIterator**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4000). Further discussion may take place here.**
---
With the attached script vtgGraphDFSIterator goes into an infinite loop after ha...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4000). Further discussion may take place here.**
---
With the attached script vtgGraphDFSIterator goes into an infinite loop after having traversed the first three nodes in the graph. For other start nodes (0,1) the iterator manage to traverse the entire graph.https://gitlab.kitware.com/vtk/vtk/-/issues/3999Z Buffer fighting2016-08-12T06:39:22-04:00Kitware RobotZ Buffer fighting**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3999). Further discussion may take place here.**
---
The VTKMapper setResolveCoincidentTopologyToShiftZBuffer and setResolveCoinciden...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3999). Further discussion may take place here.**
---
The VTKMapper setResolveCoincidentTopologyToShiftZBuffer and setResolveCoincidentTopologyToPolygonOffset functions does not seem to work correctly.https://gitlab.kitware.com/vtk/vtk/-/issues/3979Actors2D not magnified by vtkWindowToImageFilter-&gt;SetMagnification(), nor ...2016-08-12T06:39:16-04:00Kitware RobotActors2D not magnified by vtkWindowToImageFilter->SetMagnification(), nor by vtkRenderLargeImage**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3979). Further discussion may take place here.**
---
3D objects/actors are magnified correctly by the SetMagnification() method of vt...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3979). Further discussion may take place here.**
---
3D objects/actors are magnified correctly by the SetMagnification() method of vtkWindowToImageFilter.
But Actor2D objects are either not scaled (text and polydata), or scaled but
bizarrely placed and tiled (images).
vtkRenderLargeImage exhibits similar problems, with the exception that it magnifies image Actors2D correctly.
I posted an example test program in C++ that demonstrates the problem at http://public.kitware.com/pipermail/vtkusers/2006-September/087099.html
* The green test Actor2D image is placed and magnified correctly with
vtkRenderLargeImage, but the image is scaled correctly but misplaced, duplicated, and tiled using vtkWindowTo ImageFilter
* The red polyline Actor2D is rendered unmagnified by both vtkRenderLargeImage and by vtkWindowToImageFilter
* The text string Actor2D is rendered unmagnified by both vtkRenderLargeImage and by vtkWindowToImageFilter
* The 3D cone is rendered and magnified correctly in all situations tested
The test program generates two images: one unmagnified and one magnified. I compared the two images visually to draw these conclusions.https://gitlab.kitware.com/vtk/vtk/-/issues/3967Build failure: _XDisplay internals not visible2016-08-12T06:39:13-04:00Kitware RobotBuild failure: _XDisplay internals not visible**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3967). Further discussion may take place here.**
---
I'm building head of CVS as of this morning, on cygwin under Windows XP. I have...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3967). Further discussion may take place here.**
---
I'm building head of CVS as of this morning, on cygwin under Windows XP. I have xorg X11 packages installed:
cygcheck -c xorg-x11-devel
Cygwin Package Information
Package Version Status
xorg-x11-devel 6.8.99.901-1 OK
I configured with Tcl wrapping ON, and the build fails as follows:
[ 71%] Building CXX object Rendering/CMakeFiles/vtkRenderingTCL.dir/vtkTkRenderWidget.o
/tmp/local-build/VTK-cvs/Rendering/vtkTkRenderWidget.cxx: In function `LRESULT vtkTkRenderWidgetProc(HWND__*, UINT, WPARAM, LPARAM)':
/tmp/local-build/VTK-cvs/Rendering/vtkTkRenderWidget.cxx:836: error: invalid use of undefined type `struct _XDisplay'
/usr/include/X11/Xlib.h:289: error: forward declaration of `struct _XDisplay'
make[2]: *** [Rendering/CMakeFiles/vtkRenderingTCL.dir/vtkTkRenderWidget.o] Error 1
make[1]: *** [Rendering/CMakeFiles/vtkRenderingTCL.dir/all] Error 2
make: *** [all] Error 2
In the xorg header file X11/Xlib.h, we find:
/*
* Display datatype maintaining display specific data.
* The contents of this structure are implementation dependent.
* A Display should be treated as opaque by application code.
*/
#ifndef XLIB_ILLEGAL_ACCESS
typedef struct _XDisplay Display;
#endif
[...]
typedef struct
#ifdef XLIB_ILLEGAL_ACCESS
_XDisplay
#endif
{
[...]
So: you can only access internals of _XDisplay if XLIB_ILLEGAL_ACCESS is defined.
I defined that symbol and the build is proceeding. Perhaps the better solution is to see about getting the information required without poking around into X11 internals. I didn't attempt to do that.https://gitlab.kitware.com/vtk/vtk/-/issues/3965Upgrade vtkGL2PSExporter to include SVG output format2016-08-12T06:39:12-04:00Kitware RobotUpgrade vtkGL2PSExporter to include SVG output format**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3965). Further discussion may take place here.**
---
Upgrade VTK/Utilities/gl2ps to version 1.3.1 . It needs a small edit to include ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3965). Further discussion may take place here.**
---
Upgrade VTK/Utilities/gl2ps to version 1.3.1 . It needs a small edit to include the vtk_png lib (same as the vtk_zlib edit). Cmake file has to be changed to include the GL2PS_HAVE_PNG preprocessor definition.
I've included a patch for the changes to the vtk class.
The SVG output file can be viewed with Internet Explorer with Adobe's SVG plugin installed or Firefox 1.5. Inkscape has no problems editting the svg file either.
Firefox can't read a compressed svg from a local file system so compression should be switched off to output a pure ascii file. It's on be default.https://gitlab.kitware.com/vtk/vtk/-/issues/3953External package builds can not find VTK .cmake files2016-08-12T06:39:08-04:00Kitware RobotExternal package builds can not find VTK .cmake files**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3953). Further discussion may take place here.**
---
Several of the external installed ".cmake" files were placed in include/vtk-5.1 ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3953). Further discussion may take place here.**
---
Several of the external installed ".cmake" files were placed in include/vtk-5.1 instead of lib/vtk-5.1 and this broke the building of external applications (i.e. InsightApplications). I believe that the all .cmake files need to be installed in VTK_INSTALL_PACKAGE_DIR_CM24.
The following patch fixed the problem, and allowed cmake to find and build against the latest CVS version of vtk.
[hjohnson@nucleus VTK]$ cvs diff CMakeLists.txt
Index: CMakeLists.txt
===================================================================
RCS file: /cvsroot/VTK/VTK/CMakeLists.txt,v
retrieving revision 1.409
diff -r1.409 CMakeLists.txt
1249a1250
> ${VTK_CMAKE_DIR}/vtkMakeInstantiator.cmake
1256c1257
< DESTINATION ${VTK_INSTALL_PACKAGE_DIR_CM24}/CMake
---
> DESTINATION ${VTK_INSTALL_PACKAGE_DIR_CM24}/CMake
1463d1463
< ${VTK_CMAKE_DIR}/vtkMakeInstantiator.cmake
1492a1493,1504
> )
> IF(VTK_WRAP_HINTS)
> SET(__inst_files ${__inst_files} ${VTK_WRAP_HINTS})
> ENDIF(VTK_WRAP_HINTS)
> INSTALL(FILES ${__inst_files}
> DESTINATION ${VTK_INSTALL_INCLUDE_DIR_CM24}
> COMPONENT Development)
> ENDIF(NOT VTK_INSTALL_NO_DEVELOPMENT)
>
> # Save the compiler settings so another project can import them.
> IF(NOT VTK_INSTALL_NO_DEVELOPMENT)
> SET(__inst_files
1499c1511
< DESTINATION ${VTK_INSTALL_INCLUDE_DIR_CM24}
---
> DESTINATION ${VTK_INSTALL_PACKAGE_DIR_CM24}https://gitlab.kitware.com/vtk/vtk/-/issues/3941vtkImageData DeepCopy and ShallowCopy incomplete.2016-08-12T06:39:04-04:00Kitware RobotvtkImageData DeepCopy and ShallowCopy incomplete.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3941). Further discussion may take place here.**
---
vtkImageData::InternalImageDataCopy does not copy SPACING and ORIGIN pipeline in...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3941). Further discussion may take place here.**
---
vtkImageData::InternalImageDataCopy does not copy SPACING and ORIGIN pipeline information entries. These entries should be copied as other enties (e.g. WHOLE_EXTENT) are in the vtkDataObject subclass method.https://gitlab.kitware.com/vtk/vtk/-/issues/3939QVTKWidget crashes on certain keys2016-08-12T06:39:04-04:00Kitware RobotQVTKWidget crashes on certain keys**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3939). Further discussion may take place here.**
---
Pressing keys like 'ä' or 'ß' (on a german keyboard) causes an immediate crash. ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3939). Further discussion may take place here.**
---
Pressing keys like 'ä' or 'ß' (on a german keyboard) causes an immediate crash.
The problem is in QVTKWidget::keyPressEvent(), keyReleaseEvent():
int ascii_key = event->text().length() ? event->text().unicode()->toLatin1() : 0;
toLatin1() is negative for keys like 'ä' or 'ß' and therefore using ascii_key directly as array index results in a crash.
I'm using qt 4.1.4 open source.