Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve

John S. wrote:

> It's not also as one poster said "We paid a lot of money for it so it
> has to work" For [1] I haven't paid a lot, and for [2] you can still
> use the same commands you have quoted above. Having a
> command line is extra to the program. All a command line is, is a
> way to enter macros and most programs make a fuss that they can
> handle macros.

I'd agree with John S. here - I use the command line essentially as part of
the Rhino/ACAD keyboard shortcut/macro system. Sort of like an interactive
version of the message bar that most programs have in the lower left margin
of the 'window'. Everything is available in icon/menu form, if needed.

Non-visual input is the key, IMO. I don't need to move my eyeball's focal
point to a dialog box, un-consciously scan it's text, eye-hand coordinate
the mouse to select options, etc. I can simply type the command keys. It
also lets me rest my mouse hand briefly. You could almost be blind and run
command line CAD reliably. (Big selling point, right? :)

The ability to type in 'object_snap' values on the fly is something that I
especially miss from ACAD.

- Keith Rumley
(With my bias on the side of using CAD in commercial situations)