http://blogs.msdn.com/jfoscoding/archive/2005/07/12/437891.aspxIt all stems back to a rather unfortunate implementation of Control.DefaultFont. Raymond talked a bit about DEFAULT_GUI_FONT the other day, and mentioned that no one is using it anymore. Unfortunately, this is the default font for controls. DEFAULT_GUI_FONTen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/jfoscoding/archive/2005/07/12/437891.aspx#437903Tue, 12 Jul 2005 10:34:20 GMT91d46819-8472-40ad-a661-2c78acb4018c:437903Dean HardingThis question is only partially related, but what happens if I'm developing an app on two different machines: one is 96 DPI the other is (say) 120 DPI. In v1.x, the forms designer would get horribly confused when switching DPIs and I'd have to go in and fix it manually. Does the new AutoScale stuff manage that properly?http://blogs.msdn.com/jfoscoding/archive/2005/07/12/437891.aspx#458277Wed, 31 Aug 2005 06:32:52 GMT91d46819-8472-40ad-a661-2c78acb4018c:458277jfo's codingWhy do we need both SystemEvents.UserPreferenceChanging and SystemEvents.UserPreferenceChanged? <br>The...http://blogs.msdn.com/jfoscoding/archive/2005/07/12/437891.aspx#9347648Tue, 20 Jan 2009 17:59:10 GMT91d46819-8472-40ad-a661-2c78acb4018c:9347648Anzeige von Japanischen Zeichen in Swing | hilpers<p>PingBack from <a rel="nofollow" target="_new" href="http://www.hilpers.com/846943-anzeige-von-japanischen-zeichen-in">http://www.hilpers.com/846943-anzeige-von-japanischen-zeichen-in</a></p>