Qt Quick 2’s high DPI scaling is utterly ridiculous. Automatic scaling only uses integer factors, which means comically huge UI elements on a 4K desktop monitor where 150% is the appropriate factor — it literally gets rounded to 200%. The weirdest thing though: fonts sized in points are scaled to the exact DPI of the monitor, ignoring the rounded UI scaling factor. Which means that the UI elements on my desktop are bigger than on a low DPI monitor, relative to the text inside of them. What were they thinking?!
When will UI toolkit developers STOP believing that non-integer scaling is bad?
One of the worst things about current official Twitter UX is how ridiculously easy it is to lose a tweet while writing it.
On the iPad, the compose view you get when you tap the Reply button protects you from losing your tweet, but not the text field at the bottom of the screen when you’re viewing a tweet/conversation. If you accidentally swipe away that screen, IT’S LOST. And the swipe works literally everywhere. Even on the damn Tweet button. I’ve accidentally discarded several replies instead of posting them.
On Android, both reply fields don’t let you discard a tweet w/o confirmation.
But on the Web, you can lose your text anywhere. Accidentally clicked the darkened background around the popup? Pressed Esc? Your reply text is lost.
(It’s not just Twitter. It seems like NO ONE CARES ABOUT THIS ANYMORE. Firefox Share is another example.)
I can’t believe how miserably GUI tools fail at file formats. So, I received a transparent JPEG recently. After the WTF moment, I ran
/usr/bin/file and it told me it’s a PNG file (renamed to
Here’s how GUI apps handle it:
OS X’s Finder actually ran the format detection to display it correctly in Quick Look, but didn’t say “PNG renamed to JPEG” as the file format. It just said “JPEG image!”
Photoshop showed an error and refused to open it.