Controller dialog: Update controllers after controller addon installation

[garbear]

Description

This PR is a continuation of the UX fix in #15754.

The first commit adds the missing add-on events that caused the list to not refresh when an add-on is installed.

However, this led to the following problem:

The SNES controller was selected, but installing a 3DO controller updated the controller list indices and caused the wrong one to be highlighted. To fix this, I made the controller dialog focus the newly installed controller.

How Has This Been Tested?

Installed a controller and observed it being focused.

Clicked "Get all", and controllers were updated as they were installed. Unfortunately, the image is blocked by the modal dialog. I would like to make it a toast, but then how would the user cancel? Closing the dialog?

Types of change

• Bug fix (non-breaking change which fixes an issue)
• Clean up (non-breaking change which removes non-working, unmaintained functionality)
• Improvement (non-breaking change which improves existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that will cause existing functionality to change)
• Cosmetic change (non-breaking change that doesn't touch code)
• None of the above (please explain below)

[garbear]

@enen92 can you test?

[enen92]

Sorry for the delay @garbear. Tested it and working as expected 👍
One small glitch though: suppose you install all the available controllers. The "Get More" button is still enabled which leads the user to think there are more controllers to install. However if you click the button you'll only find out that "You already have installed all the controllers". Supposedly, the UpdateButtons() call in GUIControllerWindow.cpp is there to prevent this situation I guess. Which leads me to think that the subscription of addon install events I previously added in #15754 would still make some sense.

[garbear]

Which leads me to think that the subscription of addon install events I previously added in #15754 would still make some sense.

Agreed. I haven't had time to include that fix in this PR, so I think it's best if we merge as-is and follow up with a fix to the problem that #15754 tries to solved. Can you rebase on master after this merge so we can re-evaluate your patch?

jenkins build this please

[ksooo]

@garbear we are just in the middle of branching Leia. In case you want this fix in v18 you need to backport it to Leia branch.

[garbear]

@ksooo I saw the branching discussion in slack too late. Do you recommend backporting?