We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
9.0.5
Not tested/verified
Code used to work. Seems like a regression in either dotnet or windows itself
Tracking for zooming a graph in an application that has been working for many years suddenly started misbehaving around 12/2024.
With multiple monitors only, the graphics operations appear in an incorrect position on the desktop, outside of the application's window.
See demo code below.
Also see this stack overflow issue:
https://stackoverflow.com/questions/79595420/system-windows-form-method-controlpaint-drawreversibleframe-seems-to-have-a-bu
Run this app on a system with latest windows and multiple monitors. https://github.com/coderb/DrawReversibleLineBug
The text was updated successfully, but these errors were encountered:
No branches or pull requests
.NET version
9.0.5
Did it work in .NET Framework?
Not tested/verified
Did it work in any of the earlier releases of .NET Core or .NET 5+?
Code used to work. Seems like a regression in either dotnet or windows itself
Issue description
Tracking for zooming a graph in an application that has been working for many years suddenly started misbehaving around 12/2024.
With multiple monitors only, the graphics operations appear in an incorrect position on the desktop, outside of the application's window.
See demo code below.
Also see this stack overflow issue:
https://stackoverflow.com/questions/79595420/system-windows-form-method-controlpaint-drawreversibleframe-seems-to-have-a-bu
Steps to reproduce
Run this app on a system with latest windows and multiple monitors.
https://github.com/coderb/DrawReversibleLineBug
The text was updated successfully, but these errors were encountered: