HighDPI Screen Scaling #98
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… scaling, e.g. 225%) for High DPI screens like 4K
Closed
|
Thank you, I will test and merge this over the next days. |
DubbleClick
force-pushed
the
ScreenScaling
branch
from
f570355
to
d8b6824
Compare
|
Removed the howto commit, but the positioning seems to work ok. since there's no chance for 100% scaling, I'll merge this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes issue #97:
Class ScreenScaling calculates the screen scaling factor set in windows under System -> Screen: Scaling (e.g. 225%) which is typically used for high screen resuolutions such as 4K screens.
MainForm::NotifyIcon_MouseClick calculation are fixed by taking into account the screen scaling factor - therefore MainForm will always be placed correctly on the screen for any scaling factor set.
Note: this change is completely transparent for users who don't use screen scaling and has no effect in this case:
X / 1 = X * 1 = X --> calculations remain unchanged
Note2: With this change the application remains DPI-unaware so no major redesign of the GUI is required