| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
This meant that they would sometimes act upon a drag immediately,
rather than waiting for a nested area to take the grab. This resulted
in a short jump before future events were handled by the nested item.
Task-number: QTBUG-15568
Reviewed-by: Bea Lam
|
|
|
|
|
|
|
|
|
|
| |
Added guidelines for size, and shrunk tests that exceeded them.
Also updated the visuals for all text tests now that antialiasing is off
Also some other minor cleanups.
Also had to update the visuals for all tests, due to the bug in
generating the test scripts being fixed (all need to be remade).
Task-number: QTBUG-14792
|
|
|
|
|
|
|
| |
Previous commit means that the snapshots are in different frames. All
tests must be updated.
Task-number: QTBUG-14792
|
| |
|
|
|
|
|
|
| |
Since we aren't releasing for 4.6, all types are new in 4.7.
Task-number: QTBUG-10081
|
|
|
|
|
|
|
|
|
|
|
| |
The unbgrab mouse happens when the mouse area is inside a flickable and the
flickables takes control over the mouse handling. In this case, the UngrabMouse
will behave similarly to a MouseRelease, emitting released, pressedChanged
and hoveredChanged.
Visual autotest added to mousearea in qmlvisual.
Reviewed-by: Michael Brasser
|
|
|
|
| |
We've updated our handling of drag threshold in MouseArea.
|
|
|