Details

Written by Wobbles

Created: 17 May 2017

Hits: 1695

I wanted to do an in-depth video this week to celebrate our 3rd anniversery, but a failed NAS and my workstation on round-the-clock data reconstruction and recovery duty for the past 3 days has kept that from happening. So instead I taking the time to hammer some stuff out on the KB once again.

Read more: Check In: May 17 2017 (Happy 3rd Anniversary InputMapper)

Details

Written by Wobbles

Created: 10 May 2017

Hits: 1127

No video this week, working on bigger check in video for our 3 year anniversery quickly approaching next week!

One of the new features that I have been working on is theming. Virtually all aspects of IM will be theme-able by color, gradient, or image!

Another big thing being worked on is completely separating the code for input and output devices from the InputMapper core code making it accessible to plugin developers. This has resulted in a lot of side work that I am writing in parallel (which is slowing down overall releases) such as creating a standardized setting MVC as well as the overall interfaces needed for exposing IM features to developers.

Details

Written by Wobbles

Created: 02 May 2017

Hits: 1570

Just a quick one, but I think i've hammered out some bugs in the HidGuardian installer that was causing a couple people issues, and there is a possibility that BT support is now possible in HidGuardian!

Download the service and filter driver pair at: https://inputmapper.com/downloads/download/5-tools/76-inputmapper-hidguardian

Details

Written by Wobbles

Created: 25 April 2017

Hits: 1329

So with the recent video just a few days ago there wasnt really enough to warrent another video, So I'll just bang out a few words instead.

The release of the Windows service coupled with the HidGuardian drivers has gone pretty well save one or two reported issues so far. I'm continuing to look into those but the rarity suggests they are isolated incidents.

I have also spent the day looking into the possibility of adding plugin support (to a limited extent) to InputMapper 1.7. Not the same plugins as 2.0 but similiar in function in that there will be Input device and Output Device plugins. I wont be exposing the application as much as I did with IM 2, I just want future developers to have the ability to add device support to the application without needing to go through me. Its all very white-board right now so not much info beyond that right now.