| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Changes to the gesture api after the review.
Reviewed-by: Jasmin Blanchette
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
By default if the gesture is ignored, only gestures in the started state
are propagated, and accepting a gesture in the started state adds an
implicit grab meaning all the following events in the gesture sequence
will be delivered to that widget. This is similar to the way QTouchEvent
is propagated.
Also added a hint, which specifies if gestures in any state can be
propagated to the widget which has enabled the hint.
Reviewed-by: Thomas Zander
|
| | |
|
| |
|
|
|
| |
Our tests now call the recently converted registerRecognizer using a proper
static method.
|
| |
|
|
|
|
|
|
|
| |
On accepting one gesture Qt can automatically cancel other gestures
that belong to other targets. The policy is normally set to not cancel
any other gestures and can be set to cancel all active gestures in the
context. For example for all child widgets.
Reviewed-By: Denis Dzyubenko
|
| |
|
|
| |
are done
|
| |
|
|
| |
Reviewed-By: trustme
|
| |
|
|
| |
Reviewed-by: trustme
|
| |
|
|
| |
Reviewed-by: Denis Dzyubenko
|
| |
|
|
| |
Reviewed-by: trustme
|
| |
|
|
| |
Reviewed-by: Thomas Zander
|
| | |
|
| |
|
|
| |
Reviewed-by: trustme
|
| |
|
|
|
|
|
|
|
| |
When delivering GestureOverride events by default both the event and
individual gestures will be ignored. We also store the acceptance state
of individual gesture in the event and not in the gesture object, along
with its target.
Reviewed-by: Thomas Zander
|
| |
|
|
| |
Reviewed-by: trustme
|
| |
|
|
|
|
|
|
| |
When there are two different gestures are being triggered and they are
supposed to be sent to different widgets, don't stop event "propagation"
when the first event is successfully delivered.
Reviewed-by: trustme
|
| |
|
|
| |
Reviewed-by: trustme
|
| |
|
|
|
|
|
|
| |
Make sure that when a gesture recognizer explicitely sets the
targetObject to a QGraphicsObject, we deliver it only to the object and
will not try to propagate.
Reviewed-by: trustme
|
| |
|
|
|
|
|
|
|
| |
When a gesture recognizer claims to be in Finished state without any
Triggered states before, that probably means that was a singleshot
gesture that has started and ended right away, so we'll send a fake
gesture in the GestureStarted state.
Reviewed-by: trustme
|
| |
|
|
|
|
|
| |
Implemented gestures using gesture events and separate
QGesture/QGestureRecognizer classes.
Reviewed-by: trustme
|
| |
|
|
|
|
| |
Oops, forgot to remove the autotest after rewriting the gestures api.
Reviewed-by: trustme
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
| |
This is partly done to address a review comment for S60.
Reviewed-by: Marius SO
Reviewed-by: Paul
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rewritten the api almost from scratch, making it simplier and more
flexible at the same time.
The current implementation will not have complex gseturemanager class
inside Qt, but the QGesture base class, which represents both a
gesture recognizer and a gesture itself with a set of properties. A
set of common gestures that can use used in third-party applications
(and in Qt itself internally) is supposed to be found in
qstandardgestures.h, and a base class for user-defined gestures is in
qgesture.h
Gesture implementation for Pan on Windows7 has also been added as a
reference implementation for platform gestures.
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Added a context for the touch positions in press(), move(),
release() functions.
* Sending RawTouch events to QApplication object if the target widget
is not specified.
|
| | |
|
| |
|
|
| |
Modified it the same time to remove refcount and static variable.
|
| | |
|
| |
|
|
|
| |
For now the api is in the autotest itself, though in the QTest
namespace.
|
| | |
|
| | |
|
| | |
|
| |
|
