-
-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Animator support transition conditions #2096
Animator support transition conditions #2096
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should add unit and e2e test
for (let j = 0, m = length; j < m; j++) { | ||
const transition = entryTransitions[j]; | ||
if (this._checkConditions(null, transition)) { | ||
this.crossFade(transition, i); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
crossFade and play is different, i am not sure
if (!targetTransition) { | ||
for (let i = 0, n = anyStateTransitions.length; i < n; ++i) { | ||
const transition = anyStateTransitions[i]; | ||
if (this._checkConditions(state, transition)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opt solo mode
4413ab3
to
9c3510b
Compare
9c3510b
to
deedca9
Compare
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
links: #208
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: