Why are speeds sometimes truncated as 20.27KiB[..].12KiBps?

[NightMachinery]

Why are speeds sometimes truncated as 20.27KiB[..].12KiBps?

This happens even on extremely low zooms:

[cyqsimon]

The table formatting logic used to be quite flawed. I've done a complete rewrite in #305, which should fix this issue. Please test and see if you are happy with it. You can either pull the table-layout-rewrite branch and build locally, or download the latest CI build.

Further improvement suggestions welcomed!

[cyqsimon]

Notifying everyone who thumbed-up this issue:
@Fabian42 @kescherCode @Rouzip @Michcioperz @jkmpariab @Abhinickz @NikitaPuzyryov @thundergolfer

[azzamsa]

Getting better.

[kescherCode]

Much better from the table-layout-rewrite branch :D

Before	After

[cyqsimon]

I'm looking at the "Up / Down" column - maybe it would be better to put "per second" up in the column name?

So instead of this:

Up / Down
12.34KiBps / 56.78KiBps

We would have something like:

Up / Down speed (ps)
12.34KiB / 56.78KiB

What do you think?

[kescherCode]

@cyqsimon Indeed, this would make the only difference (in terms of table content) between normal and cumulative mode (-t) be the table header.

[cyqsimon]

Okay, normal mode (without -t) now looks like this:

I don't think there is a need to put per second anywhere since it's pretty obvious that's what it is, plus real estate is expensive.

[cyqsimon]

Okay, by the lack of replies in this thread, seems like people are happy. I will go ahead and merge #305.