Right. It seems like it would be easier to clone a stack, then reset everything
in it, or just keep a copy of a virgin stack around. You would have to update
it every time you made any changes to the original though.
Bob
On Dec 28, 2011, at 1:51 PM, stephen barncard wrote:
A while ago I
Bob Sneidar wrote:
It seems like it would be easier to clone a stack, then reset everything in it,
or just keep a copy of a virgin stack around. You would have to update it every
time you made any changes to the original though.
That's been my experience as well. The stack file format is
Hi All,
Does anyone know of a sample stack demonstrating how to pull all of the
properties and custom properties out of a stack, putting them into a file, and
then demonstrating how to put the file of data back into the stack (or into
another copy or clone of the original stack)?
Thanks,
-
Get the customProperties of a stack. It is an array. Get the properties of a
stack. It is (almost) all of the properties of the stack as an array. at this
point the easiest thing to do to save them as a file on disk is to
arrayEncode() them and write them to a low level file. Not sure if you
Bob-
Wednesday, December 28, 2011, 8:31:54 AM, you wrote:
Putting the standard properties back is a bit trickier though. I
don't think you can set the properties of a stack.
Most of them you can. Some are read-only. If you wrap your code below
in a try-catch construct you can avoid the
I meant all at once as in set the properties of this stack to theSavedProperties
Bob
On Dec 28, 2011, at 10:16 AM, Mark Wieder wrote:
Bob-
Wednesday, December 28, 2011, 8:31:54 AM, you wrote:
Putting the standard properties back is a bit trickier though. I
don't think you can set the
well if one were setting all of the properties of a stack, they'd have to
be set to another stack.
set the properties of stack b to the properties of stack a
Easier to copy the stack.Can all the properties be placed into a variable?
I think some props will be left out by design, otherwise
