[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    A snag...
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2004-01-07 22:12:07
Message-ID: 200401072312.07492.boud () valdyas ! org
[Download RAW message or body]

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...

-- 
Boudewijn Rempt | http://www.valdyas.org/index2.html
_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]