Input hotswapping/multi-support

[samdotjpg]

For example, right now if you are using a touchscreen device such as an android that also has a built-in controller, there is no way to do most actions with the controller. With a controller, you can break, place, swap inventory positions, open inventory, do inventory management, open chat, open and adjust settings, and change perspective. You can't move, jump, or look.

[samdotjpg]

At the very least, mobile should be able to recognize and use a controller, and prefer it over touchscreen if recognized. "Use Controller" has no reason to be grayed out since mobile does have controller support.

[BrentDaMage]

The setting is greyed out because it just serves to indicate whether or not a controller is detected. I did this (over a year ago) because I recall actual PE working like this at one point.

[BrentDaMage]

Additionally, the inability to hot-swap inputs is due to the way Mojang structured the input-handling code.

[Wilyicaro]

I can add this to the Console UI PR, if no one wants to add it separately

[BrentDaMage]

No no no, please do it in a separate PR.

[Wilyicaro]

alr (I want to make the Console UI not a draft anymore so hard lol)

[samdotjpg]

The setting is greyed out because it just serves to indicate whether or not a controller is detected. I did this (over a year ago) because I recall actual PE working like this at one point.

Yeah, for sure. It's just that even when a controller is connected on mobile (or literally built into the device), there's no way to use it without disabling touch screen input in the source code.

[BrentDaMage]

The setting is greyed out because it just serves to indicate whether or not a controller is detected. I did this (over a year ago) because I recall actual PE working like this at one point.

Yeah, for sure. It's just that even when a controller is connected on mobile (or literally built into the device), there's no way to use it without disabling touch screen input in the source code.

Yeah, I never really accounted for this. I'm sure we can just add a simple check for hasController before initializing the input handlers.