← Back to context

Comment by DecoPerson

10 days ago

I agree. Making deals with laptop manufacturers to put their trademark on keyboards is an unhealthy-for-society abuse of their market power and should be treated as such in every jurisdiction that they trade in.

However, I've had no issue remapping it to the Context Menu key on the Chinese Lenovo Xiao Xin laptop I bought recently. It shows up in the PowerToys keyboard remapper tool as an F23 key. (Yes, there are more than 12 F key codes! I believe there is 24 in Windows.)

Other OSes will not even be able to say things like "Press your Copilot key to open FEDORA SEARCH" or whatever without being cease'n'desisted to high heaven.

Terrible.

4 comments

DecoPerson

Reply
wkat4242  10 days ago

> However, I've had no issue remapping it to the Context Menu key on the Chinese Lenovo Xiao Xin laptop I bought recently.

That's probably because you're not using it as a modifier so the OP's complaint of the automatic key-up event doesn't impact you (it's not necessary to have a keep-pressed state in this type of use).

  • mrandish  10 days ago

    Correct. Further down thread I wrote to another poster a summary of what's really happening now when you remap the CoPilot key - copied here...

    The CoPilot key is really sending: Shift+Alt+Win+Ctrl+F23 which Windows now uses as the shortcut to run the CoPilot application. When you remap the CoPilot key to right-Ctrl only the F23 is being remapped to right-Ctrl. Due to the way Windows works and because MSFT is now sending F23 DOWN and then F23 UP when the CoPilot key has only been pressed Down but not yet released, those other modifiers remain pressed down when our remapped key is sent. I don't know if this was intentional on MSFT's part to break full remapping or if it's a bug. Either way, it's certainly non-standard and completely unnecessary. It would still work for calling the CoPilot app to wait for the CoPilot key to be released to send the F23 KEY UP event. That's the standard method and would allow full remapping of the key.

    But instead, when you press CoPilot after remapping it to Right-Ctrl... the keys actually being sent are: Shift+Alt+Win+Right-Ctrl (there are also some other keypresses in there that are masked). If your use case doesn't care that Shift, Alt and Win are also pressed with Right-Ctrl then it'll seem fine - but it isn't. Your CoPilot key remapped to Right-Ctrl no longer works like it did before or like Left-Ctrl still works (sending no other modifiers). Unfortunately, a lot of shortcuts (including several common Windows desktop shortcuts) involve Ctrl in combination with other modifiers. Those shortcuts still work with Left-Ctrl but not CoPilot remapped to Right-Ctrl. And there's no way to fix it with remapping (whether AutoHotKey, PowerToys, Registry Key, etc). It might be possible to fix it with a service running below the level of Windows with full admin control which intercepts the generated keys before Windows ever sees them - but as far as I know, no one has succeeded in creating that.