"peed off" with P Lists

[Peter Haworth]

I believe "mainstack" refers to your actual main stack, the one you loaded
into the IDE to do the build, not the standlone, which would be Devawriter
Pro/Contents/Mac OS/Devawriter Pro.

You can modify the plist file within Contents any time and the app will see
the changes next time It runs.  I haven't done it in savingStandalone but I
have a script that creates my standalone and then code signs it (which
changes the plist) after the standalone is built.

Or maybe I'm misundertsing what you need to do….

Pete
lcSQL Software <http://www.lcsql.com>



On Mon, Jul 30, 2012 at 11:25 PM, Richmond <richmondmathewson at gmail.com>wrote:

> On 07/30/2012 11:49 PM, Peter Haworth wrote:
>
>> There's a standaloneSaved message that you can use for that purpose.
>> Pete
>> lcSQL Software <http://www.lcsql.com>
>>
>>
> Indeed, and I quote "After a stack has been saved as a standalone
> application it is reopened. This message is then sent to the mainstack to
> allow custom build automation".
>
> To which I would reposte with a wee diagram of the folder structure of a
> Mac standalone:
>
> Devawriter Pro/Contents/Info.plist
> Devawriter Pro/Contents/Mac OS/Devawriter Pro
> Devawriter Pro/Contents/Mac OS/Externals/
> Devawriter Pro/Contents/PkgInfo
> Devawriter Pro/Contents/Resources/**Lottsastuff
>
> I assume that by "mainstack" the Documentation, in this instance, refers
> to Devawriter Pro/Contents/Mac OS/Devawriter Pro
>
> which would seem to indicate that once the standalone has been built
> things are a bit late in the day for the IDE to modify the plist.
>
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>