Hi Bidge
Providing that you save your first stack (which presumably will be the Splash screen) as the app and all the other substacks as separate stacks when you build your app, here's another way that should work:
Have an invisible field on your main prog substack called "SShown", for instance.
In the OpenCard of your splash stack, put:
Code: Select all
on OpenCard
if fld "SShown" on card 1 of stack "SuchAndSuch" is empty then
put "1" into fld "SShown" on card 1 of stack "SuchAndSuch"
else
hide stack "Splash"
close stack "Splash"
open stack "SuchAndSuch"
end if
end preOpenStack
Obviously you'll need a mouseUp handler on the "Splash" stack to open stack "SuchAndSuch" and close stack "Splash".
And a save Stack "SuchandSuch" somewhere in your closeStack script of main app.
With respect though, I can't see the point of a splash screen only showing once. The majority of software has splash screens, and to an extent, users expect one, I think. (Even if it's not shown automatically, it'll more than likely be in the About menu item). There is some code knocking around which will make the screen close after however many seconds you want if the user hasn't clicked it to close it anyway, I'll have another look to see if I can find it, if you like. (I seem to remember it converts the time to seconds then adds so many seconds so that if the variable > this total it'll close it).