You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When one wants to get/set an interpolated value, e.g. from 0 to 1, it is very convenient to use the current SliderInput.
It would be nice to have an ability for the slider input to have multiple carets, which would all interpolate on a single total basis value.
For example, 3 carets at equal distance from each other on a [0, 1] range would produce an array with interpolated values [0.25, 0.50, 0.75].
For example, I have some dynamic animation, where I build the paths and timings analytically, based on the current state of objects. The animation consists of a chain of animation sequences. I want to give an artist an ability to control the total time the animation takes, as well as the duration of each part of it in relation to each other. I currently expose those settings via attributes, but a single control would be more convenient and prevent accidental errorenous inputs, where the sum of all parts would be over or less than 100%.
The text was updated successfully, but these errors were encountered:
Feature request.
When one wants to get/set an interpolated value, e.g. from 0 to 1, it is very convenient to use the current SliderInput.
It would be nice to have an ability for the slider input to have multiple carets, which would all interpolate on a single total basis value.
For example, 3 carets at equal distance from each other on a [0, 1] range would produce an array with interpolated values [0.25, 0.50, 0.75].
For example, I have some dynamic animation, where I build the paths and timings analytically, based on the current state of objects. The animation consists of a chain of animation sequences. I want to give an artist an ability to control the total time the animation takes, as well as the duration of each part of it in relation to each other. I currently expose those settings via attributes, but a single control would be more convenient and prevent accidental errorenous inputs, where the sum of all parts would be over or less than 100%.
The text was updated successfully, but these errors were encountered: