| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
Change-Id: If797ac58344b20e8de4379343131c097247ba2f2
|
| |
| |
| |
| |
| | |
Change-Id: If68cff4efacc7dc5719c8b8e61937e85e9076870
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Ripples don't trigger when the ripple item itself is disabled. This is
used in SwipeDelegate to prevent ripples when a swipe is open. Now that
swipe.position is transitioned, a release event comes before the swipe
position reaches 0, so we must ensure that the wave exits even if it's
not yet enabled.
Change-Id: Ib4d58ff974262331898db2133e06624eb890f9ed
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Left overs from 1d8bf6d1f4ef0aa84ca7e4c1233bedeee0f606f9.
Change-Id: I53a6916ab3cb8c4effd50ecee1b12662ff7c7402
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|/
|
|
|
|
|
|
|
| |
Use animated nodes instead of using the private animator API.
Task-number: QTBUG-55652
Task-number: QTBUG-56601
Change-Id: I69d9e6afbc2cb0af6a537553fc39f9871cdd8e97
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QQuickMaterialRipple compared the anchor item to QQuickWindow's
mouseGrabberItem to ensure that only mouse-pressed buttons would use the
press point, whereas key-pressed buttons would use the center point.
However, this does not work in case the mouse grab was stolen: when
first pressing an ItemDelegate and then dragging the containing ListView,
the ripple wave would always appear from the center point, not from the
press point as it should. Since QQuickAbstractButton::keyPressEvent()
sets the press point as the center of the control, the mouseGrabberItem
check can be simply removed.
Change-Id: Ic24e5e80c9d849f3fe2684013dd40b004ef55b57
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
| |
Task-number: QTBUG-54764
Change-Id: Ie04c93a823745b6d0a85e0c80c91d4e7f77f6fcd
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Android 5 used to trigger ripple effects on press, but Android 6 made
ripple effects a bit more subtle. For check boxes, radio buttons, and
switches it still triggers on press, but these controls where the wave
is larger, it's triggered on release instead.
Change-Id: Ib4d301d5ccf72d5db106bcc6ad6afee30cef0b1e
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
Instead of creating a ripple wave item right away and handling the
delay inside the animation, use a timer event to postpone the wave
creation until it's necessary.
Change-Id: Ie8b6aa2e4ae148a51b0ae17f4d0ee50e20ddb321
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Material style ripple effect needs it to be able to anchor waves
at the press point. Export QQuickAbstractButtonPrivate to make it
accessible, and update the press point before emitting pressedChanged()
since that's what the ripple effect reacts to.
Press point dependent ripple effects follow in separate commits.
Change-Id: I63eb51eeabcbeb307dea9d0b1731bdb51b518ec7
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
Consequently, the controls that were previously using the old
Ripple type have now gained hover effects (when hoverEnabled: true).
The rest of the Material style controls will be adjusted to use the
ripple effect in follow up commits.
Task-number: QTBUG-50003
Change-Id: I436f3794411fe75de9ccbe3ecda71029130db613
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|