Flipping gamepad mode between Xbox Controller and other option can break gamepad tester

[PastaJ36]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior: (assuming starting with Xbox Controller selected)

1. Go to Settings
2. Press Legacy Controller
3. Wait for keyboard to connect
4. Press Xbox Controllers
5. Check if Gamepad Tester works
6. If it still works, repeat until it's broken

Problem seems to be in Chomium. The gamepad tester uses the web Gamepad API, when it breaks navigator.getGamePads() will just return all null.

I've tried testing it a Chrome instance open at the same time and https://gamepad-tester.com/ open. The website kept working, but Wootility broke. Could try updating Electron, see if it fixes this issue.

[Rocky04]

Hmm, I'm not sure if that is really the case...

The tester in the Wootility only works when Win has loaded the Xbox controller device, it can be of course that the site on a dedicated browser is a bit faster but besides they should behave the same.

This happened to me after some testing:

• I had the problem when I switched the state to quickly that the keyboard was still in the old state while the Wootility has showed the new one and so the tester had indicate an error instead of complaining because of the wrong state. Because if the tester is shown only depends on the setting from the Wootility and so not directly from the state of the keyboard, which is not good. This is more a general problem how the Wootility handles the connection because an UI update should be handled more carefully and so not directly from an action from the UI but rather indirect as a result of the reply / confirmation of a command which was sent to the keyboard.
• Also I had a state where XInput wasn't working completely where no data was sent over the Xbox interface after a quick toggle. Most likely because of a bad driver state.
• It also happened to me that the Win tool was working fine but I needed to restart both the browser and the Wootility in order to show it there.

Edit: By the way, due to this I had recommended to use the Win tool over the site because it can happen from time to time that there is a problem within the browser instance. Then you need to restart the browser while to ensure it was really dead in between. I assume the same thing can happen to Chromium used by Electron. So you just got lucky that your Chrome instance hasn't broke.

Edit 2: I assume it maybe has something to do with a sub process. I can remember sometimes when this happened toggling back and forth has fixed it, but on the test this wasn't the case while replugging the keyboard has worked.