Plugins Preset Loaded Triggers

• Fixed compatibility issues with VaM 1.21 and 1.20; now requires 1.20 or newer instead of the latest (1.22)
• Some very minor tweaks in the UI (as a result of updating the source files to depend on my custom "common library" for general plugins)

Added a Delay slider to the triggers panel UI.

The delay is specific to the trigger type, all actions in the trigger get the same delay.

Added a setting "Wait until targets found" with a customizable timeout:

The idea with this is that plugins like Naturalis which take some time to initialize and don't create their triggerable parameters immediately can still be stored in the same preset or scene with Preset Loaded Triggers, and the trigger actions targeting the plugin will be correctly restored when the targeted parameters (Receiver Targets) are eventually found. Any preset load events that fire will also wait until the targets are found before executing the trigger actions. (In the case of Naturalis, the parameters were available in about 0.7 seconds in my testing.)

Thanks to @xadamadax for the testing/feedback!

• "Preset" button is now named "General Preset"
• hide plugin UI in the background when trigger panel UI is open (cleaner look)

Triggers created for general presets work a bit differently from the rest. A general preset stores the currently loaded plugin files if Appearance is checked, and it also stores the parameters of currently loaded plugins regardless of what is checked, and those parameters then get loaded when the general preset is loaded if the plugin is currently present on the atom. In the case of this plugin, the triggers that you create are saved regardless of which of Appearance, Physical or Pose is checked. So, it's a bit complicated. But the point is mainly that triggering something when a general preset is loaded will actually use the triggers that are saved in the general preset file itself, rather than the currently defined triggers. This allows you to "inject" this plugin into general presets so that loading those presets causes some side effects via the triggers defined in the preset. Creating trigger actions for when a plugin preset is loaded should work similarly.