summaryrefslogtreecommitdiffstats
path: root/tests/auto/qtouchevent
Commit message (Collapse)AuthorAgeFilesLines
* Change to release licenses for 4.6.3.Jason McDonald2010-05-301-13/+13
| | | | Reviewed-by: Trust Me
* Don't crash when QTouchEvent is accepted but not handled by aBradley T. Hughes2010-02-161-0/+31
| | | | | | | | | | | | | | | | | | QGraphicsItem After propagating QEvent::TouchBegin, if there is no item that has accepted and handled the event, we must remove the touch point from our data structures. In this situation, QGraphicsScene will ignore the TouchBegin, as will QGraphicsView, and QApplication will respond by not sending any more touch events to the view/scene/item. This means our logic for handling TouchPointReleased points will never be called (and the QGraphicsScene's itemForTouchPointId and sceneCurrentTouchPoints state will be incorrect). Reviewed-by: Denis Dzyubenko Reviewed-by: Marius Storm-Olsen
* Update copyright year to 2010Jason McDonald2010-01-061-1/+1
| | | | Reviewed-by: Trust Me
* Fix crashes when deleting QWidgets and QGraphicsItems in touch event handlers.Bradley T. Hughes2009-12-111-1/+245
| | | | | | | | | | | | | | Use QWeakPointer to bail out early if a widget is deleted while we are delivering/propagating a TouchBegin event. In QGraphicsScene, we need to make sure that we clear the scene's active touch points for items that are removed from the scene. This allows us to detect when an item is removed during TouchBegin event delivery/propagation. Unlike QWidget, propagation continues since we use a hit-test instead of the item's hierarchy for propagation. Task-number: QTBUG-6654 Reviewed-by: bnilsen
* Fix tst_QTouchEvent::touchUpdateAndEndNeverPropagate()Bradley T. Hughes2009-12-111-2/+2
| | | | | | | | QGrahpicsItem behaves similarly to QWidget; if the TouchUpdate or TouchEnd event is ignored, then the event sent to the view and scene will also be ignored. Reviewed-by: Trust me
* Update license headers again.Jason McDonald2009-09-091-4/+4
| | | | Reviewed-by: Trust Me
* Update tech preview license header for files that are new in 4.6.Jason McDonald2009-08-311-13/+13
| | | | Reviewed-by: Trust Me
* Add QGraphicsView to the QTouchEvent testBradley T. Hughes2009-08-121-121/+387
| | | | | Since QTouchEvents can also be sent to QGraphicsItems, we want to test that it actually works.
* Update contact URL in license headers.Jason McDonald2009-08-121-1/+1
| | | | Reviewed-by: Trust Me
* Fix license headers after multitouch+gestures merge.Jason McDonald2009-06-291-5/+5
| | | | | | | Commercial license headers belong in source packages only. The repo must have the pre-release license headers. Reviewed-by: Trust Me
* Fix old/missing license headers from multitouch+gestures merge.Jason McDonald2009-06-291-2/+2
| | | | Reviewed-by: Trust Me
* Add tests for multiple touch points on TouchScreen and TouchPad devicesBradley T. Hughes2009-06-251-9/+434
| | | | | | Add 2 basic tests that, when faced with multiple touch points, make sure we send multiple touch events on TouchScreen devices, but only one event on TouchPads.
* Merge branch 'master' of git@scm.dev.nokia.troll.no:qt/qt-multitouchBradley T. Hughes2009-06-241-3/+3
|\
| * Fix pressure "emulation"Bradley T. Hughes2009-06-241-3/+3
| | | | | | | | | | Update the auto test for QTouchEvent to make sure the pressure is set to 1 for Pressed/Moved/Stationary, but for 0 for Released.
* | Add QTouchEvent::DeviceType and deviceType()Bradley T. Hughes2009-06-241-6/+27
|/ | | | | | | | | This enum indicates what kind of device generated the touch event (TouchScreen or TouchPad). We use this information to control how touch events are sent, specifically we restrict touch events to a single widget/QGraphicsItem on touch-pads, since there is no direct relationship between the physical touch location on the pad and the on- using the touch-pad).
* Add functions to report normalized positions in QTouchEvent::TouchPointBradley T. Hughes2009-06-231-0/+16
| | | | | | | | | This introduces normalizedPos(), startNormalizedPos(), and lastNormalizedPos() in QTouchEvent::TouchPoint, and must be set by the implementation before being fed into Qt. We are assuming and hoping that these functions will make it easier to implement certain types of gestures (especially on a touchpad).
* Move with window to a position that is not 0,0 in the raw testBradley T. Hughes2009-06-191-0/+1
| | | | | | That way the widget local positions will not be the same as the screen coordinates. (I missed a bug in QTouchEvent::TouchPoint because of this coincidence in the test).
* compile after small API changesBradley T. Hughes2009-06-181-11/+6
|
* Make QTouchEvent::TouchPoint scene coordinate functions return screen ↵Bradley T. Hughes2009-06-151-0/+12
| | | | | | coordinates for widgets Previously these returned empty/invalid values.
* remove duplicated code and API (merge QTouchEvent and QGraphicsSceneTouchEvent)Bradley T. Hughes2009-06-111-16/+19
| | | | | | | | | the API for these 2 classes is identical, the implementation is almost identical, they share the same data structures, so bite the bullet and merge them. this means we go back to using screenPos() instead of globalPos() again
* don't reset the touch widget in the basicRawEventTranslation() testBradley T. Hughes2009-06-081-5/+3
|
* test basic raw event translationBradley T. Hughes2009-06-081-0/+87
| | | | | this makes sure that we get the proper start/last position maintenance and global->local translation.
* test that TouchBegin events propagate through widgets with ↵Bradley T. Hughes2009-06-081-0/+15
| | | | Qt::WA_AcceptTouchEvents
* Send the TouchEnd event with Qt::TouchPointReleased maskBradley T. Hughes2009-06-081-1/+1
| | | | | The mask isn't used and changing it doesn't do anything, so this is just a cosmetic/clarification change.
* test that QEvent::TouchUpdate and TouchEnd never propagateBradley T. Hughes2009-06-081-2/+49
|
* add test for TouchBegin propagationBradley T. Hughes2009-06-081-0/+53
|
* add tst_QTouchEventWidget to handle touch eventsBradley T. Hughes2009-06-081-2/+33
| | | | | test that sending the TouchBegin to this widget both succeeds and accepts the event
* make QTouchEvent autotest passBradley T. Hughes2009-06-081-5/+5
| | | | the event is accepted by default, but no handled
* add a autotest for touch eventsBradley T. Hughes2009-06-082-0/+97
start off by testing basic behavior: 1. touch events are disabled by default 2. touch events are automatically accepted when enabled