-
Notifications
You must be signed in to change notification settings - Fork 46
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
Comments
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. |
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? |
I just compiled your last commit and the dialog is still hanging. |
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. |
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. |
*[PartDesign] Add Q_DECLARE_TR_FUNCTIONS to ViewProviderDatum. *[PartDesign] Small fix for ViewProviderDatum::attach translation
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.
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.
The text was updated successfully, but these errors were encountered: