Plugin Control flow

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

It is inappropriate to code an event‐processing loop within a plugin, because the RIP is the main pro‐ gram. Only dialogs controlled from the RIP's event loop can be handled properly in the plugin itself, though cooperation with another process, which is managing dialogs with its own event loop, is possible if required.

It is possible to display message boxes and the like directly from the plugin in debug versions of the plugin: this may be useful if timing constraints make using a symbolic debugger difficult. However, for production code, use the RIP facilities provided.