FreeCADView Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003067 | PartDesign | Feature | public | 2017-06-02 17:36 | 2021-02-06 06:43 |
| Reporter | abdullah | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Product Version | 0.17 | ||||
| Target Version | 0.20 | ||||
| Summary | 0003067: Add Mirror body tool to PartDesign | ||||
| Description | Create a new separate body that is symmetric to the original body and depending on it, so that the second can have some extra features but still change with the original one. In this case an automatic fuse is not desired, as they are intended as separate parts of an assembly. | ||||
| Additional Information | Not to be confused with ticket 2863 which requests mirroring a body but to fuse the result inside the existing Body container. | ||||
| Tags | No tags attached. | ||||
| FreeCAD Information | |||||
|
|
Why did you keep the same title as the 2863 ticket? It is not a feature anymore, it's a separate body. And would such a tool be really needed? This is exactly what the current Part Mirror tool does. |
|
|
@abdullah asked me to clone this ticket and it's on his agenda to rename it |
|
|
@normandc Creating this ticket is my fault. I can tell you why I thought I needed it. I was doing an enclosure consisting of two parts (first result-part and second result-part) almost symmetric about a plane, attaching with bolts/nuts. I was solving this by creating a body with the common symmetry, then I would part refine that common part and I would start a second part on that part feature to add the differences of the first result-part and I would part-mirror the refined common part and do a third part to add the differences of the second result-part. By doing a refine I was losing any connection between the common part body and the two results, so that I could not modify them afterwards. So I felt the need of it. Now I realise that if I use autorefine, I can just start a first body with the common part. At a given feature, I can part-mirror that feature and start a second body from that result (without refining). I can then continue the first body with the non-common parts of the first half. Now if I modify anything before that feature where the common part stops, everything gets updated just fine. Maybe the end result tree is not the cleanest, however the functionality is there. I just wanted the functionality. Now, if after reading this you have any input for me, then we may see if we need a new feature or not. If we do not need it, we may well close this ticket. |
|
|
I just realized that I asked for a similar thing on the forum. https://forum.freecadweb.org/viewtopic.php?f=8&t=23144 |
|
|
Changed summary to replace "feature" with "tool" and better differentiate this ticket from 0002863. This one would not create a feature under an existing Body, but create a new mirrored Body linked to the original. |
|
|
An alternative to creating a new tool was discussed with @ickby in the topic linked in comment c9569: expand the existing ShapeBinder command to create a solid when the original selection is a solid, and to have the option to mirror the ShapeBinder copy along a standard datum plane. |
|
|
I've had a recent thought about this. It is currently possible to use a Body as Base Feature of another Body. This cannot be done directly, but through the Body's Base Feature property. This is a useful method to build variations of parts, see https://forum.freecadweb.org/viewtopic.php?f=20&t=33841#p288657 What if the Base Feature was expanded to have a mirror option? I'm not sure how that would work out. Maybe create a new menu entry for creating a base feature based on another Body, and open a dialog in the Tasks tab that allows different options: mirrored from a plane inside the new Body, or even scaled? I know that scaling is already possible through a Draft Clone, but this is clunky and messes the tree, as you need to create a new Body with the clone as base feature. |
|
|
This ticket has been migrated to GitHub as issue 5705. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-06-02 17:36 | Kunda1 | New Issue | |
| 2017-06-02 17:36 | Kunda1 | Issue generated from: 0002863 | |
| 2017-06-02 17:36 | Kunda1 | Relationship added | related to 0002863 |
| 2017-06-02 17:39 | Kunda1 | Description Updated | |
| 2017-06-02 17:39 | Kunda1 | Additional Information Updated | |
| 2017-06-17 23:31 | normandc | Note Added: 0009429 | |
| 2017-06-18 19:39 | Kunda1 | Note Added: 0009453 | |
| 2017-06-19 13:44 | abdullah | Note Added: 0009455 | |
| 2017-06-19 13:46 | abdullah | Note Edited: 0009455 | |
| 2017-06-28 05:11 | normandc | Note Added: 0009569 | |
| 2017-06-28 12:38 | Kunda1 | Reporter | Kunda1 => abdullah |
| 2017-06-28 12:40 | Kunda1 | Summary | Add Mirror body feature to PartDesign => Add Mirror body feature to PartDesign (continuation of 0002863) |
| 2017-07-01 05:59 | normandc | Summary | Add Mirror body feature to PartDesign (continuation of 0002863) => Add Mirror body tool to PartDesign |
| 2017-07-01 05:59 | normandc | Description Updated | |
| 2017-07-01 05:59 | normandc | Additional Information Updated | |
| 2017-07-01 05:59 | normandc | Note Added: 0009628 | |
| 2017-07-01 06:04 | normandc | Note Added: 0009629 | |
| 2019-02-24 16:17 | normandc | Note Added: 0012748 | |
| 2019-02-24 16:17 | normandc | Target Version | => 0.19 |
| 2021-02-06 06:43 | abdullah | Target Version | => 0.20 |
