-
Notifications
You must be signed in to change notification settings - Fork 186
Initialize nativeZoom from Shell via OS call #2196
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
Initialize nativeZoom from Shell via OS call #2196
Conversation
fd4658a to
ba0696a
Compare
|
This pull request changes some projects for the first time in this development cycle. An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patchFurther information are available in Common Build Issues - Missing version increments. |
ba0696a to
057aa81
Compare
akoch-yatta
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.
Changes look good to me. I tested it a bit (opening sub-shells or second workbench windows, moving around, re-opening) with the latest I-Build by replacing the Shell class in the jar and didn't find any issues with it.
057aa81 to
e56e184
Compare
|
@ShahzaibIbrahim can you please document/link the failing tests and also bump the versions in the appropriate MANIFEST and POM files? You can use the Git patch that the bot created (#2196 (comment)) as a reference. |
HeikoKlare
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.
Is this just supposed to be a simplification or does it also improve the behavior in some situations, does it allow to remove some other tweaks or the like?
It also improves behavior in some situation as mentioned here in this ticket -> vi-eclipse/Eclipse-Platform#315 (comment), but this issue only happens with ibuilds not runtime workspace. That's why we have checked if this change doesn't break anything. |
e56e184 to
334c9af
Compare
|
Okay, I will need to have a deeper look. This seems almost identical (except for the parent check) than #2165, which produced a severe regression when I tested it. The mentioned ticket also asks to reevaluate vi-eclipse/Eclipse-Platform#241, so whether the issue can be solved without this workaround: eclipse-platform/eclipse.platform.ui#2948 Did you already test that? Is that a scenario that we can use to valudate the improved behavior due to this PR? |
334c9af to
b2bd61a
Compare
Shell can be created on secondary monitor but inheriting the zoom of parent (which could be on primary monitor) means the DPI change will not be triggered.
b2bd61a to
00c5b11
Compare
bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Shell.java
Show resolved
Hide resolved
|
FTR the failing check is unrelated and the versions have been bumped in Check failure (check-versions)
@HannesWell WDYT? |
bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Shell.java
Show resolved
Hide resolved
This is really strange. Sorry, I don't had the time yet to look into this, but I try to do it ASAP. |
|
No worries, it seemed pretty clear that this PR wasn't to blame so I went ahead and merged it :-) . Yesterday's I-BUILD seems "OK" (for SWT at least --> eclipse-jdt/eclipse.jdt.ui#2287) |
Shell can be created on secondary monitor but inheriting the zoom of parent (which could be on primary monitor) means the DPI change will not be triggered.