#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 bonefish): Replying to [comment:22 jscipione]: > Replying to [comment:21 bonefish]: > We are in agreement that key roles are the best approach, meaning that the bitmap that appears in the menu would not rely on the keymap. As explained, that is not my interpretation of key roles (at least not the whole story). > > 1. switch the legends on the keyboard in Keymap when switching between Mac/Haiku and Windows mode as done already (r43228), > > You must have meant a different commit because r43228 has nothing to do with this. I don't mean a commit, just a revision for reference (in case that the behavior changes in the future and someone reads the comment afterwards, as unlikely as that may seem considering how the comment section of this ticket grows). > > 1. not switch the shortcut bitmaps *ever*. > > If you are willing to live with the fact that on a PC keyboard the Windows key corresponds to a menu bitmap that says "OPT" and the Alt key corresponds to a menu that reads "CMD" and you are willing to live with the fact that when you switch the control and command keys via the "Switch shortcuts to Windows/Linux mode" button in Keymap the Control key corresponds to a bitmap that says "CMD" and the Alt key corresponds to a menu item that reads "CTRL" and are willing to live with the fact that on a Mac keyboard the Option key corresponds to a bitmap that says "CMD" and the Command key corresponds to a menu bitmap that reads "OPT" then ok. I really can't say what Apple has done to its keyboards. Back in the BeOS days the modifier names on Apple and Mac clone keyboards matched Command, Control, and Option exactly. There was a recent mention of changes to Apple keyboards (maybe even in this ticket) and as I understood it Apple started relabeling Option to Alt. If I misunderstood it and as you say they basically swapped Option and Command, then this demonstrates even more that what you're trying to do is simply not going to work, since 1. it would already be broken for old Mac keyboards and 2. keyboard manufacturers (at least Apple) apparently can change keys on a whim, which doesn't bode well for the future. > I find all that terribly confusing though and I think that the input server could take care of all of it for you without you having to do anything. It could only do that, if it knew how the keys are labeled on the exact model of the keyboard. Not even considering legends localization and other customization. > How is that an ideal solution? That is equivalent to saying "this problem is hard, let's ignore it." The problem is not only hard, it's not practically solvable. > > Regarding the Haiku/Mac vs. Windows mode, how/where that is implemented -- i.e. as a change to the keymaps or a flag for the input server -- is really an implementation detail. I suppose a flag would be easier to implement, but I don't care as long as it works correctly. > > It won't be an implementation detail if we support multiple keymaps because multiple keymaps break the control/command switching feature. One (i.e. the preflet in which the keymaps between the user wants to switch are specified) would simply have to keep the modifier behavior of all keymaps in sync. -- Ticket URL: <http://dev.haiku-os.org/ticket/7967#comment:25> Haiku <http://dev.haiku-os.org> Haiku - the operating system.