What Env Variable set when saving standalone?
J. Landman Gay
jacque at hyperactivesw.com
Thu Jan 25 19:24:25 EST 2018
Regardless of the stack mode, why wouldn't it retrieve info? As the
developer you'd know not to click elsewhere until the data is there, right?
--
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On January 25, 2018 5:33:27 PM Bob Sneidar via use-livecode
<use-livecode at 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 at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
More information about the use-livecode
mailing list