LiveCode Forums

@Martin - I don't know the cause of the error so I only have suggestions of where to look. if you look at the Standalone builder settings for your stack is the merge code selected in the Inclusions tab? If you don't see it in the Inclusions tab maybe check the custom properties of the stack to see i...

Looking at the Levure packaging code I see that I had to start creating the folder passed as the 2nd param to `revSaveAsStandalone`. So try creating `theOutputFolder`using `create folder` first. I also have code in Levure that assigns a custom property of the stack that is being built as a standalon...

Error 91 is "can't find stack". Line 72 is the line of whatever script was executed. I haven't tried building any GLX standalones in LC 9. I know the standalone builder has changed so you will probably have to inspect the GLX plugin code and put sprinkle some debugging statements in to see what is g...

Thanks for the update. I’m glad you got it working.

Martin,

I don’t know why you are seeing that error. As to your question about updating all stacks in the GLX project, GLX is irrelevant in this case. GLX doesn’t care on way or the other as it is the engine that handles open stack files.

You’re welcome. I’m glad all of the work was already done

Martin, The external is 32-bit and Livecode 9.0.5 is going to default to opening as 64-bit. Try downloading Levure and grabbing the Preferences external from the ./framework/helpers/preferences folder. That should work with 64-bit. Levure uses an extension by default but the external was updated wit...

I'm experimenting with watchman and trying to use the socket interface. It uses a unix domain socket. From the command line I can get the path to the file by issuing the following command: watchman get-sockname The output providers the path to the file: { "version": "4.9.0", "sockname": "/usr/local/...

@jpags.me - `string` is not a valid variable type for foreign handlers. You can use ZStringNative, ZStringUTF8, or ZStringUTF16. This file lists them and has descriptions: https://github.com/livecode/livecode/blob/develop/docs/specs/lcb-type-naming.md A reference to ZString should appear in the LCB ...

That is correct.

For Sparkle I just use the DMG file that users download. WinSparkle expects an installer. I pass it one made with Inno Setup. Just make sure you set the proper command line arguments for Inno Setup in the appcast.xml file.

Update your appcast.xml template and use `[[VERSION]].[[BUILD]]` instead of just `[[BUILD]]` for the Windows `sparkle:version` setting. WinSparkle uses the full version from the exe file rather than the build number like Sparkle does. I just updated the app_updater helper with this change a little o...

If you wanted to get to the bottom of it you could sprinkle some messages in the `windowManager.livecodescript` `openCard` handler to see if it ever gets called. There is an `if` statement in there so you could verify A) if `openCard` is making it to the `windowManager` script and B) if `set the vis...

I uploaded a new IDE plugin for use with Levure applications. It is still in the early stages of development but it makes it much easier (IMO) to browser my Levure apps within the IDE. Currently it lists your UI stacks, Template stacks, libraries, frontscripts, backscripts, and helpers. Github Repo:...

In the message_watcher.livecodescript file you will find the code that manages windows. Because of a bug in versions of LC earlier than 9.0.3 (still in development) the stack window is hidden in preOpenStack. In the windowManager.livecodescript file the window will be shown again in the openCard han...