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
Hi again!
I will refer to movement/scale/rotation/skew as operations for brevity.
As of right now, the Transformer handles all inputs and operations by itself, but it would be nice to be able to handle some more interesting cases. Here are the main options i'm missing, forgive me if they are already present and I simply did not find them.
Getting the group transformations.
As far as I can tell right now Transformer handles all the input and directly applies the operation to the group members, it would be useful to have a way to get the applied transformations.
Setting the group transformations.
Since Transformer applies its changes directly to the target objects, it does not expose a way to easily set any parameter from the outside.
This could be very useful in cases in which thanks to (1) we save somewhere the operations we performed to a group and then retrieve and set those same operations to a new Transformer, without having wokny wireframes.
Being able to hook inside the transform process.
It would be very useful to have a callback after the changes are computed but before the actual transform is performed, to be able to handle some more interesting logic.
Some use cases that would be enabled are:
Being able to add some constraints to the operations, for example forcing the group to be inside some bounds.
Being able to smooth out the interaction, say with a library like React Spring.
Being able to have movement and scaling snapping, as right now only rotation and skew are enabled.
Ideally, one such callback would take as input the delta of the current frame and the delta since the beginning of the event and be able to make any change to the operation.
Please excuse the very crude example.
It emits a transformchange event already but if you want to change the applied transform itself, you would need to override it. Let me know if you need additional consulting services.
Hi again!
I will refer to movement/scale/rotation/skew as operations for brevity.
As of right now, the Transformer handles all inputs and operations by itself, but it would be nice to be able to handle some more interesting cases. Here are the main options i'm missing, forgive me if they are already present and I simply did not find them.
As far as I can tell right now Transformer handles all the input and directly applies the operation to the group members, it would be useful to have a way to get the applied transformations.
Since Transformer applies its changes directly to the target objects, it does not expose a way to easily set any parameter from the outside.
This could be very useful in cases in which thanks to (1) we save somewhere the operations we performed to a group and then retrieve and set those same operations to a new Transformer, without having wokny wireframes.
It would be very useful to have a callback after the changes are computed but before the actual transform is performed, to be able to handle some more interesting logic.
Some use cases that would be enabled are:
Ideally, one such callback would take as input the delta of the current frame and the delta since the beginning of the event and be able to make any change to the operation.
Please excuse the very crude example.
Let me know what you think about it
The text was updated successfully, but these errors were encountered: