Version: 0.98-devel (kst_oldview_branch) (using KDE KDE 3.2.0) Installed from: Mandrake RPMs You are unable to select vectors in the change data sample ranges dialog box. As soon as you click on a vector, it highlites, and within a fraction of a second, it un-highlites (this is true even for the initial state, where all vectors are selected, a fraction of a second later they all become unselected). How to reproduce: With some data loaded, go to Change Data Sample Ranges (under Range menu). Click on a vector. Expected behavior: The clicked vector will become selected, and remain that way. Actual behavior: The clicked vector becomes unselected, and it is impossible to make any changes to the vector with this dialog box.
Which Qt version do you have? This looks like a Qt bug to me.
Qt 3.1.1 and 3.1.2 are installed on (different) machines here. I know, kinda outdated. Is this bug related to the pause button bug? Also, I've found a few more instances where this kind of behavior exists.
Your report said KDE 3.2.0. Hm if Qt 3.1.1 is installed, maybe there is a runtime problem. If you run Kst from the commandline, do you see any debug messages to the effect of: QObject::connect: No such signal ...... or similar? In particular if you run through that dialog, it might dump something out when it is first shown.
Sorry, I'm not using KDE 3.2.0, I'm using KDE 3.1.0. KDE's bugzilla won't let you submit a bug report if you're using a version of KDE <3.2.0. (I thought the warning was only if you were reporting bugs for non kdeextragear projects). I see no errors (or any text) on the command line when I start kst, or when I try and use the change data sample ranges dialog.
On April 26, 2004 22:33, Matthew Truch wrote: > Sorry, I'm not using KDE 3.2.0, I'm using KDE 3.1.0. KDE's bugzilla won't > let you submit a bug report if you're using a version of KDE <3.2.0. (I > thought the warning was only if you were reporting bugs for non > kdeextragear projects). > > I see no errors (or any text) on the command line when I start kst, or when > I try and use the change data sample ranges dialog. Ah, non-debug build. Hm. Ok I"ll have to investigate myself to see if any signals or slots from Qt >3.1 are used there.
This bug has been fixed as of (at least) 0.98.