I’d have to know more and have access to one of those

I assume that the natural coordinate system of a phone is relative to the screen :D

Yeah that’s more inline with the bugged behavior that prompted me to create this solution.

Also obviously i’m talking about using the remapped copilot button as the ctrl key in these situations, not the original ctrl.

Very odd, anything I tried ignored any shift press. What’s the key combination you had to use in powertoys? And what system?

Shift-ctrl-tab tab switching and shift-ctrl-arrow key text selection works as well? (Both when shift is pressed first and when ctrl is pressed first?)

I'm still holding out where I can, but the new laptop doesn't have win10 drivers anymore, so that's another negative. I did see some third-party hacks to move the taskbar to the side and they help a bit but it's far from optimal.

This is not about AI. It's about standard expected hardware functionality (a damn right-ctrl button) being replaced by a random feature without the option to revert it.

Ah yes you can do that but mapping it to what you'd expect to be there is an afterthought :D

Not if you want to keep shift+ctrl support intact in my experience. Could be that different vendors implement it differently but at least on my laptop the shift key was swallowed up with powertoys.

Oh don't get me started on the lack of a vertical taskbar.

This specific laptop is an Asus TUF A14 and from what I've seen it's pretty dominant across their whole lineup. The fact that there isn't even a bios setting to change the behavior and the button just sends a random key combination is pure lunacy.

The right one, yeah. It may be a minor issue for some, but I hate having the copilot crap constantly pop up when trying to navigate code because I'm used to one handed navigation with cursor+ctrl keys, and there wasn't a solution out there yet that could take the shift selection into account.

I tried everything I could find (including Sharpkeys, powertoys, etc) and all of them had the flaw that they hid any shift key interaction due to the copilot key also sending shift down and up signals. This solution eliminates all that at the driver level and solves the problem once and for all.