| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
We only support Qt 4.7 now.
|
| | |
|
| |
|
|
|
|
|
|
| |
Make sure bindings in PropertyChanges resolve urls correctly. Also
refactor the code so that PropertyChanges will always use the
standard url resolution support provided by QDeclarativeProperty.
Task-number: QTBUG-9571
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SmoothedFollow is the same as the old EaseFollow, so it's not an
animation, but its main use case is to be used as a property value
source to automatically follow the 'to' property, as in the example below.
Rectangle {
color: "green"
width: 60; height: 60;
SmoothedFollow on x { to: rect1.x - 5; velocity: 200 }
SmoothedFollow on y { to: rect1.y - 5; velocity: 200 }
}
This element shares the internal implementation with SmoothedAnimation,
both providing the same easing function, but with SmoothedFollow it's
easier to set a start value to animate intially and then start to follow,
while SmoothedAnimation is still convenient for using inside Behaviors
and Transitions.
Reviewed-by: Michael Brasser
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 973cfce37fcdd1ce330f237eaa76930db55a73f6.
Need more consideration before adding modelReset(). For example if
item insertion/removal is supposed to trigger animations through
added/removed signals, they won't be triggered if only the modelReset()
signal is emitted. Also if we add modelReset(), it should also be
implemented for ListModel to make sure it is implemented by all subclasses
of QListModelInterface and to test the impact of this on the view classes.
|
| |/
|
|
| |
wrap remains for a little while, and will produce a warning.
|
| |
|
|
|
|
|
|
| |
This reverts commit 9d9161446bfad883c298d54a122e822c5e273a9c.
This was a bad idea. It complicates the "property var" are not really
JavaScript var problem. Some of the patch is valid, and it will be
applied separately.
|
| |
|
|
| |
Task-number: QTBUG-9371
|
| |
|
|
|
|
|
| |
We already supported returning QList<QObject*> from methods, but there
wasn't really much that could be done with the return value. This closes
the loop on QList<QObject*> support by allowing them to be properties,
and used as models.
|
| |
|
|
| |
QTBUG-6082
|
| |
|
|
|
|
|
| |
Also adds qmlRegisterUncreatableType<>() to allow registration of
named types that cannot be created.
Task-number: QTBUG-9575
|
| |
|
|
| |
XmlListModel when all data has changed.
|
| | |
|
| |
|
|
|
| |
Always use private/. The WinSCW compiler doesn't search the current
directory, for whatever reason.
|
| | |
|
| |
|
|
| |
Task-number: QTBUG-9509
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QDeclarativeSmoothedAnimation inherits from QDeclarativeNumberAnimation,
as a consequence SmoothedAnimation can be used inside Behaviors and
as PropertySourceValues, like any other animation. The old EaseFollow
properties changed to comply with the other declarative animations
('source' changed to 'to'), so now 'to' changes are not automatically
'followed' anymore.
You can achieve the following behavior by putting a SmoothedAnimation
inside a Behavior of a property that is bound to another, as the
following example:
If you want to follow an hypothetical rect1, you should do now:
Rectangle {
color: "green"
width: 60; height: 60;
x: rect1.x - 5; y: rect1.y - 5;
Behavior on x { SmoothedAnimation { velocity: 200 } }
Behavior on y { SmoothedAnimation { velocity: 200 } }
}
SmoothedAnimation also supports animating multiple target(s)/property(ies)
in the transition case. When a QDeclarativeSmoothedAnimation is restarted,
it will match the QDeclarativeProperty which were being animated and
transfer the corresponding track velocity to the new starting animations.
QSmoothedAnimation is an uncontrolled animation, duration == -1.
The duration is set as -1 to avoid consecutive animation state changes
stop()/start(). This is particularly useful when using QSmoothAnimation
to 'follow' another property, which is also being animated (change the
'to' property every tick).
Reviewed-by: Michael Brasser
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change to Thiago's method:
QThread::quit() is *not* thread-safe, so we mustn't call it from
outside the QThread that the QThread holds. Unlike other QObjects,
this method and some others must not be called from the thread they
have affinity to.
So add a hack to call it in the auxiliary thread. Do that by
connecting a dummy QObject's destroyed() signal to the quit() slot in
a DirectConnection, then move the object to the thread. When we call
deleteLater(), this will cause the thread's event loop to delete the
object, which in turn calls quit() in the actual thread.
Reviewed-by: Thiago Macieira
|
| |
|
|
| |
Task-number: QTBUG-9325
|
| |
|
|
| |
Task-number: QTBUG-8984
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
Task-number: QTBUG-9439
|
| | |/
| |
| |
| | |
Base URL of engine is not what some people think it is.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
changed.
Task-number: QTBUG-9386
|
| |/
|
|
|
| |
Prevents deadlock on shutdown for very shortlived runs,
e.g. autotests
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
is set as soon as XML data is downloaded, so there is no notification
when model is actually ready to be used).
This also fixes data() to not crash if it is called before the model
is ready.
Task-number: QTBUG-7835
|
| |
|
|
| |
(fixes test too)
|
| |
|
|
|
|
|
|
|
| |
Needed by QmlDesigner, which needs to be able to remove states
at runtime.
Done my Marco Bubke
Reviewed-by: Michael Brasser
|
| |
|
|
| |
Task-number: QTBUG-9032
|
| |
|
|
| |
Fixes Particles plugin.
|
| |
|
|
|
|
|
| |
Add Translate transform.
Image::sourceWidth and Image::sourceHeight read/write properties.
Task-number: QTBUG-8984
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
with other classes with countChanged() signals.
|
| |
|
|
| |
Reviewed-by:Martin Jones
|
