Hello all,

I'm puzzling a bit more about how GridCoverageRenderer handles a world
to screen transform supplied by the cient...

Looking again at the GridCoverageRenderer code I see that I didn't
read the comments properly and the code does indeed do what is
advertised: ie. only uses the supplied transform it it is non-mull AND
contains a rotation.

But this means that in all other cases the client has to tailor the
paint area's proportions so that GridEnvelopeMapper will return a
correct affine transform, whereas when displaying vector data the
ciient doesn't have to worry about this.

Is there a problem with just accepting any non-null transform supplied
by the client and only falling back to GridEnvelopeMapper when no
transform is provided ? I've attached a new patch to the issue that
does this, but I suspect I must still be missing something in the
existing logic.

Michael

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to