bitrate is given in kbit/s, not kB/s
Details
Diff Detail
- Repository
- R824 Baloo Widgets
- Branch
- bitrate
- Lint
No Linters Available - Unit
No Unit Test Coverage
src/widgetfactory.cpp | ||
---|---|---|
126 | I would prefer generalizing KFormat to accept an optional unit suffix, for e.g. bits, byte, meter, gramm, seconds ... |
src/widgetfactory.cpp | ||
---|---|---|
126 | That is the best solution, but I'm lacking the time to do it. |
thanks for working on this, I will test the your changes.
how likely is it that we can require Kf 5.48 soon in baloo-widgets? it may be worth to land this one in the meantime or should I abandon this revision?
In D13886 the requirements were set to the same as Dolphin, and it is currently at 5.43. Imho it would be better to add a compile time switch (afterwards)
I only bumped the min deps to be able to apply some coding standards and have better known build conditions, so the unit tests could be fixed to no longer fail.
Other than that no own stakes here, just a plain end user :)
Though looking at the KA18.08 release plan, dependency freeze date has been passed, so bumping the min kf version would no longer be possible.
https://community.kde.org/Schedules/Applications/18.08_Release_Schedule#Thursday.2C_July_12.2C_2018:_KDE_Applications_18.08_Dependency_Freeze
So a build time version switch seems to be the solution to approach, if you ask me.
Sorry for the long absence, I was on holiday. Can we agree on merging this patch for applications 18.08, and I will make a patch for 18.12 which uses the new capabilities of KFormat?
We froze translatable text on 19th July, see https://community.kde.org/Schedules
master branch if someone approves this.
I'm totally fine with implementing only the label change and not using KFormat if there are still concerns. This would be fully translatable.
Come on, it shouldn't take 5 month to implement a unit label fix.
I'll see what I can do.