Hi guys,
I'm back from vacation, and by reading your comments it seems to be related
on how the widgets are managed across several view and when active view
change...
I'll check with Utkarsh what can be done about it.
Seb
On Thu, Aug 30, 2012 at 7:39 AM, Nenad Vujicic nena...@gmail.com wrote:
Dear Utkarsh,
Thank You very much for Your help. I hope Sebastien will have some idea.
Btw, in a meantime, I discovered one interesting detail. If I set
pipeline source (with widget) as currently active source
(SetActiveSource(...) in pvpython) before I execute code I mentioned
in first message
Sebastien may have some insight here since they do something similar
for the WebGL exporter. He's on vacation this week, but I can ping him
once he gets back.
Utkarsh
On Tue, Aug 28, 2012 at 6:33 PM, Nenad Vujicic nena...@gmail.com wrote:
Dear Utkarsh,
Thank You very much for Your response.
Hello everyone!
I have problems with visibility of 3D widgets when I have several
views opened in one ParaView Qt client and I switch between them. I
experience this behavior on both Windows and Linux. Here is how to
reproduce it:
0) Start ParaView Qt client,
1) Create Sphere source and press
Nenad,
vtkVRMLExporter will be the starting point where I'd start digging in.
I am guessing somewhere where it iterates over all actors it's not
checking for visibility of 3D widgets or something.
On Tue, Aug 28, 2012 at 5:45 PM, Nenad Vujicic nena...@gmail.com wrote:
Hello everyone!
I have
Dear Utkarsh,
Thank You very much for Your response.
It checks actor's visibility at vtkVRMLExporter.cxx Ln 262, but actors
are visible because of some reasons. I'm sorry, looks like the problem
is much deeper. I tried even by playing from pvpython by executing:
