Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS 11 Bug: Typing 1+2+3 Quickly in the Calculator App Won't Get You 6

It honestly seems as if Apple hired a bunch of interns to develop iOS and they said F it.

Side note. Did anyone notice how much empty space the “Today View” on the iPad Pro 12.9 has? One column of “widgets” with all blank space around it on either side lol I remember when Apple cared about the little details smh
 
  • Like
Reactions: simonmet
Act3 said:
Yes really. Spin it as you like , but simple calculator function is a bit different than dropped frames. You say you are not defending apple, really what is your agenda ? Have you’ve ever critiqued anything Apple has done on anything here?

Still waiting on you to provide link to a thread showing people on MR complaining about calculator issues on previous iOS versions. You do seem all knowledgeable about past forum discussions. Show me where it was an issue in the past. :rolleyes:
Click to expand...
The spin seems to be happening elsewhere it would appear. When it's convenient it seems that many people not experiencing an issue while a few do means that those who aren't experiencing it are just not noticing or perhaps even lying about it and the issue is really there nonetheless. Then at at the same time just because there wouldn't be much complaining about something therefore it's not really an issue. Interesting how things somehow can work one way and then the other way when it's convenient.

And as typical, it seems like when an argument couldn't be made and deflections aren't really standing up things get shifted to talk about the user making the comments. Because somehow everyone has to be either critical of something or otherwise they are for it and are defending it. As if people can't just be and have to have an agenda and something behind what they say, rather than simply exactly what they say, nothing more, nothing less.
 
Maybe they realized the presence of these bugs and probably why came up with Animojis in iOS 11...so we can clearly express our shock & disdain.

Now I see where Animojis could be useful :)
 
Last edited:
PickUrPoison said:
No, it’s not calculating just fine because I pressed 1+2+3 and it came up with 24—clearly a wrong calculation. I didn’t enter 1+23, did I? If it were calculating just fine, the calculation wouldn’t have been wrong.

If you don’t want to call a wrong calculation a calculation glitch, feel free. But the fact remains, it’s a calculation glitch. Note I didn’t say there’s any problem with the calculation algorithm. I didn’t say that it wasn’t possible to go so slowly that it would calculate correctly.

Don’t engage in user blame and try to fault me for the calculation glitch; 24 is not right when I press 1+2+3 and it’s not the behavior Apple intends.

If you told me “1+2+3 equals 24” I would tell you you’ve got a calculation glitch.

Free your mind from it’s semantic rigidity—a “calculation glitch” precisely describes 1+2+3=24. If I’d entered 1+23 and gotten 24, that would have been the correct answer, and we wouldn’t be talking about a calculation glitch at all.
Click to expand...

Well if you got 24 it means that you didnt enter 1+2+3... simple as that.
I can make the app spit out 6 if I enter 1+2+3 and I can make it spit out 24 if I enter 1+23.
 
gnasher729 said:
Actually, I have to contradict you here vehemently. The user taps all the right buttons, the user should get the right answer. One of the worst things is a UI that has to be used slowly. Not a "lagging" UI, that's bad enough, but one where the user has to slow themselves down. So things take longer than they have to, AND the user cannot trust the result. That's bad. And annoying things like this destroy the user interface.


Why is this use? Because it is absolutely pathetic. Try adding up 100 numbers. It either takes three times longer than it should, or you are guaranteed to get the wrong result.


It's a bug with a very annoying workaround. It's pathetic. You are tapping 1 + 2 + 3 = and you don't get 6. In which alternate universe is this not a bug?


If you use MacOS and display the clock in the menubar with seconds: For years, they used a font where the "1" was narrower than the other digits. With the result that when the last digit of the seconds switched from 0 to 1 and from 1 to 2, the whole display moved by a pixel. A bug like that is just pathetic.
Click to expand...


I think you didnt contradict me, I think we agree. Its an annoying usability issue. Apple should improve the UI.
Is it a bug people should be freaking out over? no.

The entitlement and lack of being in touch with the real world of people alarmed by this is mind blowing.
 
charlieroberts said:
I think you didnt contradict me, I think we agree. Its an annoying usability issue. Apple should improve the UI.
Is it a bug people should be freaking out over? no.

The entitlement and lack of being in touch with the real world of people alarmed by this is mind blowing.
Click to expand...

It's not just a usability issue that just needs "improvement" it's a serious bug. People rely on a calculator to be accurate, if there is an increased risk of faulty answers, it can have serious repercussions depending on what context the calculator is used on.

You have to understand the calculator fails under normal conditions, just by typing normally, not even quickly, it fails to give the correct answer. It may be easy to spot the flaw in the 1 + 2 + 3 example, but with other cases it may not be as easy.

About the entitlement, it has nothing to do with that. It has everything to do with the same perfectionism and excellence that Steve Jobs abided by and transmitted to all of us. Apple raises the standard, don't ask us to sit idle and let this UX atrocity slide by.

Speaking of which, this is a great read and insight on Steve Jobs's perfectionism with the calculator: https://www.cultofmac.com/421893/why-the-ipad-has-never-shipped-with-a-calculator-app/
 
Not a bug at all, over rated news.

What is happening is the app can’t react quick enough so only registers some touches, like 12 then + = and as a result gives you a valid result of 24 as normal, take your time and not an issue.

Apple could improve it by having rectangular buttons and less of a delay is Touch response

The round buttons are hard on the eye and poor attempt in design, Google still #1 when it comes to UI design Apple has got a lot to learn from Google still
 
Fixey said:
Not a bug at all, over rated news.

What is happening is the app can’t react quick enough so only registers some touches, like 12 then + = and as a result gives you a valid result of 24 as normal, take your time and not an issue.
Click to expand...

So much for A11 bionic processor with Neural Engine - Can't believe it can't react to a third grade animation quick enough. If the processor is truly powerful as they say it is, then this should be a bug?
 
  • Like
Reactions: sysyphus' sister
Back in the day, we were always told that all-in-one devices never offer the same quality as each individual device by itself. I guess some of that still holds true.
 
  • Like
Reactions: simonmet
harpyeagle said:
So much for A11 bionic processor with Neural Engine - Can't believe it can't react to a third grade animation quick enough. If the processor is truly powerful as they say it is, then this should be a bug?
Click to expand...
It's not about the processor keeping up, it's about how a particular tap/animation library is being used and/or some glitch in that library or its use.
 
C DM said:
It's not about the processor keeping up, it's about how a particular tap/animation library is being used and/or some glitch in that library or its use.
Click to expand...

I am not saying so. Was responding to a previous poster's comment abt the phone not reacting "quick enough"

Regardless, your statement, "some glitch in that library" - I guess that's what we call a bug, correct?
 
  • Like
Reactions: trifid
C DM said:
It's not about the processor keeping up, it's about how a particular tap/animation library is being used and/or some glitch in that library or its use.
Click to expand...

Which is precisely why I don't give a hoot about any of Apple's fanfare about how fast their new devices are...

None of it matters when it feels slower to use than a 3GS because i[nput-blocking]OS is artificially unresponsive since iOS 7. 7.0 was absolutely atrocious but it's still never been the same as before.
 
  • Like
Reactions: mi7chy and trifid
Altis said:
Which is precisely why I don't give a hoot about any of Apple's fanfare about how fast their new devices are...

None of it matters when it feels slower to use than a 3GS because i[nput-blocking]OS is artificially unresponsive since iOS 7. 7.0 was absolutely atrocious but it's still never been the same as before.
Click to expand...

I miss the pre iOS7 times when we had no clue what input-blocking was and didn't need to know. And animations didn't get in the way, it just worked.
 
  • Like
Reactions: sysyphus' sister and Altis
It's a damn bug, people. I love all the people taking the opportunity to claim they are smarter and more competent than the entire Apple organization because the calculator app is a "high school level project" or whatever other ridiculous stuff I've seen.

Software is hard. Especially operating systems with massive software suites with millions and millions of features and use cases. You're never going to catch everything in regression testing.
 
  • Like
Reactions: C DM
trifid said:
I miss the pre iOS7 times when we had no clue what input-blocking was and didn't need to know. And animations didn't get in the way, it just worked.
Click to expand...

Sometimes I get out my old iPhone 4S and iPad 1 (1st generation!) on iOS 6 and 5, respective, just to remind myself how good it was.

Despite having much slower hardware, iOS flies on them and registers input very consistently.

The best I ever used was an iPhone 5 on iOS 6 -- probably the fastest iOS device there has ever been.
 
  • Like
Reactions: sysyphus' sister, MacFather and trifid
Thank goodness I still have a standard desk calculator.

I can type as fast as my fingers go and get the result I expect every time.

Or an old laptop running Excel, I can use the number pad and fly through calculations.

No excuse for this. You don’t have to wait when you type on the keyboard in iOS.
 
  • Like
Reactions: trifid
dannyyankou said:
This is not true, during the beta process I compared 11.0 to 10.3.3 and it wasn’t an issue before. No matter how quickly I typed the numbers in.
Click to expand...
While some others have mentioned seeing that issue and even running into it currently in iOS 10.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back