LiveCode Forums.

Hello everyone.

I am new with LiveCode, My last time with this environment was when it was Called Revolution Studio 4. My job at my company is to create externals to this platform and do test projects to show the external functionality and features. Up until Revolution Studio or Enterprise everyone was working fine.

That was until the switch to LiveCode.

For some reason the same externals work just fine while I test the application on the IDE, however, when the Windows standalone is built, the external does not work at all. I have tested and yes, it uses the external as it should, but the program or external just doesn't work as it does in the IDE. This works just fine when the standalone application is done on Revolution Studio 3 or 4, but on LiveCode 5 it doesn't.

Please help

Thanks

Hi,

Maybe this will help. Lots of things have changed.

Kind regards,

Mark

Hello, I tried the link but it's the same documentation I have with 4.0. I am sorry, but I see no changes from RunRev 4.0 to Livecode

Hi, maybe this will help, from V5 release notes.


IDE Changes
Getting folder locations within the IDE
If you write plugins, or have code that relies on the location of IDE files then please ensure you use
the following access functions to locate them:
revEnvironmentToolsPath() The location containing the main IDE files.
revEnvironmentToolsetPath() The location of the main IDE stacks.
revEnvironmentExternalsPath() The location of the externals that come with the IDE.
revEnvironmentPluginsPath() The location of the plugins that come with the IDE.
revEnvironmentRuntimePath() The location of the standalones that come with the IDE.
revEnvironmentDocumentationPath() The location of the documentation files.
revEnvironmentResourcesPath() The location of the resources that come with the IDE.
revEnvironmentCustomizationPath() The location of the IDE customization folder.
revEnvironmentUserCachePath() The location of the folder to use for caching files.
revEnvironmentUserPreferencesPath() The location of the folder to use for preference files.
revEnvironmentUserExternalsPath() The location of the folder to use for additional externals.
revEnvironmentUserPluginsPath() The location of the folder to use for additional plugins.
revEnvironmentUserResourcesPath() The location of the folder to use for additional resources.

Important: Third-party IDE extensions must avoid placing any files inside the application
bundle or under revEnvironmentToolsPath() (not least because you will probably not have
privileges to do so!). Instead, they should use the user-externals and user-plugins paths as
provided. These paths are determined by the user's customization path setting, configurable
in the preferences.

Hi,

Can you be more specific about which features of your external don't work?

Kind regards,

Mark

Hello

I found another thing that is confusing:

my External has six functions, In RunRev everything works fine. But in LiveCode only three of these functions can be accesible on the Windows Standalone.

- If I change the order of the functions inside Visual studio (where I compile the external), some function that work now they don't and viceversa.
- If I add too many accesses to my functions in LiveCode, none work on standalone.

I wish there were a new version of the SDK because I follow all instructions.

my external is on My Doccuments\My LiveCode\Externals and for runtime is in My Documents\My LiveCode\Runtime\Windows\x86-32\Externals

What happens when you do these (in your stack or in the standalone)?
What version of Visual Studio are you using?
How (and when) are you setting the external library linkage?