I used to have one of those old server keyboards. F13 was a combination of alt or shift or control combined with F1 through F12.
Tested it with the scan codes the thing produced (when every hacker still used a paper reference) so while promising, collisions will happen as you will not get new combos.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
This only applies if the operating system on the computer, like Microsoft Windows, attempts to switch the keyboard to Scan Code Set 2. Linux implementations typically choose to use Scan Code Set 3, if it is available, by default, and therefore a 122-key keyboard, under Linux, will behave more like a 101-key keyboard instead of like an 84-key keyboard. This, however, brings with it its own set of problems, because some less-expensive keyboards are known to have problems with their Scan Code Set 3 implementations.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I used to have one of those old server keyboards. F13 was a combination of alt or shift or control combined with F1 through F12.
Tested it with the scan codes the thing produced (when every hacker still used a paper reference) so while promising, collisions will happen as you will not get new combos.
Interesting as I haven’t had a collision (yet!)
I wonder if I have just been lucky, going to have to investigate now.
I don’t often say this but I really hope you are wrong! 😜🤣
Thank you for the heads up as some of those bindings are linked to some things that if say 2 ran at once it could cause havoc, much appreciated! ❤️
Your welcome, have you found any collisions yet?
quadibloc.com/comp/scan.htm has a lot of detail about it