Russ, one thing here which could be looked at: if I do a path with dropcutter and get a result I like, then I click OK to close the dlg, it starts all over again.
This problem may not be restricted to 3Dsurface but is a problem here due to excessive calculation times. If I just waited over a minute to see the result, I don't want to wait again when I OK it.
In this regard, can something be done to keep track of whether the current path is in a "clean" state or needs recalculating due to parameters having changed?
Also look at ApplyButton enable state. Like very many path tools this only seems to track a small number of relevant parameters. I just submitted a PR to fix this in BoundaryDressup, but this needs cleaning up in nearly all path tools.
It's pretty trivial to connect the various elements' Change events to "setDirty" or whatever and set the enable state on Apply button.
For example , if I change "interval" nothing happens to Apply button state. If I simply enter the Stepover inputEdit it changes Apply button even if I don't edit the value ( this again is not optimal since presumably it will trigger a "dirty" state even though the data has not changed ). Ironically, if I edit interval then click on the greyed-out
Apply button, it does start to recalculate the path and enables what was supposedly an inactive button.
This should be triggered onChange not onEnter.