Sure will.
-j
Yes, I agree with this because: a Path:Dress-Up is just that, a path modification, and not a tool-change.
I agree about thread-jacking but I'm not a forum admin. As for the cloning, don't we already have this?bill wrote: ↑Fri Mar 02, 2018 2:59 pmIf some user(like me) needs to chase the profile with a chamfer, then copy/clone the profile operation, set an offset, and utilize another tool selection.
This is why Ive always wanted to be able to clone an operation, preserving all op detail; then just change the tool selection.
Additionally, I think this topic should be its own thread and needs to be moved since this borders on thread hijacking!
I think at 217733.chrisb wrote: ↑Fri Mar 02, 2018 4:42 pm I can split it, but I have to get it right the first time, because I am afraid will not be able to merge things later. So where should I split it:
either here: https://forum.freecadweb.org/viewtopic. ... 30#p217733
or here: https://forum.freecadweb.org/viewtopic. ... 40#p217869
Yes we have, - but it dosn't work on a operation with a dressup. Also array dosn't work on a operation with dressup.
I fixed this one - made PathArray to accept Dressups. The commit is here:
Code: Select all
isinstance(obj.Proxy, PathScripts.PathOp.ObjectOp)
and
obj.isDerivedFrom("Path::Feature")
Code: Select all
return isinstance(obj.Proxy, PathScripts.PathOp.ObjectOp) or (obj.isDerivedFrom("Path::Feature") and "Dressup" in obj.Name)