Why is Super a modifier layer (like Shift) and not a full layer (like Mod or Fn)?

Configuration question
1

Just curious what the common use cases of “Super” are that it was created to be a modifier layer rather than a standard layer?

And I understand from another post I read here that generally “Super” == “Win” == “Cmd” when it comes to keycode sent, just depends on what operating system you’re using how the keycap is usually marked?

2

Super key is oftentimes used in window manager actions, both in linux & windows. E.g. I shift window focus by Super+{h,j,k,l}, move windows by Super+Shift+{h,j,k,l} etc.

Note agent doesn’t stop you from mapping Super key to a full layer. On top of the keymap view in agent where it says “Layers”, click on the down arrow and you’ll see Super key listed there.

1 Like
3

Because from a technical standpoint, it is a modifier. It is handled exactly as shift or ctrl is. I.e., it has a bit reserved in the modifier byte of the basic keyboard usb report. It is reported to the PC and the pc decides what to do with it.

Mod and fn are not reported to the pc. They are just layer names that are processed by uhk.

3 Likes
4

Correct.

1 Like
5

Correct

Almost.

“keycode” != “scancode”. Keycodes are OS-internal abstraction. Scancodes are an abstraction between keyboard and the host PC.

(Of course this is a nitpick.)

Another name that is also used is Gui, which is especially relevant for our macro mod masks (like LG (left gui) or iLS (left shift with input mode composition mode)), since S is already taken by Shift and Win and Cmd are OS-specific.

2 Likes