AW: AW: stack design with externals?

Tiemo Hollmann TB toolbook at kestner.de
Mon Oct 20 03:22:42 EDT 2008


Hi Mark,
I didn't though about not to use destroyStack, good idea
Thanks
Tiemo

> -----Ursprüngliche Nachricht-----
> Von: use-revolution-bounces at lists.runrev.com [mailto:use-revolution-
> bounces at lists.runrev.com] Im Auftrag von Mark Schonewille
> Gesendet: Montag, 20. Oktober 2008 09:15
> An: How to use Revolution
> Betreff: Re: AW: stack design with externals?
> 
> Hi Tiemo,
> 
> The easiest way probably is to build your standalone with all needed
> externals. As far as I know, the externals stay available after the
> splash stack that is used to build the standalone closes. If in doubt,
> set the destroyStack property of the splash stack to false.
> 
> --
> Best regards,
> 
> Mark Schonewille
> 
> Economy-x-Talk Consulting and Software Engineering
> http://economy-x-talk.com
> http://www.salery.biz
> Dutch forum: http://runrev.info/rrforum/
> 
> Benefit from our inexpensive hosting services. See http://economy-x-
> talk.com/server.html
>   for more info.
> 
> On 20 okt 2008, at 09:08, Tiemo Hollmann TB wrote:
> 
> > Hello,
> > Hmm no answers - did I asked the wrong questions or was my
> > explanation too
> > complicated? The main question is, where to assign externals when
> > using a
> > splash stack, which becomes the executable (but doesn't needs the
> > externals)
> > and a main stack which stays a .rev and needs the externals. Is it
> > enough
> > just to put them into the properties\externals of the called main
> > stack
> > (rev-file) and I don't need the "binding" functionality for the
> > externals,
> > when building the standalone of the splash stack?
> > Any hint welcome :)
> > Tiemo
> 
> _______________________________________________
> 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