Skip to main content
Skip table of contents

(v13) Getting multiple-device plugin configuration and capability data

This page applies to Harlequin v13.1r0 and later; and to Harlequin MultiRIP but not Harlequin Core

The RIP needs to know about the device or family of devices a plugin supports. This information is retrieved from a single‐device plugin simply enough, using the D_CAPABILITIES selector. See (v13) D_CAPABILITIES .

Multiple‐device plugins support an indeterminate number of devices. The RIP uses the D_FIND_DEVICE_TYPE selector  for multiple‐device  plugins.  See (v13) D_FIND_DEVICE_TYPE .

The RIP also asks plugins to declare the raster data formats each device accepts, with the selector D_GET_RASTER_FORMAT . If it is a multiple‐device plugin, the RIP keeps calling D_GET_RASTER_FORMAT until the plugin has told it about acceptable raster formats for all the devices supported. See (v13) D_GET_RASTER_FORMAT .

Once everything is set up, the RIP usually uses the D_SELECT_DEVICE selector to tell the plugin which of its instantiated devices subsequent calls to D_OPEN , D_OUTPUT , D_IDLE , D_CLOSE , D_WAIT_ON_CLOSE , D_OPEN_ENDJOB , D_CLOSE_ENDJOB , D_ERROR_ICON and D_ERROR_TEXT will refer to. The plugin must maintain a record of this “current OUTPUT device” so that subsequent calls refer to the correct device.

This should not be confused with the “device currently being configured”, which should be deter‐ mined and saved separately, during the D_GETDLGDEFN call. In the example plugins, this is obtained by the use of the deviceFlags[1] value in the HqnDeviceCapabilities structure. For more information see: (v13) D_GETDLGDEFN , (v13) D_GETDOOBRIS , and (v13) D_GETSTRING .

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.