Add __experimental_sequenceProp to studio.transaction() #449
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want the ability to programmatically add keyframes to a sequence, but it looks like the best way to do this is to use
transaction(({set}) => {})
. Unfortunatelyset
doesn't create a Track from an unsequenced prop.So let's say I have some data I want to turn into keyframes.
Currently, on
main
, Ifobj.props.x
isn't already sequenced (i.e. manually from the Studio UI) thenset
will just set the static prop, which isn't what we want here. This pull allows you to at least tell Studio that you want to sequence the property.@vimlesh1975 has some code that he posted to Discord that loops over all keyframes and unsets their value at the given time, but it would be really nice to be able to clear all keyframes for the initial track data, and ensure that the track is sequenced ahead of time.
See also #411
Ideally I'd like something like:
But in the meantime at least this fixes the ambiguity of whether you want to set a static prop or a sequenced prop.