News for hackers. Stuff that matters.
Re:Logitech MX Mechanical Keyboard by zweifuss on Tuesday May 24, 2022 @08:52AM (#31491350)
What I don't like about the MX keyboards is that they don't have an IBM compatibility mode. For example, the pause key is Start+Fn+B. So the familiar break combination in Visual Studio CTRL+Pause is CTRL+Start+Fn+B. The Fn key is on the left, so it requires two-handed operation. Some key combinations can not be reached at all, not even as a macro. The macro facility (progammable key) is near useless anyway.
Re:Logitech MX Mechanical Keyboard by retSava on Tuesday May 24, 2022 @10:14AM (#31492386)
While this is a workaround rather a solution, I use sharpkeys (https://www.randyrants.com/category/sharpkeys/) to reprogram keys I don't use as much.

Eg caps lock -> delete, num lock and scroll lock -> volume down/up, paragraph key -> play/pause (I'm on SE layout). Works very well for me.

Re:Logitech MX Mechanical Keyboard by IE6 on Tuesday May 24, 2022 @09:27AM (#31491793)
fwiw this has more to do with keyboard layout and pcb programming than the switches - my 'tex shinobi' board has a dedicated Pause key (and more).
Re:Logitech MX Mechanical Keyboard by Jim_Heckler on Tuesday May 24, 2022 @10:55AM (#31492930)
they meant "Logitech MX" not "Cherry MX"
Re:Logitech MX Mechanical Keyboard by layer8 on Tuesday May 24, 2022 @11:09AM (#31493123)
Also no Menu key (in the place were they have the Fn key), which I use all the time on Windows. The combined Windows/Mac keycap labels are unfortunate as well (unless you frequently switch your keyboard between both systems I guess), seems like a cheap cost-cutting measure instead of offering two models or exchangeable keycaps.