New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect division in natural mode #941
Comments
Well I don't feel that there is a bug here. It's inherent to the use of natural writing. In natural writing, when you type "2/3" then "/4", it displays "2/(3/4)". If you want to input "(2/3)/4" just press the right arrow key after "2/3" : or The priority is represented by the length of the fraction bar. Do you agree? |
I guess I'll have to agree, but it might be confusing for some students who are expecting one answer, but get another. |
Sure! I've just tried with other calculators and https://www.geogebra.org/graphing and it's the same behavior. But the 2D natural display makes things clear, right? |
Yes, I believe so. While I have your attention, is there any planned support for mixed fractions? |
Definitely not a bug. Works the same way on other platforms, and there is no ambiguity on the display. 😄 |
Could you please give me an example of what you're looking for? |
It would be nice if typing in |
Ok! I wasn't familiar with this writing. You should open a new issue about this |
Describe the bug
When in natural writing mode, the calculator gives the wrong answer. For example, when I type in
5/4/3/2
the calculator says that the answer is15/8 = 1.875
when the answer should really be5/24 = 0.2083333
. If I type in5/4/3/2
in natural mode, then I switch to linear mode it says that it's really calculating(5)/((4)/((3)/(2)))
instead of((5 / 4) / 3) / 2
Screenshots
Left/top is natural mode, right/bottom is linear mode
To Reproduce
Steps to reproduce the behavior:
5/4/3/2
5/4/3/2
Expected behavior
The calculator should correctly follow the order of operations in both writing modes and display
5/4/3/2 = 5/24 = 0.2083333
Environment
The text was updated successfully, but these errors were encountered: