Rob,
The current saveState/loadState saves and restores the whole "state".
It works at the level of the memory and has no knowledge of what the
values represent. When you load "test2.polydb" this simply restores all
global references to the values they had when you saved the state. In
partic
On Friday 28 Nov 2008 11:06 am, David Matthews wrote:
> Phil,
>
> Philip Clayton wrote:
> > My understanding of loading a state is that new objects are created
> > whether or not the same object is already loaded. That seems the right
> > thing to do, as you say. When loading a child state howeve
Phil,
Philip Clayton wrote:
My understanding of loading a state is that new objects are created
whether or not the same object is already loaded. That seems the right
thing to do, as you say. When loading a child state however, I would
expect only objects in the child state to be created and
David,
That behaviour sounds reasonable to me. I now realize that when I was
simplifying the example we have, I went a little too far and eliminated
the hierarchical aspect of the state, making the problem I ended up
describing subtly different.
My understanding of loading a state is that n
Phil,
The idea of loadState is to be able to load information saved in a
previous session and it doesn't always work as expected when you reload
the state into the session that saved it. That isn't something I
imagined someone wanting to do.
loadState restores the values of references in the
David,
Thanks. This makes sense and explains why we were seeing an inactive
thread. It's useful to know that values can be passed from one sessions
to the next via the stack - we hadn't fully appreciated that feature.
This behaviour with threads works well for what we are trying to do but
Philip Clayton wrote:
Does anyone know what should happen to threads (created with
Thread.Thread.fork) when PolyML.SaveState.loadState is performed? It
appears that they are no longer reported as active but, despite this,
carry on running. Is it up to the user to kill these before doing a
lo
Does anyone know what should happen to threads (created with
Thread.Thread.fork) when PolyML.SaveState.loadState is performed? It
appears that they are no longer reported as active but, despite this,
carry on running. Is it up to the user to kill these before doing a
loadState?
Thanks,
Phil
