Beta 2 Bug: Gamepad Button Presses (w/ fix)

EDIT:

Okay, now that I've gotten a clean eight hours of sleep here's a clear explanation of the problem:

When a keyboard key or mouse button is pressed, the event that is built contains a value. This value is set depending on whether or not the key is being pressed or released. In the code, this is a make event or break event.

For Xbox gamepads, this value is always 0 (not sure if the problem applies to other gamepads). The way the code is written, it can't be anything else.
This is the existing code in winDirectInput.cpp in the function called DInputManager::fireXInputButtonEvent near the bottom after the code for logging.

buildXInputEvent( controllerID, SI_BUTTON, objInst, ((mXInputStateNew[controllerID].state.Gamepad.wButtons & button) != 0) ? SI_MAKE : SI_BREAK, 0);

To fix this, you need to determine the action type and set the value accordingly.
The following code is meant to replace the code above. Again, it is found in winDirectInput.cpp in the function called DInputManager::fireXInputButtonEvent.

buildXInputEvent( controllerID, SI_BUTTON, objInst, ((mXInputStateNew[controllerID].state.Gamepad.wButtons & button) != 0) ? SI_MAKE : SI_BREAK, ((mXInputStateNew[controllerID].state.Gamepad.wButtons & button) != 0) ? 1 : 0);

I used the code for keyboard and mouse button events to figure out what I was looking at, and how it's determined there. This is near identical except that it's inline in the call to the function.

I tested this fix with every "button" type on the Xbox 360 gamepad. It works as expected where the button press produces a value of 1, and releasing the button produces a value of 0. This also does not appear to interfere with the analog stick or left and right triggers as they still work as expected.