I handled the startup not being loaded in the IDE by putting an if environment is "development" then do initialize in the preopenstack. This way I can leave the code in the app when built and it will switch to the startup instead.
I guess I misinterpreted the docs about the shutdown message. It sounds like it would be the best place to set a 'save' . I thought it was saying I could put variables into a custom prop and it would actually save it. What set me off was I was quitting in the IDE and it was saving my stack with the new data in the custom prop each time I tested it so in affect "I" was doing the saving and a build of course can not save itself with the new data.
Once again I notice that I put a lot of scripts into each handler that should be it's own function. This makes so much sense for reusing the script and yet I always seem to forget and end up with very long scripts.
THanks again,
TOm
On Jan 11, 2004, at 11:52 AM, Dom wrote:
Thomas J McGrath III <[EMAIL PROTECTED]> wrote:
My problem with the preopenstack is that I have a lot of substacks that
I don't want to use what is in the preopenstack handler. That is why
the startup looks so good.
In the substacks just put:
on preopenstack end preopenstack
to trap this command.
As for "on startup", I was used to go with it in my HyperCard times, but
no more since then...
-- Digital photos (nature, garden) : http://cooldomi.free.fr/ Scripting : http://domiscript.free.fr/ _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Macintosh PowerBook G-4 OSX 10.3.1, OS 9.2.2, 1.25 GHz, 512MB RAM, Rev 2.1.2
Advanced Media Group Thomas J McGrath III • 2003 • [EMAIL PROTECTED] 220 Drake Road, Bethel Park, PA 15102
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
