Trigger the special functionality BOTH with pressing control_l AND fn buttons. brightness adjustment) and if I press the former fn (new control_l key) and the F-button I do not get the special functionality triggered, are: I press the former control_l key (new fn key) and the F-button and get the special functionality (e.g. The F keys that do work as expected, i.e. swapped fn and control_l and adjusted F1.12 keys accordingly. I have remapped my keys as can be seen in the screenshot, i.e. I may also have configured my keyremap improperly, but for now this is what I'm experiencing. Note: I doesn't happen with A Merge Japanese handling improvement by Hacci eventType:keyDown code:0x7a name:F1 flags:Shift Cmd Fn misc:.eventType:keyMod code:0x37 name:Command_L flags: misc:.eventType:keyDown code:0x8 name:c flags:Cmd misc:.eventType:keyMod code:0x37 name:Command_L flags:Cmd misc:.eventType:keyMod code:0x3a name:Option_L flags: misc:.eventType:keyMod code:0x3a name:Option_L flags:Opt misc:.This all looks very strange to me, I'd be so grateful for the help! Keyboard based mapping I get none of the *_R keys - right Ctrl is shown as Control_L in EventViewer. However, sometimes after a reboot right Alt would be shown as Opt_R in EventView and then after a couple of pushes or switches to another apps will be Command_L again. I've tried to reboot, plug/unplug the keyboard, reinstall/delete completely IntelliType For Mac (yes, it used to work with it installed), delete/reinstall/install various versions of KeyRemap4MacBook - but to no avail. I think, it should be shown as Command_R in order for my setup to work as it used to. Now, when I launch the EventViewer it shows that both left and right Alts are "0x37 Command_L". But for some mysterious reason it suddenly stopped working (after I've moved to another apartment :) ). I always plugged my MNE 4000 keyboard into the macbook air and had the KeyRemap4MacBook to remap left Alt as command and right Alt as Control (and then 'ctrl will be Meta in Emacs). I have a problem which prevents me from using my Emacs setup the way I've used to. I suspect the text is a bit confusing although my tries to make it understandable. If I think about it, it doesn't make much sense that a modifier has effect on other modifier release, so the first one shouldn't be considered used, and the final key should be sent. So perhaps if we could prevent the modifier's release from causing KeyOverlayModifiers to not send the final key, this problem could be solved. I believe there is no reason for the release of Space (a KeyOverlayModifier in this case) cause other modifiers to be considered as used, since a Space char wasn't sent after all, and there is no reason for a modifier modify other modifier. If this didn't happen, the final key would be released normally. What is happening right now (I suspect) is that the release of the Space key, is telling the KeyOverlayModifiers that other key has been pressed, and there is no reason to send the final key (cmd+c). Just like you probably do when pressing cmd+c (you release cmd before c without noticing). The more I use it, the faster I start pressing the keys, and eventually end up releasing the Space (the key I'm using to enable the mode) before releasing ASDF keys. On the release of each key, if the modifier has not been used, they send instead ctrl+s, cmd+x, cmd+c, cmd+v. Simultaneous Vi Mode is getting more usable now, with most of is quirks getting solved.Īlthough, there is still one last thing that is killing me.Īs you know, I've set the ASDF line with KeyOverlayModifiers to Shift, Control, Option and Command. This problem was once discussed by email.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |