1 /****************************************************************************
3 ** Copyright (C) 2015 The Qt Company Ltd.
4 ** Contact: http://www.qt.io/licensing/
6 ** This file is part of the documentation of the Qt Toolkit.
8 ** $QT_BEGIN_LICENSE:FDL$
9 ** Commercial License Usage
10 ** Licensees holding valid commercial Qt licenses may use this file in
11 ** accordance with the commercial license agreement provided with the
12 ** Software or, alternatively, in accordance with the terms contained in
13 ** a written agreement between you and The Qt Company. For licensing terms
14 ** and conditions see http://www.qt.io/terms-conditions. For further
15 ** information use the contact form at http://www.qt.io/contact-us.
17 ** GNU Free Documentation License Usage
18 ** Alternatively, this file may be used under the terms of the GNU Free
19 ** Documentation License version 1.3 as published by the Free Software
20 ** Foundation and appearing in the file included in the packaging of
21 ** this file. Please review the following information to ensure
22 ** the GNU Free Documentation License version 1.3 requirements
23 ** will be met: http://www.gnu.org/copyleft/fdl.html.
26 ****************************************************************************/
29 \page qml-behaviors-and-states.html
30 \title Using QML Behaviors with States
32 \section1 Using Behaviors with States
34 In some cases you may choose to use a Behavior to animate a property change caused by a state change. While this works well for some situations, in other situations it may lead to unexpected behavior.
36 Here's an example that shows the problem:
49 anchors.centerIn: parent
64 when: mouser.containsMouse
75 Testing the example by quickly and repeatedly moving the mouse in to and out of the colored rectangle shows that the colored rectangle will settle into a green color over time, never returning to full red. This is not what we wanted! The
76 problem occurs because we have used a Behavior to animate the change in color, and our state change is trigged by the mouse entering or exiting the MouseArea, which is easily interrupted.
78 To state the problem more formally, using States and Behaviors together can cause unexpected behavior when:
80 \o a Behavior is used to animate a property change, specifically when moving from an explicitly defined state back to the implicit base state; and
81 \o this Behavior can be interrupted to (re-)enter an explicitly defined state.
84 The problem occurs because of the way the base state is defined for QML: as the "snapshot" state of the application just prior to entering an explicitly defined state. In this case, if we are in the process of animating from green back
85 to red, and interrupt the animation to return to "GreenState", the base state will include the color in its intermediate, mid-animation form.
87 While future versions of QML should be able to handle this situation more gracefully, there are currently several ways to rework your application to avoid this problem.
89 1. Use a transition to animate the change, rather than a Behavior.
102 anchors.centerIn: parent
114 when: mouser.containsMouse
122 transitions: Transition {
129 2. Use a conditional binding to change the property value, rather than a state
142 anchors.centerIn: parent
144 color: mouser.containsMouse ? "green" : "red"
158 3. Use only explicitly defined states, rather than an implicit base state
171 anchors.centerIn: parent
186 when: mouser.containsMouse
195 when: !mouser.containsMouse