| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Added QGesture objects and gesture recognizers based on touch events.
Reviewed-by: Bradley T. Hughes
|
| |
|
|
|
|
| |
Changes to the gesture api after the review.
Reviewed-by: Jasmin Blanchette
|
| |
|
|
| |
Reviewed-By: Denis
|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
Reviewed-by: trustme
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The constructor that accepts a gesture type is not needed because the
gesture type id will be generated by Qt and assigned to the QGesture
object when a custom gesture recognizer is registered within the
framework.
Reviewed-by: trustme
|
| |
|
|
|
|
|
| |
Implemented gestures using gesture events and separate
QGesture/QGestureRecognizer classes.
Reviewed-by: trustme
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: trustme
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
| |
Changed the constructor of the QGesture to separate the gesture target (the
object/widget that the gesture filters events for), and the parent object.
Reviewed-by: Richard Moe Gustavsen
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
| |
By default the QGesture::reset function is protected, and it can be made public
in the derived class if necessary.
Reviewed-by: trustme
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Instead of having a protected setter for the state and forcing the application
developer to emit signals manually (which leads to misunderstanding - i.e. if
the started() signal should be emitted only once, or of the triggered() signal
should be emitted before the finished() signal, etc). So I've added an
protected updateState(state) function that sets the internal state and emits
appropriate signals depending on the old and new states.
Reviewed-by: Volker Hilsheimer
Reviewed-by: Richard Moe Gustavsen
|
| |
|
|
|
|
|
|
| |
It doesn't make much sense to have that low-level info neither in the base
QGesture class, nor in the QPanGesture, as the latter one has offset properties
instead.
Reviewed-by: trustme
|
| |
|
|
| |
Reviewed-by: trustme
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Commercial license headers belong in source packages only. The repo
must have the pre-release license headers.
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| | |
|
| | |
|
| |
|
|
|
|
| |
QGraphicsProxyWidgets.
This is still work-in-progress.
|
| |
|
|
|
|
|
|
|
|
|
| |
Each gesture can now be accepted separately and not accepted gestures
will be propagated to parent widget that are subscribed to them.
Added an internal flag to specify that gesture is a "singleshot" - aka
if the gesture is not continious and will not have a GestureStarted
state, but only GestureFinished.
Asynchronous gestures still need to fixed, as well as QGraphicsView.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
propagating event.
|
| |
|
|
| |
anymore, but just fill data on a single qgesture object.
|
| |
|
|
| |
are QObject now everything is much simplier.
|
| | |
|
| | |
|
| |
|
|
| |
Also made some small fixes that noticed while was writing a doc.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Gesture types are now separated to internal ones, which are listed as
enums (though they might be converted to strings internally), and
third party gestures which are referenced by strings.
From now on QGesture objects derive from QObject, which means third
party gesture recognizer developers can use QObjects property system
to store custom data inside QGesture without need to subclass it.
Some functions were renamed to show their purpose more clear.
|
|
|
This is a squashed merge of all of the changes in the maemo-gestures
branch on-top of the qt/4.5.0 branch.
|
