Edit: If you wish to be a tester for XIM4 Commander, you need to read ALL of the text below, and in fact the rest of this thread, as it will set you up with background info and the ability to contribute better.
That said, I should mention that there is now an early version for testing available here:
http://xim4.com/community/index.php?topic=38509.0 (20141219 - CURRENT)
http://xim4.com/community/index.php?topic=38510.0 (20141218 - obsolete)
http://xim4.com/community/index.php?topic=38511.0 (20141216 - obsolete)
http://xim4.com/community/index.php?topic=38512.0 (20141209 - obsolete)
IMPORTANT: Official support is NOT PROVIDED for this software yet. Please do not report issues or seek help in the official Support section of this forum. Any issues should be reported here, on this thread, but only AFTER thoroughly reviewing all documentation in the package you downloaded to be sure you didn't overlook the solution, not to mention checking this thread to see if anyone else has had and solved the same issue.
If you know yourself to be technologically-challenged, I would gently and politely suggest that you hold off until at least the Beta stage of testing, when documentation is improved, nagging bugs are mostly resolved, and there is much more information in the heads of other testers who can help you. Otherwise, it may be very frustrating for you in these early Alpha stages, not to mention that my own bandwidth is rather limited and I cannot afford to do very much non-bug-related troubleshooting.
TL;DR version:XIMCommander resurrection in the works. Requesting suggestions/needs.
L,BRA version:So, as most of you know, I'm tech support here with XIM, and as some of you know, I'm also a long-time senior engineer from the games industry. I've been gently prodding OBsIV several times a day for months now to see if there's any way I can use my skills to contribute to the XIM project. He's been surprisingly patient with my nagging, and as it turns out, it looks like there
is a way I can help: I'm going to be resurrecting XIMCommander.
The first thing he and I need to do is figure out the initial scope. I actually have not had the opportunity to use the original XIMCommander, as XIM4 is my first XIM and it doesn't yet support that, obviously. As I understand it, XC allowed you to capture PC inputs (mouse, keyboard, other) and pass them across a USB transfer cable to the XIM, as if the PC were one of its peripherals. Restoring that functionality is our bare minimum target.
The question is: Are there other things that are important and which have traditionally been missing from XIMCommander? Is there anything that might not be obvious to me because I am not in a group that needs the features, but which might be vital to, e.g., someone with a disability and a customized input device?
I do need to make clear the following:
- Internal support for macroing is not on the table. It's a PC, there are probably other ways you can do this if you really want to, just like you can use a macroing controller with a console, but we wish to honor the terms of service on consoles and, as such, do not condone or support this.
- Internal support for automatic behaviors such as rapid-fire are not on the table. See above.
- A mod-friendly library/SDK is not planned to be released with XC. Consider the previous two statements and the reason for this will probably be evident. This is OBsIV's call, so I won't be able to change it, no matter how many of my fingernails you tear off. Anyway, I agree with him. As such, all functionality will need to reside inside of XIM Commander and/or XIM Manager. Keep this in mind if you want to have features from previous user-created projects that were based on the old library.
Okay, over to you guys. Try to be as realistic as you can, since I am only one dev and I am brand new to this code, not to mention that I will still be doing tech support. Let's assume my bandwidth will be near-full right out of the gate and start with the most important things. Especially, let's avoid arguing about the "not on the table" points above, okay?

If you guys really insist on arguing any of those points, please start up a separate thread and take your arguments direct to OBsIV, since I defer to him. Edit: here's a thread with some arguments I moved out of this one:
http://xim4.com/community/index.php?topic=35817.0Thank you!

Items suggested and accepted so far (
working,
not working, not done):
- Do not break external accessibility programs that can massage input for disabled gamers. This also includes drivers/software for peripherals, like LGS or Synapse.
- KVM-like hotkeys for activating and deactivating XC.
- Support DInput.
- Support XInput.
- Support driving wheels.
- Don't freeze on disconnect.

- Windows voice control.
- Map axes and buttons without requiring external apps. This might be a follow-up feature.
- Give certain keys permission to bypass XC.
Items suggested but not yet accepted or declined:
- A way to record live data from XIM4.
- Integrated dead-zoner functionality, a la Kodek's stuff. Possible issues with using existing code. Must investigate.
- Chat audio injection or possibly extraction, to/from PC.
- Touchpad and sixaxis support - depends on DS4 support in firmware.
- LGS + Extreme 3D Pro joystick
- OCZ's / BCInet's Neural Impulse Actuator - SDK available?
- SmartNav head tracking mouse in
- Tobii EyeX controller and/or the Mirametrix S2 controller - use eye tracking for mouse movement
- Convert PC keyboard to on-screen keyboard sequences.
Items needing clarification:
Items declined:
- SDK, for now anyway.
- .NET version of the SDK. Not unless there IS an SDK. At that point, it's probably fine.
- Toggle to use keyboard as text input - requires the same feature on XIM4 first.