Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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?
Sure, glitch, bug, they are essentially synonymous when it comes to software.
 
While some others have mentioned seeing that issue and even running into it currently in iOS 10.
From the video on the last page, it’s clear that it was an issue with 9.3.5, it was fixed at some point including 10.3.3, and it reappeared again.

Point is it doesn’t matter how it operated before, it needs to be fixed.
 
You don't get it... the irony is the hardware is cutting edge reaching the power of conventional PCs, and yet it's being hindered by the bad software engineering.
What part of what I said says something different? Seems like I'm not the one not getting something (on purpose or not).
[doublepost=1508903874][/doublepost]
From the video on the last page, it’s clear that it was an issue with 9.3.5, it was fixed at some point including 10.3.3, and it reappeared again.

Point is it doesn’t matter how it operated before, it needs to be fixed.
So basically some that have posted here about experiencing it in iOS 10 are making it up? Another user seeing it in iOS 10 as mentioned in a post below.

And as far as that affecting whether or not it needs to be fixed, none of this is talking about that. There's a bug, and it needs to be fixed, as has been mentioned many times before, it's just that isn't what this particular part of discussion is about.
 
Last edited:
So basically some that have posted here about experiencing it in iOS 10 are making it up?

And as far as that affecting whether or not it needs to be fixed, none of this is talking about that. There's a bug, and it needs to be fixed, as has been mentioned many times before, it's just that isn't what this particular part of discussion is about.
Perhaps the bug did exist at some point in iOS 10. But it was clearly working properly on 10.3.3 based on my experience and the screen recording on the last page. Maybe the bug existed on 10.1.1 or something, who knows?
Either way, it doesn’t make a difference for me because there’s great third party calculator apps.
 
Perhaps the bug did exist at some point in iOS 10. But it was clearly working properly on 10.3.3 based on my experience and the screen recording on the last page. Maybe the bug existed on 10.1.1 or something, who knows?
Either way, it doesn’t make a difference for me because there’s great third party calculator apps.

You gotta type faster.
 
Perhaps the bug did exist at some point in iOS 10. But it was clearly working properly on 10.3.3 based on my experience and the screen recording on the last page. Maybe the bug existed on 10.1.1 or something, who knows?
Either way, it doesn’t make a difference for me because there’s great third party calculator apps.
Seems like some are seeing it in iOS 10.3.3 nonetheless:
Actually it happens on iOS 10.3.3 as well.. i Just tried it.

(Stupid calculator)
 
Well. this app has other issues... try Sin[pi] -> it returns 0.05...

The answer should be zero. When you try to same with Mathematica using the rounded value used for Pi in the iOS app, the result is, as should be, 1.22465*10^-16.

Cheers,
Bernard
 
A calculator app is supposed to be a high school level project. Yet apple cannot get it right. This is extremely embarrassing.

Something of a non-story as far as I can see. I'm no speed demon when it comes to using a touch screen and I can't get the calculator to mess up like the article suggests. This story appeared yesterday on the hilariously titled Independent newspaper website in the UK. A publication that treats truth with contempt and is unashamed in its endless propaganda filled OpEds.
Highly embarrassing?
Not really. It's not as if the mathematics functions are actually broken. If you ride a motorcycle too fast it becomes hard to control, is this "highly embarrassing" for the manufacturer?
 
I hope Apple reads these threads because this points out the issue of my bug report 100%. The new iOS is over the top with it’s view animations and they not only slow the operations down they bother the user’s eyes and now we find the clock tics required actually causes errors.

While computers are visual these days they still have to compute and this clearly is a major error, all in the name of looks.

Oh I tried the error and it happened 100% of the time.

Fix this Apple!!!!
 
  • Like
Reactions: simonmet
It's Cook economics for something that should cost $6 he will charge you $24 :p it's a feature working out Apple Cook tax
 
  • Like
Reactions: simonmet
This is absolutely pathetic. Steve Jobs once said Apple is foremost a software company, and that's actually the fundamental strength of Apple. Guess Tim Cook forgot about all this long time ago. Well don't think he ever understand it anyway.
There must have been no software issues when Steve Jobs was around.
 
Is it annoying? Yes. Is it embarrassing? Sure. Does it really matter? No. The workaround is to hit the equal button after every operation, OR use a real calculator OR use a program like Excel/Numbers.
 
I've been reporting this glitch since the first day the beta came out because it drove me nuts. I just downloaded another calculator app. So ridiculous because Apple had a good running calculator app in iOS 10. How do you screw up something so simple.

Easy. You hire mediocre developers and designers - which Apple seems to have had since iOS 10. Every release gets worse, less intuitive, and harder on the eyes and mind. Every single release is worse, more cluttered, confusing, etc. Steps back taken in simple apps - like screwing up calendar, notes, and now calculator. It’s extremely worrying.
[doublepost=1508909304][/doublepost]
Yeah, but those are Google phones. Stuff like that can happen to any mass-produced product.

But being an Apple product, this calculator bug is an example of why Apple is terrible, Tim Cook should be fired, Steve Jobs would never etc. etc. etc.

Don't get me wrong- this bug shouldn't have lasted so long. But it's also an incredibly minor thing to throw a fit about.

Isn’t it being minor - kind of the point? Apple is failing at simple tasks.
 
Well. this app has other issues... try Sin[pi] -> it returns 0.05...

The answer should be zero. When you try to same with Mathematica using the rounded value used for Pi in the iOS app, the result is, as should be, 1.22465*10^-16.

Cheers,
Bernard

Edit: As has been pointed out by some observant members below, we both made the mistake of not noticing the trigonometric mode is degrees by default, so Calculator is correct.

My bad.
 
Last edited:
  • Like
Reactions: sysyphus' sister
Well. this app has other issues... try Sin[pi] -> it returns 0.05...

The answer should be zero. When you try to same with Mathematica using the rounded value used for Pi in the iOS app, the result is, as should be, 1.22465*10^-16.

Cheers,
Bernard

That's because you are calculating in degrees and not radians. Change this with the button in the bottom left corner and then sin(pi) = 0
 
  • Like
Reactions: adrianlondon
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.