The new Microsoftslop copilot key always sends the following key-sequence when pressed:

copilot key down: left-shift-down left-meta-down f23-down f23-up left-meta-up left-shift-up
copilot key up: <null>

This means there’s no real key-up event when you release the key --> it can’t be used (properly) as a modifier like ctrl or alt.

The workaround is to send a pretend key-up event after a time delay, but then you mustn’t be too slow / fast when pressing a shortcut.

tldr: AI took a perfectly working modifier key from you.

— edit —
Some keyboards apparently do the “right” thing and don’t send the whole sequence at once, you can remap those properly with keyd, see: https://github.com/rvaiya/keyd/issues/1025#issuecomment-2971556563 / https://github.com/rvaiya/keyd/issues/825

copilot key down: left-shift-down left-meta-down f23-down
copilot key up: f23-up left-meta-up left-shift-up

this will still break left-shift + remapped copilot and left-meta + remapped copilot, but RCtrl remaps should work as expected

  • PolarKraken@lemmy.dbzer0.comEnglish
    8·
    5 hours ago

    An embarrassing new low, even with the bars they’ve already set. And fitting, for this being the (egregiously multiply-) branded button to launch the shit show. Christ, this has been a fucking carnival lmao.

    Microslop has now regressed to implementing “features” very closely resembling - in sophistication and effect - my own bumbling, desperate, ignorant attempts at similar (“making a button behave like a macro”), using AutoHotKey, somewhere between 15-20 years ago.

    And do I understand that they both shipped that, on hardware, AND it’s broken so badly it can’t be easily remedied?

    I don’t know what to say. It’s like all the geniuses of comedy who died too young are doing this, all of it.

    (No shade whatsoever to AHK, it was, probably still is, awesome at its job!)

    Edit: suddenly realized it’s just on purpose, probably. Anyway, rant remains lol