Dependency Graph for History?

Is there a way to view or edit the Dependency Graph that is created when using History? Having a dependency graph editor (ala Maya, or many other 3d softwares) would be pretty awesome. Just to explain briefly - an editor that would allow you to see the dependency connections created using History, and to be able to “re-wire” those connections if needed. Even a simple text-based dependency editor would be extremely useful. Can someone explain why this is or isn’t possible in Rhino? thank you! -d

We have nothing of the sort. The Grasshopper plugin sort of does it, but it does not cooperate with the Rhino History. It operates in parallel with Rhino, and it does allow for a lot more algorithmic approach to geometry creation than the history feature, but it comes at a cost of no more manual modelling.

We’ve been talking about using the GH interface to provide access to the Rhino history records, and although everybody likes the idea, there’s a lot of work involved in making it so, which means it’s definitely a long term project.

Cool thanks for the info David!

I’m curious: is there just one history file (or object) that contains all existing history records for a model? Or is there a separate file (or object) for each time history is enabled or disabled? When history is “broken” is the information destroyed or just marked as broken? What’s the big picture on the history data records and their lifetimes?

I am curious as to AIW’s question, and thanks for the little explanation of GH’s parallel state.

dwalden-It would seem to me that if it were possible to change history relationships, that they would likely only affect new output. That if you ctrl-z’ed a bunch of times, it would still not be possible. Although anythings possible. It would be immensely complicated to incorporate into the program I would think, and only future updates to relationships would take place.

Since history already does somewhat change the future by changing history, that would leave the immense;
Or, changing the parent changes the children. But when you change a child, and then go have it change the parent to again change the child, we get…6 fingers, mutations, and bugs! Although it doesn’t quite work like that, the degree of knowledge to program such would be quite astounding.

It would be the ultimate transformation tool though. As it would essentially be a new massive script or string of commands and specifications for each little change you make and allow you to navigate through every change made in Rhino at any point in time a file was open and history was on.

I know I sure need to make full use of the history features, which I currently am not utilizing. For now it seems that if you wanted. Making names of objects, and building a macro from the history as you go utilizing no prompts, selname, selgroups, etcc. Then managing your ongoing macro or script externally in some way or fashion could help you. Such as copy/pasting macro or script into another document that allows you make names 1 color, options of a command another, specific numbers another, would help you make changes to your macro for it. I am not even aware of any programs, but was going to research script and macro building software that would allow you add a command or string, and set certain features to have dropdown lists, replace features,etc…
I was thinking of suggesting such fancy features to macro editor, but I don’t wanna be the guy who asks for a automatic money maker-money counter-scratch post-brownie machine! I am going to research tools used for script writing and external programs that aid, and allow to set commands/options, then give a output code/macro.

It seems that even macro editor was and still is a program developed by another company that software companies can incorporate into their source code or something. There is a macro express, that might allow similar features to rhino in other software programs. Anywho.

You could, and I have thought of for macro editing sake. To make some sort of organized list, or even build a access database that has the list of commands, their suboptions, and the format of all the suboptions to utilize in macro editing. But its just as easy to run part of your macro, see how rhino responds, adjust your macro, repeat as nessisary and move on. Unless you memorize commonely used ones which are freebies.

It seems that even some of the programs in this link have a smart mouse hotkey, which I am not certain if would work or not, but may allow one to be somewhat of a overlay macro recorder. Which could allow one to record a macro by clicking on buttons, and possibly entering letters/numbers in command line and or clicking on suboptions directly in the command line. I am not sure, and definitely not sure if any of them work like this or are functional with rhino. Rhino already has the advanced features and framework for hokey macros etc, all on its own. I I just hooked up my 15 button mouse, and experimenting, it is apparent I that these mice and keyboards are not needed, but can simplify many things and expand on Rhino’s vast user friendliness, that if somehow became better, would practically babysit me and pay me in cash.
Wiki Macro software comparison

Razor Product macro recording(keyboard) or mouse buttons which record keyboard strokes/hotkey strokes

update:razor products programmable keys to hotkey rhino commands does in fact work. In the mouse/keyboard manager program synapse 2.0, you check the box link to program, and select rhino.exe This allows you hotkey to a mouse or keyboard that has programmable buttons to any string of hotkeys set in rhino. Example, go to rhino options>keyboard>hotkeys. Go to ctrl+F7. Type your macro for the hotkey you want on your programmable button. Then in synapse 2.0, for the button, enter ctrl+f7.

So, your hotkeys are limited by the amount that rhino allows, which I have counted to be 166 hotkeys maximum. Howwever, many more options are available to arrange these 166 hotkeys. With macro recording, and keystrokes, and combinations of macro buttons, and recorded macro buttons, you get the picture.