A calculator app is supposed to be a high school level project. Yet apple cannot get it right. This is extremely embarrassing.
You not calling it a calculation glitch doesn’t change reality.BUT it's NOT a calculation glitch because it's not 1+2+3 = 24. What you're getting is 1+23. If I typed 1+2+3 and that's exactly what was recognized and I get 24 then yeah that's a calculation glitch. All it is is the "+" sign isn't being picked up when quickly typed after the 2. It's a moot point if typed 1/2 a second slower.
So this isn't a bug in the calculation process (i.e. the inherent processes within the app) but a problem with the animation process in the app. Sure it should be fixed but is this really a big issue.
For a start why is anyone adding 1+2+3 or other simple calculations using a calculator? Are people really typing complex calculations that quickly?
No. I would say they are young new hires, untrained, and un-mentored-by-older staff who understood what testing is and who seem to have disappeared.Of course, people at Apple are getting old.
Speed is not tested anymore.
Rumors says Apple care will be limited to 25.
You not calling it a calculation glitch doesn’t change reality.
You seem to have trouble with such a basic concept, but let’s do a test: it’s definitely a calculator glitch, correct? As in a glitch in the calculator app...
Everyone knows that its not a real calculator unless it does reverse polish notation, so who cares, its just another toy for the kids.
Apple yet again prioritizing form over function. While I enjoy their penchant for quality aesthetic, design is also how it works and this does not work well.
+1 for Calcbot. It's what I use when I need to do some real calculations with tape and everything. It's a necessity for the iPad which still—in 2017—doesn't come with a freaking calculator.
Mathgate
Seriously Apple, do we need animation effects for the operator buttons?
I know having little funI know you are using the *gate for amusement but this is not a maths issue - the app does its calculations correctly every time. The issue is the slowness of the app and its ability to cope with "rapid" data entry.
What he's saying is that the calculator logic is fine. You're stuck on semantics of calling a "calculation glitch" because "it's in the calculator app". It is not a calculation glitch.
It's a horrible and lazy error, but it's not a "calculation glitch", because you can type slower and get the real answer every time.