-
Notifications
You must be signed in to change notification settings - Fork 542
8371302: [Windows] Stage coordinates in secondary display are not properly updated after changing settings of first display #1963
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
👋 Welcome back jpereda! A progress list of the required criteria for merging this PR into |
|
@jperedadnr This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 5 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
I'd like to review and test this, both in isolation and in connection with #1964 /reviewers 2 |
|
@kevinrushforth |
|
For testing, I've added the scale/size/position info to the main window status bar in the monkey tester: |
andy-goryachev-oracle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on windows, using the latest master + this PR + #1964
The windows, their child windows, their popup menus all work as expected when changing scale and adjusting relative position of the monitors.
Excellent work chasing all these issues!
kevinrushforth
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code changes look good. My initial testing looks good. I'll do some final testing tomorrow.
kevinrushforth
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All testing looks good. This is a safe and simple change.
This PR handles two windows events,
WM_DISPLAYCHANGEandWM_SETTINGCHANGE, that can be received by a JavaFX Window on a given display when other display changed its settings (resolution), or both displays were rearranged, and therefore its location has changed.When this happens,
com.sun.glass.ui.Windowhas the new updated location, but thejavafx.stage.Windowdoes not, and triggering aWindow.MOVEevent notifies the stage to update its location accordingly.There are no tests added to this PR (those would require two monitors, and external changes of Windows Settings), but the test attached to the JBS issue passes after this PR running some manual tests: for the stage at secondary display, check that the location is updated properly and the context menu shows up at the expected position, when the primary display resolution changes via Settings->System->Display->Scale, or when both displays are rearranged via Settings->System->Display->Drag to rearrange.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jfx.git pull/1963/head:pull/1963$ git checkout pull/1963Update a local copy of the PR:
$ git checkout pull/1963$ git pull https://git.openjdk.org/jfx.git pull/1963/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1963View PR using the GUI difftool:
$ git pr show -t 1963Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jfx/pull/1963.diff
Using Webrev
Link to Webrev Comment