Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | use nullptr consistently (clang-tidy) | Shawn Rutledge | 2018-02-26 | 1 | -1/+1 |
| | | | | | | | | | | | | | From now on we prefer nullptr instead of 0 to clarify cases where we are assigning or testing a pointer rather than a numeric zero. Also, replaced cases where 0 was passed as Qt::KeyboardModifiers with Qt::NoModifier (clang-tidy replaced them with nullptr, which waas wrong, so it was just as well to make the tests more readable rather than to revert those lines). Change-Id: I4735d35e4d9f42db5216862ce091429eadc6e65d Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> | ||||
* | replace MultiPointHandler::requiredPointCount with min/max range props | Shawn Rutledge | 2017-09-29 | 1 | -6/+12 |
| | | | | | | | | This is more flexible in case someone wants a PinchHandler to respond in the same way for either 2 or 3 touchpoints, for example. Change-Id: I360ce6f0239d86aa92dbebc225e3646883e71100 Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io> | ||||
* | Rename single and multi pointer handler classnames | Jan Arve Sæther | 2017-09-03 | 1 | -0/+112 |
Renames: QQuickPointerSingleHandler -> QQuickSinglePointHandler QQuickMultiPointerHandler -> QQuickMultiPointHandler Change-Id: I10c54944f85ca7cac374ebc6241d61793e2d38bf Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> |