Skip to main content
Skip table of contents

(v13) D_GET_IDENTITY (PostScript device plugins)

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

D_GET_IDENTITY Selector

Parameter: IdentityParam *param

Call type: Single‐call

This is the first call any plugin receives from the RIP, and it determines the type of plugin: input, out‐ put or PSDEV, and allows the plugin to decide if it will run with the supplied version of the plugin interface. You must support this selector for PSDEVs otherwise the plugin will be assumed to be an output plugin.

Note: Any other kind of plugin introduced in the future will also be identified using this call.

Plugins should be compiled for the earliest version of the RIP in which they can run. For example, a new field is added to DEVICETYPE and the plugin tried to set the new field, for older versions of the RIP that do not have such a field, the plugin would be setting invalid memory. The fVersionOK field is used to inform the RIP whether the plugin can run with a given version of the RIP. See fVersionOK below for more details.

version

The field should be ignored.

pluginType

The PSDEV plugin should set this field to PT_POSTSCRIPT .

protocolVersion

This field allows for changes to the way in which plugins are accessed in the future while still sup‐ porting existing ones.

pluginInterfaceMajorVersion and pluginInterfaceMinorVersion

These fields are set by the RIP to specify the major and minor plugin interface version numbers, respectively. Version 17.0 was the first plugin interface version for PSDEVs.

fVersionOK

If the plugin can run with the given version of the RIP, this field should be set to TRUE . If this field is set to FALSE , further loading or use of the plugin is prevented.

The CHECK_VERSION macro is provided to simplify this:

p->fVersionOK = CHECK_VERSION (p, 18, 11);

This says that the plugin runs with any RIP containing plugin interface version 18.11or higher.

JavaScript errors detected

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

If this problem persists, please contact our support.