Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#11658 closed defect (invalid)

Different font sizes in 2.9 and 2.9.1

Reported by: triton Owned by:
Priority: normal Milestone: 2.9.1
Component: wxMSW Version: stable-latest
Keywords: msw different font size default sample Cc:
Blocked By: Blocking:
Patch: no

Description

I compiled a new 2.9.1 build from trunk and noticed in my apps that the font sizes are different between the two builds. So I also checked one sample and noticed the same problem.

This might be related to r62566.

AFAIK, I don't request any explicit font size in my app, so I think the font sizes should be the same between wxWidgets versions, at least it seems all the other apps in my system use the smaller font sizes (hard to say though).

Screenshot attached to show the problem.

Attachments (1)

font-size.png download (74.8 KB) - added by triton 4 years ago.
Different font sizes in Notebook sample between 2.9 and 2.9.1

Download all attachments as: .zip

Change History (5)

Changed 4 years ago by triton

Different font sizes in Notebook sample between 2.9 and 2.9.1

comment:1 Changed 4 years ago by vadz

I don't think the change could be related to this revision but there were other changes to fonts used in MSW GUI by default. Before I start tracking them down, could you please give the exact numbers of revisions you tested with? I.e. was "2.9" 2.9.0 release or something else?

Thanks!

comment:2 Changed 4 years ago by catalin

I think the change is older - r61790 - and you'll only see a change on Vista and probably Win7; not on XP.

But the behavior is correct in 2.9.1; there's a very good explanation here:
http://en.wikipedia.org/wiki/Windows_Aero#Font

HTH

comment:3 Changed 4 years ago by vadz

  • Resolution set to invalid
  • Status changed from new to closed

Yes, this is indeed the change I had in mind. If your previous version was older than r61790 then it's indeed normal that the fonts changed -- and the new behaviour is indeed correct.

Please reopen if this analysis is not correct.

comment:4 Changed 4 years ago by triton

I see, thanks. I read the MSDN links you provided and you are right. This is the correct behaviour.

Note: See TracTickets for help on using tickets.