starting the Project Browser

[Douglas Ruisaard]

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??


Douglas Ruisaard
Trilogy Software
(250) 573-3935


> 
> You may also need to implement the workaround that accounts for a recent change in the standalone
> builder.
> 
> <http://runtime-revolution.278305.n4.nabble.com/Standalone-build-workaround-tp4728140p4728141.html>
> 
> --
> Jacqueline Landman Gay | jacque at hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com
> On October 25, 2018 11:49:36 AM Douglas Ruisaard via use-livecode <use-livecode at lists.runrev.com>
> wrote:
> 
> > thanks for the reply... as I mentioned, the location/sizing thing was
> > the less important issue.  I didn't explain the standalone issue well enough.
> > I had the call to the rev-stack within a "if environment is development"
> > condition, so a standalone compile would have ignored the goto ... it
> > was the fact that when this call executed BEFORE trying to generate a
> > standalone, i.e. running the code from  the IDE, that it wiped out my
> > standalone setting.  If I had saved the stack without noticing this
> > fact, then I would have lost all of those settings (which were
> > fundamental to my app working!)
> >
> > So, the issue was not DIRECTLY involved with the "generation" of the
> > standalone, it was the issue that using this call set the standalone
> > setting back to a "new-stack" default!
> >
> > Douglas Ruisaard
> > Trilogy Software
> > (250) 573-3935
> >