dump newbie image questiosn

[John Ridge]

Did you get any response to this query? If so, I've missed it - no surprise,
given the volume!

I got interested in the issue, and have been playing with the lockLoc
property of the image. I do find the language confusing - the "image" is the
control within which you display a JPEG (say). When lockLoc is true, the
image (the control) stays as is, and the picture is forced to fit within it
- which can lead to  massive distortion, of course. When lockLoc is false
(the default) the picture arrives in its native size - so your image may
turn out to be a small window into it. You can grab the image and slide it
around under the window. I've also done a ShrinkToFit handler, but I bet
there are better ways of doing the job!

If you're interested, I can send the stack to the User Space, or
somewhere...

Regards,
John
-- 


From: Jon <jbondy at sover.net>
Reply-To: How to use Revolution <use-revolution at lists.runrev.com>
Date: Wed, 01 Jun 2005 15:20:17 -0400
To: Revolution List <use-revolution at lists.runrev.com>
Subject: dump newbie image questiosn


Is there any way to specify the magnification ratio of the image (the
ratio between the native/intrinsic size and the displayed size)?  One
might want to alter this ratio in order to "zoom" or "unzoom" an
image.   Note that I do NOT want a separate "zoom" window or magnifier.
I want to take a image and either display it to "fit" in a window, or
display it "normally" (1:1).

Is there any way to specify the displayed width of an image independent
of the actual width of the image (in pixels)?  One might want to do this
to "fit" an image into a fixed screen space, even if it is larger or
smaller (in pixels) than the screen space.

I've tried to manipulate real (large) images using the pixels, and have
found Revolution to be stunningly slow (perhaps 100 times slower than
native code).  Am I doing it "wrong", or is Revolution aimed at doing
things other than manipulating millions of pixels in tight loops?

Thanks!

Jon