Are you able to confirm what I'm guessing from functionality: that there is currently no attempt to keep track of whether a tool path actually requires recomputing? ie. OK Exit from path dlg always triggers recomp. and an OK exit from job edit dlg always results in recomp. of ALL active paths.
While it would be tidy to have 2.5D tools also only do required work, my experience of FC has been that this is fast enough to reasonably ignore the wasted effort.
I don't think the same can be said of 3D tools.
For example I just added a new 4mm tool controller to my job, ie it is currently unused. That triggered a total recalc on four 3Dsurface paths which is good for about 4min of thumb twiddling for ZERO result. None of the paths needed reworking.
I'm thinking that a dirty flag could be added initially only for 3D paths and ignored by others, until a real need is seen for broader implementation.
There is also some room for workflow improvement in 3D paths since several options are currently only available in the treeview and not settable from the dlg. This means that as soon as you take the focus off that param you trigger a recomputation. eg I change " boundary enforcement" and want to change "cut pattern angle" ( neither available in the UI ), that means TWO long recalculations, not one.
Maybe integrating them into the UI is a simple solution, since there you make as many changes as required and you have control over when and if the recomp happens.
I think there is a real need for this on 3D, so maybe a discussion about how to implement it would be a first step.
Each path element could get a "dirty" status. 2.5D tools are free to ignore this until someone thinks it matters.
Changes in Job Edit would determine whether the job is dirty ( implying setting dirty bit of all existing paths ). Adding a NEW tool, does not affect anything existing: not dirty. Changing a tool's parameters could either set all paths dirty or, in the fullness of time only touch those which use that tool.
Currently, if I change the output filename by one character in the job Editor, it triggers a recomp of all active tool paths. This is crazy !
I have some more detailed ideas, which are not hard to sketch out, but I won't bother formulating a protocol unless there is some agreement about the desirability of advancing the issue.