Use of images

[xavier.bury at clearstream.com]

Christian,

In the revdocs, look at the stack properties. "alwaysbuffer", 
destroywindow, and destroystack"

And, set the destroystack of this stack will not destroy it ;)

One solution would be to copy at runtime the images you need from the 
other stacks and use those
new images' ids... 

Depends on what you need to do... 

cheers
Xavier

use-revolution-bounces at lists.runrev.com wrote on 02/01/2006 13:17:59:

> 
> Le 2 janv. 06 à 13:00, xavier.bury at clearstream.com a écrit :
> 
> > Hi Christian
> >
> > the image path example is probably the easiest.
> >
> > The other method would require loading the stack in memory causing
> > problems on low memory
> > conditions... You would also have to consider watching image id 
> > conflicts
> > if you want to edit those
> > and possibly other issues like network latency saving your stack 
> > and the
> > like...
> >
> 
> > One solution to that would be to split up the images across a few 
> > stacks
> > to reduce the memory
> > footprint but still it would innelegant unless you want to secure your
> > images so no one copies them...
> 
> Is there not the problem that closing a stack in standalones  will 
> not removing them acually from memory ?
> 
> So loading them when needed will not remove them and so the memory 
> problem persists...?
> 
> 
> Christian
> 
> 
> >
> > cheers
> > Xavier
> >
> > use-revolution-bounces at lists.runrev.com wrote on 02/01/2006 12:53:40:
> >
> >> Hello,
> >>
> >> I have to work with about 280 images making about 200mb.
> >>
> >> which method would have the best performance in Rev :
> >>
> >> - letting the images outsite the app and setting the filename of img
> >> to them
> >> - importing them in a stack and working with it as an invisible stack
> >> (referring to them by setting the icon of a button to the id of imgs)
> >>
> >>
> >> ???
> >>
> >> Thanks for any reflection,
> >>
> >> Christian L.
> >
> >
> >
> > -----------------------------------------
> > To make communications with Clearstream easier, Clearstream has
> > recently changed the email address format to conform with industry
> > standards. The new format is 'firstname.familyname at clearstream.com'.
> >
> > Visit us at http://www.clearstream.com
> >
> > IMPORTANT MESSAGE
> >
> > Internet communications are not secure and therefore Clearstream
> > International does not accept legal responsibility for the contents of
> > this message.
> >
> > The information contained in this e-mail is confidential and may be
> > legally privileged. It is intended solely for the addressee. If you 
> > are
> > not the intended recipient, any disclosure, copying, distribution or
> > any action taken or omitted to be taken in reliance on it, is
> > prohibited and may be unlawful. Any views expressed in this e-mail are
> > those of the individual sender, except where the sender specifically
> > states them to be the views of Clearstream International or of any of
> > its affiliates or subsidiaries.
> >
> > END OF DISCLAIMER
> > _______________________________________________
> > 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
> 
> _______________________________________________
> 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