Runaway QSlider : it's a Qt bug

Matthias Ettrich ettrich at
Mon Mar 8 12:57:58 GMT 2004

On Monday 08 March 2004 10:16, Lubos Lunak wrote:
> On Sunday 07 of March 2004 11:39, Guillaume Laurent wrote:
> > On Sunday 07 March 2004 11:33, Matthias Ettrich wrote:
> > > While I don't argue that it might be possible to find a generic
> > > solution to this and similar problems on the toolkit level, I'm not
> > > quite sure how, yet. General rule: do not exclude user input when the
> > > mouse is pressed down.
>  Actually I think the general rule rather should be: do not use misleading
> or wrong names. ExcludeSocketNotifiers ignores socket notifiers events, but
> keeps them pending. The same for the hidden ExcludeTimers. But
> ExcludeUserInput doesn't really exclude user input (at least according to
> what my dictionary says 'exclude' means), it discards it -> it should be
> either fixed to do what it says, or it should be called DiscardUserInput.

You are right. In Qt 4, we will actually queue the input events. In addition, 
we make it possible to query the processEventFlags from the event loop. 
"user" timers such as auto-repeat buttons or sliders will check whether 
user-input is excluded to stop runaway bugs.


More information about the kde-core-devel mailing list