GNOME Bugzilla – Bug 691220
Text of "mouse" and "typing" items not visible and window not resizeable
Last modified: 2013-07-17 21:31:29 UTC
I can not read the description text of different items and the window is not resizeable. I guess we should a) make the window resizeable b) use multiple lines for the text
what version?
Created attachment 232866 [details] [review] More sensible window size so all the text is viewable by default.
Newest version has this problem with 1 option in shell and one option in mouse. The solution could be to make resizeable true in the shell.ui but that does not seem adequate. A better default resolution could be specified so these two options are readable that would be best. The system I used to test this was archlinux running GDM. Dont think resizing is very important aslong as all the text is readable.
I'm trying to keep the window the same size as gnome-control-center, I think increasing it is only a workaround until some other maintainer puts a super long string in their gsettings schema Ellipsizing the labels should be sufficient. If it is still not readable with ellipsizing then the schema should be changed to be more concise.
(In reply to comment #1) > what version? git master
So the problem is with the long winded gsettings descriptions.
(In reply to comment #6) > So the problem is with the long winded gsettings descriptions. No, I would say that the problem is that gnome-tweak-tool does not gracefully handle description strings that are outside the expected range. Please make the window resizeable, as it would have no real drawback and keeping it the same size as the gnome control centre is (IMHO) silly, because gnome control centre should be resizeable too. Trust that the users can choose their window sizes responsibly.
Please, make the window resizable. Actually, EVERY window should be resizable. I wonder why this is not obvious for everyone.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 704149 ***