Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following two examples show one possible mapping between a duplex unit feature as described in a PPD file and its counterpart in the GDL file. This first example is an excerpt from the PPD file.
*OpenUI *DuplexUnit: Boolean
*DefaultDuplexUnit: True
*DuplexUnit True/Installed: ""
*DuplexUnit False/Not Installed: ""
*?DuplexUnit: "
save
currentpagedevice /Duplex known
{(True)}{(False)}ifelse = flush
restore
"
*End
*CloseUI: *DuplexUnit
The next example is an excerpt from the GDL file, and shows the DuplexUnit feature definition that corresponds to the duplex unit feature in the preceding example.
*Feature: DuplexUnit
{
*FeatureType: PRINTER_PROPERTY
*% *BidiQuery and *BidiResponse constructs must have the same names
*BidiQuery: DuplexUnit
{
*QueryString: "\Printer.Configuration.DuplexUnit:Installed"
}
*BidiResponse: DuplexUnit
{
*ResponseType: BIDI_BOOL
*ResponseData: ENUM_OPTION (DuplexUnit)
}
*Option: False
{
*BidiValue: BOOL(FALSE)
}
*Option: True
{
*BidiValue: BOOL(TRUE)
}
}