This seems a bit obvious:
So few tools allows for history parameters to update. Basically only BlendCrv and BlendSrf, I think?
But since History manages to rebuild itself somewhat in Rhino (even if it could be so much better and more stable), that means that the parameters are kept somewhere, only not exposed to the user.
A history panel could, for example, show the number of objects in an Array and allow the user to change them… or even change the radius of a fillet…
I must admit that it feels weird that nobody has talked about this… it doesn’t feel like that large of a task, a few weeks for a developer? I mean, no new core functionality needs to be added, just a new UI which reads the existing parameters, populates them in an editable list and triggers a history update when the user changes them.
Does it already exist and I just missed it or did I search for the wrong thing before creating this thread?