RFR: 6899304 : java.awt.Toolkit.getScreenInsets(GraphicsConfiguration) returns incorrect values
anass baya
duke at openjdk.org
Thu Jan 23 22:10:44 UTC 2025
Screen number 0 is not always the primary screen, so we’ve removed the code that assumes it is.
We used an existing test and took the following considerations into account for Windows:
- On Windows, undecorated maximized frames are placed over the taskbar.
- On Windows, the top-left corner of an undecorated maximized frame may have negative coordinates (x, y).
- Consider the fractional part after scaling.
-------------
Commit messages:
- Remove trailing whitespace.
- delete whitespaces
- annotations adjustmentx
- Test to verify that java.awt.Toolkit.getScreenInsets(GraphicsConfiguration) returns xcorrect values
- Remove extralines
- Screen number 0 is not always the primary screen
- Screen number 0 is not always the primary screen.
Changes: https://git.openjdk.org/jdk/pull/23183/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=23183&range=00
Issue: https://bugs.openjdk.org/browse/JDK-6899304
Stats: 72 lines in 2 files changed: 38 ins; 20 del; 14 mod
Patch: https://git.openjdk.org/jdk/pull/23183.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/23183/head:pull/23183
PR: https://git.openjdk.org/jdk/pull/23183
More information about the client-libs-dev
mailing list