LiveCode Forums.

I have a GLX Framework based application and am having problems getting it to launch in Mac OS X 10.11.6 El Capitan. It works fine on Yosemite. I am using LC 6.7.3.

The problem is that when the main stack opens there are handlers in it that the first scripts that run can't find. It seems that El Capitan tries to start running scripts before all the stack is loaded.

I have tried to workaround this by adding wait with messages for a couple seconds for the stack to fully load so all the handlers are available.

The way GLX works is a launcher stack first opens and then launches subsequent stacks. I have a login stack which then launches my main application stack which has the handlers that other handlers on that stack say it can't find.

Another way I tried to reso'vle this is to force the loading of the main application stack while the login stack is open by the method of using "put there is a stack [path/to?tack/file.livecode? described by Trevor here.
http://www.bluemangolearning.com/liveco ... to-memory/
That does not work since it returns false I presume because the stack is no longer present in the file structure as it is packaged in the standalone.

Is there another way to ensure that the stack is in memory before trying to open it?

Has anyone else seen this behaviour in El Capitan? Any ideas?

Thanks

Martin

Martin,

I haven't had any problems with GLX Framework apps on OS X 10.11 so let's see if we can find the variable. Some questions -

1. Is the script of the main stack in the message path? You say you open the stack but are you inserting it into the message path?
2. The glxapplicationPackager doesn't add any stacks to the standalone other than the the glxappLauncher stack. There should still be a stack file on disk within your .app bundle. Have you looked in the bundle to find your main stack file and then confirmed that the path you are checking is the right one?

Just to concur with Trevor. I also have had no issue with el Capitan (nor now with Sierra).
My GLX app works fine both in the IDE as well as a standalone.
I am now using LC8.1 and suggest you also move to the latest stable build (unless there is really something that LC 7 or 8 breaks).

Hi Trevor and James.

I found this was not an El Capitan issue. Just a silly mistake on my part but one made sillier because the script editor did not notice its silliness.

The handler where the error occurred was supposed to create a .plist file for the app if there was none in the /Users/Library/Preferences folder. I am developing using Yosemite and I already had the .plist file in my preferences files on my Mac so the error was never triggered while developing and testing there. I was testing the app on El Capitan by loading it on other Macs running El Capitan and since it did not have the .plist file (as the App had not been installed there yet) it would encounter the error all the time. That was what made me think it was a El Capitan vs Yosemite issue.

The error that was causing the problems was the result of a put statement for putting a value into a variable. I forgot to put 'into' into the statement i.e.
I did not catch the error when editing in the IDE since the script editor would compile the code in spite of the syntax error.

I have posted that as a bug http://quality.livecode.com/show_bug.cgi?id=18511

I am planning to transition my app to LC 8.1. James I am glad to hear that your GLX based app is working in LC 8.1 That was one of my concerns. The one other thing that has been holding me back is that I use lcVCS for version control. I want to make sure I can continue with that or another way of continuing to do version control in LC 8.1.

Thanks for your help Trevor and James.

Martin

Thanks for your suggestions.

Glad you found the solution. You're welcome.