Slashdot Mirror
If You Type 1+2+3 Into Your iPhone's Calculator on iOS 11, You Probably Won't Get 6 (qz.com)
A reader shares a report: If you've upgraded your iPhone's operating system to iOS 11, try this: Go to the calculator app and quickly type 1+2+3. You likely won't get 6. You might get 23, or 24, or 16, or 32, or something else, depending on what buttons you tap and in what order, and, obviously, none of which is the right answer. It seems to be because of a new animation in the calculator app, where a button briefly fades to white when you press it. The result is that if you press an operator button (i.e., the plus sign) before the short animation finishes, the app ignores it. So, 1 + 2 + 3 accidentally gets read as 1 + 23.
UI and software quality is falling because of the emphasis on appearance rather than function, hence Unity and GNOME 3 and this article's stupidity.
It's pretty funny really, because Apple makes a big deal about how app developers are not supposed to block UI, and about how to make animations interruptible. The fix will probably be pretty simple...
The calculator issue is really bad though. Even just moderately fast pressing of buttons yields input blocking depending on what you are doing.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
CPU time and network time should be better spent on the really important stuff that computers are supposed to do: check for app and o/s updates.
"But remember, most lynch mobs aren't this nice." (H.Simpson)
-- Joe
No, if you type 3+3 and then hit x you get the answer of 3+3 = 6, then you "x" and "3" you get 18. You are asking the calculator what is 3+3 and then asking it to multiply that answer by 3. This is working as designed because it's not a scientific calculator. If you simply switch to Scientific in the options, you can use "( )" and/or other functions to put in a formula. As far as I know the standard Apple calculator does not a scientific option. The user is in error if they want 3+3 * 3 in a non scientific calculator and start hitting buttons.
Sent from my TARDIS
Typical Apple. Form over function.
They already made smartphones which couldn't make phone calls, so I guess this is just one more instance in that vein.
When AC says Honda, I'm assuming he means the in-dash navigation and radio. Imagine, for a moment, that you think you hear sirens, but you don't see flashing lights, so you decide to turn the radio down to hear them better. You can't really wait for a safe place to pull over to do that, since you may end up impeding an emergency vehicle before then, so you're stuck fumbling with the damn infotainment system and waiting for it to animate every... single... button... press... before... it... will... do... anything... else.
By the time you've turned the damn thing down enough to hear, the ambulance or fire truck is up your ass, because you had to take your eyes off the road (and your rear-view mirror) to look for the spot on the screen to touch for volume in the first place.
Can we just have fucking physical knobs and buttons back, please?
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
So, how are we expect to get the true math answers with these calculations then? :(
If you want "true math answers", do math symbolically instead of numerically.
There are entire books and courses on numerical methods that talk about doing calculations on numbers instead of symbols, how to minimize errors, and why they appear.