-
Notifications
You must be signed in to change notification settings - Fork 5
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
"no device names" and "big numbers" do the same thing #8
Comments
I cannot reproduce this behaviour. When I change setting from "no device names" to "big numbers" I can see that it not only shifts the numbers but also made them bigger. But maybe you've found a specific use-case where this size change is not visible? |
I can see you have a little bit different spacing then me but still "big numbers" was created from "no device names" to preserve more space for showing bigger numbers with container being wider (not squared). From the screenshots I can see that "big numbers" actually preserves a little vertical space in vertical panel. The weird spacing in "full view" is caused by the need to keep the font smaller so higher numbers are not overflowing the arrows. One line is mostly made for horizontal panels. But maybe I'm not answering the right points you want me to... Please feel free to suggest some changes or ideas :) |
Basically, I have expected picture 2 to look like picture 1 (small text, arrows), but without the "enp5s0" text. There is almost no difference between picture 2 and 3 as it is now, at least for me. |
You are right they look very similar. They was created on some users' demands to show bigger numbers. I think all 4 options are used by users so I'm probably going to leave them there of the time being. |
I think this might be a bug. I expected "no device names" look like "full view" but without, well, the device names. However, selecting it makes the up/down arrows disappear and the number grow bigger. Setting it to "big numbers" shifts the numbers a bit, but the size stays the same.
The text was updated successfully, but these errors were encountered: