Thanks all. What I did was put a function in the backscript script called homestack(), which simply returns the name of what ought to be the Main Stack (but isn't anymore in a standalone). I think anyone who wants to start saving as standalones should be alerted to this little quirk. Even though in the standalone settings I have the option to save substacks as individual stacks unchecked, it does it anyway. It just puts them in the app package instead of in another folder.
I suppose I should be using the latter method as that would allow me to much more easily update a particular stack without redistributing the whole app all over again. Something to think about. Bob S On Jan 11, 2017, at 18:43 , Mark Wieder via use-livecode <use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> wrote: On 01/11/2017 04:30 PM, Bob Sneidar via use-livecode wrote: I read in the dictionary: If you place the constant statement in a handler, you can use the constant anywhere in the handler. If you place the constant statement in a script outside any handler, you can use the constant anywhere in the handlers of that script. Any way to declare a global constant? I think I know the answer, but I thought I'd ask. Heh. There are requests for this in the bug database going back to 2004. To make matters worse, if you're really diabolical you could declare different values for constants in different scripts. script 1: constant onePlusOne = 2 script 2: constant onePlusOne = 3 -- Mark Wieder ahsoftw...@gmail.com<mailto:ahsoftw...@gmail.com> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
