Reply to thread

It sure is possible but it sounds like a major pain. If a user has a dependency on a plug-in that's not being supported anymore she can stick to an older version of MP1.

Could you get it to work? You would need to use the same SharpLibHid version that's used by the MP version you are targeting.

MP1.15 is using SharpLibHid v1.3.1.

It does not need to. However ideally plug-in should not have to deal with key handling themselves.

Here is the way it should be done:

• Have a framework that let plug-ins publish their own actions.
• Plug-ins actions can then be mapped to keys much like built-in actions.
• Plug-ins can then handle actions rather than keys.

Until this is done however you should use SharpLibHid.