| Summary: | Kst settings dialog is "ridiculously wide" | ||
|---|---|---|---|
| Product: | [Applications] kst | Reporter: | Matthew Truch <matt> |
| Component: | general | Assignee: | kst |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | ||
| Priority: | HI | ||
| Version First Reported In: | 1.x | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Matthew Truch
2005-11-15 20:32:03 UTC
Any hint on which systems show this? > ------- Additional Comments From staikos kde org 2005-11-15 20:49 -------
> Any hint on which systems show this?
I see the bug on my FC4 machine under kde, but another FC4 machine
(maybe not as updated, I should check) does not see it when running kst
under gnome. Unfortunatly, I don't have any other test cases right now.
> Any hint on which systems show this?
Ok, so I lied, I don't see it on FC-3 but do see it on FC-4.
On a FC-3 machine:
[truch@pigpen ~]$ kst --version
Qt: 3.3.4
KDE: 3.4.2-0.fc3.2 Red Hat
Kst: 1.2.0_svn_478844
On FC-4:
[matt@cherry ~]$ kst --version
Qt: 3.3.4
KDE: 3.4.2-0.fc4.1 Red Hat
Kst: 1.2.0_svn_478844
The version numbers make me think that there isn't much of a difference
between the two KDE versions, but I wouldn't know.
On Tuesday 15 November 2005 15:10, Matthew Truch wrote: > > Any hint on which systems show this? > > Ok, so I lied, I don't see it on FC-3 but do see it on FC-4. > > On a FC-3 machine: > [truch pigpen ~]$ kst --version > Qt: 3.3.4 > KDE: 3.4.2-0.fc3.2 Red Hat > Kst: 1.2.0_svn_478844 > > On FC-4: > [matt cherry ~]$ kst --version > Qt: 3.3.4 > KDE: 3.4.2-0.fc4.1 Red Hat > Kst: 1.2.0_svn_478844 The only possibilities are that KComboBox has changed between those, Qt is patched, or the timezone database has a quirk that affects the combobox somehow. The timezone combo code is actually copied into our tree. > The version numbers make me think that there isn't much of a difference > between the two KDE versions, but I wouldn't know. Hard to say... On Tuesday 15 November 2005 14:57, Matthew Truch wrote:
> I see the bug on my FC4 machine under kde, but another FC4 machine
> (maybe not as updated, I should check) does not see it when running kst
> under gnome. Unfortunatly, I don't have any other test cases right now.
That's very odd. By the way, don't forget that as of the last time I
checked, Gnome's session manager still caused random crashes in Qt apps by
returning invalid data.
SVN commit 484808 by arwalker:
CCBUG:116442 Explicitly set fixed number of columns to try and prevent a very wide widget.
M +7 -0 ktimezonecombo.cpp
--- trunk/extragear/graphics/kst/kst/ktimezonecombo.cpp #484807:484808
@@ -18,6 +18,7 @@
Boston, MA 02110-1301, USA.
*/
+#include <qlistbox.h>
#include <qmemarray.h>
#include <klocale.h>
@@ -40,6 +41,12 @@
db = new KstTimezones;
}
+ if (listBox()) {
+ listBox()->setVScrollBarMode(QScrollView::AlwaysOn);
+ listBox()->setColumnMode(QListBox::FixedNumber);
+ listBox()->setRowMode(QListBox::Variable);
+ }
+
insertItem("UTC");
const KstTimezones::ZoneMap zones = db->allZones();
d->_offsets.resize(zones.count()+1);
Matt, could you test on your machine to see if the code changes made any difference. Thanks. On Mon, Dec 05, 2005 at 11:20:30PM -0000, Andrew Walker wrote:
> Matt, could you test on your machine to see if the code changes made
> any difference. Thanks.
Sorry, I didn't notice the commit on Friday.
Nope, the kst settings dialog is still "ridiculously wide." :-(
Should be fixed for 1.2.1 release This is a bluecurve bug. George wrote:
> This is a bluecurve bug.
And it's only a bluecurve bug in FC4 (not in 3, and not in 5). So, even I don't care any more.
|