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
Need to nail down the user flow for the clip plane: enable/disable, rotate/translate modes, and hide/show plane.
It must also take into account that the Area Light can have rotate/translate modes too. And the default user mode is to zoom/pan/rotate the camera around the volume data.
Solution
I think the app needs a notion of a currently selected object, and distinct rotation and translation modes. Then the object of a clip plane and the object of a area light could be thought of as manipulatable/positionable objects.
The selection and rotation / translation modes can be global user modes in the viewport, similar to many content creation apps.
The solution needs to define how users get in and out of these modes, and what exactly happens in terms of what is shown or hidden in the viewport.
The text was updated successfully, but these errors were encountered:
Use Case
Need to nail down the user flow for the clip plane: enable/disable, rotate/translate modes, and hide/show plane.
It must also take into account that the Area Light can have rotate/translate modes too. And the default user mode is to zoom/pan/rotate the camera around the volume data.
Solution
I think the app needs a notion of a currently selected object, and distinct rotation and translation modes. Then the object of a clip plane and the object of a area light could be thought of as manipulatable/positionable objects.
The selection and rotation / translation modes can be global user modes in the viewport, similar to many content creation apps.
The solution needs to define how users get in and out of these modes, and what exactly happens in terms of what is shown or hidden in the viewport.
The text was updated successfully, but these errors were encountered: