I also notice that when "Load State" is invoked, the undo/redo stack is
cleared. Is that a result of the current views being destroyed?
(mentioned by Utkarsh, below)
thanks,
Geoff
On Tue, 11 Nov 2008, Geoff Draper wrote:
Ken, Utkarsh,
Thank you for your responses. In reference to Utkarsh's comment near the end
of his note: I think it would be a good idea to automatically delete existing
objects before loading state, although I can see the logic of the current
approach as well. Maybe this could be toggled via a Preferences option?
--Geoff
On Tue, 11 Nov 2008, Moreland, Kenneth wrote:
Geoff,
I just added a feature request for the color loss issue. It's not
specifically wrong, but I can see how it can be annoying.
http://www.paraview.org/Bug/view.php?id=8081
As with respect to the "large" disk, this is caused simply by the fact that
the disk is larger than the cone. ParaView resizes the window whenever an
object is made visible when no other objects are made visible. When you
loaded the new state, the smaller cone was made visible first, which caused
the window to resize to its bounds. When the disk is made visible, it
looks larger because the camera is zoomed in. It would be really annoying
to have the camera reset every time you made an object visible. (Trust me,
we tried it.)
-Ken
________________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On
Behalf Of Utkarsh Ayachit [EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 6:31 AM
To: Geoff Draper
Cc: [email protected]
Subject: Re: [Paraview] unexpected behavior w/ "Load State" command
Geoff,
When one sets up display properties from the Display tab, these
properties apply to the way that data is shown in the current active
view. When state file is loaded, all current views are destroyed and new
views, as specified in the state file, are created and only those
objects that were visible in the state file remain visible. Since new
views are created (and old ones destroyed) all the changes you made to
the Display tab are lost.
Actually, there's even talk of deleting all existing objects before
loading state. If that's done then you'd even loose the disc source.
Utkarsh
Geoff Draper wrote:
I'm not sure if this is a bug, or if I'm just misusing the tools. Please
advise. To duplicate what I'm seeing:
(1) Start with a blank scene. Create a simple object (e.g. Sources ->
Cone, and Apply).
(3) Save it as a .pvsm file (File -> Save State)
(4) Exit ParaView, and restart it.
(5) Create another simple object (e.g. Sources -> Disk, and Apply).
(6) On the Display tab, click "Set Solid Color" and pick a color for the
disk.
(7) Restore the previous file (File -> Load State). The disk disappears.
(8) No problem, we simply make the both objects visible by clicking the
"eye" icon in the Pipeline Browser.
(9) Now for the unexpected part (for me, anyway): When the disk object
reappears, it has lost its color, and is rendered about twice as large
as before.
Is this how it's supposed to work? Thank you for any insight you could
offer!
--Geoff
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
