Jacqueline Landman Gay wrote:
>
> "Raymond E. Griffith" wrote:
> >
> > On 6/13/2000 11:05 PM Jacqueline Landman Gay <[EMAIL PROTECTED]>
> > wrote:
> > >
> > >
> > > I've got a stack that repeatedly sets the filename property of various
> > > images. Is there a way to keep these in memory even a
Recently, Jacqueline Landman Gay at [EMAIL PROTECTED] wrote:
> if there is
> a way to "preload" images and have them stay in RAM, I'd like to know
> for future reference.
You can load them offscreen.
One technique you might use is to reference images locally within your stack
via a button objec
>Not exactly. Getting the filename isn't a problem; I'm trying to avoid
>the hit that happens when you load an image from disk.
>
>I spent the evening putting the images into the stack and changing
>everything to use buttons with icons. It seems snappier. But if there is
>a way to "preload" ima
"Raymond E. Griffith" wrote:
>
> On 6/13/2000 11:05 PM Jacqueline Landman Gay <[EMAIL PROTECTED]>
> wrote:
> >
> >
> > I've got a stack that repeatedly sets the filename property of various
> > images. Is there a way to keep these in memory even after the image
> > content changes so that, once l
On 6/13/2000 11:05 PM Jacqueline Landman Gay <[EMAIL PROTECTED]>
wrote:
>
>
> I've got a stack that repeatedly sets the filename property of various
> images. Is there a way to keep these in memory even after the image
> content changes so that, once loaded in, they are immediately available?
>
