standalone image problem

Chipp Walters chipp at chipp.com
Sun Nov 7 12:52:40 EST 2010


Not sure if this helps, but I usually set the filename to empty, THEN
set it to the specific file when swapping out files with the sane
name.

On Sunday, November 7, 2010, Richard Gaskin <ambassador at fourthworld.com> wrote:
> J. Landman Gay wrote:
>
>> On 11/6/10 12:29 PM, Richard Gaskin wrote:
>>> For many years the engine used the folder where the executable
>>> resides as the defaultFolder, which for Mac was inside the
>>> bundle - when did this change?
>>
>> I can't find a reference to the change in any of the change docs I
>> looked at, but sure enough, it's changed somewhere along the way.
>> I'm sort of surprised I hadn't noticed till now, but I usually
>> don't depend on the (default) defaultfolder in my standalones.
>> Generally I set it myself if I need it.
>
> Me too.  I figure any property subject to change at any time by any script needs to be saved, set to what I need explicitly, then restored when I'm done.
>
> Thanks for the reality check, since I couldn't find mention of when it changed either but felt (almost) certain I wasn't imagining that it had previously been different.
>
> Now that I think about it a bit more I wonder if that change was concurrent with the change to how image paths are found, maybe somewhere in the v3.0 time frame....
>
> --
>  Richard Gaskin
>  Fourth World
>  LiveCode training and consulting: http://www.fourthworld.com
>  Webzine for LiveCode developers: http://www.LiveCodeJournal.com
>  LiveCode Journal blog: http://LiveCodejournal.com/blog.irv
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



More information about the Use-livecode mailing list