| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Gesture is now associated with a target widget and whenever several
gesture events occur at the same time if they are supposed to be handled
by different widgets, each widget will receive only gestures related to
itself.
For example this makes possible to use gesture framework with multitouch
when user interacts with two widgets at the same time.
GraphicsView implements is not implemented yet.
|
| |
|
|
| |
to receive them.
|
| |
|
|
| |
events in gesture recognizers.
|
| | |
|
| |
|
|
|
| |
specifies a timout for mouse event delivery to allow the gesture
framework to successfully recognizer a gesture.
|
| |
|
|
| |
to start.
|
| |
|
|
|
| |
... since we don't want these to persist after QApplication has been
destroyed
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
