-
Notifications
You must be signed in to change notification settings - Fork 6.5k
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Unit conversion bug #31310
Comments
Displaying incorrect conversion values in PowerToys Run when changing units |
Short story is: 10^2 = 1000 and 2^10 = 1024. A long, long time ago these were mixed up, meaning a kilobyte is/was 1024 bytes, while "kilo" should mean 1000. Nowadays, we invented the term kibibytes. Not even talking about the combination of the two types mentioned on storage devices... It's actually bad practice of Microsoft to keep using the wrong unit, like, everywhere. |
Not sure if it was ever a mix up. Computer use base 2 not base 10. It is standard practice to refer to a kilobyte to be 1024 and not 1000. |
|
@Jay-o-Way The initial screenshot show 1024 MB being reported as 1.024 GB. This would be correct to you right? |
Just a short rant against Microsoft, haha. Conclusion for this issue is valid: non-issue. |
It's been over 20 years since the standards were established... I didn't know because I've only been using Windows OS. Thanks for letting me know |
I never realised I am duplicating.. sorry! |
Since PowerToys is uniquely Microsoft related product I would love to hear your thoughts on potentially "fixing the historical issue" and provide accurate results for both each time regardless of the query?
|
Microsoft PowerToys version
0.78.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
PowerToys Run 에서 단위변한 시 잘못된 변관 값 표시
예)
%%1024Mb in Gb
✔️ Expected Behavior
1.000Gb
❌ Actual Behavior
1.024Gb
Other Software
No response
The text was updated successfully, but these errors were encountered: