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

iOS 11.2 Beta Fixes Calculator Bug Causing Incorrect Calculations when Numbers Are Rapidly Entered

C DM said:
Perhaps it might make sense to read the rest of my comments regarding the rest of it? Certainly makes that stupid and dishonest part quite ironic.
Click to expand...

I did read your entire comment. I'm not going to paw through your comment history to understand the inner workings of your mind.
[doublepost=1509407675][/doublepost]
chucker23n1 said:
Then maybe you shouldn’t call for “more or better OS developers“, thus implying the developers at Apple are somehow incompetent. That’s a rather insulting generalization.
Click to expand...

No, my post left open the possibility that they are understaffed or that the iOS update cycle needs to be lengthened. I'm also open to other explanations.

Anyways, it's not a generalization to suggest that iOS developers might be among those responsible for their own product.
 
rGiskard said:
I did read your entire comment. I'm not going to paw through your comment history to understand the inner workings of your mind.
Click to expand...
Nothing about any history or anything of the sort is involved. Seems like you simply read one of my comments to one part of your reply, but not the rest of my comments regarding the rest of your reply.
 
Hey Apple, while you're at it, how about a version for the iPad? Of course, first make sure it's good at math.
 
C DM said:
Realistically speaking it was being discussed here quite a bit before an actual article was put up: https://forums.macrumors.com/threads/calculator-app-is-unusable.2078357/ (and mentions of the issue go back even further into iOS 11 beta stage).
[doublepost=1509388467][/doublepost]
We can complain about the realities of the software development lifecycle, similar to complaining about the fees we have to pay for this or that here and there, and many other things in life basically, but none of that really changes the reality of things being what they are.
Click to expand...
Dated all the way back to september on Reddit. https://www.reddit.com/r/ios/comments/71zjm6/problems_with_calculator_app_on_ios_11/
 
  • Like
Reactions: trifid
Now they need to remove other animations throughout iOS (and macOS) that cause your input to be rejected. I might also accept implicitly cancellable animations (animations that stop to accept your input).
 
  • Like
Reactions: Act3 and Altis
C DM said:
And as I mentioned just because two things might seem similar doesn't mean that they are in fact similar, let alone the same. Just because keyboard animations are working fine or because other calculator apps which might not use animations or use one version or another that's available to them, doesn't mean that it all directly applies to another app in the same manner. We can make conjectures, but we still don't know the actual details.
Click to expand...

We know animations don't have to restrict the rate of touch input. Besides the keyboard and other calculators, there are various music keyboards that allow not only rapid entries, but simultaneous entries, all with animations, and there are countless games that have animations running while they accept input. Someone screwed up with the calculator, and the quickest fix was to throw out the animation, but you're not going to convince me it's the only fix, or even the only relatively easy fix. Yea, it's conjecture, but a pretty safe bet.
 
Last edited by a moderator:
  • Like
Reactions: trifid
I can't imagine Apple of 5 years ago taking till .2 release to fix a embarrassingly glaring bug like this. This worries me.
 
  • Like
Reactions: Jambalaya
CedricT said:
I can't imagine Apple of 5 years ago taking till .2 release to fix a embarrassingly glaring bug like this. This worries me.
Click to expand...
Nah, they just released iOS versions (like iOS 4) that just actually practically completely crippled some iPhone models so badly that Steve Jobs had to personally address it and promise that the issue would be taken care of in a future software update. But I mean what's crippling the whole device compared to calculator sometimes not working properly, right? Talk about worrisome.
 
Is to just me or are there too many dissenting 'newbie' posts popping up all over the shop?

What's that phrase for it that orange fella uses?

Anyway, what else is new in this latest update? That is if we can get past the Calculator thing - that most of you never actually noticed until it was publicised...
 
****, this needs an OS update to fix??????

Apple needs to separate APPs from OS, period. A calculator fix should simply be an update from the app store, period.
 
SohleBlatt54 said:
iOS 11.2 Beta 1 is out.
Nice - but where’s the 11.1 final version?
Click to expand...

Indeed. I have to say this looks and feels like a total shambles. My iPhone 6 regularly hangs now, way beyond a "lag".

As I posted before I have had iPhones since 3G and have always upgraded iOS straight away and without any issues. iOS11 has been and more importantly continues to be a right "dogs breakfast" (as we say here, i.e. you through a load of left overs into a bowl and mix it up, hey ho the dog will just gladly eat it all up)
 
samwight said:
We know animations don't have to restrict the rate of touch input. Besides the keyboard and other calculators, there are various music keyboards that allow not only rapid entries, but simultaneous entries, all with animations, and there are countless games that have animations running while they accept input. Someone screwed up with the calculator, and the quickest fix was to throw out the animation, but you're not going to convince me it's the only fix, or even the only relatively easy fix. Yea, it's conjecture, but a pretty safe bet.
Click to expand...
A fair conjecture, but still not one we can confirm, nor use to rule out other conjectures without knowing the actual details. Just that simple.
 
C DM said:
A fair conjecture, but still not one we can confirm, nor use to rule out other conjectures without knowing the actual details. Just that simple.
Click to expand...
What's your point? Others can make calculators with animations and rapid input, but Apple ditched their animation to get rapid input to work. We may have to speculate on the specific reason, but there's no conjecture about the possibility of calculator animations with rapid input, and Apple's failure to deliver one.

If the comma key in Apple's messaging app always generated a semi-colon, and Apple's fix was to remove the comma key, we'd have to conjecture about the specific reason why, but that would not stop us from being critical of Apple. Nor, presumably, would that stop you from defending Apple.
 
samwight said:
What's your point? Others can make calculators with animations and rapid input, but Apple ditched their animation to get rapid input to work. We may have to speculate on the specific reason, but there's no conjecture about the possibility of calculator animations with rapid input, and Apple's failure to deliver one.

If the comma key in Apple's messaging app always generated a semi-colon, and Apple's fix was to remove the comma key, we'd have to conjecture about the specific reason why, but that would not stop us from being critical of Apple. Nor, presumably, would that stop you from defending Apple.
Click to expand...
The conjecture is about what the underlying issue actually was and what was needed to address it (and why it all happened the way it did). Nothing more, nothing less.
 
C DM said:
Nothing about any history or anything of the sort is involved. Seems like you simply read one of my comments to one part of your reply, but not the rest of my comments regarding the rest of your reply.
Click to expand...

What was your point again? That I've insulted Apple's software engineers?

You know what I find insulting? When I update my A8 iPhone from iOS 10 to iOS 11 and it becomes a stuttering unresponsive mess. The A8 is used in current Apple products (iPad Mini 4) so there is no excuse for this. I've tried a full reset and restore to no avail and others report the same issues on the A8 so the problem is definitely with iOS 11.

If you have a better explanation than any of those I suggested then I'd love to hear it.
 
rGiskard said:
What was your point again? That I've insulted Apple's software engineers?

You know what I find insulting? When I update my A8 iPhone from iOS 10 to iOS 11 and it becomes a stuttering unresponsive mess. The A8 is used in current Apple products (iPad Mini 4) so there is no excuse for this. I've tried a full reset and restore to no avail and others report the same issues on the A8 so the problem is definitely with iOS 11.

If you have a better explanation than any of those I suggested then I'd love to hear it.
Click to expand...
Reading what I said would actually cover that. But since it doesn't seem like it has happened (or will happen) it doesn't sesm like there's more to say about it.
 
Bryan Bowler said:
The fact that this has been reported over and over since the initial iOS beta testing period and Apple is not getting around to it until 11.2 shows that Apple is in way over its head.
Click to expand...

I don't have numbers enough to call that a fact, do you?
 
C DM said:
The conjecture is about what the underlying issue actually was and what was needed to address it (and why it all happened the way it did). Nothing more, nothing less.
Click to expand...
Right, but then why defend Apple by saying "bugs happen, even with good programmers"? Bugs do happen, and so does debugging. The point is: if Apple is unable to (or doesn't want to) deliver a feature ubiquitous in other apps on the iPhone, they deserve criticism. Bugs are excusable; Apple's response is unworthy, though it probably just indicates the low level of priority they consider the problem to be.
 
samwight said:
Right, but then why defend Apple by saying "bugs happen, even with good programmers"? Bugs do happen, and so does debugging. The point is: if Apple is unable to (or doesn't want to) deliver a feature ubiquitous in other apps on the iPhone, they deserve criticism. Bugs are excusable; Apple's response is unworthy, though it probably just indicates the low level of priority they consider the problem to be.
Click to expand...
Making a statement about reality doesn't mean defending, just because it's not attacking at the same time.
 
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