To be seeing this, you must have turned on qt.qpa.input categorized logging. You need to get used to managing your qtlogging.ini depending on what you are trying to debug. (And I think we should write some sort of tool to manage it, because there are a lot of categories now.) Maybe logging mouse movements is a bit too much though...
On Feb 20, 2015, at 20:17, Guido Seifert <[email protected]> wrote: > Just forget it. Happens with all programs. Must be my Qt dev version. > Just one thing I don't understand... one Qt dev spams the console... > how does this not drive the other devs crazy? :-D ;-) > > Guido > >> Hi, >> just discovered in one of my ancient programs. >> Linux/Qt 5.5 >> >> Whenever I move the mouse in a widget, I get console output like this: >> >>> qt.widgets.gestures: QGestureManager:Recognizer: ignored the event: >>> QPanGesture(state=Qt::GestureState(NoGesture),lastOffset=QPointF >>> (0,0),offset=QPointF(0,0),acceleration=0,delta=QPointF(0,0)) QEvent(Leave, >>> 0x7fff83652e10, type = QEvent::Type(Leave)) >>> xcb: moved mouse to 1291, 228; button state 0 >>> xcb: moved mouse to 1302, 226; button state 0 >> >> Any idea what causes this? Apart from the obvious 'xcb' and >> 'QGestureManager'? >> And more important... How do I get rid of this? >> >> Guido >> _______________________________________________ >> Interest mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/interest >> > _______________________________________________ > Interest mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
