CGM Export Options

For information on how to use Help, press F1 or choose Using Help from the Help menu.

The Export Options dialog allows you to specify options which determine how information in the file is exported.

When exporting, the application specifies coordinates in Virtual Device Coordinate (VDC) units, with each VDC unit corresponding to 0.001 inch.

The Defaults button sets all buttons and/or checkboxes to default conditions.

Text can be exported as CGM polygons (All text as polygons checked), or as CGM text (All text as polygons unchecked).

General Messages

CGM-specific Messages

Macro Script Options


Macro Script Options

Since the Export Options dialog isn't displayed when the program is driven from a macro command script (via GS Scripter or Visual Basic), an Options="..." string can be specified in the script.  The string consists of comma-separated parameters, which specify the behavior of the various export options.  An typical example would be:

...(File="contour.cgm",Options="Defaults=1")

This would set all export options to their default values,  and specify the CGM file (contour.cgm) as the output file.

Option	Action	Default
Defaults=1	Set all options to their default values	No
ForgetOptions=1	Don't remember options for later use	No
AllTextToPolygons=1	All text converted to polygons	Yes


CGM-specific Messages

The following messages may appear while exporting CGM files.

Cant swap odd number of bytes

Cant swap odd number of words

Too many vertices


 Cant swap odd number of bytes

CGM metafile format has a word defined as the higher-order byte first, while the outprocessor writes files in the Intel 80x86 format, in which the lower-order byte of the word appears in the file first. It is necessary to swap the bytes of each word before writing it out to a CGM file.  Since it swaps each pair of adjacent bytes, the total number of bytes to swap must be an even number.


 Cant swap odd number of words

CGM metafile format has a floating point value defined as the higher-order word first, while the outprocessor writes files in the Intel 80x86 format, in which the lower-order word of the floating point value appears in the file first. It is necessary to swap the words of each floating point value before writing it out to a CGM file.  Since it swaps each pair of adjacent words, the total number of words to swap must be an even number.


 Too many vertices

There are too many vertices to be packed in a 64K-byte record in the CGM file. The vertices will be truncated to fit in 64K bytes.


General Messages

The following messages may appear while exporting files in any format.

Can't load Output Processor resource

Coordinate conversion error

Could not create the Output Device Context

Error opening the export file

Error reading Output Processor profile information

Error while writing to export file

Internal inconsistency in Output Processor

Invalid Output Device Context handle

Invalid Output Processor caller instance handle

No pushed ODC to pop

ODC has no associated Windows DC

Out of global memory

Out of local memory

Output Processor can't create a BeginPaint ODC

Output Processor can't create a Bitmap ODC

Output Processor can't create a Metafile ODC

Output Processor can't create a Printer ODC

Output Processor can't create a Window ODC

Output Processor doesn't support GSODevToLog

Output Processor doesn't support GSOGetOutputCaps

Output Processor doesn't support GSOLogToDev

Output Processor doesn't support GSOSet/GetViewport

Output Processor passed bad parameter

Unknown fill pattern type


Can't load Output Processor resource

Free memory may be exhausted, or memory contents are corrupted.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Coordinate conversion error

The program has detected an internal error.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Could not create the Output Device Context

Free memory may be exhausted, or memory contents are corrupted.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Error opening the export file

The file you specified cannot be created or modified.  Make sure there is ample free space on the output device and you have the proper file access permissions.


Error reading Output Processor profile information

Information stored in the application's .INI file could not be located.  If the .INI file is corrupted, you will need to restore a backup copy or, possibly, reinstall the stoftware.  You should probably check with Technical Support before proceeding.


Error while writing to export file

Make sure there is ample free space on the output device and you have the proper file access permissions.  It is also possible that free memory may be exhausted, or memory contents are corrupted.  Close all active applications and restart Windows.


Internal inconsistency in Output Processor

The program has detected an internal error.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Invalid Output Device Context handle

The program has detected an internal error.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Invalid Output Processor caller instance handle

The program has detected an internal error.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


No pushed ODC to pop

The program has detected an internal error.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


ODC has no associated Windows DC

The program has detected an internal error.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Out of global memory

Free memory may be exhausted, or memory contents are corrupted.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Out of local memory

Free memory may be exhausted, or memory contents are corrupted.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Output Processor can't create a BeginPaint ODC

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor can't create a Bitmap ODC

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor can't create a Metafile ODC

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor can't create a Printer ODC

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor can't create a Window ODC

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor doesn't support GSODevToLog

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor doesn't support GSOGetOutputCaps

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor doesn't support GSOLogToDev

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor doesn't support GSOSet/GetViewport

The application has requested the Output Processor DLL perform an unsupported operation.  This is probably indicative of an internal error.  Close the application, then restart it.  If this problem persists, contact Technical Support.


Output Processor passed bad parameter

The program has detected an internal error.  Close all active applications and restart Windows.  Please report this situation to Technical Support.


Unknown fill pattern type

The application has requested that the Output Processor DLL fill the interior of an object with a pattern the Output Processor doesn't support.  Choose a different fill pattern.