Skip to content
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

Distinguish "calculate immediately" and "calculate after pressing ENTER" #1489

Closed
lsht-cn opened this issue Feb 7, 2021 · 3 comments
Closed
Labels
duplicate Issue identified as a duplicate of another issue(s) Enhancement Pri: 2

Comments

@lsht-cn
Copy link

lsht-cn commented Feb 7, 2021

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.

@ghost ghost added this to Pitch in Feature Tracking Feb 7, 2021
@lsht-cn lsht-cn changed the title *Distinguish "calculate immediately" and "calculate after pressing ENTER" Distinguish "calculate immediately" and "calculate after pressing ENTER" Feb 7, 2021
@VarunAroraCode
Copy link

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?

@MicrosoftIssueBot
Copy link
Collaborator

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

@mcooley
Copy link
Member

mcooley commented Feb 17, 2021

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.

@mcooley mcooley closed this as completed Feb 17, 2021
@mcooley mcooley added the duplicate Issue identified as a duplicate of another issue(s) label Feb 17, 2021
@microsoft microsoft locked as resolved and limited conversation to collaborators Mar 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate Issue identified as a duplicate of another issue(s) Enhancement Pri: 2
Projects
Development

No branches or pull requests

4 participants