Rhino has a great feature - many commands remember the last option you chose and default to it (instead of the factory setting) the next time you use the command. Thanks! Great feature!
Except…
Quite often, I watch a how-to article or video and follow the instructions faithfully – and it doesn’t work when I do it. But it clearly works when the author did it!
And then I realized why. It’s that rememory feature on commands. The person making the lesson made a choice to a command that enables it to get the desired results. But they don’t remember making that choice, it’s now just part of their environment. Because they don’t remember making that choice, they don’t mention it in their instructions.
And that’s why it works for them but not for me. Sometimes I’m lucky and the video shows the command line (at a resolution I can read!!!) so I can figure out what’s different. Otherwise, I may have quite a lot of experimentation to do to get it to produce the desired results. Not fun. Wastes time.
It would be great if it was really easy AND EXTREMELY OBVIOUS for the author to know which command options aren’t factory default ones. The use of color and font would be one way.
ALSO allow an author to (a) save their current command defaults under a named file, (b) restore to factory settings, (c) do their article or video, and then (d) restore the command defaults from the named file. That way, people who actually already know how to make the command work can figure out exactly which values actually work.
I suspect this would be a very easy thing to implement.
(And if it’s already implemented, let me know!!)