Please add more properties to setElementProperty

[MaxZieb (Loves Hype)]

@jonathan Please add more properties to kPublicPropertyMapping. At least the basics and potential CSS dash properties. As always only a suggestion!

[Ed_Sager]

HI MAX - what would be this in plain English?

@MaxZieb

kPublicPropertyMapping. ... potential dash properties.

[MaxZieb (Loves Hype)]

Meaning that the runtime got an mapping from the internal animation engine to the API that is exposed to the public. Internally the engine can animate everything and the mentioned map exposes the attributes Hype chooses to expose. Potentially nearly every attribute you can see in the timeline properties could be public. Only thing as internally the properties use shortcuts the map would increase the size of the runtime but a few new basics shouldn’t be a problem. At least in my personal opinion as a regular user/citizen!

[Ed_Sager]

Hab' Dank @MaxZieb

@MaxZieb

...the mentioned map exposes the attributes Hype chooses to expose.

OK, I hope this is also somehow addressing my initial challenge:

@DBear

The API only works with “rotateZ” at the moment.

[jonathan (Jonathan Deutsch)]

Thanks for the request! (you’re right about the basic tradeoff in runtime size is mainly why they are limited, but there are some ways we could mitigate this)