I Hate (Most) Keyboard ‘Fn’ Keys – Dan Q

Skip to content

Duration 12:55

Podcast Version

This post is also available as a podcast. Listen here, download for later, or subscribe wherever you consume podcasts.

Download this episode

All episodes

RSS

Spotify

Pocket Casts

Apple Podcasts

YouTube

In my living room1 is an ageing Windows<br>media centre PC, which is connected to the TV and principally used for Jellyfin, Netflix, Nebula, Steam, and the like. For convenient sofa use, I’ve equipped it with a wireless<br>keyboard/trackpad combo.

The keyboard is, for the most part, fine. You wouldn’t want to type an essay on it, but if you’re searching for a YouTube video it does the job.

Unfortunately, the manufacturers of this keyboard decided that it needed a dozen extra functions, and repurposed the F-keys F1 through F12 for these<br>purposes.

It was nice that they gave dedicated keys to volume control/toggling muting – we use those all the time. And there are three other dedicated keys in the top right which we never use… so<br>there was clearly capacity for a little extra. And they still they felt the need to do… this:

That F4 key has been repurposed as a “sleep” button. This poses a problem.

I don’t want any of these “special function keys. Occasionally, I suppose, I might need one2,<br>but mostly I’d just like F1 through F12 to remain the multi-purpose, context-dependent keys that they have been since they first appeared in 1965.

And so, because I don’t want to hold Fn every time I want to press an F-key for its intended purpose, I used the arcane shortcut Fn+Caps<br>to “lock” the keyboard into “standard” mode, where multipurpose F-keys remain multipurpose F-keys unless I hold down the special magic button that transforms them into<br>rarely-used single-purpose special function keys.

But here’s where the problem occurs. If the batteries get changed, or if the keyboard gets turned-off for an extended period, or sometimes – seemingly – just randomly… that<br>function-lock gets switched off.

And I’ll grab the keyboard and, to quickly quit Steam Big Picture or a Jellyfin Client or something, I’ll press Alt+F4. Which will send the “sleep”<br>command. And because this computer’s a bit older, it’ll hibernate.

Instead of closing one application, which is what I intended, I now have to wait upwards of a minute for the old box to finish copying all of its RAM into a file, and shutting down, and<br>then booting up again (in response to my repeated and frustrated hammering of the space bar), and then loading everything back into RAM… just to put me back where I started3.

What’s most-frustrating is at F4 is the only key with such a time-consuming and annoying function. If I accidentally paused some music or opened the system<br>settings or did whatever-the-hell the icon on the F6 key is supposed to mean, that wouldn’t be so bad. But man; the three or four times a year that this catches me out<br>are just aggravating enough to piss me off without being quite bad enough for me to do something about it4.

This is the WASD Code keyboard on another of my computers5, showing how a Fn key can be done right.

It doesn’t have to be this way.

My WASD Code gets it right by resigning the effects of all double-duty keys to minor conveniences only, and making them the secondary functions of the keys to which they’re<br>attached. I use these volume control buttons and they’re fine6.

My Keychron K10 gets it right by having the double-duty keys mirror those of the Mac it attaches to7:<br>again, all minor, low-impact functions that are easily and quickly un-done. Also, when you lock it to traditional F-key mode it stays that way, even if it’s disconnected<br>and left unpowered for an extended period.

I had one of those Macbooks with the stupid LCD screen in place of keys, once, and I hated that “feature” and was glad to see it disappear (although occasionally I still see it on<br>other hardware): who the hell wants a hardware keyboard that they can only use by looking at it? This is a much saner design, and I appreciate how easy it is to switch it to<br>“normal” mode8.

These keyboards – which are my daily drivers – show that an Fn key can be done right.

Here’s what “doing Fn right” looks like, to me –

Where keys do double-duty, it’s a low-impact and quickly reversible operation , so there’s little cognitive load or delay in correcting any mistakes.

The default state is the traditional key function , or if that’s not the case, switching mode is easy (doesn’t involve looking up an underdocumented shortcut or<br>installing a proprietary driver).

When you switch the default state, it stays switched and doesn’t swap back to factory defaults just because of a loss of power or other arbitrary and unrelated<br>trigger.

Sadly, a great number of keyboards get their Fn key implementations wrong. And I hate them for it.

Footnotes

1 By which, right now, I mean the living room of the<br>Chicory House, on account of my actual house being busy having its underfloor foundations torn...