Sceneform-android-sdk: Rotating proper TransformableNode

[terezo]

Hi,

why the RotationController on TransformableNode does not work the same way as TranslationController? I mean it's called (rotated) even the gesture does not collide with TransformableNode. I assume TranslationController uses CollisionShape to decide whether translate the node or not. RotationController appears to be called on currently selected node, even the selected node is out of view and user is viewing different node.

Rotating something out of view it's not intuitive, especially when comparing to TranslationController logic (which I think is intuitive).

Am I doing something wrong? Any suggestions how to rotate only visible node (to user) which collide with twisting gesture, not anywhere on the screen?

[malik-at-work]

Hi Terezo, Thanks for the question!

We came up with a many kinds of interactions to do rotations. We spent some time debating and researching the best ones, and the UX recommendations have changed slightly recently. The current UX recommendations are to have 2 different rotation gestures:

Select + swipe left/right: Works really well when you have multiple objects in the scene and/or if you want to see the full impact of the rotation without covering the object(s) with your finger(s), but not very discoverable.

Twist: Many users try to do this first. Works really well if you only intend to allow users to rotate along one axis. If the developers support rotation on multiple axes, this gesture can control an x/z-axis rotation in conjunction with a select + swipe L/R to control y-axis rotation.

Sceneform currently only supports select + Twist object, so there is an action item to update this.

[terezo]

@malik-at-work that would be great!

Thanks for the response.

[chnouman]

@malik-at-work @dsternfeld7 any update on this because I want to enable rotation only with one finger swipe.