summaryrefslogtreecommitdiff
path: root/methods.py
diff options
context:
space:
mode:
authorJosh Grams <josh@qualdan.com>2016-03-27 07:19:05 -0400
committerJosh Grams <josh@qualdan.com>2016-03-27 07:19:05 -0400
commit8920ab0fbfd31098b97894d27db5704072c5cd2b (patch)
tree72c6fa4508db3f058f6d8c225e0f480c3619095a /methods.py
parent15d1fca0614ad87fd16fa7532e4db867b342d00e (diff)
* AnimationTreePlayer (_process_node): remove `switched` argument.
The _process_node function (which recurses through the blend tree generating blend values and the active animation list) had an argument named `switched` which would loop an animation back to the beginning if it had reached the end (regardless of whether or not it was supposed to be a looping animation). This argument was only used in four places: two of them were overridden by a seek-to-zero, and I believe the other two are bugs. In OneShot, it was used to reset the oneshot animation to the beginning when fired. But this would fail if the oneshot node was fired before it had completed its previous run. While this *could* be a valid way for oneshot to work (firing does nothing if it's already running), the code currently resets the fade-in, so I believe that it is intended to reset. I replaced this usage with seek-to-0. In Transition, it was used on the previous (fading out) animation when seeking the Transition node, which I believe is incorrect: why would you want to loop a non-looping animation instead of simply fading out from the end? Also it will never happen unless you seek the Transition node twice during one cross-fade. The other two uses are in Transition and _process_animation, where it is used along with a seek-to-zero which overrides it.
Diffstat (limited to 'methods.py')
0 files changed, 0 insertions, 0 deletions