Closed kuon closed 8 months ago
Thank you (again!) for that super complete feedback and for digging that far in the source code to help me on fixing things !
I've read all your links, very interesting reads thank you! I believe I handled the most critical cases by always validating and clamping numeric values and falling back to min value or 0 anytime it's changed. So I guess things should be "ok", and i'm really only using number field for actual numbers. I'm also a bit relluctant in updating the component that handles kinda all input types within Twitchat as making a mistake can have impacts everywhere if I make a mistake. But I'll definitely keep that in mind for the future, thank you very much for sharing this !
In the meantime, i fixed the missing fields default values for OBS transform animations and will deploy that in the coming days !
Yes, not using number field was more of a general suggestion and not a required immediate change.
The default values should be good now !
If I create a trigger to move a source, it works only if "Animate change" is unchecked.
With "Animate change" checked, the source doesn't move, and here is the debug log from OBS:
There is no message to set the transform.
In the trigger log, I see:
The
animation duration
was set to the default500ms
value. If I rewrite 500, then the animation works. It seems there is a problem with the default value in the form. I use firefox, and it might be why the behaviour is different.As a side note, I see that the input is of type
number
. I highly suggest you do not use that.