lockLoc [was Re: Alpha Channel?]

[Graham Samuel]

On Thu, 10 Jun 2004 15:34:01 +0100, Frank Leahy <frank at backtalk.com> wrote:

[a long - but not too long! - and reasoned explanation of why RunRev 
remembers the original size of a graphic]

Frank, thanks for all that. I'm a digest reader, so maybe this conversation 
has swept past this, but I think what your explanation shows me is that 
there are many completely different ways of looking at issues like this. I 
see now that my sole interest to do with images has always been to show 
them **at the screen resolution**, because the kind of stuff I've done up 
to now is basically viewed rather than kept for later printing etc. So the 
change of size of an image to me means just that, like it does in 
Photoshop: if you change the size of an image, by default you keep the 
original resolution and thus lose detail. In my context, this has never 
been a problem, all images having the screen resolution - but as you point 
out, it could well be very bad news in some other contexts. So I will live 
with the lockLoc way of doing things.

A parallel case is perhaps shown by my interest in being able to print to 
the maximum available printable area on a page: this seems to me a must for 
any even vaguely print-oriented app, yet I was met with incomprehension 
and/or indifference from people on this list when I pointed out that RR 
doesn't have a way of getting at printer driver APIs in particular so as to 
see minimum margins. I've put this in Bugzilla as an enhancement request 
(#1619 - vote if you agree with me!). I was seeing it one way, and other 
people couldn't see what the fuss was about. I guess differences of view 
are a consequence of the extremely wide range of uses to which a tool like 
RunRev can be put.

Graham


---------------------------------------------------
Graham Samuel / The Living Fossil Co. / UK & France