summaryrefslogtreecommitdiff
path: root/doc/classes/Tween.xml
diff options
context:
space:
mode:
authorHugo Locurcio <hugo.locurcio@hugo.pro>2020-01-31 17:56:03 +0100
committerHugo Locurcio <hugo.locurcio@hugo.pro>2020-01-31 18:00:15 +0100
commit810b1341cef475c28c97cc476f54e1199f5c3d2d (patch)
tree8972a74dbdc79918c9ceeb615cc8f01293cf1bed /doc/classes/Tween.xml
parent6f092c299e6aff131a9de7df93b10c7683b716e5 (diff)
doc: Add a short AnimationPlayer versus Tween comparison
Many newcomers are confused about which one to choose for animating properties. This should help clarify the situation with regards to AnimationPlayer versus Tween.
Diffstat (limited to 'doc/classes/Tween.xml')
-rw-r--r--doc/classes/Tween.xml1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/classes/Tween.xml b/doc/classes/Tween.xml
index 9345cd059a..97d436c707 100644
--- a/doc/classes/Tween.xml
+++ b/doc/classes/Tween.xml
@@ -5,6 +5,7 @@
</brief_description>
<description>
Tweens are useful for animations requiring a numerical property to be interpolated over a range of values. The name [i]tween[/i] comes from [i]in-betweening[/i], an animation technique where you specify [i]keyframes[/i] and the computer interpolates the frames that appear between them.
+ [Tween] is more suited than [AnimationPlayer] for animations where you don't know the final values in advance. For example, interpolating a dynamically-chosen camera zoom value is best done with a [Tween] node; it would be difficult to do the same thing with an [AnimationPlayer] node.
Here is a brief usage example that causes a 2D node to move smoothly between two positions:
[codeblock]
var tween = get_node("Tween")