Hi Dave - re: instrumenting UI to capture/record stuff.

Actually there is one kind of recording mechanism already in place, which is used by MoI's current history function.

When a geometry factory produces its objects, the factory name and all of its inputs are converted to a chunk of text and stored on the output objects. This is what is then used during history updates, like when you do an Loft for example and then edit the curves that were inputs into the Loft and then the Loft updates.

That kind of recording is happening all the time when you just do any modeling in MoI.


So there's kind of one ingredient of that in place, but that does not really mean that it would be at all easy to make a macro recorder though, it would probably need to have some additional stuff for reconstituting factories and analyzing inputs on history data and stuff like that set up.

There are plenty of other confusing issues involving recording macros, like when you select an object while the macro is running, do you intend for that particular object to be used when the macro is replayed (say as a cutting object in a boolean), or would you want to be able to pick objects to use at that point, stuff like that. There's probably enough issues that it would be more properly part of a larger and deeper history mechanism that had various mechanisms set up for modifying parameters on a sequence of operations.

- Michael