Thanks Michael
I find the history function when sweeping a profile then fine tuning it after generation invaluable.
I typically would array the stone solids and beads and array them along a shoulder profile and once correct don't change it, perhaps a history dump button or option on the history could get rid of the back history and reduce file size .
I see your point that saving all that data will generate large file sizes, my pc seems to handle large files with over 2000 solids (a lot of them with fillets ) Ok , some of the stl output files are in the 100's of mb
Feel free to add history on arrays to my wish list :) oh and the variable radius fillets (like the 2 distance chamfer) :) I realise thats a hard one also

perhaps an on off toggle in the options for those not wanting it rather than mucking around with the side pane buttons

thanks
shayne

Hi shayne, yeah there are some different possible approaches. But since I'm planning on doing a significant overhaul to how history works, it very well might be a kind of "dead end" to do much work on the current system, so at least currently I'm not really prioritizing work that would only apply to the current history system and then not do any good when it's all redone...

Also now that I think about it some more I seem to remember that in addition to the file size issue there was also a problem that the current history system actually only works in the cases where one single object is the output from the command like with a regular sweep for example. With multiple outputs the history system doesn't currently know how to process it.

- Michael