Calculator app is unusable

mrex

macrumors 68040
Original poster
Jul 16, 2014
3,284
1,350
europe
After the ios11 the new calculator app is unusable. It is laggy and you should t-y-p-e veeeerrryyy sloooowly otherwise it doesnt recognize your tapping.. i cannot use it at all.

Trying to calculate 12x12 i usually see 1212 rather than 144 on the screen because it didnt recognized tapping the x.

Anyone else?
 

C DM

macrumors Sandy Bridge
Oct 17, 2011
47,549
16,046
After the ios11 the new calculator app is unusable. It is laggy and you should t-y-p-e veeeerrryyy sloooowly otherwise it doesnt recognize your tapping.. i cannot use it at all.

Trying to calculate 12x12 i usually see 1212 rather than 144 on the screen because it didnt recognized tapping the x.

Anyone else?
Strange. No matter how fast I try to do it, 12 x 12 always gives me 144.

Quickly trying to add 1 + 2 + 3 + 4 + 5 will sometimes not work as an addition would not get registered at times, but I'd need to do all that fairly quickly for that to happen sometimes.
 
  • Like
Reactions: Sdtrent

Feenician

macrumors 603
Jun 13, 2016
5,180
4,788
After the ios11 the new calculator app is unusable. It is laggy and you should t-y-p-e veeeerrryyy sloooowly otherwise it doesnt recognize your tapping.. i cannot use it at all.

Trying to calculate 12x12 i usually see 1212 rather than 144 on the screen because it didnt recognized tapping the x.

Anyone else?
Yes, it’s been discussed to death. Pretty ridiculous it happened and even more so that it hasn’t been fixed yet. Priorities and all but this is something an intern should be able to do in an afternoon.
[doublepost=1508221720][/doublepost]
Strange. No matter how fast I try to do it, 12 x 12 always gives me 144.

Quickly trying to add 1 + 2 + 3 + 4 + 5 will sometimes not work as an addition would not get registered at times, but I'd need to do all that fairly quickly for that to happen sometimes.
It’s because when you press an operator the operator gets highlighted, when you press a number afterwards the operator begins to fade. If you press a number, then operator again before that fade finishes the input is blocked and the number you press next is appended. In the case of 12x12 there’s no opportunity for that to happen/.
 
  • Like
Reactions: trifid

C DM

macrumors Sandy Bridge
Oct 17, 2011
47,549
16,046
Yes, it’s been discussed to death. Pretty ridiculous it happened and even more so that it hasn’t been fixed yet. Priorities and all but this is something an intern should be able to do in an afternoon.
[doublepost=1508221720][/doublepost]

It’s because when you press an operator the operator gets highlighted, when you press a number afterwards the operator begins to fade. If you press a number, then operator again before that fade finishes the input is blocked and the number you press next is appended. In the case of 12x12 there’s no opportunity for that to happen/.
OP seems to say that it's happening with 12 x 12, given that's the first (and only) example that was provided. Which made it sound a little odd.
 

mpavilion

macrumors 6502a
Aug 4, 2014
924
534
SFV, CA, USA
Yes, it’s been discussed to death. Pretty ridiculous it happened and even more so that it hasn’t been fixed yet. Priorities and all but this is something an intern should be able to do in an afternoon.
[doublepost=1508221720][/doublepost]

It’s because when you press an operator the operator gets highlighted, when you press a number afterwards the operator begins to fade. If you press a number, then operator again before that fade finishes the input is blocked and the number you press next is appended. In the case of 12x12 there’s no opportunity for that to happen/.
Were the operator keys highlighted previously (pre-iOS 11), and the "highlight" disappeared immediately when a number key was pressed (instead of doing the slow fade)? I don't remember how it worked.
 

KGB7

Suspended
Jun 15, 2017
925
733
Rockville, MD
It is an annoying bug. Not matter what calculation you try to type in quickly, it doesnt work properly.

You have to type it very very slowly, there is a 1-2 second wait period between each button press.
 
  • Like
Reactions: g-7

C DM

macrumors Sandy Bridge
Oct 17, 2011
47,549
16,046
It is an annoying bug. Not matter what calculation you try to type in quickly, it doesnt work properly.

You have to type it very very slowly, there is a 1-2 second wait period between each button press.
I have to try to type it quickly to get some calculations to get messed up, otherwise with normal typing it seems to work correctly pretty much every time for me.
 

Feenician

macrumors 603
Jun 13, 2016
5,180
4,788
Were the operator keys highlighted previously (pre-iOS 11), and the "highlight" disappeared immediately when a number key was pressed (instead of doing the slow fade)? I don't remember how it worked.
I don't remember if the animation was as slow. Even if it was I think the problem lies in the animation (any animation really) blocking input.

OP seems to say that it's happening with 12 x 12, given that's the first (and only) example that was provided. Which made it sound a little odd.
Indeed. bad example by the OP.
 

mrex

macrumors 68040
Original poster
Jul 16, 2014
3,284
1,350
europe
Yes a very bad example, i should have provided inifinite examples xD

The point is that the calculater is utterly slow and useless as it is now. But good to know that it is not only me who has this issue - so i dont need to consider to reinstall anything..
 

Feenician

macrumors 603
Jun 13, 2016
5,180
4,788
i should have provided inifinite examples xD
Just one that actually fails would have done the trick. It doesn't matter how fast you type your example, as long you type it accurately it will work correctly because it doesn't trigger the bug in question which requires hitting an operator, then a number, then the operator again before it has completed its fading animation.

Which, again, is not to excuse the actual bug, which is pretty ridiculous.
 

BigMcGuire

Contributor
Jan 10, 2012
4,623
5,670
California
Wow you're right. 1+1+1+1+1 is SUPER laggy and impossible to do fast. Literally have to do it slower than 1 second a keypress. How interesting.
[doublepost=1508260299][/doublepost]
Just one that actually fails would have done the trick. It doesn't matter how fast you type your example, as long you type it accurately it will work correctly because it doesn't trigger the bug in question which requires hitting an operator, then a number, then the operator again before it has completed its fading animation.

Which, again, is not to excuse the actual bug, which is pretty ridiculous.
Yep, this explains it. Nice.


Anyone have a paid calc app that they recommend? I can't stand ads.
 

Feenician

macrumors 603
Jun 13, 2016
5,180
4,788
Wow you're right. 1+1+1+1+1 is SUPER laggy and impossible to do fast. Literally have to do it slower than 1 second a keypress. How interesting.
[doublepost=1508260299][/doublepost]

Yep, this explains it. Nice.


Anyone have a paid calc app that they recommend? I can't stand ads.
Pcalc lite is free, has no ads and is a good basic calculator, even having some constants and conversions in there for free too. The full version of Pcalc is $9.99 but you will never want for anything in a calculator again.
 

BigMcGuire

Contributor
Jan 10, 2012
4,623
5,670
California
Pcalc lite is free, has no ads and is a good basic calculator, even having some constants and conversions in there for free too. The full version of Pcalc is $9.99 but you will never want for anything in a calculator again.
Wow you weren't kidding. This calculator app is amazing! Thanks!
 
  • Like
Reactions: Ravi_MR

macfacts

macrumors 68040
Oct 7, 2012
3,508
4,134
Cybertron
I have to try to type it quickly to get some calculations to get messed up, otherwise with normal typing it seems to work correctly pretty much every time for me.
Translation: people are typing it wrong aka holding it wrong. Too many words per minute, slow down.
 
  • Like
Reactions: Demo Kit

zorinlynx

macrumors 603
May 31, 2007
5,556
6,517
Florida, USA
This is probably the most embarrassing iOS 11 bug.

- It was reported early in the beta process.
- It is trivial to reproduce.
- There is no reason for it to exist (Calculator has no new features since iOS 10; they didn't need to touch the code at all but they not only did, but BROKE it too)
- It should be trivial to fix.

Luckily there's a lot of third party calculators available, but I could see someone getting an incorrect result from this bug and that could be pretty bad depending on what it is.