I’m pleased to see the WIP is getting stable enough the last few releases that I can start using it for actual work. Today I had a workflow which required extracted isocurves to update when the source surface changed (itself updated by editing it’s creation curves), and it all worked. Wouldn’t in V5. Always happy to see more commands become history enabled, thanks!
Two comments on Broken History warning dialog boxes;
One, after working in a file for a long while today, I began to notice I was no longer getting broken history warnings when I clearly should have been. Can’t reproduce it now with same file but different computer.
Two, it has become second nature to me to dismiss broken history dialogs with the Escape key, but in V6 in addition to closing the dialog Rhino undos the action which called it. Kind of a minor point, but I always keep history recording on, so I get a lot of these, and having to reach for the mouse feels like an imposition. I prefer the V5 behaviour.
Hi Mark, all - just fyi, on the isocurve front, there is also MoveExtractedIsocurve. This initially asks you to pick the surface the iso is from but thereafter remembers and automatically enables History at the same time. This is especially handy when used in conjunction with MatchSrf > CurveNearSurface=On and the iso is the target curve and even better if History is enabled for the MatchSrf - all used together, it makes it possible to create nicely adjustable surface that not only holds onto the target surface if that is edited, but also allows you to slide the edge along without breaking continuity.
I think you should post more videos like that showing the new capabilities in the WIP, it is hard for the end user to just “discover” them.
Today I am getting almost no broken history warnings, but not none (I got one after missing probably fifty of them, but I failed to spot a pattern). This is on a Win7 box, on Win10 it is working as expected.
