3 ms·
It works like you say in standard mode by design because it's trying to match the behavior of older desk calculators that worked that way. In scientific mode it
by contextfree 6y ago
It works like you say in standard mode by design because it's trying to match the behavior of older desk calculators that worked that way. In scientific mode it respects order of operations.
There's a proposal to change the UI to make this clearer: https://github.com/microsoft/calculator-specs/blob/247bbb50d6d7f1d02410e967673a7ae095778d4f/active/TransactionalHistory/README.md https://github.com/microsoft/calculator-specs/blob/247bbb50d...
- dhosek 6y agoIt seems absurd to make the default behavior incorrect because older cheap calculators did the wrong thing. This isn't like making an incompatible change to a programming language to fix an incorrect behavior, this is more like if the designer of a new programming language decided to make 1+2*3 give nine because his cheap desktop calculator did the same.
- treesprite82 6y agoI've found that a surprising number of people (outside of fields like math, engineering, programming) are used to the idea of entering an operation and having it applied to the current value. E.G: pressing the [√] button immediately square roots the current number, pressing [X][2] doubles the current number, etc. It's a different paradigm to using the buttons to enter a full expression then pressing [=] to evaluate it, but I don't think it's accurate to call it "the wrong thing" - just that the button presses aren't transcribing to the equation you expect (the equation actually displayed by Windows 10 calculator is now accurate).