Saving stack with a large number of cds

[Geoff Canyon]

As noted by Edwin, this is a consequence of the way Revolution handles 
stacks (loading them entirely into memory). Consider storing the data 
externally and reading it in. On a machine like that the data could be 
as much as 50MB or more and probably you could still read it into an 
array and reference it into a 1-card stack. It would be much faster 
that way.

On the Application Browser, take a look at revNavigator (shareware I 
wrote) it does many of the same things, and allows you to limit the 
number of cards to be displayed while still displaying whichever card 
you're on.

On Wednesday, July 9, 2003, at 09:36  AM, Joël Guillod wrote:

> I have a stack with 13752 cards and found that it takes more than 40 
> secs to
> save it after just having edited the script of the stack.
>
> I run under MacOSX 10.2.6, G4 1Gz, 500MB RAM. Is this duration 
> expected or
> is there something wrong?
>
> And do not try to open the Application Browser or a Property palette
> otherwise it takes many minutes before giving me the hand back (of 
> course,
> it tries to load a list of all cds names...). After 5+ minutes, I 
> canceled
> it...
>
> Cheers,
>
> Joel
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>

regards,

Geoff Canyon
gcanyon at inspiredlogic.com