Since #25808 (Don't enable WS_EX_COMPOSITED by default in wxMSW any longer, 2025-09-23) text appears too small when a wxPropertyGrid is moved to a monitor with higher DPI.
In 3.2 it works fine, so I think the actual culprit change must be a different one.
The regression can also be seen in the propgrid sample.
wxPropertyGrid in the opened dialog looks like this.wxPropertyGrid now appears in a size that is much too small.—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()
Thanks, I can see this. It's really weird that it happens only to the minimal sample and not the main propgrid, I wonder what is the difference between them...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
... must be the use of wxPG_EX_NATIVE_DOUBLE_BUFFERING.
So it's just a refresh problem, apparently.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
I think it does have to do with wxPG_EX_NATIVE_DOUBLE_BUFFERING. The scale of m_doubleBuffer is not updated after a DPI change.
-if ( w < width || h < (height+dblh) ) +if ( w < width || h < (height+dblh) || scaleFactor != m_doubleBuffer->GetScaleFactor() )
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
Yes, you're right, I was just typing the comment saying that this particular herring was not red at all but didn't want to do in too much haste to avoid correcting myself once again.
Anyhow, #26549 should fix this (maybe not in the most efficient way, as we could just change the scale factor at least when increasing the DPI, but I don't think we really care), @taler21 please let me know if you still see any problems with it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
I can confirm that #26549 fixes this issue. Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()