-
Notifications
You must be signed in to change notification settings - Fork 75
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
Editing part information #492
Comments
yeah I know, PartInfo and BOM are broken. I hoped that someone would come up with a good solution, but they all bring some personal solution. I'll bring back my old limited code. What fields do you think should a PartInfo have ? My suggestion currently is:
These should be filled by the designer. Additionally, I thought about adding following fields that are filled by the software :
These are easy for Bodies (links-to bodies) but more difficult for Parts (and therefore sub-assemblies) |
Got a similar problem. Actually, I get a truncated BOM with the BOM workbench, it lacks any field apart from Number, Qty, Label, Description and File information. To be fair, I haven't typed in any PartInfo whatsoever. I worked with bodies, sketches and padding and created an assembly out of it. IMO a BOM should just take the measurements of the bodies/parts and sum it up (if that only was so easy...). Also most PartInfo can be autofilled if not specified: Name = Name of body, of file etc. Author = name of user. Material = no autofill (not necessary for simple woodworking). That said, using the generic BOM function of Assembly4 doesn't work at all here. Latest versions on linux.
|
When trying to edit the part information fields I get the following error:
12:58:23 Traceback (most recent call last): File "C:\Users\Electromuis\AppData\Roaming\FreeCAD\Mod\Assembly4\.\infoPartCmd.py", line 594, in accept for prop in infoPartCmd.partInfo: <class 'AttributeError'>: type object 'infoPartCmd' has no attribute 'partInfo'
Assembly 4 version: 0.50.12
FreeCAD version: 0.21.2
The text was updated successfully, but these errors were encountered: