At 5:27 PM -0500 16/2/01, [EMAIL PROTECTED] wrote:
>Apparently, a MetaCard standalone cannot "save" itself. All changes
>made to a standalone are thus forgotten as soon as the user quits.
>EVERYTHING is forgotten, including changes made to the CONTENT of
>the fields.
>
>The only alternative that I can think of for saving changes made to
>metacard standalones is to script the writing (e.g. save) and
>reading (e.g. restore) of external text files.
>
>This read/write alternative is viable, but it seems like a 'hack' to
>me, especially for something as fundamental as being able to resume
>where one left-off. I would have to litterally restore everything:
>content, all of the properties that might change, etc. Ouch!
>
>What are other folks doing to maintain/remember the content/state of
>your metacard standalones?
It kinda is so, and it ain't so.
But no need to save changes to external text files.
What you can't do is save changes to the stack that is attached to
the Metacard engine. But you can save changes to any stack in an
external file. So the easiest thing to do is build your standalone
from a tiny stack that simply opens the external stack at start up.
This approach also makes cross platform distribution easier as the
external file can be identical for all platforms.
Cheers
Dave Cragg
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
