Hey Timothy,

have gotten several reports from user that use my PlugIns. Its seems that GSE 2.0 is not recognizing external plugins and thus the macros are not available, even though the GSE Core, Converter and the Plugin are loaded.

I have been able to reproduce the issue, with my Paladin PlugIn but the Hunter one seemed to work. Now reports coming in that they have the same issue on the Hunter Plugin.

When downdraded to GSE 1.5, everything works as usual and all PlugIns are recogniozed.

Could you please look into this?

Thanks

Hiro

This is a long response to a simple question.

The entire macro language and storage system is different in GSE2 than it was in GSE1. The plugin spec has changed but I didn't get it finalised with 7.1.5 breaking more things than anticipated. GSE2 includes a module called GSE Legacy Adaptor - this provides a bridge between GSE1 plugins and GSE2. None of the methods or controls from GSE1 are carried over to GSE2. Even the language and macro specification is different.

In GSE2's conventions a plugin does a a one time import into the users library. Any changes in the files post that import are not detected unless the user goes back to the Plugins button and reimports everything or the Plugin Author performs some checks and makes specific changes. For example the user may update the macro in place or detect if there are any changes and then either add a new version or a completely new macro and control how they advise the user of the changes. They could store their macros in an encrypted format and decrypt as they are being reloaded. The other parts to this that aren't in place yet are for macro authors to disable people sharing their macros in game, editing them or exporting them. None of these things are possible within the old GSE API. The whole aim is to give the plugin author a lot more control over how they update.

The first part of this is the updated GSE Reference Plugin - https://github.com/TimothyLuke/GnomeSequencer-Enhanced/tree/master/PluginShell

I still need to work on this in the next day or so so I can get this in a proven method via the HP Macro set. It works for the initial plugin and reloading by the user but it doesn't work to identify that the plugin has been updated yet. This has been of less a priority than getting the bugs people had with importing, running and editing out of the way.