#8148: The option names in "Modifier Keys" dialog are incorrect ----------------------------------+---------------------------- Reporter: rq | Owner: jscipione Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All ----------------------------------+---------------------------- Comment (by jscipione): Replying to [comment:10 rq]: > May I suggest a further improvement? I think it would make more sense to swap the columns and turn Key Roles instead of Keys into dropdowns. This would prevent assignment conflicts (where two roles are assigned to same keys), yet would allow to assign same role for more than one key, if anyone for any reason would ever want that (you could still issue a warning if the user would try to save such settings, but it would be a warning, not an error). I originally wanted to have the Key column on the left and the Key Roles column on the right (reverse of now) but I couldn't get that to work. That being said, the current behavior seems logical to me. The Keyboard Layouts assume that each key is defined exactly 1 time, so one set of Shift keys, one set of Control keys, one set of Option keys, one set of Command keys. While you could repeat a set of keys and it would work as far as pushing the keys goes, it wouldn't display correctly in Keymap. Given that and also that defining a key role more than once purposely would be rare it isn't worth it to allow you to do this from the Modifier Keys dialog. However, the reason I took Caps Lock out from the dialog was exactly that, if you defined Caps Lock as Ctrl for instance the Caps Lock key wouldn't show up in the display as Control assuming you also had control defined. Perhaps someday I'll allow you to map Caps Lock to control (or another modifier) in the regular dialog instead, and also update the Keyboard Layout so that the display shows correctly. At that point not only do you have a custom keymap, you also have a custom keyboard layout. So, before that could work I would have to support having a custom keyboard layout and checking a "Custom" option in the Layout menu. However, AltGr is a much more important feature to implement so I'll be focusing on that next. -- Ticket URL: <http://dev.haiku-os.org/ticket/8148#comment:11> Haiku <http://dev.haiku-os.org> Haiku - the operating system.