LiveCode Forums

Hi all, After reading the article by Matthias on notarization I put together a helper for Levure that will notarize a DMG image when you package your Levure application. Here is the link: https://github.com/trevordevore/levurehelper-macos_notary To use it you will need to update to version 0.9.2 of ...

@LCMark - That is great news! I've been unable to wrap a number of Win32 API calls due to this limitation in the 32-bit interface.

@LCMark - If the 64-bit only has a single calling convention does that mean that callback functions will now work on Windows?

Example: https://docs.microsoft.com/en-us/window ... _enumproca

You're welcome. I'm glad it is working now.

Hi @mimu. Levure doesn't define any specific folder for shell scripts or executables. But you can definitely define your own folder using names that make sense to you. The only thing you need to do is make sure that the folder you define is copied to your packaged application for delivery to the end...

Great. You're welcome.

@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 ...