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

Calculator result are wrong if using . instead of , for decimals #22905

Closed
ternium1 opened this issue Dec 20, 2022 · 5 comments
Closed

Calculator result are wrong if using . instead of , for decimals #22905

ternium1 opened this issue Dec 20, 2022 · 5 comments
Labels
Issue-Bug Something isn't working Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ternium1
Copy link

Microsoft PowerToys version

0.65.0

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

PowerToys Run

Steps to reproduce

Execute a simple calculation in Powertoys run involving a decimal number (for example 100*0.01) and using . as the decimal separator

✔️ Expected Behavior

1000.01 should output 1 with the comma or the dot as a decimal separator. However, 1000,01 works fine.

image

❌ Actual Behavior

1000.000000001 outputs 10, 1000.1 also outputs 10 however 100*0,01 outputs the correct result (1)

image
image

Other Software

No response

@ternium1 ternium1 added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Dec 20, 2022
@htcfreek
Copy link
Collaborator

htcfreek commented Dec 21, 2022

@ternium1
Please check the plugin settings to make sure the input format is used as configured. You can change the decimal delimiter there.

@Jay-o-Way
Copy link
Collaborator

@htcfreek again, it's not the decimal that is the problem, it's the leading zeros that come after it. They get clipped off, so the engine always calculates 100*0.1

@Jay-o-Way
Copy link
Collaborator

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #19741

@ghost
Copy link

ghost commented Dec 21, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Dec 21, 2022
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Dec 21, 2022
@htcfreek
Copy link
Collaborator

@htcfreek again, it's not the decimal that is the problem, it's the leading zeros that come after it. They get clipped off, so the engine always calculates 100*0.1

@Jay-o-Way
And why does it then work for me with plugin setting "en-us format for input" set to enabled?!

I can reproduce it in the exact other way than reported. And that makes sense as I changed the input format to en-us.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug Something isn't working Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants