Well yeah – you are right…
So why then do I feel there is a problem with “delete hole”?
Lets take the “make hole” command:
Firstly you are asked to select planar closed curves (press enter when done)
So as you do this, the curves are highlighted as you pick.
Once you have selected all the curves you want, you press enter and are then asked to select a surface or polysurface.
Once done, you press enter to complete the task (or optionally select further options). The command ends.
Now “delete hole”:
You are asked to select a hole edge, the edge is highlighted, and once you have selected an edge, either via the mouse, or pressing enter, the command deletes the hole without further confirmation, AND STAYS ACTIVE, with no visual information as to this being the case except the command line.
The difference here is that the Make Hole command gives feedback of what is about to happen, to possibly multiple holes, and then waits for confirmation before it carries out the command on enter, and ends.
The Delete Hole command gives feedback of what is about to happen to one hole, and then deletes it on enter without waiting for confirmation, and further stays active.
This is not consistent behavior.
Delete Hole should:
Ask you to select a hole edge. Once this is done via a pick with the mouse or enter, it should ask you to select the polysurface, and then complete the task via enter, and end.
Now, just because the command already “knows” which polysurface you mean because you have already selected an edge, doesn’t mean it should rush ahead and do it without confirmation.
Because other commands don’t do that….and they don’t stay active once the task is carried out.
Split: Asks for objects to split, press enter when done. Then asks for cutting objects. You select these, press enter to carry out the command, and it completes.
Copy: Asks for objects to copy, press enter when done. Asks for from point, all the while giving feedback as to what is about to happen, and once you are done with copying, terminates.
The difference is Delete Hole is “overly smart” compared to the general command set of the program, where the convention is Enter is used during the command to confirm options and to complete a command, with the command terminating when done.
Further, another example of this “overly smart” command is WireCut, which doesn’t wait for an enter after selecting the cutting curve, but goes directly to asking for the object to be cut.
To be consistent, it should require an “enter” once the cutting curve is selected. I use this command often and I still screw it up more often than not by pressing enter after selecting the cutting curve, whereupon the command unhelpfully terminates.
It can be argued this is nonsense, and endlessly having to pressing enter when the software can be coded so it isn’t necessary is stupid!
I would so agree; however unfortunately that is the convention that Rhino has adopted, and I would argue that it is counterproductive to allow rogue commands to operate outside it.
I suppose I should note that I almost always use the command line and shortcut macros; perhaps if I used the menu or the icons this kind of thing wouldn’t be such a problem…
Mitch, thank you for the marcos, which I will certainly adopt.