Registered Member
|
Many windows have invalid default dimensions, or suboptimal ones on a fresh KDE install (think Amarok's squished main window, Ark's smashed "Extract" dialog, super-skinny/long Ktorrent, etc).
This isn't just application windows, either -- the crash report dialog needs to be expanded vertically, as does a Kwallet dialog, since the text is actually cut off in these windows (and there's no scroll bar in either). The notification area fluctuates madly when a file operation is in progress, as well -- it also needs to set a default size so it isn't reduced to an amalgamous puddle of rapidly morphing Jell-O. This is one element of "polish" I almost expected to see in the 4.6.x series that for some reason simply hasn't been addressed yet. I therefore propose that this dimension fix be applied either by extensive and exhausting human effort on a case-by-case basis...OR at the code level via an internal dimension check of existing Qt code. All windows, for example, could have their default dimensions set according to the calculated width of text or number of lines that text would occupy. This would solve the 'morphing' problem in status dialogs/widgets dealing with multiple filenames, Ark's problem, the KWallet/bugreport dialogs, etc. |
KDE Developer
|
Qt will automatically set the correct window size unless:
The developer has inadvertently hardcoded a default window size The developer hasn't set his layout properly (normally a missing spacer, and it's quite easy to do.) Because it only appears in 'broken' code, it can't be set by other code. Solution: It needs to be done on a case by case basis. 'This is one element of "polish" I almost expected to see in the 4.6.x series that for some reason simply hasn't been addressed yet. ' Do it then. Each time you see it, open a bug report on bugs.kde.org ideally with a screenshot. The reason it hasn't been done is simply lack of manpower. I'm a KDE developer and I'm utterly swamped with work on my project. If you want something fixing - fix it , or at least do the hard part of finding these cases. It would be much appreciated. |
Registered Member
|
I've submitted reports like this in the past, but they mainly went ignored. That was during the KDE4.2 development stage, though, when the focus was on stability and basic functionality, so perhaps now is the time to try again? I would love to know how to commit these changes on a code level if it would save people work. |
Registered Member
|
There are some cases what are depending thirdparty like KDE to fix their code in KDE SC. This example in digiKam where the file preview panel is too huge because bug in KDElibs and KDE refuses to fix the problem.
|
Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]