http://bugzilla.novell.com/show_bug.cgi?id=444801 http://bugzilla.novell.com/show_bug.cgi?id=444801#c8 Will Stephenson <wstephenson@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO CC| |wstephenson@novell.com Info Provider| |eich@novell.com --- Comment #8 from Will Stephenson <wstephenson@novell.com> 2009-12-02 17:19:27 UTC --- Egbert, do you agree with Matthias here? If so I'll upstream to Qt's bugtracker. I guess Qt could discard any MotionNotifys at the same coordinates as the ButtonPress. (WIP - analysis for Qt: Summary: Some X11 mouse drivers generate MotionNotify events between ButtonPress and ButtonRelease with the same coordinates. Our X developers say this is within Xlib specification. Because of how QHeaderView handles mouse move events, it is impossible to click QHeaderView given these 'stationary' move events: If QHeaderView receives mouseMoveEvent while in state QHeaderViewPrivate::MoveSection even if the move is less than startDragDistance, it shows the section indicator. If this is visible at the mouseReleaseEvent, the event is treated as the end of a drag, instead of a click. I suggest not showing the section indicator until a move event that is not at firstPos. ) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.