Standalone issue ... was starting the Project Browser

[Brian Milby]

If your code does things that break when called as a part of the build process, then you need to check and exit the handler before the code executes. Putting it at the end of the handler is not needed. If needed, it probably needs to go toward the top of the handler.

When the IDE first launches, the revStandaloneProgress stack is not loaded. After you build any project, then it will remain in memory for the rest of the session.

Thanks,
Brian
On Oct 27, 2018, 10:26 AM -0500, Douglas Ruisaard via use-livecode <use-livecode at lists.runrev.com>, wrote:
> I've changed the subject line (from Re: starting the Project Browser) to reflect this discussion more accurately.
>
> If that's true then there's (sigh!) one more reason to stay away from LC v9... but I really don't understand the reason why this is necessary in the first place. I've never had a standalone fail with a "can't find stack" error:
>
> from http://runtime-revolution.278305.n4.nabble.com/Standalone-build-workaround-td4728140.html#a4728141
>
> "... when you open the stack for the first time (without having built a
> standalone before), the stack "revStandaloneProgress" is not loaded yet
> (thus the "can't find stack error)...."
>
> So, does this situation only occur for the first standalone build? Not the second time? What is implied should be done if one of the conditions in the function is false? .... very confusing!!!
>
> I guess I was looking for something more specific about where to put this "fix":
>
> e.g.
>
> In an openStack call, you'd put this ... where? At the end of the code just before the "end openStack"? (that's where I put it):
>
> if isBuildingStandalone() then
> exit openstack
> end if
>
> and have the following function call accessible to call cards (i.e. in the stack)?
>
> function isBuildingStandalone
> return the environment is "development" AND \
> there is a stack "revStandaloneProgress" AND \
> the mode of stack "revStandaloneProgress" > 0
> end isBuildingStandalone
>
>
> My question, then, is do I have to have a similar "if isBuildingStandalone()" call in all the "opens" and "closes" you list (and others) and do I "exit" the call if isBuildingStandalone() returns "true"?
>
> WOW! ... if THAT's needed then I can't imagine anyone editing all of their code to do this!!!
>
> Douglas Ruisaard
> Trilogy Software
> (250) 573-3935
>
>
> >
> > It's referring to all engine messages that contain either "open" or "close", so:
> >
> > preOpenStack
> > preOpenBackground
> > preOpenCard
> > ...etc
> > openStack
> > openBackground
> > openCard
> > ...etc
> > closeStack
> > closeBackground
> > closeCard
> > ...etc
> >
> > I understand why this is necessary now, but it is pretty instrusive, is going to bite a lot of people,
> > and clutters up scripts. I'd like to see some sort of toggle where we could use the older method if
> > there is no problem doing that.
> >
> > On 10/26/18 11:20 AM, Douglas Ruisaard via use-livecode wrote:
> > > Thanks, Jacqueline.
> > >
> > > I have not had any issues with using the StandAlone builder but then I am using LC v8.1.9. on
> > Windows 7. I did put Panos's code into my app ... made no apparent difference but good to have there
> > anyway.
> > >
> > > I'm a bit confused about the reference to "Similar in all other (pre)open*/close* messages." ...
> > what is being recommended here (I get the "preOpen" bit) .. but the reference to the "close" I don't
> > get ... some other function call??
> >
> >
> > --
> > Jacqueline Landman Gay | jacque at hyperactivesw.com
> > HyperActive Software | http://www.hyperactivesw.com
> >
> >
>
>
> _______________________________________________
> 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