A snag...

Patrick Julien freak at codepimps.org
Thu Jan 8 01:28:11 CET 2004

Why do you absolutely need to get every event?

Qt isn't the only toolkit do this, every windowing system/toolkit I know does 

On January 7, 2004 05:12 pm, Boudewijn Rempt wrote:
> I've hit a snag in Krita that demands some serious thinking. I noticed that
> even if I were not doing anything more demanding than a kdDebug statement,
> I wouldn't get all the mouse positions, let alone doing some heavy duty
> brush positioning and compositing.
> It turns out that Qt kind of collapses mouse move events if the mouse moves
> faster than the application can handle, and even kdDebug (or qDebug) is too
> demanding.
> Dimitri from Trolltech pointed out that this is intentionally done in
> qapplication_x11.cpp
> in QETWidget::translateMouseEvent(),
> near this line:
>         while( XPending( appDpy ) )  { // compres mouse moves
> The workaround he suggested was to handle the mouse events in an
> application event filter; however, that is not an easy solution, exactly.
> So I'll be thinking on it...

More information about the kimageshop mailing list