Just to continue on this meditation for any future forum browsers who find it useful....
Merely recording in a 3rd party object the "actual" position of the Shape for the purpose of rendering isn't going to cure Shape's woes when it's used on screen in a position-mutable capacity. Shape has several methods which depend upon accurate representation its origin (ULHC) to perform their function. contains() and intersects() are two of these. If anyone were to query any of these methods, they'd get a "wrong" answer also, just as they would if they asked it for its bounding box. So it's not just about rendering in the proper place via translation or translating mouse events. Creating a custom Shape implementation which overrides contains and intersects to report accurately is fine, but existing implementors of Shape all have the uncorrected problem. Are we to override them also? If composition is used, then any any access to the internal Shape has to be forbidden, since it provides uncontrolled access to the defective contains and intersects. Now we have quite a little design problem on our hands. [Message sent by forum member 'swv' (swv)] http://forums.java.net/jive/thread.jspa?messageID=228024 =========================================================================== 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".
