Everyone has some. It is a common way of making standalones, where the splash stack is the executable and everything else, like other stacks "attached" to it, or external files that are accessed by it. The executable cannot be saved, which is why other stack files are attached to it. These can be saved. And of course external files can be read and written to.Are there any examples around of a 'splash stack' ?
Try this. Make a new stack, name it "XXX" and save it. In the card script of "XXX""
Code: Select all
on openCard
go stack "YYY"
end openCard
Code: Select all
on mouseUp
put random(99999) into fld 1
end mouseUp
Code: Select all
on closeStackRequest
save this stack
end closeStackRequest
Now go to menu "File/Standalone Application Settings". In the General pane, name your standalone, say "ZZZ". Now in the "Stacks" pane, click "Add Stack File" and navigate to stack "YYY".
Now go to "File/Save as Standalone Application..."
When all this is done, your first stack ("XXX") is the "splash" stack. which does nothing but open "YYY". But you can now click in "YYY" and each new number will be saved. Nothing in "XXX" can be. "XXX" might, however, read and write to external files.
I am not testing this as I write it, but I think it should work. If not, some little tweak will fix it if I messed up. But that is the general idea.
Craig