Linked by Thom Holwerda on Wed 15th Sep 2010 19:14 UTC
Permalink for comment 441267
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2009-08-26
Technically yes it is Direct2D but it's the same underlying problem. WPF is also hardware accelerated and basically has the same text renderer. I don't want to get into the details but they basically built WPF with the assumption that we would all have super high dpi monitors by now. Anyways it really pissed off a lot of .net developers since in many cases they didn't notice until testing the program later on a laptop with a lower res. Reverting back to GDI isn't something you can do with a couple clicks. Anyways MS improved the situation for WPF but it is still an issue for fonts that are not designed for ClearType. With most WPF .net applications you can control the font list but IE9 of course has a big problem which is web fonts.
Anyways this the problem in detail from MS without of course the part about pissing off .net developers:
http://windowsclient.net/wpf/white-papers/wpftextclarity.aspx