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
1.4.0 Text Off Set Under Columns #41
Comments
Hi @Geyup, Yes I think setting every columns "left align" should result in a more consistent UI. |
I've pushed this tweaking in the develop branch of my own repo: https://github.com/gfarmerfr/nicotine-plus/tree/develop. |
YEAH it's working nice, everything aligned to the left... :) Can fonts or themes have an effect on this, I would think not, but I can test if you like? THANKS gfarmerfr keep up the great work! |
Yes I would appreciate if you found out if themes would influence this. I don't this they would mess with gtk cell alignment but we never know. At least on the 2-3 themes I have on Gnome 3 I don't see any difference. |
Ok will let know... thanks |
I'm using Slackware 14.2 x86_64 with python-2.7.13.
I noticed under the
Search
andDownloads
sections text is offset, meaning, for the given section text is not appearing directly underneath the section aligned under the first letter as some of the sections are.Size
under theSearch Files
the text is located more to the right, and right next to the text forSpeed
. The numbers should appear under the S, appearing as an example like below;Size
9.5MB
In queue
under theSearch Files
the text is also located more to the right, and right next to the text forImmediate Download
Same thing, text, the numbers for
In queue
don't appear lined up under the letterI
as they should like below;In queue
20
Length
section the numbers are off set to the right and not appearing under, the letterL
lined up like below as example;Length
3:59
Please see the attached screen shot for what I mean.
It would be nice to have separation of the text, like how the other sections all appear. Not sure why these sections are like this, hmm...
Thanks
The text was updated successfully, but these errors were encountered: