[vtkusers] VTK CVS + wxPython...

[Charl P. Botha]

Andrea Gavana wrote:
> But even if use the old call (together with the frame.SetSize call), nothing is
> changed. For example, the vtkOrientationMarkerWidget is frozen, and in general
> the rendering process is slower than when I had VTK 4.2 and I used
> wxVTKRenderWindow and wxVTKRenderWindowInteractor together. With the VTK CVS, I
> can not do it anymore, I get all sort of runtime errors from Python.

You did say that the new wxVTKRenderWindowInteractor.py example works 
fine.  That means that the mechanism itself does work.

> I put my Script on my website only to let you visualize the problems I'm having,
> not to ask you to go through all the code. You can skip almost all the code,
> the relevant part of it is the visualization in the function readandplot(self).
> If you delete all the lines regarding the axis, the outline and other
> beautifications, you end up with 40-50 lines of code. The rest of the Script is
> only to do pre-post processing with external files, in which I/you am/are not
> interested, because they work.

It is impossible to eliminate the interaction of other code, even when 
you are convinced that there's nothing.  That is why it's so important 
to attempt to construct a SMALL example which is JUST extensive enough 
to demonstrate the problem.

> I'm trying to do it. I'm using the standard VTKData in order to reproduce the
> problems, but please take into account for a moment that:
> 
> 1) There is no VTKData file in which I have grid comparable to mine, and a bunch
> of actors like my application. Again, the grid construction process is fairly
> different, because I use vtkFloatArray() and its friends. It seems to me that
> there is no Python example on a Structured Grid with a standard VTKData file.
> 
> 2) I have still not found where is the problem on my application (the questions
> are: why the vtkOrientationMarkerWidget does not follow the camera? Why the
> rendering process is solwer? Why after some interactions the window gets
> frozen?). Where it can be? The grid construction process? The vtkTransform? All
> the text actors? It is not so easy, at least for an unexperienced user like me.

Is the grid-type dataset important to reproduce your rendering problem?
You have to start a new example from scratch with a synthetic dataset. 
Use for example the vtkSuperQuadricSource, or use 50 of them.  The point 
is NOT to whittle down your problem code till there's only an example 
left (although that is not a bad idea when all else fails).  The idea is 
to construct a new example and to TRY to reproduce the problem.

Good luck,
Charl

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/