Add auto detect option in input dropdown
Also might want to add a clear option or "none" selector when selecting buttons and axis' as you currently can't unset a button or axis, once it is set.
As of 7d4a417 there is a "none" option! I also added some groundwork for input detection.
Awesome, I see you also added the axis count in that release. If you want, I can compile the library when I get home and test some of the new features? Was especially thinking because the axis stuff on my controller is completely bonkers. :P
Yeah sure, anything helps.
What do you mean the axis stuff is bonkers?
The image I attached in the other post, my Y axis for my controller is axis 6, where as the others are 1, 2 and 3. But I think that is the controller setup, not the software. :)
That's odd. Does it still allow you select Axis 6 after I limited the display of axes? Do 4 and 5 do anything?
I will try to compile it tonight or tomorrow and test it out.
It apparently lists all 6 axis, so we are good on that one, now I just wonder wtf axis 4 and 5 are for? :P Also I can't seem to find the code for the detect feature, so am I to assume that it is currently just there for show?
Also might want to do some trailing spaces clipping:

And for the use of the configs, maybe we make it so that you can select a config, so for example if several controllers are built on the same chipset, you can just have one config and use it with all controllers? Also I think ipega calls all their controllers the same as in the screenshot, might be other companies doing the same, so this might also be a potential issue of not letting people choose a profile.
In ControllerOptions.cs (this is the class for the options window) at line 47 it uses dev.joystick.Capabilities.AxesCount to find how many axes the controller reports having. Before it had that, I was just using 24.
I actually just plugged in a controller that has 4 axes but one of the axes isn't in the first 4 so it is unselectable right now. I'm gonna investigate if I can get the controller to say exactly which axes are used and which aren't.
Also, I responded to the second part of your comment in #5.
Hmm, odd. You want me to log any data about my controllers, to get some reference points?
Also my controller shows up as a 15 key controller, yet I can't seem to find btn3, btn6 and btn13, again I think this contributes to the oddity of the controller, but still an interesting point.