VTK issueshttps://gitlab.kitware.com/vtk/vtk/-/issues2016-08-12T06:50:50-04:00https://gitlab.kitware.com/vtk/vtk/-/issues/6204vtkWrapPython produced a segfault while wrapping2016-08-12T06:50:50-04:00Kitware RobotvtkWrapPython produced a segfault while wrapping**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6204). Further discussion may take place here.**
---
vtkWrapPython produced a segfault while wrapping class vtkTriCubicHexahedron
(t...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6204). Further discussion may take place here.**
---
vtkWrapPython produced a segfault while wrapping class vtkTriCubicHexahedron
(this class is not yet an official component of vtk, it's in the wish list).
Patch:
Index: vtkWrapPython.c
===================================================================
RCS file: /cvsroot/VTK/VTK/Wrapping/vtkWrapPython.c,v
retrieving revision 1.84
diff -u -r1.84 vtkWrapPython.c
--- vtkWrapPython.c 11 Apr 2007 18:11:10 -0000 1.84
+++ vtkWrapPython.c 27 Dec 2007 13:15:45 -0000
@@ -381,7 +381,8 @@
char *get_format_string()
{
- static char result[1024];
+ static char result[10240];//Soeren Gebbert 27.12.2007 this field must be enlarged to process the vtkTriCubicHexahedron class
+
int currPos = 0;
int argtype;
int i, j;
@@ -501,7 +502,7 @@
void get_python_signature()
{
- static char result[1024];
+ static char result[10240]; //Soeren Gebbert 27.12.2007 this field must be enlarged to process the vtkTriCubicHexahedron class
int currPos = 0;
int argtype;
int i, j;https://gitlab.kitware.com/vtk/vtk/-/issues/6202vtkProjectedTexture documentation correction2016-08-12T06:50:49-04:00Kitware RobotvtkProjectedTexture documentation correction**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6202). Further discussion may take place here.**
---
Some of the methods in vtkProjectedTexture are not displayed in the auto-generat...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6202). Further discussion may take place here.**
---
Some of the methods in vtkProjectedTexture are not displayed in the auto-generated doxygen.
I've also added a couple more lines to the description of SetAspectRatio; feel free to ignore it if you consider that to be too detailed.
Unified diff attached.https://gitlab.kitware.com/vtk/vtk/-/issues/6194Segfault with python and vtk3dwidgets2016-08-12T06:50:47-04:00Kitware RobotSegfault with python and vtk3dwidgets**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6194). Further discussion may take place here.**
---
I'm getting a segfault when I use a 3dwidget and don't keep a (python) referen...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6194). Further discussion may take place here.**
---
I'm getting a segfault when I use a 3dwidget and don't keep a (python) reference on it.
https://gitlab.kitware.com/vtk/vtk/-/issues/6186Problems installing VTK on Visual Studio C++ 2008, ( windoes xp Home edtion)2016-08-12T06:50:44-04:00Kitware RobotProblems installing VTK on Visual Studio C++ 2008, ( windoes xp Home edtion)**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6186). Further discussion may take place here.**
---
Please any one can help how to setup VTK/CMAKE on Visual Studio C++ 2008.
The f...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6186). Further discussion may take place here.**
---
Please any one can help how to setup VTK/CMAKE on Visual Studio C++ 2008.
The fllowing log a building error I got.
Best regards
Pedro
C:\Documents and Settings\User.BICHOHOME\test\src\VTK\Filtering\vtkImageData.h(27) : fatal error C1083: Cannot open include file: 'vtkStructuredData.h': No such file or directory
vtkAbstractPropPicker.cxxhttps://gitlab.kitware.com/vtk/vtk/-/issues/6154X error when undocking a QDockWidget which contains a QVTKWidget2016-08-12T06:50:35-04:00Kitware RobotX error when undocking a QDockWidget which contains a QVTKWidget**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6154). Further discussion may take place here.**
---
Putting a QVTKWidget into a QDockWidget works fine, as long as this QDockWidget ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6154). Further discussion may take place here.**
---
Putting a QVTKWidget into a QDockWidget works fine, as long as this QDockWidget does not get undocked. Undocking it causes an X error "BadWindow":
-------------
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 3 (X_GetWindowAttributes)
Resource id: 0x4a0001e
-------------
Followed by a couple of further error messages:
-------------
X Error: GLXBadCurrentWindow 159
Extension: 149 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x4a0001e
-------------
with different Minor opcode's.
If the application has more than one QVTKWidget, none of these widgets is working anymore - no matter which parent widget it is contained in.https://gitlab.kitware.com/vtk/vtk/-/issues/6119vtkCellLinks::DeepCopy causes memory corruption2016-08-12T06:50:24-04:00Kitware RobotvtkCellLinks::DeepCopy causes memory corruption**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6119). Further discussion may take place here.**
---
if you copy a vtkCellLinks (which happens if you DeepCopy a vtkUnstructuredGrid ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6119). Further discussion may take place here.**
---
if you copy a vtkCellLinks (which happens if you DeepCopy a vtkUnstructuredGrid after calling BuildLinks) the internal table of pointers is copied but the pointers all point to locally allocated data. The result is that when you delete the vtkCellLinks instances they double-free the local data.https://gitlab.kitware.com/vtk/vtk/-/issues/6118vtkCellLinks leak in vtkUnstructuredGrid::BuildLinks2016-08-12T06:50:24-04:00Kitware RobotvtkCellLinks leak in vtkUnstructuredGrid::BuildLinks**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6118). Further discussion may take place here.**
---
If you call vtkUnstructuredGrid::BuildLinks more than once, a new vtkCellLinks (...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6118). Further discussion may take place here.**
---
If you call vtkUnstructuredGrid::BuildLinks more than once, a new vtkCellLinks (this->Links) is created each time but the old one is not deleted so it leaks.https://gitlab.kitware.com/vtk/vtk/-/issues/6115Memory leak in vtkFixedPointVolumeRayCastMapper.cxx2016-08-12T06:50:22-04:00Kitware RobotMemory leak in vtkFixedPointVolumeRayCastMapper.cxx**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6115). Further discussion may take place here.**
---
In vtkFixedPointVolumeRayCastMapper.cxx function vtkFixedPointVolumeRayCastMappe...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6115). Further discussion may take place here.**
---
In vtkFixedPointVolumeRayCastMapper.cxx function vtkFixedPointVolumeRayCastMapperComputeCS1CGradients() is an memory leak in the line 212. Three buffers are allocated (dxBuffer, dyBuffer, dzBuffer) but no of them is freed.https://gitlab.kitware.com/vtk/vtk/-/issues/6092vtkThreshold does not allow custom points datatype2016-08-12T06:50:15-04:00Kitware RobotvtkThreshold does not allow custom points datatype**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6092). Further discussion may take place here.**
---
vtkThreshold always output points in float format. In vtkThreshold.cxx (5.0.3) i...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6092). Further discussion may take place here.**
---
vtkThreshold always output points in float format. In vtkThreshold.cxx (5.0.3) in RequestData there is a local variable vtkPoints* newPoints. This defaults to float and being a local variable does not allow any customization. Either this variable should be made a public member, or better, a vtkThreshold::SetDataType method should be provided.https://gitlab.kitware.com/vtk/vtk/-/issues/6017vtkRungeKutta4 is leaking / wrong logic in vtkInitialValueProblemSolver::Init...2016-08-12T06:49:50-04:00Kitware RobotvtkRungeKutta4 is leaking / wrong logic in vtkInitialValueProblemSolver::Initialize**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6017). Further discussion may take place here.**
---
Following code is showing leak:
#include "vtkRungeKutta4.h"
#include "vtkGen...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6017). Further discussion may take place here.**
---
Following code is showing leak:
#include "vtkRungeKutta4.h"
#include "vtkGenericInterpolatedVelocityField.h"
#include "vtkInterpolatedVelocityField.h"
int main()
{
vtkRungeKutta4 *ivps = vtkRungeKutta4::New();
vtkInitialValueProblemSolver *fs1 = vtkInterpolatedVelocityField::New();
vtkGenericInterpolatedVelocityField *fs2 = vtkGenericInterpolatedVelocityField::New();
ivps->SetFunctionSet( fs1 );
ivps->SetFunctionSet( fs2 );
fs1->Delete();
fs2->Delete();
ivps->Delete();
return 0;
}
Summary:
void vtkInitialValueProblemSolver::SetFunctionSet(vtkFunctionSet* fset) does not properly reset this->Vals and this->Derivs
Same conclusion for vtkRungeKutta4 / this->NextDerivshttps://gitlab.kitware.com/vtk/vtk/-/issues/6008vtkTimeStamp & itkTimeStamp atomic increment optimisation and cleanup patch2016-08-12T06:49:47-04:00Kitware RobotvtkTimeStamp & itkTimeStamp atomic increment optimisation and cleanup patch**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6008). Further discussion may take place here.**
---
After profiling our application, we discovered that significant time is spent in...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6008). Further discussion may take place here.**
---
After profiling our application, we discovered that significant time is spent in vtkTimeStamp::Modified(). Time was lost because a mutex was being taken to safely increment an integer. A mutex is a fairly expensive construct. A Windows-only optimisation exists in the code that uses the InterlockedIncrement() API to atomically increment the number without the need for a mutex. Mac OS X has a similar API.
This patch:
- makes the analogous optimisation on Mac OS (10.4 and later only) in both vtk and itk
- adds the Windows optimisation to the ITK version of TimeStamp
- changed the return type of operator> and operator< from int to bool
- other misc changes to make the two classes less divergent (added consts, etc.)
I have been using this code for weeks now on Mac OS X 10.5 in both 32 and 64 bit, and it seems just fine. I have not tested on other OSes however.
I could commit this myself, but I would appreciate someone review the changes first.https://gitlab.kitware.com/vtk/vtk/-/issues/6004Keyboard event handling in new style widgets is horribly broken.2016-08-12T06:49:46-04:00Kitware RobotKeyboard event handling in new style widgets is horribly broken.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6004). Further discussion may take place here.**
---
There is a major issue with the handling of keyboard events in the new style wid...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=6004). Further discussion may take place here.**
---
There is a major issue with the handling of keyboard events in the new style widgets. Apparently it is assumed that providing a KeySym string to the callback mapper which is set to NULL will cause the event translator to only compare the provided key code to the key code of an event, and ignore the KeySym string/character.
This assumption fails when various control keys (such as ctrl or shift) are pressed: these keys return a keycode value of 0. The vtkEvent::operator==() method will not compare keycodes if either of the events has a keycode 0 (the keypress has this keycode), it will not compare keysyms if either is NULL (the widget set it to NULL), and as a result the comparison will return 1, and the widget will receive a keypress event, even though the key which was pressed was not the one that the widget wanted.
Another issue with the key handling is in vtkAbstractWidget::ProcessEventsHandler(). The comparison (modifier == vtkEvent::AnyModifier) will always be false, because the previously called vtkEvent::GetModifier() never returns the value vtkEvent::AnyModifier. The part where first event translations which want vtkEvent::NoModifier are checked, and then the ones that want vtkEvent::AnyModifier never gets executed.
https://gitlab.kitware.com/vtk/vtk/-/issues/5989VTK nightly fails to build with mingw 5.1.32016-08-12T06:49:41-04:00Kitware RobotVTK nightly fails to build with mingw 5.1.3**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5989). Further discussion may take place here.**
---
On nightly, after creating a mingw makefile with cmake 2.4.7, did a
c:\MinGW\bi...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5989). Further discussion may take place here.**
---
On nightly, after creating a mingw makefile with cmake 2.4.7, did a
c:\MinGW\bin\mingw32-make.exe
At 18%, got the following error:
[ 18%] Building CXX object Common/CMakeFiles/vtkCommonPythonD.dir/vtkInformation
Python.obj
In file included from C:\VTK\bin\Common\vtkInformationPython.cxx:10:
C:/VTK/Common/vtkInformation.h:285: error: function `void vtkInformation::SetReq
uest(vtkInformationRequestKey*)' definition is marked dllimport.
C:/VTK/Common/vtkInformation.h:286: error: function `vtkInformationRequestKey* v
tkInformation::GetRequest()' definition is marked dllimport.
mingw32-make.exe[2]: *** [Common/CMakeFiles/vtkCommonPythonD.dir/vtkInformationP
ython.obj] Error 1
mingw32-make.exe[1]: *** [Common/CMakeFiles/vtkCommonPythonD.dir/all] Error 2
c:\MinGW\bin\mingw32-make.exe: *** [all] Error 2https://gitlab.kitware.com/vtk/vtk/-/issues/5980CreateAWindow calls itself in vtkCocoaRenderWindow if not rendered.2016-08-12T06:49:38-04:00Kitware RobotCreateAWindow calls itself in vtkCocoaRenderWindow if not rendered.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5980). Further discussion may take place here.**
---
If a vtkCocoaRenderWindow is used in a user created NSWindow and NSView, it is o...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5980). Further discussion may take place here.**
---
If a vtkCocoaRenderWindow is used in a user created NSWindow and NSView, it is overwritten by its own window.
See SimpleCocoaVTK as an example:
http://www.rogue-research.com/VTK/simpleCocoaVTK.html
The way SimpleCocoaVTK is done right now calls
vtkRenderWindowInteractor::Initialize() before it is rendered
the first time.
At that point, CreateAWindow in vtkCocoaRenderWindow is called.
It doesn't matter if the window is created of not. However, OpenGLInit()
is called, which calls ReadOpenGLExtensions. That seems to required that
the renderWindow been rendered once at that point (which is not the case).
If not, it calls render. However, render looks if OnScreenInitialized has
been set to 1. It has not since we are still in CreateAWindow (it is set at the next line).
Since it has not, it calls CreateAWindow again (which overwrites the one we are using)!https://gitlab.kitware.com/vtk/vtk/-/issues/5969Intel 10 compiler warning2016-08-12T06:49:34-04:00Kitware RobotIntel 10 compiler warning**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5969). Further discussion may take place here.**
---
/scratch/hjohnson/src/brains2/iplFreeware/unpackdir/VTK/Common/vtkVariant.h(324)...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5969). Further discussion may take place here.**
---
/scratch/hjohnson/src/brains2/iplFreeware/unpackdir/VTK/Common/vtkVariant.h(324): warning #858: type qualifier on return type is meaningless
const bool operator()(const vtkVariant& s1, const vtkVariant& s2) const;
^
https://gitlab.kitware.com/vtk/vtk/-/issues/5968VTK Dashboard "Bug" link broken.2016-08-12T06:49:33-04:00Kitware RobotVTK Dashboard "Bug" link broken.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5968). Further discussion may take place here.**
---
VTK Dashboard "Bug" link does not point to the new Mantis bug report system.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5968). Further discussion may take place here.**
---
VTK Dashboard "Bug" link does not point to the new Mantis bug report system.https://gitlab.kitware.com/vtk/vtk/-/issues/5932failure earlier reported in 00041832016-08-12T06:49:22-04:00Kitware Robotfailure earlier reported in 0004183**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5932). Further discussion may take place here.**
---
$ ../../../bin/vtk Histogram.tcl
ERROR: In /tmp/vtk-5.0.2/VTK/Filtering/vtkImag...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5932). Further discussion may take place here.**
---
$ ../../../bin/vtk Histogram.tcl
ERROR: In /tmp/vtk-5.0.2/VTK/Filtering/vtkImageData.cxx, line 1450
vtkImageData (0x8224f80): GetScalarPointer: Pixel (0, 0, 0) not in memory.
Current extent= (0, -1, 0, -1, 0, -1)
Segmentation fault
The failure is still occurring in Windows XP SP3
I do have VTK 5.0.3 as was stated to have solverd the problemhttps://gitlab.kitware.com/vtk/vtk/-/issues/5921NoClassDefFoundError2016-08-12T06:49:19-04:00Kitware RobotNoClassDefFoundError**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5921). Further discussion may take place here.**
---
I get the following error when I try and run the Cube Gyph Plot. I beleive I'm r...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5921). Further discussion may take place here.**
---
I get the following error when I try and run the Cube Gyph Plot. I beleive I'm running VTK 4.2 I tried to intall a new version VTK 5.0.3 (installer), but nothing happens when I run the file.
https://gitlab.kitware.com/vtk/vtk/-/issues/5896PlaceWidget does not work for vtkPointHandleRepresentation3D when Translation...2016-08-12T06:49:11-04:00Kitware RobotPlaceWidget does not work for vtkPointHandleRepresentation3D when TranslationMode is off**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5896). Further discussion may take place here.**
---
In the latest CVS version, vtkPointHandleRepresentation3D does not properly plac...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5896). Further discussion may take place here.**
---
In the latest CVS version, vtkPointHandleRepresentation3D does not properly place the handle after calling PlaceWidget if TranslationMode is on. The problem is that the change to the default TranslationMode setting is not passed to Cursor3D until some interaction takes place, but PlaceWidget calls vtkCursor3D::SetModelBounds, which reacts differently depending on the setting of vtkCursor3D::TranslationMode.
This patch fixes this behavior by setting vtkCursor3D::TranslationMode when vtkPointHandleRepresentation3D::SetTranslationMode is called.https://gitlab.kitware.com/vtk/vtk/-/issues/5891vtkVectorText::RequestData() is slow, optimisation is obvious2016-08-12T06:49:10-04:00Kitware RobotvtkVectorText::RequestData() is slow, optimisation is obvious**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5891). Further discussion may take place here.**
---
Profiling has revealed that vtkVectorText::RequestData() is a significant bottle...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5891). Further discussion may take place here.**
---
Profiling has revealed that vtkVectorText::RequestData() is a significant bottleneck in our application. Examination of the code reveals that this function performs work in a loop that could be moved out of the loop. The code in the loop is converting large string constants into ints and floats, but these strings are _constant_ and so the conversion need only be done once.
In fact, the code could be rewritten to avoid the strings altogether and instead use constant arrays of floats and ints. This would have the benefit of avoiding locale problems also, and fix bug 1431 as a side effect.