LiveCode Forums.

It is straightforward to write a Revolution External wrapper for any DLL, refer to Mark Waddingham's write up on how to write externals for Revolution. His article includes a stack that will create an xcode or visual studio project for you, so that all that is required is to write some functions to ...

This is just an addition to Oliver's post.

You can load externals dynamically when they are required. For example using a simple handler:

on loadExternal pDLL
-- Use "the externals" property of the templateStack to set the DLL
set the externals of the templateStack to pDLL
set the name of the ...

Hi Malte,

The Standalone builder should include the MinFreeSpace element in the manifest. If it is missing or indeed incorrectly calculated then this is a bug, although we may need to assume a certain flexibility when doing this calculation.

Hi Mark,

You can signal to the launchpad whether an install should continue using a quit code, if it is nonzero, the launchpad will discontinue the install.

Thus, you only need to do:

on disagree
quit 1
end disagree

No files should be left on the system, and you should not have to do any work ...

Hi,

Thank you for your suggestion. I agree that the current find and replace interface can at times be confusing. It seems too easy to delete code by mistake, and there may be no way to undo this operation (a revert may cause the loss of other entered but not applied code).

We will be looking to ...

Hi,

When you open Revolution it should ask to set the file associations if these have not been defined (and the dialog is allowed to show). If this does not happen or indeed it does not work, then this is a bug.

I had a look at this stack, but I do not see how it improves the current documentation.

Are there particular search terms that work in this stack as opposed to the Revolution documentation?

If you provide us with some clear examples where you find the Revolution documentation does not provide good ...

I am aware of the difference between the IDE and the engine.

More specifically, the problem is in the IDE engine - where allowInterrupts is set to false on exit from the licensing code (this is a bug that has yet to be fixed).

The standalone engines have never been affected by this problem where ...

Any reason you say this is the case? The IDE currently has allowInterrupts set to false by default; setting it to true solves the problem. Whether or not you can always interrupt execution is an entirely different question.

Some of you have noticed that allowInterrupts has been set to true by default in the 2.7.2 IDE. This prevents you from interrupting scripts by pressing control-. (Windows) or command-. (Mac).

This is a bug and will be fixed shortly. In the mean time you can work around it by running:

set the ...