Regression in wxMSW `wxPropertyGrid` on DPI change (Issue #26490)

33 views
Skip to first unread message

taler21

unread,
May 21, 2026, 2:05:45 AM (14 days ago) May 21
to wx-...@googlegroups.com, Subscribed
taler21 created an issue (wxWidgets/wxWidgets#26490)

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.

To Reproduce:

  1. Start the propgrid sample at a DPI scaling of 200%.
  2. Go to 'File' > 'Run Minimal Sample'
    The wxPropertyGrid in the opened dialog looks like this.
    propgrid-DPI-200_started.png (view on web)
  3. Change the DPI scaling to 100% or move the dialog to a monitor with such DPI scaling.
  4. Set the DPI scaling back to 200% or move the dialog back to the original monitor.
    The text in the wxPropertyGrid now appears in a size that is much too small.
    propgrid-DPI-200_moved-back-from-DPI-100.png (view on web)

Platform and version information

  • wxWidgets version you use: master (bbad4b8)
  • wxWidgets port you use: wxMSW
  • OS and its version: Windows 11


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.Message ID: <wxWidgets/wxWidgets/issues/26490@github.com>

VZ

unread,
Jun 1, 2026, 6:42:28 PM (2 days ago) Jun 1
to wx-...@googlegroups.com, Subscribed
vadz left a comment (wxWidgets/wxWidgets#26490)

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.Message ID: <wxWidgets/wxWidgets/issues/26490/4597080201@github.com>

VZ

unread,
Jun 1, 2026, 6:47:36 PM (2 days ago) Jun 1
to wx-...@googlegroups.com, Subscribed
vadz left a comment (wxWidgets/wxWidgets#26490)

... 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.Message ID: <wxWidgets/wxWidgets/issues/26490/4597107223@github.com>

Maarten

unread,
Jun 1, 2026, 7:29:56 PM (2 days ago) Jun 1
to wx-...@googlegroups.com, Subscribed
MaartenBent left a comment (wxWidgets/wxWidgets#26490)

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.Message ID: <wxWidgets/wxWidgets/issues/26490/4597312845@github.com>

VZ

unread,
Jun 1, 2026, 7:37:03 PM (2 days ago) Jun 1
to wx-...@googlegroups.com, Subscribed
vadz left a comment (wxWidgets/wxWidgets#26490)

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.Message ID: <wxWidgets/wxWidgets/issues/26490/4597345998@github.com>

taler21

unread,
Jun 2, 2026, 3:23:45 AM (yesterday) Jun 2
to wx-...@googlegroups.com, Subscribed
taler21 left a comment (wxWidgets/wxWidgets#26490)

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.Message ID: <wxWidgets/wxWidgets/issues/26490/4599731575@github.com>

VZ

unread,
Jun 2, 2026, 8:55:39 AM (yesterday) Jun 2
to wx-...@googlegroups.com, Subscribed

Closed #26490 as completed via cda683d.


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.Message ID: <wxWidgets/wxWidgets/issue/26490/issue_event/26237630975@github.com>

Reply all
Reply to author
Forward
0 new messages