I had suggested that the application builder include a Splash Stack method that inserted a default splash stack, but allowed you to substitute your own in the process of building the app. The Splash Stack would become the default main stack for the projects and would be modified to call the actual mainstack before compilation.
It was not received with much enthusiasm, but perhaps this would be the optimum solution. It could be an option you could turn off if you wanted but enabled by default. Bob On Jan 15, 2011, at 9:44 AM, Peter Haworth wrote: > > This thread reminds me so much of going through all the same questions when I > first started using LC. Seems like a document that listed all these little > idiosyncracies of LC, specifically targeted at newbies, would be extremely > useful. Maybe one already exists somewhere? > > One thing I'd add to Calvin's list of gotchas is to realise that you cannot > permanently store data in a stack in a standalone program. Lots of > recommended workarounds of course but this is something you don't typically > find out about until well down the development path (at least I didn't) > because it's not a problem when working in the IDE, and it can mean fairly > major changes to your application. > > Pete Haworth _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
