[Use-revolution] Re: Image resizing
Jeanne A. E. DeVoto
jeanne at runrev.com
Fri Nov 23 17:05:00 CST 2001
At 10:30 AM -0800 11/23/2001, Shari wrote:
>>It's being scaled for display, not copied.
>>Scaling images is not recommended as a general rule, especially where
>>responsiveness is critical, because it does slow down display of images.
>>But obviously there are situations where it's not practical to create
>>separate images ahead of time in all the required sizes.
>So eventually the image will become corrupted?
No, that's what "being scaled for display" means. The actual image data
remains the same; the slowdown is because the engine needs to recompute the
scaling from scratch every time the image is displayed. (You wouldn't want
to use this technique, for instance, on a card with many images all of
which were scaled.)
But the original image data always remains the same, so scaling it
repeatedly won't corrupt it.
Jeanne A. E. DeVoto ~ jeanne at runrev.com
Runtime Revolution Limited - Power to the Developer!
More information about the use-livecode