You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Distinguish "calculate immediately" and "calculate after pressing ENTER"
Evidence or User Insights
After making this improvement, meaningless issues will be reduced (for example issue#1349 (has been closed))
This suggestion is to avoid the problems like issue#1349
Proposal
I saw some users complaining about the calculation logic. The calculator should provide an option to distinguish between the two calculation orders-one is to calculate the result to support the next calculation request immediately after entering each calculation symbol, and the other is to allow the user to enter the calculation before performing the calculation .
Goals
Non-Goals
Low-Fidelity Concept
Requested Assignment
Sorry, I cannot realize it. But I really want
I'm just suggesting this idea. I don't want to implement it.
PS. Translated by Google Translate, the text may not be so clear. But it is okay if you can understand what I mean.
The text was updated successfully, but these errors were encountered:
lsht-cn
changed the title
*Distinguish "calculate immediately" and "calculate after pressing ENTER"
Distinguish "calculate immediately" and "calculate after pressing ENTER"
Feb 7, 2021
I have a project for a software methodology class to contribute to an open source repo and I am very interested in this project. Could I be assigned to this issue?
Thanks for the suggestion! It seems like this is a suggestion to address feedback like #138. We recently made an improvement (in #1453) which we think will make the behavior easier to understand, so I don't think any additional changes are needed at this time.
Distinguish "calculate immediately" and "calculate after pressing ENTER"
Evidence or User Insights
After making this improvement, meaningless issues will be reduced (for example issue#1349 (has been closed))
This suggestion is to avoid the problems like issue#1349
Proposal
I saw some users complaining about the calculation logic. The calculator should provide an option to distinguish between the two calculation orders-one is to calculate the result to support the next calculation request immediately after entering each calculation symbol, and the other is to allow the user to enter the calculation before performing the calculation .
Goals
Non-Goals
Low-Fidelity Concept
Requested Assignment
Sorry, I cannot realize it. But I really want
I'm just suggesting this idea. I don't want to implement it.
PS. Translated by Google Translate, the text may not be so clear. But it is okay if you can understand what I mean.
The text was updated successfully, but these errors were encountered: