mghansen256 wrote:Perhaps this can be made an option for Draft::Move, to always move the parent objects instead of the derived objects? Edit->Duplicate for example also asks whether it should duplicate dependencies when you duplicate a part union.
IMHO this would introduce much more headache than it would solve. And it is very important, I think, that the draft move moves only the selected objects, otherwise many people will not understand what happens under the hood. Besides, all objects keep very clear the difference between moving a "parent" and a "child" object, and react accordingly (or prevent one of them, if needed, as PartDesign does).
Yesterday I committed a change that I believe will be pretty powerful: All Arch objects now have a "Move With Host" property that, if set to True, will make them move together with any parent Arch object they are included in. So the user has precise control over what he wants to obtain.
Note that this "grouped move" at the moment will only happen if you use Draft Move or Draft Rotate. Changing the Placement will not move the children (yet. I must still figure out a way to handle Placement changes more reliably)