Live data from Hacker News

Is my vision that bad? No, it's just a bug in Apple's Calculator

martin.wojtczyk.de

221–230 of 408 posts

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#221

Earlier quoted context omitted.

It’s very easy to reproduce this bug, even if you don’t go quickly. Basically, if your tap becomes a “swipe” that leaves the button area, then a previously registered “tap” that’s already shown up in the field will actually “unregister” and disappear from the field. Try it yourself: tap down on a button, watch the dot appear, then without lifting your finger, swipe out of the button, and watch it disappear. This happ…

The "keypress" behavior is not a bug in my opinion, it's a well-established behavior across platforms. You could do the same thing with a button+mouse on a desktop. The dot for the typed character appearing immediately is different from alphanumeric keyboard behavior, because you can't register any key press before releasing the touch (or key) there, due to composition. In my opinion, this is sensible behavior and yo…

The bug is that it shows they character as entered into the passcode when it really isn't. The bubbles should only update when you get lift your finger, not when you initially press it down.

> The dot for the typed character appearing immediately is different from alphanumeric keyboard behavior, because you can't register any key press before releasing the touch (or key) there, due to composition.

That is exactly why the dot should not appear immediately upon the down event.

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#222
post #85

> I would contact Apple, if there was a feedback option, but there isn’t There is: https://feedbackassistant.apple.com/ That said, it isn’t very user-friendly, and I find that they don’t seem to pay much attention to it. When they do respond, it tends to be some form of “#wontfix. Please close this.” That looks like a fairly ugly little bug. I suspect they know about it now, thanks to the HN Bug Reporter. It tends to…

Conversely all 4 of the bugs I reported with that were fixed in the next minor release!

I reported a bug that occurs in a specific configuration of the Music app (trying to use Home Sharing + using bluetooth headphones), never heard anything back. I wonder if it's been fixed in the latest version of the OS, I still haven't upgraded...

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#223

Comically, I didn't even notice those wobbly numbers in the first screenshot, I was too busy noticing: - "Unicode" button label way off center - The 8/10/16 selector being off center in its own position - The indicators for bits 31 and 63 are not aligned with each other - x and + not being horizontally aligned (I believe this is an icon-font issue, seen on HN before so knew to look for it)

Interesting. I saw the wobbly numbers instantly, but I didn't see any of that, and can't even see the 31/63 issue now.

The 31/63 issue for me is that they appear to be aligned differently to the 0s directly above them. The left-edge of the 6 seems to be further left than the left edge of the 3. The 3 in 31 at least looks vertically aligned with the 0 above it.

However, I suspect they both have the same ("Incorrect" seems too harsh a word... "Visually imprecise"?) layout constraints and they look different in practice because "63" is a wider number than "31".

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#224
post #55

Earlier quoted context omitted.

It’s crazy that I had to buy BetterDisplay (great tool btw) just to get fonts from incomprehensible to merely ugly on a 25x16 monitor via a fake 2x scaled one. Windows renders razor sharp even without gfx drivers.

There’s a great article with explanations on the net. But the gist is that macOS renders like a giant image with no care for pixels and small details. It works fine when using native resolution (low dpi) or have enough pixels for their “retina” approved resolution. Anything else and it looks blurry. Linux and Windows use actual pixels for their rendering, and even with anti-aliasing, it looks sharp. If you’re stuck w…

Ideally, you want a screen that natively runs at a resolution that’s a perfect 2x multiplier of a mainstream 1x resolution that has the right amount of screen real estate for the screen size.

So for example, a 20”-24” screen should be 4K so it can run at 1920x1080 @ 2x. Similarly for 27”, you want 5K which is 2560x1440 @ 2x.

This is a really good post describing how it all works:

https://bjango.com/articles/macexternaldisplays2/

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#225
post #169

Earlier quoted context omitted.

Apple's greatest weakness is that many of it's fans and I'd assume people in house assume they are the epitome of UI design when actually it's not. The thoughtlessness/pixel ratio might be worse than Microsoft in some cases, which can be hard to believe.

> Apple's greatest weakness is that many of it's fans and I'd assume people in house assume they are the epitome of UI design when actually it's not. Which led to people like me making a fool out of themselves. Always been using Android, and listened to iPhone users singing the praise of the amazing UI and UX of iOS. Well, eventually iPhone 12 Mini released so I figured, "why not give it a try, can't be worse than my…

>slow animations. Same on Android by default, but at least I can speed it up.

Enabling the power user/developer menu in Android's settings lets me disable animations entirely. My old phone feel really snappy now and I'd do the same on a new phone too.

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#226

Earlier quoted context omitted.

The "keypress" behavior is not a bug in my opinion, it's a well-established behavior across platforms. You could do the same thing with a button+mouse on a desktop. The dot for the typed character appearing immediately is different from alphanumeric keyboard behavior, because you can't register any key press before releasing the touch (or key) there, due to composition. In my opinion, this is sensible behavior and yo…

There’s always been two button modes. “mouseup” is indeed the most common. However, “mousedown” is used in certain cases where the feedback is immediate, for example in the phone app where the number shows up as soon as you tap. However, notice that the lock screen uses neither of these, but rather a strange combination of both: it registers on “mousedown”, just like the phone app, showing a new dot in the field, but…

Yes, but I feel this is totally Ok here?

I think it would slow me down even more if it didn't have this behavior, because of typing in extra unintended numbers?

I don't have any issues with typing my passcode in quickly, and tbh hadn't noticed the tweak with the immediate feedback on "tapdown" (and the possibility of the number disappearing).

Would have to try, but I still feel I prefer the current behavior to what you suggested, and I'm pretty sure it's intentional.

Anyway, thanks for bringing this up, hadn't noticed! I'll admit, for me this is good interaction design.

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#227
post #169

Earlier quoted context omitted.

Apple's greatest weakness is that many of it's fans and I'd assume people in house assume they are the epitome of UI design when actually it's not. The thoughtlessness/pixel ratio might be worse than Microsoft in some cases, which can be hard to believe.

> Apple's greatest weakness is that many of it's fans and I'd assume people in house assume they are the epitome of UI design when actually it's not. Which led to people like me making a fool out of themselves. Always been using Android, and listened to iPhone users singing the praise of the amazing UI and UX of iOS. Well, eventually iPhone 12 Mini released so I figured, "why not give it a try, can't be worse than my…

I've used a few apple products -- the iPhone 3 was my first smartphone, and an iPad mini back when tablets were starting out. At the time of the switch to android, I didn't think too much of it, but definitely enjoyed the customisation.

A couple years ago I was gonna get a new phone and, half my family being Apple devotees, I was considering switching again so I could stop hearing the 'blue bubble' nagging, plus they seem to genuinely enjoy their phone.

In pure luck, a friend had a new iPhone 13 and hadn't switched from his old phone yet, and allowed me to use it for a couple days so I could see just how incredible the phones are and I should switch. After about 48 hrs, I was so done with the product, and like you, preferred to switch back to my old 'crummy' phone until I bought my next flagship.

I can't imagine being locked in till it dies, because as you said, the iPhone is such a miserable product. I'm sure you could resell and get a flagship for a similar price. You'd still net loss, but IMO it would be better than keeping the phone since you don't like it.

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#228
post #215

Earlier quoted context omitted.

I am curious where you perceive the slowness. I always had flagship Androids before my switch to a 12 mini. Overall I am happy. There are plenty of things that annoy me lots but I never really noticed slowness. Where do you notice it? Do you play games or use compute intensive apps?

> I always had flagship Androids before my switch to a 12 mini. And I had budget Android phones (Motorola Moto G) before my 12 mini, yet the iPhone is worse on most points besides the display and sound. > Where do you notice it? Do you play games or use compute intensive apps? Anywhere where there is an animation/sliding/transition. Everything feels like it's moving in molasses. But it's very much not a Apple-specifi…

This sounds backwards, based on my experiences. I keep thinking of switching back to Android, so I keep a recent-ish Pixel in my inventory.

I do not observe this on my 12 Mini that is on iOS 16. Comparing it to my Pixel 6a with stock Android 14, I’d say the iPhone is faster/smoother and less glitchy moving around the UI.

Perhaps something is up with your 12? That would still be a ding on Apple.

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#229
post #213

Earlier quoted context omitted.

CarPlay is a thing because carmakers just can't seem to make a decent "radio" with a touchscreen no matter how they try. It would be nice to see a business school case study that reveals why.

> CarPlay is a thing because carmakers just can't seem to make a decent "radio" with a touchscreen no matter how they try But CarPlay is 100x worse than Android Auto, even though Apple is supposed to excel at UI and UX, this was the point I was trying to make, not that car makers such at UI/UX.

Having used both, I disagree. What do you prefer with AA?

Re: Is my vision that bad? No, it's just a bug in Apple's Calculator

#230
post #169

Earlier quoted context omitted.

> Apple's greatest weakness is that many of it's fans and I'd assume people in house assume they are the epitome of UI design when actually it's not. Which led to people like me making a fool out of themselves. Always been using Android, and listened to iPhone users singing the praise of the amazing UI and UX of iOS. Well, eventually iPhone 12 Mini released so I figured, "why not give it a try, can't be worse than my…

>Everything is dog slow, not because poor performance but because of slow animations. Did you try Accessibility > Motion > Off? >Things are impossible to discover unless you watch tutorials on YouTube There's a pretty useful manual built into the device itself called Hints I think? Did you read that?

I think you’re talking about iOS. If so, it’s Settings -> Accessibility -> Reduce Motion -> On
Post reply on HN