How to use Gizmo

[tingspain]

Hello,

How to enable the use of Gizmo on the view? I tried the X, W, E, and R keys but it doesn't work.

Could you provide an example of how to use it?

Thanks in adavance

[Irev-Dev]

@tingspain I think Gizmo is just for "click and drag" functionality for moving the camera with the mouse. scrolling also zooms in. I'm no away of any other hotkeys.
I might be wrong though.

[tingspain]

Of course, Gizmos (well gizmos is more than that in general terms), but Transformation Gizmos are for modifying the selected element using the mouse. There is one GIF showing the use of them at the main page, but I dont know how to activate them, that is why I tried different shortcuts to activate the Gizmo, but I didnt have any luck.

[tingspain]

Ok, looking around the code, I can see that the way to use the Gizmos is by applying the function Transform to the shape. However, it doesn't work well for me. I don't know if I am doing something wrong, or it is just some bugs because it is in beta.
Also, I noticed that the short keys are off for me, instead of being R for Rotate, T for Translate, S for Scale, the short keys are mapped to W for Translate, E for Rotate, and R for Scale. I am using an Intel MacBook Pro and macOS 11.2.1,

This is how I use it:

let shape = Translate([-25, 0, 40], Text3D("Hi!"));
let trans = Transform(shape);

[raydeleu]

I have seen the Gizmo in my earlier attempts, but lately the gizmo no longer appears when I use the function Transform. In the developer window I noticed the following error message:

TransformControls.js:15 Uncaught TypeError: Class constructor Pe cannot be invoked without 'new'
    at new THREE.TransformControls (TransformControls.js:15)
    at CascadeEnvironment.<anonymous> (CascadeViewHandles.js:10)
    at Worker.cascadeStudioWorker.onmessage (?THREE.TransformControls @ TransformControls.js:15
(anonymous) @ CascadeViewHandles.js:10
cascadeStudioWorker.onmessage @ ?

As I do not see the point of the gizmo in a code-based CAD system I do not miss this functionality, but I was unable to produce screenshots for the manual. Perhaps omit it completely from the manual as it does not work? Or am I doing something wrong?

[zalo]

You probably aren't missing anything; the Gizmos were more of a hack to see if I could get in-window interactions to bidirectionally edit the code.

Unfortunately, it relies on generating error messages in the backend, and parsing the stack-traces of those error messages in a super brittle way between browsers. It's probably worth leaving out of any documentation.

[zalo]

Also, the transform gizmo implementation was broken in a recent update; here's a working version now.