3 ms·
I guess the best way to solve this would be to (partially) ignore the dpi awareness flag in applications and instead apply a series of heuristics and white/blac
by zokier 13y ago
I guess the best way to solve this would be to (partially) ignore the dpi awareness flag in applications and instead apply a series of heuristics and white/blacklists (with user override) for determining if applications truly are hidpi capable. That would be bit of a pita for the applications that actually do support hidpi properly now and might get still bitmap scaled, but that would be just a temporary issue.
- rbanffy 13y agoWhat bothers me is that this crisis has been obvious since well before Apple started releasing their Retina screens on mobile devices. X has 75 dpi and 100 dpi fonts for a reason and we had 2D acceleration on every decent computer for what? 15 years? We've been using pixels as size units for no reason other than laziness.
- seanmcdirmid 13y agoVector rendering is still not advanced enough to completely (or even mostly) replace bitmaps. Until they are, we'll have to redline our bitmaps for each resolution manually. It's not just a matter of laziness.
- marcosdumay 13y ago> Vector rendering is still not advanced enough to completely (or even mostly) replace bitmaps. Wait, what?!? Vector rendering matured before bitmaps were common place. They are faster and use less memory, that's why programmers of the 70's and 80's loved to use them. Bitmaps are easier. That's the only reason people use them. And only in a world where everybody gets images on the same size and resolution.
- seanmcdirmid 13y agoYour information is just plain wrong. My wife does a lot of pixel redlining at her job: the artifacts they produce are all done in Illustrator, a vector program. And believe me, they would love to leave them as vectors...less work for them! However, they must be converted to bitmaps and manually redlined to eliminate sub-pixel alignment problems. Bitmaps are not easier, otherwise the designers would be cranking out pixels directly in Photoshop and not Illustrator. The fact that NO ONE has produced a decent general purpose vector renderer that avoids pixel artifacts, even a non real-time one, means that my wife will be redlining for quite a few more years. Even font rendering (arguably simpler than icons) requires substantial hinting to be effectively resolution independent.
- rbanffy 13y agoThe high density displays we are starting to see may end up solving the artifact problem - we won't be able to discern individual pixels for much longer. The other problems: elements that vanish, such as lines and thin structural rectangles, would require some pixel-related restrictions in their definition. I'm not sure vector programs are able to deal with them right now, but it would be useful.
- seanmcdirmid 13y agoRight. I was replying to parent in that we don't still do bitmaps because we are lazy. Quite the contrary: we have moved to vector-based tools for producing application art assets and would love it if we could just output to SVG or something similar and be done with it. However, the current reality is that we still have to convert our vectors manually to bitmaps, even those for high res screens. Rasterization is just still not good enough to do the job automatically (it works fine for objects in motion where the imperfections aren't very noticable, but not those that don't move).
- rbanffy 13y agoI understand there is a need for some pixel-tuning, but most of it can be expressed as rendering constraints on the vector images, such as "this rectangle has to be, at least, five pixels wide".
- georgemcbay 13y agoWindows does let you disable high dpi scaling on an app by app basis (if you right click an app icon, pull up properties and go to the Compatibility tab). In Windows versions prior to 8.1 the UI wouldn't let you do this for 64-bit executables, only 32-bit ones. For 64-bit apps the checkbox to disable dpi scaling was greyed out, even though if you set the key in the registry (using the same key that the UI would set for 32-bit apps) it would work just fine for 64-bit apps too. In 8.1 they fixed this stupidity and the compatibility tab UI will work for any app regardless of being 32 ot 64 bit.