(v13) Input plugin startup call sequence

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

The initialization sequence for an input plugin involves the following selector calls:

1. � D_SELECTOR_SUPPORT
This may be called at various times to ascertain whether or not some other selector is supported by the plugin. See (v13) D_SELECTOR_SUPPORT (input plugin) .
2. � D_GET_IDENTITY .
   This call identifies the type of the plugin. See (v13) D_GET_IDENTITY (input plugin) .
3. � D_GEN_BOOT .
   This call allows the plugin to tell the RIP how much memory should be allocated for it. See (v13) D_GEN_BOOT .
4. � D_IP_PLUGIN_INITIALISE .
   This call allows the plugin to set up any initial state information it needs. See (v13) D_IP_PLUGIN_INITIALISE .
5. � D_SECURITY
This call allows the plugin to verify that it can work with this copy of the RIP and with the dongle attached. See (v13) D_SECURITY (input plugin) .
6. � D_IP_GET_CHANNEL_CLASS_DESCRIPTIONS .
   This call allows the plugin to describe the channel classes it supports. It describes one channel class per call. The RIP calls the selector repeatedly until the plugin indicates that it has sent descriptions for all the channel classes it supports. See (v13) D_IP_GET_CHANNEL_CLASS_DESCRIPTIONS .

Any time after the D_IP_GET_CHANNEL_CLASS_DESCRIPTIONS calls, the RIP can obtain the dynamic dialog information necessary for interaction with the user. Any such calls can be interleaved with channel creation calls and should not affect them.