Yes, that is the basic idea... whatever is going to be the least demanding on system memory will work best. Use actual thumbnails when possible; load images into memory only when needed.
Another method to consider is to keep the images out of the stack; encrypt the images on disk (encrypt command); and decrypt them (decrypt command) as they are loaded. This will make them slightly larger on disk and use more memory, but it will keep your stack small and stable. Keep in mind that without extreme workarounds (i.e., using certain DirectX routines), images are never really secure on a computer; a press of the Print Screen button will put that picture on the clipboard. By embedding them in a stack or encrypting the image files on disk, you're only making it a little less difficult to access them. Bill ----------------------- Rob Cozens wrote: > Would it help to: > * Set images' alwaysBuffer to false? > * Replace Photo Index Card's buttons with images whose imageData > is set to the imageData of the thumbnail image? _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
