Benefits or problem splash screen
pixelbird at interisland.net
Fri Dec 5 14:26:42 CST 2003
> Date: Fri, 5 Dec 2003 10:04:35 -0500
> From: Thomas J McGrath III <3mcgrath at adelphia.net>
> Subject: Benefits or problem splash screen
> Since I decided after all of this work to add the splash screen I
> couldn't just make it the mainstack. I was worried about memory issues
> and about cross platform issues.
Like Rob says, if you put the engine in the splash stack, i.e., build it,
and it only, it becomes the _only_ standalone, you essentially have a non-UI
Rev player. When it's done doing what ever it does at startup (who
knows...encryption, file gathering, whatever), I'd send it offscreen so it
stays running and the app user can't accidentally close it.
Now you don't have to create a distr build of your Main stack. And it makes
changes a snap, because you can always open it from the Rev IDE, make your
changes, and be done, i.e., drag & plop the new version in your
distributable folder and deliver.
Makes sense, doesn't it?
More information about the use-livecode