| Summary: | Please follow BinaryUnitDialect, appropriately | ||
|---|---|---|---|
| Product: | [Applications] plasma-systemmonitor | Reporter: | Erik Quaeghebeur <bugs.kde.org> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | ahiemstra, andreas_nordal_4, dave, jrb3218, kde, nate, plasma-bugs, vmelkon, zakhar.nasimov |
| Priority: | NOR | ||
| Version: | 5.24.4 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=364321 https://bugs.kde.org/show_bug.cgi?id=475459 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Bug Depends on: | 57240 | ||
| Bug Blocks: | |||
|
Description
Erik Quaeghebeur
2022-05-15 20:36:20 UTC
I have tested this on Kubuntu 22.04 I can confirm that I have the same result. KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 I have tried BinaryUnitDialect=2 and BinaryUnitDialect=1. In both cases, KSysGuard just ignores it and keeps on showing kiB, MiB, GiB, TiB. *** Bug 464604 has been marked as a duplicate of this bug. *** There is no UI for this setting and seems it is not even global, only KIO reads it https://lxr.kde.org/search?%21v=kf5-qt5&_filestring=&_string=%22BinaryUnitDialect%22 (In reply to David Redondo from comment #3) > There is no UI for this setting That is the topic of the linked bug report: https://bugs.kde.org/show_bug.cgi?id=364321 This is a chicken-and-egg problem: as long as applications to not support it, the value of a GUI is limited and developers will not find it urgent, and application developers will point to the lack of a GUI to say that it is not urgent > it is not even global, only KIO reads it I cannot comment on this. I guess that means it is harder to implement? AFAIU previously, it was just a matter of using existing framework functions that do support it. Then perhaps a new bug report is in order to request for better support for this in a framework. *** Bug 467317 has been marked as a duplicate of this bug. *** *** Bug 391596 has been marked as a duplicate of this bug. *** > AFAIU previously, it was just a matter of using existing framework functions that do support it That's correct, yes. The frameworks-provided function has been fixed to read the setting properly; see https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/352. Now System Monitor just needs to use it and then this will get fixed automatically. *** Bug 474155 has been marked as a duplicate of this bug. *** Is it a good idea to use the same configuration for everything? There may be opposite conventions to follow: For network speed, I would even suggest that if the configuration isn't SI, the configuration is wrong. But opposite for memory and partition sizes. Not that I would argue for more options. Rather that getting the default right in each case without not making the user choose between two wrongs is more important. Good idea.
"Not that I would argue for more options. Rather that getting the default right in each case without not making the user choose between two wrongs is more important."
>>I would argue for more options. Nothing wrong with more options, as long as it is documented somewhere. After all, Microsoft documents their registry keys and someone publishes 500 page books on Windows Server.
If Microsoft can program a feature, then so can anyone.
(In this case, Windows doesn't have such features).
|