The only application that doesn't handle scaling is Unit圓D, so everything is tiny (no fallback to raw image scaling). Things scale correctly and no blurriness. The actual scaling is perfect for the vast majority of things. The GUI still only gives you a single scaling option for all monitors, but the autodetection can do different for each monitor, and environment variables can be set to solve it manually. The autodetection can be dodgy, and the DPI scaling for text isn't linked to the rendering scaling for windows, for some reason. The actual scaling isn't great - having a window half on one monitor and half on the other leads it to 'picking one' and looking weird on the other. Most applications scale badly with blurry text because it's just literally scaling the image afterwards. It was seamless from monitor to monitor, scaling done well. OS X, years ago when the first retina MBP was released, did everything right.
#Zen autopurge windows#
My experience (currently running two 27" panels at 3840x2160 and one 27" panel at 2560x1440 in KDE for most stuff, Windows for gaming, and previously had one of the first edition retina MBPs with external non-retina displays): I am willing to strain my eyes with smaller font sizes on my phone than on my laptop, just so that I can see more than 5 sentences of text at the same time. You have plenty of "space" for windows and content, and want to get the optimal scaling.īut once you get to very small screens like phones, there is a tradeoff between keeping font and UI sizes comfortable, and being able to actually fit enough content on the screen without endless scrolling. With large screens, for example 24-30" on your desk, just the per-pixel FoV measure will probably be good enough. That is a good starting point for calculating the default "optimal UI scaling", but there are going to be adjustments needed for the FoV of the whole screen area (not per pixel) too. > I've always thought that arcdegrees should be what we measure UI's in: how much of a user's field of view does this thing consume? After all, what makes text "small" is that how much of my FoV it consumes (or doesn't). (of course, some displays have borders, so that fudges it a bit.) (I'm also assuming that the monitor can report it's physical size and resolution combined w/ viewing distance, it should be possible to calculate FoV.) If you did this, you should be able to mostly seemlessly split a window between two displays, and have it be equal "size" in the FoV. Some definite defaults exist (phones are typically about the same distance away, same with desktop monitors) but unique situations certainly can exist. I assume the real hard piece is figuring out the distance the display is going to be viewed at. Perhaps one can work backwards and fudge point as a measure of angle if you consider 12 point font at a typical viewing distance.) (Admittedly, "points" are still likely a good measurement for print. I've always thought that arcdegrees should be what we measure UI's in: how much of a user's field of view does this thing consume? After all, what makes text "small" is that how much of my FoV it consumes (or doesn't). We're super interested in your feedback! Everything is fair game - Kernel, Security, Desktop apps, Unity/Mir/Wayland/Gnome, Snap packages, Kubernetes, Docker, OpenStack, Juju, MAAS, Landscape, default installed packages (add or remove), cloud images, and many more I'm sure I've forgotten.ġ7.10 will be our 3rd and final "developer" release, before we open the 18.04 LTS (long term support, enterprise release) after October 2017 (and release in April 2018), so this is our last chance to pull in any big, substantive changes. ROLE/AFFILIATION: (Optional, your job role and affiliation) Bonus points for constructive criticism -)
DESCRIPTION: A lengthier description of the feature.
HEADLINE: 1-line description of the request
Please include in your replies the following bullets: This is the first time we've ever posed this question to the garrulous HN crowd, so I'm excited about it, and I'm sure this will be interesting! I'm interested in HackerNews feedback and feature requests for the Ubuntu 17.10 development cycle, which opens up at the end of April, and culminates in the 17.10 release in October 2017. Dustin Kirkland here, Product Manager for Ubuntu as an OS platform (long time listener, first time caller).
0 kommentar(er)
