Fix some problems with MouseDblClick handling

The sequence of events delivered from a double click is:

 [Press,Release,Press,DblClick,Release]

The problem was that a DblClick was delivered just like a press event, so
it would clear the passive grabber that was established because of the
former Press event.
When the Release event then got processed, there was therefore a risk that
the Release event was not delivered to the passive grabber.

The fix is to not deliver DblClick events at all to handlers, and to not
deliver DblClick to items if the former Press event was accepted by a
handler.

Change-Id: I49c0e32ef4e33f7b6014d35dc065da2527b94779
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>

1 files changed, 1 insertions, 0 deletions

diff --git a/src/quick/items/qquickwindow_p.h b/src/quick/items/qquickwindow_p.h
index fa39eca9a6..a40301bcfa 100644
--- a/src/quick/items/qquickwindow_p.h
+++ b/src/quick/items/qquickwindow_p.h
@@ -262,6 +262,7 @@ public:
     bool componentCompleted : 1;
 
     bool allowChildEventFiltering : 1;
+    bool allowDoubleClick : 1;
 
     Qt::FocusReason lastFocusReason;