4 ms·
Wow, I'd love to hear more about this! It seemed that plenty of folks (myself included) found WPF text to be rather unusable until they fixed it years later (a
by MichaelGG 15y ago
Wow, I'd love to hear more about this!
It seemed that plenty of folks (myself included) found WPF text to be rather unusable until they fixed it years later (after the VS 2010 blurry text editor thing). I can't use IE because of the 'smoothed' text, but Chrome still seems to get it "right" (snaps to pixels, like in Word). Are we talking about the same thing?
At high DPI it does look fine; unfortunately high DPI didn't actually happen like Microsoft thought, just like 6GHz CPUs (both predictions at PDC 2003). Although, now that the iPad3 shipped a high DPI screen, maybe other OEMs will get their stuff together.
- jbeda 15y agoYou can probably blame me for this, to some degree. We were really trying to build for the future with WPF and as such wanted to be truly resolution independent. As such, we (I) locked a px to a 1/96th of an inch. The end result is that things animated smoothly but that you got blurry lines and poor edge interaction under lots of circumstances. Text exacerbates this. One of the things that I had been working on when I left Microsoft was to come up with a comprehensive 'pixel snapping' system that would start to address these issues. I was looking at taking ideas form the autohinting systems used in the font rasterizers. At the time that WPF shipped, it appeared that no one had picked up that work. I haven't tracked it since then so perhaps things have been improved.
- MichaelGG 15y agoWell, we can just hope high DPI becomes a reality so things look good again. WPF has fixed its problems by doing the pixel snapping, but other engines like whatever powers IE9's rendering (and FF, I think) have regressed and prefer "accuracy" over readability :(. MSFT even admits around half of the users dislike it, but the justification is that "everyone else is doing it". Oh well...