I like some of the functions inside the _line command (particularly the perpendicular option.)
Why can’t we have those options inside _polyline, too? I understand “BothSides” wouldn’t make sense, but the other options should work…at least for the first line segment drawn.
I’d say
a) The Gumball. I just type ‘m’ and then snap to places. I never just move things willy nilly.
b) History. Breaks too easily so I don’t bother with it. Ever.
Really? The Gumball is so much more than just dragging stuff “willy nilly”. Move a specific distance, scale, rotate, extrude and now “cut”… I couldn’t live without it.
One that comes to mind for me is the Weight command. I know technically this is NURBS software and without the R we just have NUBS, but I’ve always heard that changing the weights is bad practice.
Doesnt do it for me. The simplicity of move, scale, rotate commands give me maximum freedom to choose specific origins of rotation or scaling, or move by specific amounts already. The gumball has some preconceived notion of obect center and is a repackaging of existing features that feels like a net negative overal. In my 25 years with Rhino there has never been an instance where I wished I had a gumball.
Also Rhino’s clever implementation of viewport interactions (where a command can start in one and end in another) also work as a gumball in some sense. I think most Gumball users are likely working on a single perspective viewport and like the XYZ locks it gives them.
That is correct. The Gumball is a local coordinate system, of course, freely transformable, and can as such be useful in many ways.
How would you lock direction with the move command? Serious question. I find the Smart Track feature often too unreliable.
On topic: I never use named CPlanes, because named Views store their CPlanes, too.