Bob,
Is the problem that at app-login time, the app doesn't know whether its
opening was caused by the standalone builder or by the user? If so,
maybe something this would work:
on standaloneSaved
put true into url (specialFolderPath("temp") & "/saved"
end standaloneSaved
on appLogin -- in card script of login stack
if there is a file ( specialFolderPath("temp") & "/saved" ) then
delete file ( specialFolderPath("temp") & "/saved" )
else
modal the owner of me -- or whatever mode you want
end if
end appLogin
It's crude but would probably work. Of course it's always possible I'm
solving the wrong problem. :-)
Phil Davis
On 1/25/18 3:31 PM, Bob Sneidar via use-livecode 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
--
Phil Davis
_______________________________________________
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
