Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | MouseArea shouldn't grab the mouse until there is an effective drag. | Andrew den Exter | 2013-02-22 | 1 | -0/+44 |
| | | | | | | | | | | A MouseArea shouldn't prevent a parent MouseArea or Flickable from handling a drag event unless it is going to do something useful with it. Task-number: QTBUG-29717 Change-Id: I17caa51ebc2e547e73e727fd185e60644591ad2b Reviewed-by: Alan Alpert <aalpert@rim.com> | ||||
* | MouseArea: use current value of drag.axis | Alberto Mardegan | 2012-07-27 | 1 | -0/+22 |
| | | | | | | | | | | | | | If the drag.axis is changed while a drag operation is in progress, put it into action immediately. This allows, for example, start a dragging operation out of an item in a scrollable ListView to anywhere on the screen. See the linked bug number for an example. Task-number: QTBUG-26440 Change-Id: I4ffa71c08b97a767aec7f69d19271000a2631327 Reviewed-by: Rick Stockton <rickstockton@reno-computerhelp.com> Reviewed-by: Andrew den Exter <andrew.den-exter@nokia.com> | ||||
* | Import relevant source from Qt 4.8 | Matthew Vogt | 2012-01-30 | 12 | -0/+289 |
Change-Id: I5078db4081d95290c54f39d3c0efc2fc2f62e6a6 |