| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Updated version of LGPL and FDL licenseheaders.
Apply release phase licenseheaders for all source files.
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Zeno Albisser
|
|
|
|
| |
Reviewed-by: Zeno Albisser
|
|
|
|
|
|
|
|
| |
Constructing a QLineF to get at the centerPoint is not precise and can be done simpler.
The scale factor can be assigned directly to d->scaleFactor instead of creating a temporary
scaleFactor variable.
Reviewed-by: Zeno Albisser
|
|
|
|
|
|
|
| |
The scaleFactor/totalScaleFactor should now represent a proper value
to allow an object tracking a touchpoint during a Pinch Gesture.
Reviewed-by: Frederik Gladhorn
|
|
|
|
| |
Reviewed-by: Denis Dzyubenko
|
|
|
|
|
| |
Merge-request: 751
Reviewed-by: Bjørn Erik Nilsen <bjorn.nilsen@nokia.com>
|
|
|
|
|
|
|
|
| |
The new default timeout is 700ms and is what Nokia Research found
through usability studies. Nevertheless lets provide public API to
set this through a platform plugin or similar.
Reviewed-By: Denis
|
|
|
|
|
|
|
|
| |
The QTapAndHoldGestureRecognizer now can trigger also on mouse and
GraphicsSceneMouse events and all of them will cause the gesture start
event to be sent after the touch interval timed out.
Reviewed-by: Denis
|
|\
| |
| |
| | |
4.7-staging1
|
| |
| |
| |
| |
| | |
Merge-request: 535
Reviewed-by: Andreas Aardal Hanssen <andreas.aardal.hanssen@nokia.com>
|
|/
|
|
|
|
|
|
|
| |
In order for gestures to work in graphicsview the hotspot should be set. The
fix adds the hotspot to standard gestures that are shipped with Qt.
Task-number: QTBUG-10967
Task-number: QT-3406
Reviewed-by: trustme
|
| |
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
When the gesture finishes it might not necessery set the ScaleFactorChanged
flag.
Also fixed the touch-event based pinch gesture.
Reviewed-by: trustme
|
|
|
|
|
|
| |
Added QGesture objects and gesture recognizers based on touch events.
Reviewed-by: Bradley T. Hughes
|
|
|
|
|
|
| |
Made sure we emit the same values for the pinch gesture as on Mac.
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: Bradley T. Hughes
|
|
|
|
| |
Reviewed-by: trustme
|
|
|
|
|
|
| |
Changes to the gesture api after the review.
Reviewed-by: Jasmin Blanchette
|
|
|
|
| |
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
|
|
| |
Implemented gestures using gesture events and separate
QGesture/QGestureRecognizer classes.
Reviewed-by: trustme
|
|
|
|
| |
New API will most likely not be in the Beta release.
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
That's the last of them... for now.
|
|
|
|
|
|
|
| |
Added QPinchGesture::whatChanged() which specifies which property in the pinch
gesture changed - the scale factor or rotation angle or both.
Reviewed-by: Bradley T. Hughes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Made properties in QPanGesture and QPinchGesture more consistent - all of them
have value, lastValue and totalValue. Documented that totalValue means the
value from the beginning of the gesture, while the 'value' - from the beginning
of the current sequence. This is especially useful on Windows when you zoom
with two fingers and then release one finger and touch again to continue
zooming.
Also added a workaround for native Rotate gesture on Windows which contain a
'bad' value in the first WM_GESTURE message in every gesture sequence.
Reviewed-by: Bradley T. Hughes
|
|
|
|
|
|
|
|
|
|
|
| |
Added a new widget attribute Qt::WA_DontUseStandardGestures that disables all
implicit gestures (i.e. gestures that are automatically enabled by Qt itself).
This change also changes the way gestures are handled on
QAbstractScrollArea-based widgets on Windows - the gestures are supposed to be
created on the viewport widget.
Reviewed-by: Bradley T. Hughes
|
|
|
|
| |
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
| |
Note: if this fails building on any platform, talk to Denis!
|
|
|
|
|
|
| |
This is more in accordance with touch points, and graphics view
Rev-By: Discussed with Denis and Brad
|
|
|
|
| |
Rev-By: denis
|
| |
|
| |
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
When Pan is implemented with touch events, make sure it pans only when two
fingers are used.
Reviewed-by: trustme
|
| |
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
| |
Reviewed-by: brad
The declaration of getQApplicationPrivateInternal was only available
as 'friend' on Q_WS_WIN.
|
|
|
|
|
|
|
|
|
|
|
| |
Added a new standard gesture, which is implemented using a native zoom and
rotate gestures on Windows and with a direct touch event handling on other
platforms.
Improved pan support - we subscribe to native pan gesture only when it's really
needed, and we pass proper flags for single finger horizontal/vertical panning.
Reviewed-by: Richard Moe Gustavsen
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Moved the code that subscribes to native gestures on Windows to a private
function in QWidget which will check which gestures the widget is subscribed to
and enable native gestures as requested.
Reviewed-by: trustme
|
|
|
|
|
|
|
|
| |
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
|