MX Keys (multi-OS version) Insert Key

[atjb]

Hello!

Real quick one - I'm one of those freaks who still likes to use the Insert key to enable Overtype mode in IDEs and word processors.

I picked up an MX Keys (regular version, not the for Mac version) and really quite like it, EXCEPT for the fact that the insert button doesn't register in macOS.

It's not a hardware issue - the button registers fine in Windows - same keyboard.

I've tried:

• Karabiner elements + karabiner eventlogger
• USB Overdrive
• Ukelele
• All combos of Logitech Options & the Beta Options +
• No drivers at all - just connecting via receiver and also bluetooth

Not a peep from my insert key in macOS.

Anyone using an MXKeys with an insert key? Or able to test whether theirs works?

Thanks so much!

 

[xraydoc]

Does it work in Microsoft Word for Mac?
I'm not certain how much support for there is in MacOS for the Insert key since it doesn't exist on Apple's keyboards.

 

[MacGizmo]

I can't for the life of me even figure out what the Insert key does and what it would be used for. But you could try using the Keyboard Shortcuts prefs panel and enter "Send Escape Sequence" and choosing a keyboard shortcut. Since I have no idea what it does, I can't tell you if it's working properly.

 

[atjb]

It doesn't work in Word for mac - but I think that's a software rather than OS issue.

Visual Studio Code and Atom are 2 apps that I'd like to use the insert key in - to enable overtype mode.

There's a very simple website here that will tell you what key is being pressed:

Javascript Key Event Tester

If anyone does have an MX keys and could try it out on that page, I'd be most grateful.

keydown keyCode=46 (.) which=46 (.) charCode=0 keyup keyCode=46 (.) which=46 (.) charCode=0 keydown keyCode=35 (#) which=35 (#) charCode=0 keyup keyCode=35 (#) which=35 (#) charCode=0 keydown keyCode=34 (") which=34 (") charCode=0 keyup keyCode=34 (") which=34 (") charCode=0 keydown keyCode=33 (!) which=33 (!) charCode=0 keyup keyCode=33 (!) which=33 (!) charCode=0 keydown keyCode=36 ($) which=36 ($) charCode=0 keyup keyCode=36 ($) which=36 ($) charCode=0

is the readout I get from pressing all 6 keys in the ins/home/end/del/pgup/pgdwn group - only 5 keys actually register.

 

[mfram]

I have the MX Master for Mac keyboard. There is no "insert" key on the keyboard. There is a 'fn' (function) key where the Insert key would be on a PC. Nor are there 'insert' keys on Mac keyboards in general as far as I've seen. That may be part of the problem.

 

[atjb]

Yes - the MX Master for Mac swaps the insert key out for a 2nd function key.

I'd imagine that it's part of the problem, in that Logitech didn't bother making the keyboard send a signal to the OS when it's pressed. However, there's nothing at all stopping macOS from making use of an Insert key - my previous K800's insert key worked perfectly for example. I understand that many mac users don't use the insert key - but I do. I even have one on a keyboard that's advertised as being for all operating systems - it's just that in this particular operating system, it seems to be disabled.

The step I'm at at the moment though, is working out whether it's just my particular MX Keys on mac config that won't transmit the insert key, or all MX Keys on all macs. For that reason, it would be much appreciated if another MX Keys user would go to the site above, or similar, and let me know if anything is logged when they press their insert key.

 

[mk313]

It doesn't work in Word for mac - but I think that's a software rather than OS issue.

Visual Studio Code and Atom are 2 apps that I'd like to use the insert key in - to enable overtype mode.

There's a very simple website here that will tell you what key is being pressed:

Javascript Key Event Tester

If anyone does have an MX keys and could try it out on that page, I'd be most grateful.

keydown keyCode=46 (.) which=46 (.) charCode=0 keyup keyCode=46 (.) which=46 (.) charCode=0 keydown keyCode=35 (#) which=35 (#) charCode=0 keyup keyCode=35 (#) which=35 (#) charCode=0 keydown keyCode=34 (") which=34 (") charCode=0 keyup keyCode=34 (") which=34 (") charCode=0 keydown keyCode=33 (!) which=33 (!) charCode=0 keyup keyCode=33 (!) which=33 (!) charCode=0 keydown keyCode=36 ($) which=36 ($) charCode=0 keyup keyCode=36 ($) which=36 ($) charCode=0

is the readout I get from pressing all 6 keys in the ins/home/end/del/pgup/pgdwn group - only 5 keys actually register.

I just tried it and got the same thing (MX Keys 'Windows' version), the Insert Key doens't give any feedback/code, whereas all 5 other keys own the group do.

 

[atjb]

Thanks mk313.

That's infuriating. There's absolutely no reason for it not to send an Insert signal - or any signal whatsoever to be honest. Insert may not be on many mac keyboards, but it's supported - shown both in official documentation as well as by the fact that insert on other keyboards works just fine.

I've found a workaround - run the keyboard in Windows mode (fn + P for 3 seconds) and then swap the cmd + alt buttons with Karabiner (or manually if you prefer). This lets the insert key work on this keyboard, and actually binds F1 + F2 to scroll lock and num lock - these aren't used on mac but can of course be rebound to something more useful. I now have F1 to toggle dark/light mode, and F2 to launch my terminal app.

I guess I'll have to try to get through to someone from Logitech to put this simple function back - not holding my breath though.

 

[kevindrew]

I wish they had not taken away insert and repurposed this key space on the mac keyboard. I am used to using Ctrl-Ins and Shift-Ins on a Windows machine, and was trying to get these to work as Copy and Paste with Karibiner or even in Sublime Text. I use a "Compaq" PC USB keyboard plugged in to a Mac.

I actually do get keyCode=45 and which=45 with that JS key tester.

One thing I noticed. These key combinations work in Slack. So it must be possible to read these keystrokes, at least on some keyboards.

 

[atjb]

I actually do get keyCode=45 and which=45 with that JS key tester.

That's interesting - you're using the MX Keys for all OSs (Black on black)? Are you using it in Windows or Mac mode? It's a longpress of function key + O or P to toggle between the two modes.

Mine now works - but only in windows mode, not in mac mode. Being in windows mode means that my option and alt keys are swapped - but otherwise everything works.

I guess I'm grouchy that they decided to include weird custom keys at all. For example, the function key on this keyboard reports a special Logitech proprietary keycode, even in mac mode. This means you can't use it to change input methods, like you can for the mac's built in keyboard's function key. It's literally the same key - why not make it work the same way?

The hardware is nice though.

 

[kevindrew]

That's interesting - you're using the MX Keys for all OSs (Black on black)? Are you using it in Windows or Mac mode? It's a longpress of function key + O or P to toggle between the two modes.

Mine now works - but only in windows mode, not in mac mode. Being in windows mode means that my option and alt keys are swapped - but otherwise everything works.

I guess I'm grouchy that they decided to include weird custom keys at all. For example, the function key on this keyboard reports a special Logitech proprietary keycode, even in mac mode. This means you can't use it to change input methods, like you can for the mac's built in keyboard's function key. It's literally the same key - why not make it work the same way?

The hardware is nice though.

What's MX Keys? I have a beige colored Compaq USB Keyboard KU-9978. It's rather old, but I like the key feel. It doesn't have a FN key. It has insert there.

 

[atjb]

What's MX Keys? I have a beige colored Compaq USB Keyboard KU-9978. It's rather old, but I like the key feel. It doesn't have a FN key. It has insert there.

MX Keys by Logitech.

It's a very pleasant keyboard to use, and advertised as being supported across macOS / Windows / Linux - with the ability to quickly switch between 3 different machines.

On the downside - for whatever reason, which they won't tell you, they've decided to disable the insert key on macOS. There are ways around it, so I guess it's a problem solved. I'd still be very happy if they just reenabled support though.