Update/add more default input mappings

[TakuikaNinja]

This suggestion comes from the discussion in #3842.

The default controller mappings in general aren't updated often, so that might be doable here.

An especially glaring issue is that cores for computer systems (C64, ZX Spectrum, MSX, etc) lack default mappings for their keyboards. It would be a good idea to create sensible defaults for these, along with updating the rest of the mappings.

[Asnivor]

I was sure I included default mappings for ZXS. Looks like they were all removed to fix this (or another) issue: https://github.com/TASEmulators/BizHawk/commit/ec3a23259cf0f9528aef661b9df51846997485f4

If the key priority thing is now properly fixed, someone should be able to add the defaults back in maybe?

[YoshiRulz]

Ah, I was looking for https://github.com/TASEmulators/BizHawk/issues/3257#issuecomment-1786291002. To summarise my opinions:

• I think we shouldn't have any default hotkey keybinds which are just a single key. (Maybe some standard things like F1, Alt alone, or Pause.) But I don't think it's a good idea to change those unless it's as part of a complete overhaul of the defaults.
• Similarly, I think mapping most of the host keyboard to the virtual keyboard is a bad out-of-the-box experience. If only because the default keybinds must not have conflicts. I still wouldn't like it if all the hotkeys used modifiers though.
  • Earlier, I suggested we could have some sort of preset to populate the keyboard binds for those who wanted that immersive experience; see #1636.
• Modifier keys are inherently different: If one is mapped to a virtual key (as was the default for C64 before the above commit), trying to input e.g. Shift+R on the virtual keyboard may instead trigger another binding (e.g. the Rewind hotkey). Thankfully we don't seem to have any virtual buttons bound to Ctrl or Shift for any system at the moment.
  • Perhaps if a modifier key alone is bound to anything, a message should appear at the bottom the keybinds dialog explaining how to use the bind priority toggle?

[vadosnaprimer]

Similarly, I think mapping most of the host keyboard to the virtual keyboard is a bad out-of-the-box experience. If only because the default keybinds must not have conflicts.

We have a priority button exactly for those conflicts. If the goal is not ever having to use that button, then the replacement system should have been implemented first, before removing all keyboard bindings.

As I said there, having to rebind every key for every release is a worse experience.

[Morilli]

I wasn't aware of #3257 or ec3a23259cf0f9528aef661b9df51846997485f4 and now that I do I really don't understand the resolution.

How is a normal user expected to interact with virtual keyboard controllers, if not by mapping each of the virtual keys to a real key? Removing all default keybindings because some of them conflict with default hotkey keybindings is nonsensical imo. Why not remove all default hotkey bindings instead at that point?

We have a priority button exactly for those conflicts.

This. This problem of conflicts between hotkey and key bindings is already resolved in bizhawk through the priority system, and if this setting is somehow not adequate or not communicated clearly enough then that should be fixed, and not default bindings removed.