WhiteMagic

Attempting to interrupt macros via `terminate_macro` is futile as it won't do that. All it does is remove macros that are repeatedly running, i.e. repeat, toggle, hold, etc. from the...

1. I'm very hesitant on that front, the vJoy version that this is based on (njz3) is known to cause grief and I would need to know what it actually...

You should be able to make use of the `is_active` signal (https://github.com/WhiteMagic/JoystickGremlin/blob/d740f59c83bd59a1900658e0e7d98000841fd32e/gremlin/event_handler.py#L344). Alternatively you could always add a low-frequency Timer/Thread that simply checks if the code runner is active.

Not opposed to having callbacks on more events, it's actually one of the items I have on the list #551. But it needs to be quite general such that adding...

With regards to the first issue, I can't say what causes this as behind the scenes there is no difference between a "Map to Keyboard" action and a "Macro" action...

The underlying issue with this appears to be the fact that the map to keyboard action executes the release in the same order as the press, i.e. if an input...

That shouldn't even be needed, I just have to implement it in the sensible order. There is no good reason I could think of that would benefit from the order...

Re-implementation of this action for R14 fixes this particular issue with commit 7a0cf3e28c8f88a2304777c9fe05c7e4861ff532.

While I can technically change this for R14 I am quite hesitant to do so as whatever high-precision I choose will be too much or too little in some cases,...

I don't really see how Gremlin could cause this. The only aspect of it that interfaces with physical hardware is dill, which only receives DirectInput events and forwards those to...