3 ms·
> Even if an application has no modifications for retina displays, it will look mostly right (minus some blurring issues for pixel art). There will be no scalin
by zokier 13y ago
> Even if an application has no modifications for retina displays, it will look mostly right (minus some blurring issues for pixel art). There will be no scaling issues, no texts will be cropped and everything will be scaled to the same factor.
That is how it (should) work in Windows too. All applications that do not explicitly claim to be DPI aware get just bitmap scaled, just like on OSX.
The real problem is that tons of applications claim to be DPI aware, but in reality are not. The reason Apple does not have these kind of issues is that their Retina thing is more recent and thus there are no legacy apps that claim to be DPI aware.
- deleted 13y ago[deleted]
- zokier 13y agoYour understanding how DPI scaling works on Windows is completely wrong. > As far as I know there is no magical 'hey, I'm DPI aware' flag in Windows Yes, there is exactly that kind of flag. Your application either sets the flag in its manifest, or calls `SetProcessDpiAwareness` function. > In Windows (I'm talking about the old native-code API here - no idea about Windows.Forms or WPF), when you say "draw me a 1px wide line here", you get a 1px physical line drawn. No. The default (ie if you are not claiming to be DPI aware) is that your draws end up on a 96DPI "virtualized" surface, which is then scaled up by the compositor (DWM) to the real DPI. Effectively that means that your 1px line becomes 2px line. You can only draw real 1px lines on hidpi screens if you claim to be DPI aware. This article documents the behavior quite extensively: http://msdn.microsoft.com/en-us/library/windows/desktop/dn469266%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/windows/desktop/dn46...
- scoopr 13y agoLike SetProcessDPIAware[0], or the manifest equivalent? =) [0] http://msdn.microsoft.com/en-us/library/windows/desktop/ms633543(v=vs.85).aspx http://msdn.microsoft.com/en-us/library/windows/desktop/ms63...
- pilif 13y agoSetProcessDPIAware was added in Vista. I haven't done any Windows programming in quite a while so my knowledge was hopelessly outdated (XP level). Hence I've removed my comment - no need to spread misinformation.
- seanmcdirmid 13y ago> All applications that do not explicitly claim to be DPI aware get just bitmap scaled, just like on OSX. I don't believe that is true. If you render text using the right high-level OS X APIs, your OS-provided vectors are rendered natively without being bitmap scaled. WPF can do this just fine also, but few apps are written in WPF :p (well, WinRT inherits this nice property). GDI, I'm not sure....
- rsynnott 13y ago> All applications that do not explicitly claim to be DPI aware get just bitmap scaled, just like on OSX. That isn't what happens for Cocoa apps on OSX, though. Non-retina-aware apps aren't bitmap scaled; the Cocoa UI stuff is still scaled up properly (XBench, which had its last release in 2006 targeting MacOS 10.3, looks perfectly sharp on an rMBP, for instance). It's just non-standard stuff that may be a problem.
- eropple 13y ago> The reason Apple does not have these kind of issues is that their Retina thing is more recent and thus there are no legacy apps that claim to be DPI aware Not actually true. Many games are fairly messed up in either windowed, full-screen, or both noises. Usually it's because of a bad middleware toolkit that either enables the Retina backbuffer our not but the OpenGL scaling doesn't match the window scale. Especially prominent in games that use the older, Carbon method of exclusive full screen mode. Aside: full screen games manage to be even worse on OS X than on Windows. That takes effort. (Games as full screen spaces is a really nice, usable concept, but the performance hit is so nasty nobody wants to support it instead of the invasive and messy Core Video tour.)
- eropple 13y ago(aside: This post was doubly a victim of autocorrect. s/noises/modes/ and s/tour/route/. My bad.)