Saving a stack state and variables

[Jim Ault]

On 5/18/06 12:49 PM, "Rob Beynon" <r.beynon at liverpool.ac.uk> wrote:

> I therefore need to write out to a file the contents of all fields,
> and the status of all buttons and menus, as well as some variables.
> Because some fields can have many lines, it is not as simple as one
> entry per line. 
> <<full quote below>>

One simple technique for saving multi-line entries is to 'pack' them like
this...

replace cr with "^^" in textBlock  -- of course using a char you choose
--now add textBlock to the other content

--on reading back to form
replace "^^" with cr in textBlock

Hope this helps,

Jim Ault
Las Vegas


On 5/18/06 12:49 PM, "Rob Beynon" <r.beynon at liverpool.ac.uk> wrote:

> 
> Hi all,
> I have a slightly weird stack
> http://www.liv.ac.uk/pfg/LocalTools.html
> that does something specific for our research.
> 
> Basically, you enter one field (sequence) or download from the web,
> then perform various operations based on choices, to generate an SVG
> file that can the be edited externally. It's a bit specialised, but we
> like it.
> 
> However, I now want to use save and load menus to save the sequence
> and the options in a file, and then reload it to generate that view
> sometime in the future.
> 
> I therefore need to write out to a file the contents of all fields,
> and the status of all buttons and menus, as well as some variables.
> Because some fields can have many lines, it is not as simple as one
> entry per line.
> 
> What more sophisticated methods would you suggest? The saved file
> doesn't have to be human readable, although that would be a bonus.