Version: 1.2post (using KDE 3.1.0) Installed from: compiled sources Compiler: gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-108.7.2) OS: Linux (i686) release 2.4.7-10 Two more dialog rendering problems: Number 1 -------------------- Select Format -> Page Layout. Click on the tab labeled "Header & Footer". The grouping labeled "Footnote/Endnote" is mostly blocked by "Spacing between footnote and body". Number 2 --------------------- Select Format -> Style Manager. Click on the tab labeled "Font". "Position" and "Colors" are partially obliterated.
From where I am sitting Number 1 seems to be fixed. Can anyone else confirm? But the Number 2 problem, the Style Manager, is still there. This can be fixed to some extent just by making the dialog larger in lib/kotext/koStylist.cc, line 107. However it is already 600 wide and 570 high. It's also possible to change the numbers of rows displayed in the KFontChooser listboxes, (the three listboxes font, Font Style, Size) by passing an extra argument to the constructor of KFontChooser in lib/kotext/koFontDia.cc, line 378. The default is currently used, which is 8, but changing it to 6 looks ok. Even with this, the dialog must be made around 640 high to make everything visible. This might be too big? There's lots of space on the other two tabs, could the "position" or "colors" group boxes be moved onto another tab? For the width, it could be made wider (640 would probably do it), but the font size listbox is way too wide, surely it could be made smaller? Here it looks about twice as wide as it needs to be. This would have to be changed in KFontChooser. (kdelibs/kdeui/kfontdialog.*) At the moment, the min. width of this listbox is set on line 281 of kfontdialog.cpp: sizeListBox->setMinimumWidth( minimumListWidth(sizeListBox) + sizeListBox->fontMetrics().maxWidth() ); I don't know why this makes it so large, but this code must be used by a lot of apps, so may be tricky to change it. Easy way is just to make the dialog wider.
Seems to be fixed.
I suppose that this bug report is included in bug #76757, which is fixed. Have a nice day! *** This bug has been marked as a duplicate of 76757 ***