@hitthetowpath

'Menu' is, however, already a different key, usually to be found next to the right GUI key at location A11 on the #ISO9995 layout.

The 'Super' key from the 1970s Space-Cadet keyboard long pre-dates the 'Windows' key from Microsoft's 1990s Windows keyboards. It is indeed a bit misleading to conflate the two, and confuses the Hell out of novices looking for 'Super' when their doco says to use it.

The irony of using 'Super' as the name is twofold. First: The Space-Cadet keyboard that people wistfully want only had 100 keys, fewer than even an old 101-key U.S.A. Model M keyboard, let alone a modern 124-key Windows keyboard, with its Internet+multimedia keys and 8 electrically and wire-protocol distinct modifiers.

Second: Things like the USB HID specification avoid trademarks like 'Windows' & 'Apple' anyway, calling the two keys (usages 0xE1 and 0xE7 on the keyboard page) the left and right 'GUI' keys.

#ComputerKeyboards #retrocomputing #USBHID #HumanInputDevices

The #nosh Guide has a whole chapter going into a lot more detail on HID configuration; which can range at the administrator's discretion from explicitly choosing accept-all-HIDs to a strong stance on supernumerary, misbehaving, or downright malicious #HumanInputDevices.

Given that I was one of several people who proposed going this way in the 1990s, it is long past the time that recompiling one's kernel was the way to choose what #HumanInputDevices to trust.

http://jdebp.info/Softwares/nosh/guide/user-virtual-terminal-configuration.html

#uservt

@Jayenkai

It always is. Fn is not a genuine on-the-wire key and what it does depends from the whim of the keyboard manufacturer.

* https://jdebp.uk/FGA/fn-key-is-local.html

#HumanInputDevices #FnKey

@Jayenkai @WiteWulf

On laptops, I was encouraged off mice the first time that I experienced a Thinkpad with that little rubbery button thing. I was fully weaned when I got an Aspire with a touchpad years ago. The widescreen Aspires have enough width to fit a proper numeric keypad in, too.

I've even been weaned off of mice for desktops, since then. It's trackballs for desktops, now.

#HumanInputDevices #NumericKeypads

@matty

Not nearly enough modifiers added there for what is obviously a very simple action. They should definitely require that you simultaneously pull the clutch lever too. (-:

And if "Meta" isn't Alt for them, what key *is* it?

One has to love a "universal format" that uses a key that is pretty much universally *not present on* keyboards, and is variously understood as a range of different approximations.

Whose notice is this?

#emacs #ComputerKeyboards #HumanInputDevices

https://jdebp.uk/Humour/exiting-emacs.html

@cazabon

My code (because of the way that #USB #HumanInputDevices work) has to store button/key press information as an array of boolean flags in two distinct places (1 local and 1 shared), so of course it has array bounds checks.

The Elecom Deft's report descriptor bug had me looking for quite a time for where I'd accidentally put the wrong bounds check on mouse button values.

#nosh #uservt

@cazabon

I don't really have a wide enough sample set for that conclusion.

The aim of the collection wasn't to cross-check manufacturers; it was to test that my softwares could handle things such as devices that have no NumLock key, the 104/105/106/107/109-key layouts, "office"/"multimedia" keyboards, and devices that report being multiple keyboards and mice at once.

So it's annoying when a keypress/button not registering turns out not to be my bug.

#USB #HumanInputDevices

@cstross

The best thing about things like that would be if they persuaded every operating system to handle the Unicode usage page (0x10) for USB HIDs, something that custom wacky keyboard builders have been asking about on WWW fora for a decade.

And can we just declare by fiat that it is de facto UTF-16 whatever the spec says?

Hmm. I must put this on the check list for my keyboard driver, I suppose. Practice what one preaches and all that. (-:

@attoparsec

#USB #HumanInputDevices