Forked PD tree

[kisolre]

Moving Tip up the PD tree and creating features there forks the tree:
.

ForkedPDtree.JPG (94.27 KiB) Viewed 1035 times

.

OS: Windows 8.1 Version 6.3 (Build 9600)
Word size of FreeCAD: 64-bit
Version: 0.20.27188 (Git)
Build type: Release
Branch: master
Hash: ad24b32fefe5a7be6afb9e238ab2eeee53d15170
Python version: 3.8.8
Qt version: 5.15.2
Coin version: 4.0.1
OCC version: 7.5.3
Locale: Bulgarian/Bulgaria (bg_BG)

[chrisb]

Yes, of course!

[GeneFC]

Wow!

"Forked tree" was the equivalent of "TNP" back in the old days. That is why the "Tip" concept was reinforced several years ago. At one time it was very easy to fork, now it only happens when the user specifically causes it.

What is your point?

Gene

[kisolre]

now it only happens when the user specifically causes it.

What is your point?

And you think I made that intentionally? Could you show a steps that will produce such result, because I cant think of such.
I was at Miirrored and wanted a chamfer. Decided to make it as early as possible so switched Tip to Pocket001. Created the chamfer but did not notice that it was created at the end of the tree instead after Pocket001. Then created the Hole sketch and feature which again appeared at the end of the tree. And when preparing for export I noticed that the slot was not there. But the Hole was the last feature and the Tip was there?!?!?

[kisolre]

Yes, of course!

Seriously? You would not expect the newly created features to be inserted between Pocket001 and Pocket002? Are we using the same program?

[GeneFC]

And you think I made that intentionally?

The "Tip" is the point in the tree that is exposed for new operations. When you change the tip you are changing the point where new features are added.

At one time merely selecting an element not at the end of the tree caused forking. Now it is necessary to specifically move the tip for that to happen.

You moved the tip.

Gene

[Shalmeneser]

Yes, of course!

Seriously? You would not expect the newly created features to be inserted between Pocket001 and Pocket002? Are we using the same program?

I was also expecting to insert the new tip function INSIDE the tree, not forking it.

[kisolre]

When you change the tip you are changing the point where new features are added.

They are not "added" there. They should be "inserted" there.
It does not mention forking here setting tip

[TheMarkster]

This looks like a bug to me. For each solid feature its BaseFeature property should always point to the previous feature in the tree. This is not the case with the uploaded file where Chamfer's BaseFeature property points to Pocket001 rather than the previous feature (Mirrored). The consequence of this is now Pocket002 and Mirrored are left out of the solid feature chain and are no longer part of the tip (Hole).

I have tried to reproduce the issue, but have been unable to do so.

[kisolre]

I also couldn't reproduce by trying to remember what I did exactly... Lets hope it pops again sometime since I move the tip around frequently...