Opened 12 years ago

Closed 7 years ago

#11008 closed defect (fixed)

wxWidgets controls don't use the user-configured large font

Reported by: vegpuff Owned by:
Priority: normal Milestone:
Component: wxMSW Version: 2.8.10
Keywords: font DPI DEFAULT_GUI_FONT Cc: vegpuff@…, awrobel, cmbruns@…
Blocked By: Blocking:
Patch: no


Operating System : Windows XP Service Pack 3

User sets his DPI to 120dpi (125%) from 96dpi (100%) and opens wxMSW widgets demo .

Title, Menubar show fonts of size 125%, but controls like wxTextCtrl, wxCheckBox, wxComboBox do not reflect the change in DPI and show 100%. See screenshot.

PS: This issue originally came from NVDA

Attachments (1)

MSW-Controls-DPI.jpg download (125.8 KB) - added by vegpuff 12 years ago.
Screenshot of MSW Widget Controls Demo with 120dpi (125%)

Download all attachments as: .zip

Change History (14)

Changed 12 years ago by vegpuff

Screenshot of MSW Widget Controls Demo with 120dpi (125%)

comment:1 Changed 12 years ago by vadz

Is the problem that the fonts don't change correctly when the user changes the DPI while a wx program is running or are they still incorrect even after restart?

If it's the latter, it's indeed a serious problem which needs to be fixed but I wonder what could we be doing wrong here: we just use DEFAULT_GUI_FONT which should have correct size...

comment:2 Changed 12 years ago by BillNotTed

This is also an issue in 2.9.0 RC6. It appears that the DPI settings are not respected even after a restart. However MS does not recommend the use of DEFAULT_GUI_FONT any longer (

comment:3 Changed 12 years ago by cmbruns

This might be the same as issue 1981, reported five years ago. In any case, I have written a report of possibly related undesired font size behavior when selecting "Large Fonts" on Windows XP. Please take a look at my report for details.

comment:4 Changed 12 years ago by vadz

  • Cc awrobel added
  • Status changed from new to confirmed
  • Summary changed from Controls in wxWidgets do not reflect change in DPI to wxWidgets controls don't use the user-configured large font

Adding reporter of #1981 to the cc list of this one.

comment:5 Changed 12 years ago by vadz

BillNotTed is correct in comment:2, we shouldn't be using DEFAULT_GUI_FONT and apparently should never had (see

So we should be using GetNonClientMetrics() (from include/wx/msw/private/metrics.h) instead of it. The only problem is which of the fields of this structure should be used. lfMessageFont? lfCaptionFont? lfMenuFont? Different ones for different controls (e.g. lfStatusFont for wxStatusBar)? Does anybody have any ideas?

Ah, and how is all this related to the font returned by SPI_GETICONTITLELOGFONT? I hope it's always the same one as one of the above but I wouldn't bet on it...

comment:6 Changed 12 years ago by cmbruns

  • Cc cmbruns@… added

comment:7 Changed 12 years ago by cmbruns

The wx method wxGetCCDefaultFont() should probably return GetNonClientMetrics->lfMessageFont on Windows. I say this because lfMessageFont appears to be the "default" font in Tk 8.5, which does respect the user's windows font size choice.

That said, a complete solution should also used different fonts for different controls.  For example, lfMenuFont in pull down menus, and lfStatusFont in the status bar.  Perhaps those controls already retrieve the correct fonts.  I have only tested the wxButton and wxStaticText widgets, which do not respect the font size.

comment:8 Changed 12 years ago by vadz

  • Keywords font DPI DEFAULT_GUI_FONT added

I tested this and actually this is not the correct thing to do for the previous Windows versions (2000) which didn't use the same font there. But simply using message box font for all controls which are not list/tree seems to work fine for me under both 2000 and Vista so I will just commit this for now and let's update other controls as necessary later.

comment:9 Changed 12 years ago by VZ

  • Resolution set to fixed
  • Status changed from confirmed to closed

(In [61790]) Use correct font instead of DEFAULT_GUI_FONT.

DEFAULT_GUI_FONT is a misnomer, not only is it not a default (and never was)
but it shouldn't be used at all. Instead use lfMessageFont from the
NONCLIENTMETRICS structure as it seems to correspond to the font used by
the native controls under 2000, XP and Vista and respects Vista global DPI
setting unlike DEFAULT_GUI_FONT.

Closes #11008.

comment:10 Changed 12 years ago by vadz

  • Resolution changed from fixed to port to stable
  • Status changed from closed to portneeded

This could be backported to 2.8 if no problems are found (although non trivially so because wxMSWImpl::GetNonClientMetrics() doesn't exist there so it would need to be duplicated in wxSystemSettings probably).

comment:11 Changed 12 years ago by cmbruns

Thanks so much vadz for fixing this problem.

I encourage you to consider backporting to 2.8.  My life will be improved the day this change arrives in a mainstream release of wxPython.  In any case, thanks again for your diligent effort.  It is much appreciated.

comment:12 Changed 12 years ago by vadz

If no problems are found with it we could do it in the future but it's too early yet.

I hope wxPython release using 2.9.0 or the upcoming 2.9.1 will be ready soon though.

comment:13 Changed 7 years ago by vadz

  • Resolution changed from port to stable to fixed
  • Status changed from portneeded to closed
Note: See TracTickets for help on using tickets.