#7967: Update menu modifier images to more accurately reflect the corresponding key that appears on the keyboard ------------------------------+---------------------------- Reporter: jscipione | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All ------------------------------+---------------------------- Comment (by jscipione): Replying to [comment:29 axeld]: > Whatever solution is chosen, it has to work with different keyboards attached to the system at a time. If you have a Mac keyboard attached to a PC laptop, which symbols are you planning to show? There is a built in assumption of 1 keyboard being attached right now inherited from BeOS. For instance there is a get_keyboard_id() function in InterfaceDefs.h that gets the PS/2 id of the attached keyboard. I assume that we'd like to extend that to probe multiple keyboards in the (near-)future, including USB keyboards, in a different way, so that we can make per keyboard decisions. I am making a lot of assumptions here but the point is that you would show the bitmaps corresponding to the first keyboard (keyboard 0), which, as I envision it, would be the built-in laptop keyboard. > Since this is about shortcuts, anyway, I don't think there is much wrong with the key roles; it's pretty easy to grasp, and use, without having a look at the Keymap application first. While I wouldn't mind if it all magically worked flawlessly, having to configure this manually is rather awkward, too. I agree that configuring this manually would be misplaced. It should work as magically as possible with as little explicit configuration as possible. > Having said all that, I find the key role approach the most convincing solution so far. Simple, and not over-engineered, and it will work flawlessly in every environment (even when François finishes his Atari and Amiga ports ;-)). Well, my concern is that the bitmaps corresponding to the key roles will confuse people with PC keyboards because they won't understand the concept of key roles or that the role of the key is different than the label on the key. This is bound to include a large percentage of users. But, if the vocal minority believes that the key role approach is the best way to go, I am willing to capitulate. Before this is done though the responsible thing to do is to post a notice on the general mailing list informing the silent majority that this change is going to happen. I consider changing the "ALT" bitmap to "CMD" in the menus to be a pretty big change and I'd hate to blindside people who aren't paying attention to this discussion. I would also like to alter the "... (Mac)" system keymaps to flip the command and option keys if not already done so that muscle memory is maintained -- meaning the key that is in the same location as Alt (Command), not the key with the same key code as Alt (Option), performs the B_COMMAND_KEY action. In other words I'd like the Option key to perform the B_OPTION_KEY action and the Command key to perform the B_COMMAND_KEY action by default. I hope that is not controversial. Again, I would first inform the silent majority about the change. -- Ticket URL: <http://dev.haiku-os.org/ticket/7967#comment:30> Haiku <http://dev.haiku-os.org> Haiku - the operating system.