fix: Gamepad not detected due to window handler definition error

[w0wca7a]

PR Details

When connecting a Logitech RumblePad II gamepad, SharpDX.DirectInput returns an error related to an invalid window identifier.

Related Issue

#1791

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[w0wca7a]

@dotnet-policy-service agree

[Doprez]

How reliable is this to always get the game window? If there is a possibility that the game window may not be in focus, there may be a better way to do this with a GameWindow reference.

[w0wca7a]

Thanks for the review. It doesn't really matter how we get the Window handler, gamepad working with SharpDX.DirectInput depends from the CooperativeLevel mode. It seems that if I can make CooperativeLevel work in Exclusive mode, it will allow ForceFeedback to work. At the moment, Exclusive mode will crash Stride.Input when window not in a focus. I will try your recomendation.

[Eideren]

Converting this to draft while the contributor gets back to us

[w0wca7a]

Sorry for the long delay. I can't get back now gamepads from true gamers. I hope to return to this PR in 2-3 months

[w0wca7a]

I tested connection/disconnection a game controller in a foreground/background game window, and also running two games that support game controllers. The game controller works in both simultaneously.
There were no crashes when the game window lost focus.
In any case, this is a temporary solution that allows game controllers to work out of the box. Silk.Net.Input Silk.Net.Input looks more promising.
This script is for testing. Any comments are welcome.