OS X (#880/#1460): Broken Commands

[molybdenum]

For 880 and 1460, I've created a workaround that should make the game playable for non-US keyboards. It's not a true fix; I tried a bunch of different ways and there really isn't a good way to do it properly. I'm just sending keyboard events from menu items.

1. I added items for '~', '[', ']', '{', and '}', since those were the only keys that were reported as not working. Are there any others that should be added? I could just add a whole bunch for all of the non-alphanumeric commands, just to be safe.

2. Since I'm just sending a key press, I'll invoke a keymap if the user has defined one. What is the best way to send the underlying command to Angband? I've tried a different few things, but there are all sorts of weird side effects.

[Pete Mack]

Keymaps are the traditional right way to do this, but since I don't own a mac, let alone a mac with international keyboard, I can't help you here, except to point out that keymaps belong in the lib/prefs directory....

[molybdenum]

Keymaps are the traditional right way to do this, but since I don't own a mac, let alone a mac with international keyboard, I can't help you here, except to point out that keymaps belong in the lib/prefs directory....

Yeah, I assume that players will eventually set up keymaps for that. I'm thinking that this fix is for new players who don't have keymaps and wonder why ~ doesn't bring up knowledge on their non-US keyboard. But, your response somehow made me remember the \ command, so thanks!