Keyboard mapping for the two Amiga keys

[dirkwhoffmann]

Currently, vAmiga has the option to map the Cmd keys directly to the Amiga keys. This is done by subclassing NSApplication and overwriting function sendEvent(_ event: NSEvent). However, more recent macOS releases tell the user that vAmiga intercepts keyboard events in a ways that sounds like vAmiga is malware. Therefore, I will change the mapping scheme to something less intrusive.

I plan the following changes:

Let the user choose from one of the following mappings:

• Left option -> Left Amiga, Right option -> Right Amiga
• Shift+Left option -> Left Amiga, Shift+Right option -> Right Amiga
• Ctrl+Left option -> Left Amiga, Ctrl+Right option -> Right Amiga
• Cmd+Left option -> Left Amiga, Cmd+Right option -> Right Amiga

Currently, the opt key (in combination with some other keys) can be configured to retain or release the mouse. This has to go away as it conflicts with the new Amiga key mappings. I will map the mouse retaining / releasing functionality to Cmd+G, which, I think, is consistent to what UAE and FSUAE do.

[dirkwhoffmann]

My original plan didn’t work as expected. Mapping Shift + Option to the left Amiga key failed because pressing Shift caused the Amiga’s own Shift key to go down. I’ve adjusted the mapping instead: Command + Option now acts as the Amiga key. You can enable or disable this option in the Settings.