[Bug?] Draft transformations with Copy don't take care of Std_Part

Have some feature requests, feedback, cool stuff to share, or want to know where FreeCAD is going? This is the place.
Forum rules
Be nice to others! Read the FreeCAD code of conduct!
Post Reply
User avatar
flachyjoe
Veteran
Posts: 1869
Joined: Sat Mar 31, 2012 12:00 pm
Location: Limoges, France

[Bug?] Draft transformations with Copy don't take care of Std_Part

Post by flachyjoe »

Hi,
even if Draft object are created as children when an active Std_Part exists, Draft transformations ( Draft_Move, Draft_Rotate, Draft_Scale, Draft_Clone) still create objects at top level when the Copy box is checked.

Code: Select all

OS: Ubuntu 22.04 LTS (XFCE/xubuntu)
Word size of FreeCAD: 64-bit
Version: 0.21.30018 (Git)
Build type: Unknown
Branch: master
Hash: d68736537e1c0109fdc6c1f7449fd3a43ae4adb6
Python 3.10.4, Qt 5.15.3, Coin 4.0.0, Vtk 7.1.1, OCC 7.5.2
Locale: French/France (fr_FR)
- Flachy Joe -
Image
heron
Posts: 307
Joined: Mon Apr 20, 2020 5:32 pm

Re: [Bug?] Draft transformations with Copy don't take care of Std_Part

Post by heron »

This seems to be its normal behaviour. Maybe would may to open a github issue to change it if there is no one yet.
I believe that this thread may be interesting to Roy. @Roy_043 What do you think?
Greetings.
User avatar
Roy_043
Veteran
Posts: 8450
Joined: Thu Dec 27, 2018 12:28 pm

Re: [Bug?] Draft transformations with Copy don't take care of Std_Part

Post by Roy_043 »

When copying an existing object you may also want to look at the Std_Group/Std_Part the original object is nested in. I am not sure what the most logical behavior is then.

FYI: When an object is copied with a Draft command, the new object is currently placed in the same layer (which is in fact a group) as the original.
Post Reply