Re: Standalone issue ... was starting the Project Browser

2018-10-29 Thread Bob Sneidar via use-livecode
That interferes with the standalone builder, specifically auto detecting addons/plugins. It may cause other issues as well. It's a catch 22. Bob S > On Oct 27, 2018, at 12:56 , J. Landman Gay via use-livecode > wrote: > > I'd be happy with a simple toggle that lets me turn on lockmessages b

Re: Standalone issue ... was starting the Project Browser

2018-10-27 Thread J. Landman Gay via use-livecode
On 10/27/18 10:26 AM, Douglas Ruisaard via use-livecode wrote: 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: I

Re: Standalone issue ... was starting the Project Browser

2018-10-27 Thread Brian Milby via use-livecode
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

Standalone issue ... was starting the Project Browser

2018-10-27 Thread Douglas Ruisaard via use-livecode
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 s