-
Notifications
You must be signed in to change notification settings - Fork 248
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
[BUG] Position#set calls not queuing as expected. #474
Comments
Definitely a bug. |
@alexanderGugel care to look? |
Added testcase for transitionable: t.test('set without transition in callback', function (t) {
time = 0;
var transitionable = new Transitionable(0);
transitionable.set(100, { duration: 1000 }, function () {
transitionable.set(0);
});
time = 500;
t.equal(transitionable.get(), 50);
time = 1000;
t.equal(transitionable.get(), 100);
time = 1000;
t.equal(transitionable.get(), 0);
t.end();
}); Can't reproduce with Transitionable. If this is a bug, it's associated with the Will investigate that. How/when are you |
Can reproduce. This is a little bit tricky. Will submit PR. @jd-carroll Thanks for reporting this. |
Resolves Famous#474 Example: var position = new Position(parent0); position.set(100, 100, 100, { duration: 500, curve: 'inOutExpo' }, function () { position.set(0, 0, 0); });
Instead of doing the following
I'm doing
The result is that
cardPosition.set(0,0,0)
never takes effect.It seems like the preceding animation might still place at least one more command into the command queue after the call to
cardPosition.set(0,0,0)
.In order to make it work, I have to do the following:
This bug might exist with other components if they're all designed the same way, but I haven't checked.
The text was updated successfully, but these errors were encountered: