These documents describe the design of “Parent” plugins designed to separate dialog data  collection from the rest of the code, storing the data in a Dictionary structure, and having the plugin processing routine  use only the data from the dictionary. The purpose of this is to allow “Child” plugins to create a matching Dictionary and call the Parent processing routine without needing to bring up a dialog, or to have to worry about global variables being used in the Parent processing routine.

These techniques are employed in cmdutils.plg to allow Parent plugins to extend the commands available to Execute Commands, without needing to update cmdutils for each new feature.

• On Hiding Dialogs in Plugins
• Parent-Child Plugins
• RunPluginEntry_cu and Parent-Child Plugins
• Plugins Designed to be Run by Other Plugins
• Using New macro-plugin to Generate a Custom Macro or Plugin
• Tutorial-Generating a Custom Macro using Add Text To Blank Page
• Tutorial-Generating a Custom Plugin that will create an Instrument Change
• Tutorial-Execute Commands cmdutils- Using RunPluginEntry_cu and Parent-Child Plugins