It's not possible to use two mouse area with propagateComposedEvents because even in that case I will have two event on double click: 1. Single click on the upper area (or maybe two single click) 2. Double click on the lower area
By now the only solution is with a timer for the single click event. --- Matteo Brichese Software Engineer mbrich...@came.it Came Cancelli Automatici S.p.A. www.came.com ________________________________________ Da: Rutledge Shawn [shawn.rutle...@digia.com] Inviato: martedì 21 maggio 2013 8.34 A: Matteo Brichese Cc: interest@qt-project.org Interest Oggetto: Re: [Development] Nested Mousearea don't pass events On 20 May 2013, at 4:36 PM, Matteo Brichese wrote: > I've solved it in my code with a Timer. It's probably more efficient to go back to using two MouseAreas and propagateComposedEvents as documented in the MouseArea docs. Not being able to distinguish clicked from doubleClicked within one MA is inconvenient, but I suppose the alternative would be for Qt to internally use a timer, which would slow down the clicks. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
