11-11-2020, 02:40 AM
Thanks Mark,
I don't think that was it -- despite a couple of differences differences between the stack code in the toolkit and the code you provide, no error was being generated and nothing worked.
The differences with the toolkit code that i could see were the location of the SDK within the mac app bundle (according to your path above, the SDK is in /Contents/Resources/_MacOS/data/config/CanelaDB, whereas in my bundle it's in /Contents/Resources/_MacOS/CanelaDB. Also the stack script is slightly different - yours uses specialFolderPath("support"), whereas the stack script is specialFolderPath("resources") in case "MacOS"
Changing all of the above to match your script above made no difference whatsoever.
Then i decided to see if the startup script was even being triggered, by adding an answer dialog to state what environment was being detected in the preOpenStack script.
And then the login worked!
I wondered if the wait 0 milliseconds with messages needed a larger value, but removing the debug code didn't make a difference - it still works now.
I can only presume this is some kind of odd gremlin/corruption in my stack which has somehow ironed itself out.
I'm now faced with other unexpected behaviour with the standalone (i've set the database to be local and sync from cloud on start up but this isn't happening now in standalone - only works inside liveCode) -- but that's a struggle for another day
I don't think that was it -- despite a couple of differences differences between the stack code in the toolkit and the code you provide, no error was being generated and nothing worked.
The differences with the toolkit code that i could see were the location of the SDK within the mac app bundle (according to your path above, the SDK is in /Contents/Resources/_MacOS/data/config/CanelaDB, whereas in my bundle it's in /Contents/Resources/_MacOS/CanelaDB. Also the stack script is slightly different - yours uses specialFolderPath("support"), whereas the stack script is specialFolderPath("resources") in case "MacOS"
Changing all of the above to match your script above made no difference whatsoever.
Then i decided to see if the startup script was even being triggered, by adding an answer dialog to state what environment was being detected in the preOpenStack script.
And then the login worked!
I wondered if the wait 0 milliseconds with messages needed a larger value, but removing the debug code didn't make a difference - it still works now.
I can only presume this is some kind of odd gremlin/corruption in my stack which has somehow ironed itself out.
I'm now faced with other unexpected behaviour with the standalone (i've set the database to be local and sync from cloud on start up but this isn't happening now in standalone - only works inside liveCode) -- but that's a struggle for another day