A couple more ideas: in the Stack script…
on savingStandalone processLogin "false" pass savingStandalone end savingStandalone command processLogin pLogin if pLogin = "false" then exit processLogin modal stack "Login" end processLogin I tested this, but I’m not 100% sure it would be successful in your case, it seemed to work OK here. Or simply holding the alt key down while making the standalone with: if not the altKey is down then modal stack “login” # within the appropriate handler of course I tried this on a simple stack and the alt key doesn’t seem to interfere with the build process, but you would need to test with your setup. Paul > On Jan 25, 2018, at 3:31 PM, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Trouble is I DO want to open the login stack modally in development, because > it pulls setup information for each user from the Login database, such as > custom settings (like local file paths, recent customers list, access level > etc). The only time I do NOT want to open that stack is when I am saving as > standalone. > > It's not killing me to set the stack mode to top level each time, it's just > irritating. > > Bob S > > >> On Jan 25, 2018, at 13:57 , J. Landman Gay via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> You could try it a different way. Save/keep the login stack as toplevel all >> the time, then in the handler that opens the login stack: >> >> if the environment is not "development" then modal "login" >> else go stack "login" > > > _______________________________________________ > 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 _______________________________________________ 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
