diff options
| author | Sven Gothel <[email protected]> | 2013-09-27 15:31:17 +0200 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2013-09-27 15:31:17 +0200 |
| commit | 3abff83dbc0a99c8d227788c9dddbe59cd15b9ba (patch) | |
| tree | 20e4530c4786e6ca355d140ee8a8ac477e714892 /src/test-native/displayMultiple02_mch.c | |
| parent | 469311764a1cb3c3af8439c1638160926741c1e5 (diff) | |
Fix Bug 816: JAWTWindow.getLocationOnScreenNonBlocking(..) shall use JRootPane for last position offset; AWTMisc.getInsets(..) add special JRootPane case.
Please note that we use JAWTWindow.getLocationOnScreenNonBlocking(..) to determine the
location on the screen 'only' b/c we cannot allow AWT to aquire the tree-lock!
The latter would be the case if using AWT's 'getLocationOnScreen()'.
If anybody has a more reliable implementation to achieve the same .. please provide your patch!
The following fix has been performed to fix the last issue w/ vZome.
- JAWTWindow.getLocationOnScreenNonBlocking(..) shall use JRootPane for last position offset
- w/ vZome, the frame's position was 0/0 (invalid), instead JRootPane's position is good.
Use JRootPane's position and stop traversing here (LW top-level).
- AWTMisc.getInsets(..) add special JRootPane case.
+ * Exception is JRootPane.
+ * Return it's parent's Window component's insets if available,
+ * otherwise return JRootPane's insets.<br>
+ * This is due to <i>experience</i> that <i>some</i> JRootPane's
+ * do not expose valid insets value.
-
Diffstat (limited to 'src/test-native/displayMultiple02_mch.c')
0 files changed, 0 insertions, 0 deletions