- keyboard-layout(3).png (14.35 KiB) Viewed 4187 times
- keyboard-layout(4).png (14.86 KiB) Viewed 4187 times
Though, interestingly enough, if I use "gzdoom", and set the / key on my UK laptop, and copy that game over to my desktop with the American keyboard, the / doesn't register. I have to rebind it. But then it's incompatible with the UK laptop.BadCommand wrote: ↑16 Sep 2020, 16:072B is shared by both of those physical locations (and they are functionally the same). Of course, that depends on the scan code set - much more info to be found in John J. G. Savard's article: http://quadibloc.com/comp/scan.htm
The PS/2 scan codes are different in principle, but many keyboards actually send the [\|] code for the key between ['"] and [Return], because it's semantically the equivalent key, and manufacturers don't want to have different firmware for different regions.Inxie wrote: ↑16 Sep 2020, 16:28Though, interestingly enough, if I use "gzdoom", and set the / key on my UK laptop, and copy that game over to my desktop with the American keyboard, the / doesn't register. I have to rebind it. But then it's incompatible with the UK laptop.
But for 99.99% of the time, it's identical, 2B. But on that .01%, they are different.
Then what would be the proper PS/2 scancodes for these two keys to send in a board of this layout?
I can confirm this for USB HID Keyboard "usage codes".
Interesting. It should work in Windows according to MS docs and it should work in Linux according to source — but it will be treated just like ‘normal’ [\|].Findecanor wrote: ↑17 Sep 2020, 11:01I did once make my keyboard send that code, but it didn't work in Linux or MS-Windows.
If this is what I think, I have a Unicomp M122, it is the model with the ANSI/ISO hybrid (\| in on the right but with vertical enter, and long shift on the left), and I popped the shift and found that the membrane was still there despite no spring or plunger. Pressing it ALSO generated \|, just like the other key. This was on Windows. So my M122 technically has two \| keys which generate different USB scancodes (just like my gzdoom, that key hidden under shift would not respond to the same bindings as the other \| key), but Windows treated them both the same in nearly every program I used.kps wrote: ↑17 Sep 2020, 16:42Interesting. It should work in Windows according to MS docs and it should work in Linux according to source — but it will be treated just like ‘normal’ [\|].Findecanor wrote: ↑17 Sep 2020, 11:01I did once make my keyboard send that code, but it didn't work in Linux or MS-Windows.
I'm curious — can you tell that the keyboard actually sent different USB codes (e.g. with USBPcap)? My IBM M122 uses Set 3 and sends different code, but presumably the Unicomp PS/2 M122 uses Set 2 and doesn't.Inxie wrote: ↑17 Sep 2020, 17:29at I think, I have a Unicomp M122, it is the model with the ANSI/ISO hybrid (\| in on the right but with vertical enter, and long shift on the left), and I popped the shift and found that the membrane was still there despite no spring or plunger. Pressing it ALSO generated \|, just like the other key. This was on Windows.
The key beside left shift is completely different, even in the Windows scancode set (0x56). It just happens to be mapped to \| in some layouts.So my M122 technically has two \| keys which generate different USB scancodes (just like my gzdoom, that key hidden under shift would not respond to the same bindings as the other \| key), but Windows treated them both the same in nearly every program I used.
I will have to get back to you at least after 6pm EST (or am I in EDT now? I lost track), my mother is working from home and she's using the M122 currently.
Alright here we go.