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: int32 * devdefversion

Note: The spelling of D_INITIALISE is the British English rather than the U.S. English spelling.

D_INITIALISE is the second selector called by the RIP (following D_GET_IDENTITY ) after loading the plugin. The implementation should initialize any data the plugin requires in order to work.

The plugin is also expected to locate any output hardware it is associated with during this call. It should report the hardware's condition, by setting d_error appropriately, so that if there is a problem the RIP can generate a warning dialog.

If no hardware or software resource exists, the plugin can either return the error code ‐1, or report an error condition. If the plugin returns ‐1, the RIP ignores it thereafter. If the plugin reports an error condition, the RIP takes appropriate action. See (v13) Error Handling in Output Plugins .

At startup, the RIP attempts to initialize all the plugins it knows about, to check which of them are available. (Some might not be for example, a plugin might have to consider itself unavailable for the RIP's use if its output hardware is disconnected.) Therefore, to keep startup time within acceptable limits, plugins should defer time‐consuming operations until later on.

Note: D_INITIALISE should return ‐1 if the parameter sent to it is NULL . This is a security requirement: normally, the argument is a pointer to the now obsolete version number of the deviceDefinition structure.

If the plugin is to use plugin library functions (such as for RIP Monitor messaging for example), it should call PluginLibInitialise() here. See (v13) PluginLibInitialise .

JavaScript errors detected

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

If this problem persists, please contact our support.