Box.x and Box.y flawed [Bug 502]
Charles Goodwin <[email protected]>
| Newsgroups | gmane.comp.java.xwt.core |
|---|---|
| Organization | XWT Foundation |
| Message-ID | <[email protected]> |
This, frankly, sucks. It's incredibly annoying putting one value to a property to get another completely different value back. I must say that I _greatly_ prefer the absolute method (ie origin being parent's topleft) to the inline method (ie origin being a boxes starting position) for using x/y. But, either way, box x/y reading needs to be the same as box x/y writing. -----Forwarded Message----- From: [email protected] To: [email protected] Subject: [xwt-bugs] [Bug 502] New: Box.x and Box.y flawed Date: Mon, 15 Mar 2004 06:31:17 -0800 http://bugs.xwt.org/show_bug.cgi?id=502 Summary: Box.x and Box.y flawed Product: Ibex Version: unstable Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: Core AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] When you put to Box.x or Box.y, it transforms the box relatively from it's starting position. Yet when you read from Box.x and Box.y, it gives a value relative to the parent's topleft corner. This is incredibly counter-intuitive. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ bugs mailing list [email protected] http://lists.xwt.org/listinfo/bugs -- - Charlie Charles Goodwin <[email protected]> Online @ http://www.charlietech.com