Macros cannot be made smart, nor do they react to the things they help create. Macros allow you to automate tasks you would normally do by hand but not by brain. If your job is to open Rhino files, add a line from 0,0,0 to 10,0,0 to each one and save the file again, you would probably get very tired very quickly from typing _Line w0,0,0 w10,0,0 six times a minute. The _Line command at the top of this page is an example of a very simple macro. I shall only briefly pause at the subject of macros, partly so we know which is which and partly because we might at some point simulate macros using RhinoScriptSyntax in Python.Ī macro is a prerecorded list of orders for Rhino to execute. I do not wish to offend those of you who write macros for a living, but it cannot be denied that it is a very primitive way to automate processes. The lowest form of programming in Rhino is using macros. Programmers pump text into Rhino and they expect to get text in return. It’s no use programming the mouse to go to a certain coordinate and then simulate a mouse click, that is just plain silly. Programmers have no emotions in this respect, they are all wedded to the command-line. Emotions run high on the subject some users are command-line fanatics, others use only toolbars and menus. Because of this second (graphical) interface some people have done away with theĬommand-line entirely. You can also click on the Line button and then twice in the viewport to define the starting and ending points of a line-curve.

Editing interface in rhino for mac