How to manage memory load in standalone substacks?

David Burgun dburgun at dsl.pipex.com
Tue Apr 18 14:56:45 EDT 2006


Hi,

I think you'd be better off holder the video clips in a separate file  
and loading them dynamically when you need them. Apart from anything  
else it will be hard to ship a 75+ MB Stack File!

I can give you some pointers if you need them.

All the Best
Dave

On 18 Apr 2006, at 19:49, Ben Bock wrote:

> I have to build a standalone, and I'm now working on the splash  
> screen and management scripts for the 10 substacks.  Some of the  
> substacks are ~75 MB, and one has 5 different videoclip players.     
> I don't want to use up all RAM, and don't understand the ins and  
> outs of the substacks in a standalone.  I will need to open the 5  
> videoclips at different times throughout the standalone.  Does a  
> Rev standalone only load these when needed, or load all substacks  
> when the splash screen is opened?  How do you limit what opens to  
> save RAM and avoid slowing?
>
> I would like something along the lines of this in the last card of  
> the splash screen, which might be buggy:
>
> on mouseUp
> close this stack
> open stack "videoclips" -- But I only want a single videoclip to  
> load at a time
> go card "video 1" of stack "videoclips" --and have the videoclip load
> end mouseUp
>
> --then the player plays the clip, the player script:
>
> on playStopped
>
> hide me
>
> end playStopped
>
> lock messages
>
> -- prevent sending playStopped down the line
>
> unlock messages
>
> close stack "videoclips"
>
>
>
> I suspect the answer is easy, but I haven't find straight answers  
> in searching the docs.  I may have made several mistakes in these  
> scripts, I'm still new with Rev.
>
> thanks for any help,
>
> Ben
> _______________________________________________
> 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