Currently the most widely used version of InputMapper considered feature complete, however is being phased out in favor of InputMapper 1.7 which is more modern and stable and has less issues with Windows 10 and exclusive mode.
Some tweaks to macros make it possible for me to finally start filling out more triggers and commands, and some long awaited documentation makes it possible for those interested in playing around with c# to do the same!
First example of the new macro system, seems functioning so far but will keep an eye out for bugs. Now I need to create a bunch of triggers and commands that can be used in macros to make the system fully operational!
Also, there was a bug found in recent versions of the DirectInput device plugin that causes mouse to hitch, if you have noticed this when using the IM nightly build then disable this plugin and it should work fine again.
I discuss the most recent nightly build which is probibly one of the most stable and useable builds of 1.7 yet.
Framework for IM triggers mostly built, enough so that I can start working on the UI aspect to test macros and make changes as necessary. A big part of this is setting up the necessary framework to allow for late device arrival binding. What this means is if you make a macro that expects a specific controllers face button to activate it, it needs to be able to do so even if the referenced controller is not present at the time the macro is loaded into memory from the file when IM is launched. The trigger needs to detect late arrivals and test if the controller is the one it is interested in, and if it is then hook the appropriate events as needed.
Issues with the way Microsoft implements databinding and datacontext forced a unplanned re-design of the channel selection control. Figuring the best way to select items from a list would be Microsoft's very own list box with multi-selection turned on. Unfortunately though, for whatever reason, while Microsoft provides a .net control for multi selection, they offer no way to bind to the selection in a MVVM enviornment. Thanks M$... So I made my own, and after some hurdles it seems to be working well.