What Env Variable set when saving standalone?

[J. Landman Gay]

I might not have been clear. You'd keep the login stack a toplevel stack 
all the time. In whatever handler actually launches that stack, you'd 
check the environment and only open it as modal if the environment is 
"standalone".

During development the login stack is toplevel. It should be able to 
retrieve db info normally in that mode. The reason you want a modal is 
so that users can't click away until the data loads, but as the 
developer you'd know not to do that. You'd just wait for the data and 
then proceed normally.

Seems like the simplest solution to me. A toplevel stack won't hinder 
development or standalone builds, and it will show up as modal if the 
environment is "standalone" (or if it's not "development", or whatever 
other test you want to apply.)

On 1/25/18 7:02 PM, Bob Sneidar via use-livecode wrote:
> I assume because it's opened modally, and the builder obviously needs to open another stack but can't because the modal stack is blocking the progress of the script that told my app to open it. (I know it's confisung but that is how modality works I guess).
> 
> Bob S
> 
> 
>> On Jan 25, 2018, at 16:24 , J. Landman Gay via use-livecode <use-livecode at lists.runrev.com> wrote:
>>
>> 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
> 


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com