[Paraview] ParaView session state

[Sebastien Jourdain]

Hi Eduardo,

That message is indeed the state but only for the proxy object and the VTK
instance underneath. Unfortunately (for you) the state of the
vtkSMSessionProxyManager
is not the whole state of the application. Each state is specific to its
instance.

In order to get the full state of the application you will have to traverse
the tree of objects that compose the application and gather all the states
on the way.

Unfortunately I couldn't find the time to walk through the code to validate
what I'm saying.

Hope this help and sorry I could not get you a better answer or better
pointers on where to look at.

Seb




On Wed, Sep 27, 2017 at 3:26 PM, <eduardo at berrocal.info> wrote:

> Hi Aron and all,
>
> Following this discussion....
>
> For what I can see, all the session state is stored in a variable called
> "State" inside Internals of vtkSMSessionProxyManager (
> vtkSMSessionProxyManagerInternals). This State is of type vtkSMMessage,
> which is a typedef of *paraview_protobuf::Message*.
>
> In other words, the state of the whole session is stored as a generated
> protobuf class (or package), which is defined in vtkPVMessage.proto. I
> guess this make sense as -- I image -- this makes read/write from a flat
> XML much easier (as well as transferring from client-to-server and vice
> versa). It would be great if someone with more knowledge on these details
> can clarify that I am in fact correct...
>
> Cheers,
> Eduardo.
>
> September 26, 2017 10:33 AM, "Aron Helser" <aron.helser at kitware.com
> <%22Aron%20Helser%22%20%3Caron.helser at kitware.com%3E>> wrote:
>
> Hi Eduardo,
> I think you've basically got it, but the state is more complicated than
> you think. Basically everything has a vtkSMProxy, and those proxies contain
> the state of the pipeline, representation, and views. Anything that is
> modified from the defaults gets saved in the state file. The vtkSMSessionProxyManager
> is the root of a session, as you've found.
> The input data is saved in the state file as absolute paths, and you do
> need the input data. When you read state, it has that intelligent option to
> search for the data files in another directory...
> I've just been learning this stuff trying to add dynamic lights to
> ParaView, so hopefully I'm close :)
> HTH, Regards,
> Aron
> On Tue, Sep 26, 2017 at 12:33 PM, <eduardo at berrocal.info> wrote:
>
> Hello list,
>
> Where is the data structure(s) in the code where all the objects for *the
> state* of a particular ParaView session are kept while it is running?. I
> have been reading the code, and I think it should be in the "internals" of
> vtkSMSessionProxyManager, but I am unsure. As far as I understand, the
> state (which can be saved to XML) is all it takes to recreate a session (Am
> I right here? Probably you need the input data as well, right?).
>
> Thanks for the help!,
> Eduardo.
>
> P.S.: Are my emails going to SPAM? Can someone respond ("hi") to this
> email to confirm otherwise? Thanks !.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171002/65cc1050/attachment.html>