> It would be nice if there was a way for you to switch on a "history view" that showed the
> sequence of operations that were used to generate the currently selected object.

> Probably the main purpose of that would be so that you could alter some of the parameters
> that were used and have the object recalculated. But that could also be a good place to capture
> some steps as a macro as well.

Sort of an "object" versus "session" history? This is more like the "modifier stack" that XSI and Max (among others) have I suspect. Since these can get very long and involved, I think most apps have a way to collapse/discard all or part of the stack to conserve time and space. It also tends not to be very selective and includes lots of stuff you probably never will want to modify.

> If you were able to more visually edit different parameters with different UI controls for each one
> that kind of interface would probably be possibly usable by a wider set of people.

That's the key, to identify those operations and parameters the user wants to modify and create a custom UI for that. Sounds like an interesting feature...