The intended appearance of lines and regions can be dependent on many seemingly obscure settings in the header of the DXF file. Sometimes the correct interpretation of a DXF file can be very difficult. One program might place the objects on different layers of the drawing, while another might use different pen colors, while a third might use named "blocks" to group the data.Īlthough DXF is widely used for the exchange of simple line data, an application designer wishing to support DXF must consider that AutoCAD can store these many types of data in different ways.
So basically, it is the same old story: the documentation is incomplete, there are various incompatible licensing issues that have to be sorted out, & even if these issues could somehow be resolved to the satisfaction of all involved there is still no guarantee the import or export process would work as seamlessly as users would expect.ĭXF also allows a perplexing number of ways of doing nearly the same thing, such as describing objects as separate editable groups. For these reasons many CAD applications use the DWG format which can be licensed from Autodesk or non-natively from the Open Design Alliance.ĭXF coordinates are always without dimensions so that the reader or user needs to know the drawing unit or has to extract it from the textual comments in the sheets. Other object types, including AutoCAD 2006's dynamic blocks, and all of the objects specific to the vertical market versions of AutoCAD, are partially documented, but not well enough to allow other developers to support them. Certain object types, including ACIS solids and regions, are not documented. As AutoCAD has become more powerful, supporting more complex object types, DXF has become less useful.
0 kommentar(er)
