starting the Project Browser

[Douglas Ruisaard]

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

> 
> On 10/24/2018 02:10 PM, Douglas Ruisaard via use-livecode wrote:
> > Thanks for the reply, Klaus... but I'm sure we all agree this is totally non-intuitive.  However,
> using this call in my openStack script does two negative things:
> >
> > 1) least important but somewhat self-defeating to my "goal", this now opens the Project Browser
> right on top of my app in some default height and width.  As a result I have to move it over to the
> side and adjust the size.  If I just open the Project Browser via the LC tools, it opens in the same
> position and size as to the last saved stack.
> >
> > 2) more importantly, after allowing this code to execute within my app, I went to create my
> standalone version and found that all of the Saved Standalone Application Settings were GONE! and the
> setting had reverted back to the default ones for a brand-new stack.  Luckily, by not saving the stack
> at that point and commenting out that call, the settings came back .. whew!
> 
> I'm probably misunderstanding what you're trying to do, but a couple of
> observations:
> 
> 1. if you open the PB and then set the loc of it, both in your openStack (or preOpenStack) handler,
> then the browser should appear where you tell it to.
> 
> 2. trying to do this in a standalone app is bound to fail. The PB is part if the LiveCode IDE, and
> thus a separate application from your standalone. If you really need to launch the browser in the IDE
> then you'll need to set up a means of communication between the two. Most probably socket
> communication via a plugin stack, but ymmv.
> 
> --
>   Mark Wieder
>   ahsoftware at gmail.com
> 
>