Skip to content
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

Fix dpi changed handling in the windows #202

Closed
dsafa opened this issue Jul 11, 2019 · 0 comments · Fixed by #215
Closed

Fix dpi changed handling in the windows #202

dsafa opened this issue Jul 11, 2019 · 0 comments · Fixed by #215
Labels
bug Something isn't working

Comments

@dsafa
Copy link
Owner

dsafa commented Jul 11, 2019

Describe the bug
If the settings window is dragged from one monitor to a monitor with a different dpi, the mouse is in the wrong relative position. Also it may get caught in a resize loop.

To Reproduce
Steps to reproduce the behavior:

  1. Have two monitors with different DPI
  2. Move the settings window from one to another

Expected behavior
The window will be adjusted properly for the new dpi. The mouse stays in the same relative position.

Actual behavior
The mouse is in a different relative position. Sometimes the window will also glitch out.

Details
Since the WM_DPICHANGED changed message is manually handled, it should actually be handled properly. Currently the lparam is ignored when it shouldn't be. Using the suggested rect provided should be enough to fix the issue.

Version Info

  • Windows 10 1903
  • AudioBand Version 0.9.2
@dsafa dsafa added the bug Something isn't working label Jul 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant