Thanks very much for your answer
Quote |
---|
emme wrote:
You're not doing anything wrong. Using normalized time on variation should work perfectly fine. |
Yes, is true that it seems to be working correctly and would not be a problem if you can be sure that it will not give any possible error, and another thing is that even when it may be working correctly,
you can not submit a filter with a red warning as it not allowed.
Quote |
---|
emme wrote:
I think the warning is there just because the expected input type for variation is an integer - which normalized time is not, As the quoted text points out, normalized time is automatically mapped to IntSlider inputs using rounded linear interpolation between the default min-max values. |
Yes, you are right, and this is the same that I have thought, BUT if the quoted text is right, then WHY you get the warnings IF the animation component is already mapped accordingly to the input that is connected?
I mean that if it is already allowed to connect an animation component to all the shown input as in the quoted text and the animation component is then adapted to the connected input, why you get a warning?
So this may be a bug that is wrong and should be fixed or modified?
Quote |
---|
emme wrote:
So no need to worry about warnings as long as everything works |
Yes, I agree with you and you are right that is not needed to worry if it works, unless you may want to submit a filter to the library.