The component access methods of AffineTransform are perhaps poorly
named. They might have been more accurately named getM00, getM01, etc.
but the problem with that naming convention is that you have to be
very familiar with how transform matrices work and how this particular
implementation uses them (is it row or column based) in order to know
which one will give you the information you want.
In an attempt to make them more readily accessible for developers I
came up with the semi-descriptive names get[Scale/Shear/Translate][X/Y]
to provide a primitive semantic reminder about which call to use to
grab the information that you might want. Unfortunately and in retrospect
the names do definately imply that the methods are magically decomposing
the transformation sequence into an identifiable scaling operation and
returning the necessary information.
I'm not sure there is a good naming convention that is both semantically
helpful and yet mathematically unconfusing, but this is all water under
the bridge. At least they are documented pretty explicitly as to what
information they are returning.
...jim
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
