Failed to read old DXF file about dxf HOT 4 CLOSED

Thanks for attaching a file, this made investigations much easier.

In 0.3.1 I have some bugs with reading extension data that I've recently been working on and you're hitting with this file, but haven't quite finalized this release yet. If you can take a source dependency and build locally (instead of the NuGet package), the autocad-compat branch contains a lot of fixes for compatibility issues I had between AutoCAD and this library and I've confirmed that I can open your file with this branch.

from dxf.

I've built a custom version already (based on 0.2) that was working
flawlessly. I think.. hope, that version is sufficient for 99% use cases.

I can only update if updates are stable (no offense), since we're close
to release. No need to press additional functionality, if you're not ready.

Am 12.01.2016 um 19:34 schrieb Brett Forsgren:

Thanks for attaching a file, this made investigations much easier.

In 0.3.1 I have some bugs with reading extension data that I've
recently been working on and you're hitting with this file, but
haven't quite finalized this release yet. If you can take a source
dependency and build locally (instead of the NuGet package), the
|autocad-compat| https://github.com/IxMilia/Dxf/tree/autocad-compat
branch contains a lot of fixes for compatibility issues I had between
AutoCAD and this library and I've confirmed that I can open your file
with this branch.

—
Reply to this email directly or view it on GitHub
#56 (comment).

from dxf.

No offense taken, I understand the need for stability. That being said, if your custom version based off of 0.2 is working then I'd stay with that as I'm not yet ready to declare the autocad-compat branch ready to merge into master yet.

On a related note, if you're willing to share I'd like to see/merge your changes if I haven't already addressed the issues in the autocad-compat branch, but I also understand if you'd like to keep your changes private for either personal or business reasons.

from dxf.

I didn't have any changes, I just pulled your latest version including
fixes for one of my earlier problems - you just didn't publish a nuget,
that's why I built my own. Currently, I have no need for extended
functionality - this may change in the future, when customers start
loading strange files :) The file attached to this report is a standard
use case for us. As long as no special use cases arise, I'll stay with
my self-built version. From time to time, I'll follow your releases,
evaluate and check back.

Am 12.01.2016 um 20:25 schrieb Brett Forsgren:

No offense taken, I understand the need for stability. That being
said, if your custom version based off of 0.2 is working then I'd stay
with that as I'm not yet ready to declare the |autocad-compat| branch
ready to merge into |master| yet.

On a related note, if you're willing to share I'd like to see/merge
your changes if I haven't already addressed the issues in the
|autocad-compat| branch, but I also understand if you'd like to keep
your changes private for either personal or business reasons.

—
Reply to this email directly or view it on GitHub
#56 (comment).

from dxf.