You need savingStandalone if you want to pre-twiddle. StandaloneSaved is for post-twiddling like zipping and moving to a clients Dropbox share or building an installer.
Cheers -- M E R Goulding Software development services mergExt - There's an external for that! On 31/07/2012, at 6:38 PM, Richmond <richmondmathew...@gmail.com> wrote: > standaloneSaved: > > "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". > > What is reopened? > > 1. the original stack [at which point, if standalones have been hived-off > it is > difficult to see how this could affect the standalone]? > > 2. part of the standalone [this is also a bit funny, as in the case of Mac > standalones > the application bundle contains all sorts of components]? > > "custom build automation" > > What does this mean? > > 3. if the standalone has already been built this seems to be meaningless. > > The description in the Documentation is all rather unsatisfactory. > > ------------------------------------------------------------------------------ > > In an ideal world [Ho,Ho,Ho!] standaloneSaved would allow programmers to > 'twiddle about with' how a standalone is generated prior to the standalone > build process. > > Richmond. > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
