https://bugzilla.novell.com/show_bug.cgi?id=230699 ------- Comment #8 from sh@novell.com 2007-01-08 11:52 MST ------- In general, the disk usage pane and the filter pane above it have to negotiate screen space demands. Since the upper pane (the filter pane) is really a stack of all the available filter views, in most cases it can put more screen space to good use: To display more of the RPM groups tree, more languages from the languages list, more patches (and more patch description) of the patches view, more patterns of the patterns list. Most of those filter views can scroll, i.e. they don't have a really useful default height. The same is true for the disk usage list. If there are no other restraints, the QSplitter widget that contains both panes will try to make a compromise - it will simply give each pane half of the available space. This behaviour is of course pretty simplistic, but it's what that QSplitter will do by default. So we have to introduce more restraints; obviously splitting the entire left pane in half height-wise is not the way to got. That restraint is a fixed preferred size for the disk usage list. In addition with Qt's size policies, we can manage to hold down the amount of screen space used for the disk usage pane, thus allowing more space for things that are commonly more useful for the user. Given a great amount of time, we could probably create our own resizing management of that left pane -- say, a minimum for the disk usage, plus somewhat more if there is a lot more than any of the filter views in the upper pane can reasonably use. But apart from programming time and resources this will also create a lot more bloat in the software for questionable return. It will certainly not make the code any more robust. I have doubts if it even will work in all scenarios; some users will want more screen space for one or the other of the filter views, some will want more space for the disk usage. You can't be everybody's darling. Been there, done that. That's ultimately why the dividing line can be moved. There is no generic solution to that problem. There can always only be a compromise, and compromises by their very nature do not please everybody. Sorry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.