one of the reasons i never touch history is because i never know what commands and objects have a history attached to them.
somethings that might be nice would be when running a command with history the “record history” button changes to certain color when running the command so you can turn it on quick. another would be some visual indicator that a selected object has a history.
thnaks.
I think the problem with this point is that if you want to use history with a command that supports it is that history needs to be turned on BEFORE you run the command.
AFAIK, the only place to see if a command supports history is in the help file.
I agree it would be useful to have a “master list” to refer to.
atleast some way to know if a selected object has history, like a dedicated color or display style? it’s something that’s been brought up before but i don’t think there has ever been a consensus on how to do it.
Hi -
The way that is handled in Rhino now is that you can set children objects to be locked.
-wim
Sounds pretty tedious, obscure and potentially very error-prone for an actual user who is trying to use history. Seems Rhino could be much more helpful and streamlined. Back when computers were really great with 1ghz and 512K of memory this level of support might have been appropriate but there’s enough cycles and bits available today that Rhino could do a lot more to help the user keep track and remind him/her that a mistake is about to be made.
I run history on all the time, and have a hot key for purging history when I’m done with it.
that removes the question “is it on?” cuz the answer is yes. it’s on.
then when I want it off, I kill it with history purge.
simple, effective.
Right now the history button at the bottom of the screen only shows text in black if history is on, or grayed out if it’s not on.
However this does not address the question raised here which is an excellent suggestions: “is this tool recording this in history right now?” …which means: “I know I turned history on, but is this one tool I’m running right now history capable?”
…what if when those two conditions are met:
Then the History button changes to green? or flashes? (Maybe too annoying) or the backdrop of the button becomes red (like a recording button)?
G
That’s a great way to know, as long as you also know how to ‘open the hood’ to properties; and this still does not tell you anything about which actual tool is history enabled.
There is a list in Help about half way down the article:
http://docs.mcneel.com/rhino/6/help/en-us/index.htm#commands/history.htm
Now you have moved us from having our hands dirty under the hood of properties, to the owner’s manual in the glove compartment.
Serious question: do you remember that list by heart? I know I don’t. Let alone knowing when a new history support of a command gets added to it.
We are going to disagree on this one John, like we usually do: You think it’s fine as it is, I don’t.
I still love you.
Have a great week and happy riding if you go out!
G
You seem to forget that I do not design using Rhino, and never have.
