DXF Limitations
DXF Limitations
The principle limitations of the DXFCVT converter are summarised as follows:
- DXF files must be in plain ASCII. The converter does not support the DXB binary file format.
- Three-dimensional DXF drawings are flattened to two-dimensions ('plan' view) by the converter as Proteus only supports two dimensions.
- The entities (alone or as part of a BLOCK entity) supported are the BLOCK, LINE, SPLINE, POLYLINE, LWPOLYLINE, ELLIPSE, CIRCLE, ARC, TEXT, SOLID, TRACE, and INSERT entities. All other entities are ignored and do not affect file conversion. The SOLID and TRACE entities are converted to unfilled three or four sided polygons. In particular, the DIMENSION entity is not supported.
- Only those attributes of an entity that can be honoured by the layout module are converted. Thus text attributes such as font face, weight (boldness) and italic slope angle are discarded and do not affect the file conversion.
Other minor limitations include:
- Quadratic Bezier curves (1 per quadrant) are used to represent ARCS and ELLIPSES, resulting in a small inaccuracy. This is the behaviour of the default Quadrant arc mode; setting Arcs to Linearised on the dialogue form instead approximates each arc with straight line segments, to the accuracy given by the Tolerance field.
- Line types (dots, dashes, thicknesses, etc.) are lost. All lines are converted to the standard graphics line width.
- Colours are lost: all converted entities are displayed in a colour appropriate to the layer they are on.
- Text styles (from the DXF TABLES section) are ignored. The converter relies (for those attributes it converts, such as rotation, mirroring, etc.) on these attributes being specified as part of the TEXT entity, which is the norm.
- The conversion of DXF TEXT entities drawn in a proportional text style will convert to a fixed-pitch font on the layout where the width of the characters may result in the overall length of the string in the layout being different to the overall length of the string in the DXF drawing. This may then lead to alignment problems unless the user has made judicious use of the DXF text alignment flags (e.g. text that is specified as fitting between two points). As the Proteus text primitive is limited to fixed-pitch characters which only allows for the specification of a character height and character width for the text string, the only way around this problem would be to adjust the layout character width such that the number of characters in the string multiplied by the adjusted character width is the same as the overall length of the string in the DXF file. Unfortunately, except for certain justifications, the DXF file does not contain the overall string length and so this isn't possible. The actual behaviour of the converter is to calculate the character height as being equal to the height of the DXF TEXT entity and the character width as being equal to the TEXT entity height scaled by the TEXT entity's x-scaling factor (the latter defaults to 1.0).
- The following text attributes and properties are not converted:
- Obliquing angle (for italics).
- Styles. All text is in the layout's fixed-pitch vector font.
- Control characters. These occur in the DXF file as a caret followed by an ASCII character; all such characters in the string are preserved.
- The following text attributes and properties are converted:
- Rotation.
- X and Y mirroring.
- Justification, except attribute '5' ("Text is fit [sic] between two points (width varies)") as it is ambiguous and hasn't been tested.
- Only the following entities are converted, as noted:
- LINE and 3DLINE entities.
- CIRCLE entities.
- ARC entities (by default, by using bezier quadrant arcs).
- SOLID, TRACE and 3DFACE entities are converted to unfilled three or four sided polygons. The 'hidden' attribute of 3DFACEs is not honoured.
- TEXT entities are converted as described above.
- BLOCK entities.
- INSERT entities are converted but any associated ATTRIB entities are discarded, so text declared in the INSERT via an ATTDEF entity is lost.
- LWPOLYLINE and POLYLINE with associated VERTEX entities. All polylines are assumed to be continuous (i.e. not a mesh) and all VERTEX entities are assumed to be single point or a bulge.
- ELLIPSE using bezier quadrant arcs.
- SPLINE entities are only supported if they are non-rational (weighting is 1) and or degree 3 or lower. Fit points are not supported.
- In addition to the above some other omissions are:
- DIMENSION entities. These are usually exported as LINE, SOLID and TEXT entities as well, so there should be no loss of visible information.
- ATTRIB and ATTDEF entities, as outlined above.
- SHAPE entities.
- If the DXF file does not specify the units it is the user's responsibility to specify the scaling parameters (via the appropriate options on the dialogue form) scale the dimensions to 1th. Positive angles are assumed to be measured in degrees counter-clockwise from an implied zero axis corresponding to the positive x-axis. The necessary DXF file header variables are checked and a warning issued if this is not the case.
Layer names are honoured throughout the conversion, with the layer name "0" (the single character zero) being taken to have the layer name of its parent. For example, for a BLOCK object with entities on layers 0, BLUE and GREEN and an INSERT of the BLOCK on layer RED, the BLOCK entities on layer 0 are deemed to be on layer RED. Which entities within a BLOCK are output is determined by which layers are enabled and by the settings chosen under the Symbol Mode group on the dialogue form.
See Also: