Albert Zhykhar wrote: > Just tried another Windows-XP - it's the same result :( > And with an old good ball mouse nothing changes. > Maybe to clarify again with the example: > as long as no button is pressed, moving the mouse generates exactly > one mouseMoveEvent pro pixel. But with the middle mouse button being > pressed I see 3-5 mouseMoveEvents in the output pro pixel. > The first one shows actually change in globalPos(), but the rest > mouseMoveEvents come with the same globalPos(). > Any ideas would be appreciated
I don't know why it would happen for you, but here's something you can do to check if it Qt or Windows that's sending those excessive events: In qapplication_win.cpp, you'll find a function called bool QETWidget::translateMouseEvent(const MSG &msg) around line 2800. You can insert debug info/a break point there to track when Windows sends a mouse move event to Qt. Then you can compare that to how many events are delivered to QGraphicsView::mouseMoveEvent. If the match is 1-1, then the problem is outside Qt, but if it's 1:many, it's inside Qt. Andreas :-) -- Andreas Aardal Hanssen Senior Software Engineer, Team Lead / Widgets Trolltech ASA - Sandakerveien 116, NO-0484 Oslo, Norway To unsubscribe - send "unsubscribe" in the subject to [EMAIL PROTECTED]
