Standalone problem (solved?)

dunbarx at dunbarx at
Tue May 22 09:45:46 EDT 2012

Jacques and Klaus...

Thanks to both of you.

My standalone problem is solved, sort of. It was always the pathname to the external. I had thought so, and mentioned it as a likely culprit in my initial post.

It seems the external must be explicitly referenced, as verified by the authors, and not, in their words, "relatively" referenced. The issue therefore is, I guess, inherent in the particlular external I am using. The important point here is that the external need not be placed in the "externals" folder in the "contents" folder of the standalone package. As Klaus said, LC does not place third party externals there automatically anyway.

I solved the problem by creating a folder with a specific name, placing the external in that folder, and putting it in my "Applications" folder, which is common to all OSX systems. This is NOT an "applications" folder found in a user account, but rather the default.

In the inspector, I set the external reference to the bundle in that specific folder. I now make the standalone, Then I place the standalone in that folder as well. I can now take that folder, containing both the standalone and the external, and copy it to the "Applications" pane in any new machine, and it works. This is a kluge, but at least I understand it.

It is academic to me why this must be, especially since I thought I had learned something new and important in that one must load third party externals into the contents folder of a standalone package by hand. In my case, doing this had no effect at all. I assume that this method (the "ordinary" method) gives one a "relatively" referenced pathname to ones external. The authors actually said they did not know how to write such a "relative" pathname.

Is this of interest to anyone but me?

Craig Newman

-----Original Message-----
From: J. Landman Gay <jacque at>
To: How to use LiveCode <use-livecode at>
Sent: Mon, May 14, 2012 11:25 am
Subject: Re: Standalone problem

On 5/13/12 11:50 PM, J. Landman Gay wrote:
> You can only
> load externals in a preOpenStack handler,

I had a thinko. It's "startup" I believe. They may both work, it's been 
a while so I'd need to check.

Jacqueline Landman Gay         |     jacque at
HyperActive Software           |

use-livecode mailing list
use-livecode at
Please visit this url to subscribe, unsubscribe and manage your subscription 



More information about the Use-livecode mailing list