-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Undocumented flag in DXF layer after dwg2dxf #1077
Comments
@vagran Do you have some example DWG file? |
Unfortunately, I see this issue with our customer proprietary file, which I cannot share. |
@vagran ok. AC1015, LAYER table, and something with xref.
To see your version of the layer settings. |
@vagran And do you export to AC1015 DXF? |
I do not specify any options for |
BTW isn't this just an obvious bug in the source code:
Comment (which is taken from the specification) does not match the bits set for |
@vagran Ah ok. You have AC1032 DWG file. |
Yes, maybe. I need to check. |
I created some fixes to LAYER table: #1078 |
@vagran Could you test fixes in master branch? |
I tried to test it. It crashes with
The corresponding code looks quite bad: Line 1282 in 203edc0
Besides the questionable decision to use static variables, it increments the pointer, which is freed two lines below. Regarding the layer, it now looks like this:
Group 70 is 0. Is it supposed to be zero now? If it was 8 before, should it become 16? Or the flag itself also was wrong? |
I think yes.
This mean without xref. |
@rurban I have output of dwgread in the way:
How to prevent printing these new flags by logging in Free section of output? |
#ifndef IS_FREE |
Hello,
After converting my DWG file using
dwg2dxf
utility, I have flag8
set in one of my layers flags (group 70). This value is not described in the DXF specification. Looking through thelibredwg
source code I have discovered this place:libredwg/src/dwg.spec
Line 3788 in 56d392a
I do not really aware of this macro-based syntax, but this place looks suspicious, and probably does not correspond to its preceding comment which cites flag values from DXF docs, also not mentioning value
8
. Maybe it should be changed like this:The text was updated successfully, but these errors were encountered: