Subtractions/Additions when Arch.Component is placed in App.Part

A forum dedicated to the Draft, Arch and BIM workbenches development.
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
gbParametric
Posts: 23
Joined: Wed Apr 20, 2022 9:06 pm

Re: Subtractions/Additions when Arch.Component is placed in App.Part

Post by gbParametric »

Roy_043 wrote: Sat Aug 13, 2022 6:42 pm What is your reason for putting the Subtraction object in a different Std_Part, with a different Placement, from the component that you want to subtract from? Can you clarify your intended workflow?
1) I have Column assembly(App.Part), that consists of Steel Column(Arch.Structure), bunch of plates(Arch.Structure)and bolts, lets say i wanna cut the end of the column off, so that it would be in the same angle as roof.

2) I have the same column, but this time there's a roof beam, that need to be connected, both are inside the 2 different App.Part objects,
i wanna use one of the beam planes to cut column and one of column planes to cut the beam.
gbParametric
Posts: 23
Joined: Wed Apr 20, 2022 9:06 pm

Re: Subtractions/Additions when Arch.Component is placed in App.Part

Post by gbParametric »

Roy_043 wrote: Sat Aug 13, 2022 6:44 pm With the current Link system objects can have multiple parents. So it is probably not as straightforward as you may think.
We could start by supporting only one parent, and there could be checks for multiple parents, that handle edge cases afterwards.
User avatar
Roy_043
Veteran
Posts: 8450
Joined: Thu Dec 27, 2018 12:28 pm

Re: Subtractions/Additions when Arch.Component is placed in App.Part

Post by Roy_043 »

gbParametric wrote: Sat Aug 13, 2022 7:37 pm handle edge cases afterwards.
These are not edge cases, if a new system is devised it should include support for them. Note that what you want also results in out of scope links.
User avatar
Roy_043
Veteran
Posts: 8450
Joined: Thu Dec 27, 2018 12:28 pm

Re: Subtractions/Additions when Arch.Component is placed in App.Part

Post by Roy_043 »

Workaround for Example_for_forum2.FCStd:
  1. Create a Link (Std_LinkMake) from the Cube.
  2. Change its "Link Transform" property to true.
  3. Make sure Std_TreeSyncPlacement is off.
  4. Drop it in Part.
  5. Use the following expression for its Link Placement Position:
    Part001.Placement.Base - href(Part.Placement.Base)
    The use of href is required to suppress a cyclic reference warning (object in Part references a property of Part).
Attachments
Example_for_forum2_workaround.FCStd
(17.41 KiB) Downloaded 20 times
User avatar
Roy_043
Veteran
Posts: 8450
Joined: Thu Dec 27, 2018 12:28 pm

Re: Subtractions/Additions when Arch.Component is placed in App.Part

Post by Roy_043 »

Workaround for Example_for_forum3(cut with plane).FCStd:
  1. Create a Part_ElementCopy from a face of the column and a face of the beam.
  2. Make sure Std_TreeSyncPlacement is off.
  3. Move the copies into the correct Part containers.
  4. Select the beam and the copied column face and call Part_SliceApart.
  5. Move the created Exploded Slice group into the Part that holds the beam.
  6. Expand the group and make Slice.0 invisible.
  7. Do the same for the column.
Attachments
Example_for_forum3(cut with plane)_workaround.FCStd
(43.31 KiB) Downloaded 23 times
gbParametric
Posts: 23
Joined: Wed Apr 20, 2022 9:06 pm

Re: Subtractions/Additions when Arch.Component is placed in App.Part

Post by gbParametric »

Roy_043 wrote: Sat Aug 13, 2022 10:18 pm Workaround for Example_for_forum3(cut with plane).FCStd:
Thanks alot for helping with workarounds. Part_ElementCopy and Std_TreeSyncPlacement helped alot.
Came up with this workflow: Std_TreeSyncPlacement <-- This is what i needed, i had this off so when i transfered elements between App_Part, they changed global placements.
Post Reply