The big issue a lot of apps have is that some elements are designed to work with the scaling system while others aren't, or that the app developer uses DPI-aware units (pt, em, etc) for some elements but non-scalable units (px, etc) for others - you can see this in any app that, when scaled in 'application' mode, has some elements that are oddly larger than others. The issue with DPI scaling in non-vector frameworks is a compound one some frameworks don't handle it very gracefully, but also some developers just aren't good at designing DPI-aware UIs. These apps are subject to the GDI-based rendering system and have to handled by Windows' scaling system, which does its best but can't account for developer mistakes. Most third-party GUI frameworks are not actually vector-based, however, and may not use Windows' vector controls at all. That's the entire benefit of vector graphics. I believe it has vector-based controls, yes, and WPF is entirely vector (well, except for the image rendering aspects) but that's actually pretty irrelevant to the issue of DPI scaling, since WPF doesn't have any scaling issues at all - in fact, if the UI were vector (or WPF-based) then we wouldn't be having this conversation in the first place, because scaling would Just Work (unless they just did something really really stupid).
0 kommentar(er)
