I understand the motivation for creating this driver, but if it:
a) doesn't change the device name to not look like an Xbox 360 controller, or
b) doesn't support the XInput API
... then it is an absolutely terrible idea. Any application that properly supports XInput per MSDN's method (including my own) will end up not supporting these controllers at all.
With Windows 7, and likely earlier versions, you literally just plug the Xbox 360 controller in. It detects it, connects to Windows Update, downloads the device drivers and installs them.
Asking an end-user to install a third-party driver because you don't wish to support XInput is bad. Yes, it's BS that Microsoft makes us support a new API for a single controller; but two wrongs do not make a right.
|
Index 
Flat 
Re: EDIT: I think I understand what's going on now.
Reply
