DPI API Fixes for Wpf on Windows 7 #2297
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
|
Thanks for the fix! Looks great. |
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 commit fixes the crashes I experienced as described in #2295. It makes everything work in my application and it should probably make everything else work too, but imo these APIs are not exposed or checked very well.
@cwensley I'd like to first merge this and then implement a much more thorough fix that will expose only APIs with error checking and fallbacks (i.e. 1 method for get dpi, try set awareness, get awareness, & whatever else is needed) - this would avoid something like this happening in the future with these APIs.
This PR just adds fallbacks to the
SystemDpiandIsSystemDpiAwareAPIs that work on Windows 7.