At 11:47 PM -0600 12/17/00, Jacqueline Landman Gay wrote:
>I wonder if creating a different player object for each movie would
>help, rather than trying to load the movies into the same object. There
>are only about ten movies, so it wouldn't be too hard to hide and show
>various players if it would fix the problem. I don't want to put the
>effort into changing the stack if it won't help though. Anyone know if
>this would help?
You should definitely try the acceleration and safe mode suggestions first--
The above is close to my suggestion, but not quite the same: I would
suggest using a new player for each movie, _destroying_ the old one
each time. Scott can speak to memory issues much more authoritatively
than I, of course, but I think hiding the players will retain their
memory, building up a large memory block. I'd try to remove the
player's hold on memory, first by simply deleting the player, then by
deleting it and going to a different card, etc. There may be a
setting for this that is all you need to do--I don't know offhand.
But in a worst case scenario, would it be possible to have a special
one-card stack, just for the purpose of displaying these movies, with
destroystack, etc. set, and close and reopen that stack for each
movie to be displayed?
Regards,
Geoff
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
