-
Notifications
You must be signed in to change notification settings - Fork 14
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
move returns values outside the bounds of current state #21
Comments
Your Ellie is broken: "The |
Weird -- The Ellie claims it's still at 3.0.0, but it seems like it's not really. |
Looks like it's a known issue with Ellie: ellie-app/ellie#121 (see also ellie-app/ellie#57). I'll see about updating to the latest though. |
Here's a new Ellie that reproduces it with
|
I'm having the same issue, where the ranges should be constrained to 0.0 and 1.0 at the bounds, but it goes above that when calling this: valueProgress : Float
valueProgress =
Animator.move timeline <|
\state ->
case state of
Idle ->
Animator.at 0
Active ->
Animator.at 1.0
Inplace ->
Animator.at 0.5 It appears to depend on the duration of the animation itself, where if its short enough, it'll stick inside the bounds, but otherwise it'll go out, as high as 1.3. |
Sometimes
move
will return a value that's outside the bounds of what's been passed togo
to update the model. This is illustrated in this ellie; code reproduced below for reference.See #19 for discussion of the general structure of this code. There's a new column now labeled "move". Sometimes the value in the "move" column will be larger than the "real" value, which should be impossible. You have to build with
--debug
and step through frame by frame to actually be able to see this. When values like this are being used to drive a visual animation, though, it manifests as a visible "bounce".The text was updated successfully, but these errors were encountered: