-
Notifications
You must be signed in to change notification settings - Fork 9
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
PSX preparations #1786
Merged
Merged
PSX preparations #1786
Changes from 1 commit
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
35274ff
SUBWINDOW_MOVE_CORRECTION: Add constant
t-b ac5c066
IsSubwindow: Add it
t-b 0b275b9
PixelToPoints/PointsToPixel: Add them
t-b 9753e1c
PS_InitCoordinates: Allow to store the coordinates of exterior subwin…
t-b 97b81e9
UpdateInfoButtonHelp: Add it
t-b 2902c0a
SFH_GetFormulaGraphs: Factor it out
t-b 0f28b8e
SFH_CreateResultsWaveWithCode: Store the name of the browser as well
t-b 974702f
LimitWithReplace: Add it
t-b 5d326cc
HASH_SHA2_256: Introduce constants
t-b 00b5568
SFH_GetArgumentAsNumeric/SFH_GetArgumentAsText: Add optional paramete…
t-b 4f5b91c
IsFunctionCalledRecursively: Factor it out
t-b c57b1a1
PS_COORDINATE_SAVING_HOOK: Introduce constant
t-b f08b5f6
PS_RemoveCoordinateSaving: Add it
t-b 13cf1e7
StoreCurrentPanelsResizeInfo: Fix typo and grammar
t-b 2f5073f
CA_OutputCacheStatistics: Output three decimal digits for the timestamps
t-b 9160560
GetOverrideResults: Fix comment
t-b 7749c59
PSQ_CreateOverrideResults/TP_CreateOverrideResults: Prefer GetOverrid…
t-b 80da1fd
SFH_GetArgumentAsText/SFH_GetArgumentAsNumeric: Enhance error messages
t-b File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
I suspect the reason is:
"By default, panels are drawn using pixels if the screen resolution is 96 DPI but using points for higher-DPI settings. This gives backward compatibility on standard screens and reasonably-sized controls on high-resolution screens."
from
DisplayHelpTopic "Control Panel Resolution on Windows"
from
DisplayHelpTopic "Control Panel Units"
at 100% GUI scaling in windows
print screenresolution
results in 96 in IP.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.
But why is that only relevant for exterior subwindows?
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.
I think because MoveWindow coordinates are always in "points".
Whereas MoveSubWindow are in "points" or "control panel units". If it is "control panel units" then the mentioned distinction for screenresolution == 96 dpi -> pixels, otherwise points kicks in.
What is a bit unclear to me is, that the MoveSubWindow docu states: "coordinates are taken to be fixed locations measured in points, or control panel units for control panel hosts".
Because according to that, it should be like: