Skip to main content
Skip table of contents


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


Parameter: devHCPPlusSecurityParam * HCPPlusSecurityParam

These calls are included for backward compatibility. This call has been unavailable. Current plugins use (v13) D_GEN_SECURITY_NAME .

The RIP calls this selector to determine whether the following HCPS (color management) options are enabled for the current single‐device plugin, or the current device of a multiple‐device plugin:

  • Harlequin Full Color System (HFCS)
  • Harlequin Standard Color System (HSCS)
  • Harlequin ICC Profile Processor (HIPP)

If this selector is not implemented, no device limited color management options are supported.

If this selector returns NOERR then device‐limited HCPS options are allowed, and a device descriptor must be returned using the parameter described here:

    typedef struct devHCPPlusSecurityParam {
      uint8 atbzOEMName [HCPPLUS_SECURITY_STRLEN]; uint8 atbzPluginName[HCPPLUS_SECURITY_STRLEN]; uint8 atbzDeviceName[HCPPLUS_SECURITY_STRLEN];
    } devHCPPlusSecurityParam;

Each distinct value of the device descriptor produces a separate HCPS entry, visible in the Extras dialog box in the RIP and requiring a password to enable a particular HCPS option for use with it. This may become unworkable with a large number of plugins and devices. Alternatively, by choosing appropriate (shared) values for the names described in atbzOEMName through atbzDeviceName, you can produce groupings of plugins, devices, or both; all represented by one HCPS entry. For example, one possible grouping might relate to all uses of a printer with a particular type of output media.

However, you choose the names, you must declare all the names to Global Graphics so that suitable passwords can be supplied.


The plugin should copy the OEM name into this string. (This string does not appear in the Extras dialog box.)


To create a unique HCPS entry for each plugin, the plugin should copy its own name into this string. To create a HCPS entry that groups related plugins, the plugin should enter a more generic shared name.


To create a unique HCPS entry for each device, the plugin should copy the device name (or the cur‐ rent device name for a multiple‐device plugin) into this string. To create a HCPS entry that groups related devices, the plugin should enter a more generic shared name.

Enabling options in the Extras dialog box

For each single‐device plugin, or for each ʹlogicalʹ device configured in the Device Manager for a mul‐ tiple‐device plugin, a new device entry appears in the Extras dialog box accessed from the Configure RIP dialog box. This entry takes the general form:

HCPS <Plug-in Name>, <Device Name> [<option>]

The <Plug-in Name> and the <Device Name> are the values of atbzPluginName and atbzDeviceName , respectively. The OEM name is omitted from the entry for space reasons. If the option is not enabled,

<option> is an empty string (so just [] appears).

If the user adds the feature then the RIP prompts the user for a password, as with other Extras features. The RIP then sets <option> to one of HIPP , HSCS , or HFCS depending on which feature the given password enables.

Note: The option is not displayed as “enabled” until the password is checked. The user must exit and re‐enter both the Configure RIP and the Extras dialog box to see the updated status.

JavaScript errors detected

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

If this problem persists, please contact our support.