-
Notifications
You must be signed in to change notification settings - Fork 192
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
saveas() error: AssertionError: dictionary handle not resolved #833
Comments
I need the test data to help (upload as zip-archive). |
This is a complex DXF file created by a 3rd party application and also contains some errors: Autodesk DWG Trueview 2023 can't open the file:
BricsCAD can open the file, but the
Ezdxf can read the file but isn't able to fix all issues and re-saving the file raises an exception:
For such files you will always have to use the from ezdxf import recover
doc, auditor = recover.readfile("your.dxf")
auditor.print_fixed_errors()
auditor.print_error_report() But that doesn't work for this example. I will try to extend the ezdxf auditor to process this file, but the problem is difficult to debug due to the size of the DXF file (183MB). You can't do anything now, you have to wait for the release of the next version of ezdxf. |
@mozman Thank you very much for your help, I understand this is my dxf file has error, I will get the dwg file using AUTOCAD to convert and retest. Thank you again for your time. |
Check if every entity is the entity that is stored for this handle in the entity database. This can happen if the same handle is assigned multiple times to different entities.
The application you are using is VERY bad and assigns the same handle for multiple entities - which is an absolute NO GO, every entity handle in a DXF document has to be unique. Ezdxf removes entities with duplicate handles from the OBJECTS section and can export your example file, that now can be opened by TrueView 2023. But some data is lost, ezdxf maybe deleted important data. You can not trust this exported DXF file and you should not trust that application you use! |
@mozman |
The text was updated successfully, but these errors were encountered: