Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

toponaming issue PartDesignExample #32

Closed
dulouie opened this issue May 12, 2020 · 5 comments
Closed

toponaming issue PartDesignExample #32

dulouie opened this issue May 12, 2020 · 5 comments

Comments

@dulouie
Copy link

dulouie commented May 12, 2020

Hey, I tested your toponaming algorithm a little harder today. I'm really pleased with the results. So I can use your branch for my important stuff right now. Just stupid construction with sketches on surfaces :)

But I noticed a bug.

  1. open the PartDesignExample file from the FreeCAD start screen
  2. open the Sketch of the Pad
  3. draw an additional circle in the middle of the tower
  4. unfortunately, the moat (Pocket) has now jumped to the bottom

I have worked out a workaround:
First put the tip on the pad and draw the circle. Then set the
the tip back to pocket002.
The moat has stayed in the right place this time.

@realthunder
Copy link
Owner

This is not really a bug per se. It is caused by the fact that you are opening a legacy document, hence no topo name there yet. Those names are only generated after recomputation. Therefore, editing the model before any recomputation may give you the same problem as in upstream. I just added a commit to prompt the user for recomputation upon opening a legacy document.

@dulouie
Copy link
Author

dulouie commented May 13, 2020

All right, at first I thought that old files didn't work, but then I read the "auto-generated element name" messages and was impressed. So maybe old corrupted files can be repaired?

@dulouie
Copy link
Author

dulouie commented May 13, 2020

I just compiled your last commit and the dialog is still hanging.

realthunder added a commit that referenced this issue May 13, 2020
@realthunder
Copy link
Owner

Should be fixed now. I have also changed the 'auto-generated element name' warning message to 'Pending recompute...', because the name is not really generated on restore. It is only that the object is marked for recompute.

@dulouie
Copy link
Author

dulouie commented May 13, 2020

It works perfectly. Meanwhile, I use your branch for my big stuff. If I find any faults, I report them immediately. Besides, I'm already totally excited about the upcoming multibody properties.

@dulouie dulouie closed this as completed May 14, 2020
realthunder pushed a commit that referenced this issue May 6, 2022
*[PartDesign] Add Q_DECLARE_TR_FUNCTIONS to ViewProviderDatum.

*[PartDesign] Small fix for ViewProviderDatum::attach translation
@yahbluez yahbluez mentioned this issue Jan 18, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants