| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
If there is no touch input device attached on Windows7, we shouldn't even
bother subscribing to native gesture events.
Task-number: QTBUG-6007
Reviewed-by: Thierry
Reviewed-by: Prasanth
|
|
|
|
|
|
|
|
| |
Moved the gestureManager pointer to a QApplicationPrivate to make sure if
QApplication object is destroyed, QGestureManager pointer is set to zero.
Task-number: QTBUG-7029
Reviewed-by: Thiago
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
| |
Now we don't filter some events through the gesture manager and use QMap
instead of QHash, which seem to be a bit faster in our cases.
Reviewed-by: Olivier Goffart
|
|\
| |
| |
| |
| | |
Conflicts:
src/gui/painting/qbrush.cpp
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \
| |/
| |
| |
| | |
Conflicts:
src/gui/kernel/qwidget_win.cpp
|
| |\ |
|
| | |
| | |
| | |
| | | |
Reviewed-by: paul
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
The option allows to disable native Windows7 gestures since they require the
creation of the native window handle. This partially disabled alien widgets
concept and make window resizing slower and more flickery.
Reviewed-by: Espen Riskedal
|
| |
| |
| |
| |
| |
| | |
Added QGesture objects and gesture recognizers based on touch events.
Reviewed-by: Bradley T. Hughes
|
|/
|
|
| |
Reviewed-by: Bradley T. Hughes
|
|\
| |
| |
| |
| |
| | |
Conflicts:
dist/changes-4.6.0
src/gui/kernel/qevent.h
|
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
Reviewed-by: trustme
|
| |
| |
| |
| | |
Reviewed-by: trustme
|
| |
| |
| |
| | |
Reviewed-By: Denis
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| | |
There is no reason to use QMap when the key is a pointer.
Reviewed-by: Thomas Zander
|
| |
| |
| |
| |
| |
| |
| | |
When application closes and we haven't deleted the unregistered gestures
and gesture recognizer, we should delete them.
Reviewed-by: Thomas Zander
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When there are several gesture recognizers registered for the same
gesture type, we need to know which recognizer we need to get a state
object for since those QGesture objects are tied to the recognizer that
created them.
Reviewed-by: Thomas Zander
|
| |
| |
| |
| | |
Reviewed-By: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
Reviewed-by: Denis Dzyubenko
|
| |
| |
| |
| | |
Reviewed-by: Denis Dzyubenko
|
| |
| |
| |
| | |
Reviewed-by: Denis Dzyubenko
|
| |
| |
| |
| | |
Reviewed-by: Denis Dzyubenko
|
| |
| |
| |
| |
| |
| |
| |
| | |
We shouldn't add several graphicsobject contexts for the same gesture
type when looking for the gesture-enabled QGraphicsObject under a
hotspot.
Reviewed-by: Thomas Zander
|
|/
|
|
| |
Reviewed-by: tom
|
|
|
|
| |
Also fix grammer and avoid using combined words.
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|