| Re: [hatari-devel] Keyboard layout and two small bugs |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Keyboard layout and two small bugs
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Sat, 12 May 2018 00:03:02 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1526076184; bh=zTMrKDvV6emxxUFyxvrzPUyZUtnqdM3utfk0z1Z0wFA=; h=Date:From:To:Subject:From; b=G5ab5nS69Gxk8x9KYeT/2it7bDQtJb70+XlH7kthtTqQIVhP52AWk8V7syjmW956A 83Br9Z1u3Da/+jpQh0paCiaXZdxan7wzxyb0dFm8y4VK9uSQlQM4VeZt25QkYMIfbr 7VIBCrbBPO8HOybAmP+4XWacdEqEZuHINTy2myqMBnlTiQ6CVIFriVqFr8P+UMLMIX 5yrYWL7U2UkC0pURwNygV8omMn2VgSBmMiAjjGp+TUcOv06onisVpxQumKpcsJNsQ+ DiUQ1Fkpb8XvIe5QPK59VRF0Ymee+Nit4xGsyLfmMazd7nqsd2t3LBZ8vSj4/7+7Yj WO1iOkCUC9jIA==
Am Sun, 6 May 2018 14:10:07 +0200
schrieb Christian Zietz <czietz@xxxxxxx>:
> Christian Zietz schrieb:
>
> > It is with the SDL2 build, the "official" Windows binary as
> > available on <http://download.tuxfamily.org/hatari/2.1.0/>. I'm
> > afraid I've given up building Hatari from source under Windows, at
> > least for the time being...
What problems did you encounter? It should work if you use MinGW with
MSYS ... and I once even compiled it with Visual Studio (though that
was quite a pain, indeed).
> I used the "--trace keymap" option suggested by Eero in the other post
> to debug the issues reported by me:
>
> a) Symbolic keymapping: "´"/"`" key does not work. Pressing it
> produces the following output:
> key down: sym=180 scan=46 mod=0x0 name='┬┤'
> key map: sym=0xb4 to ST-scan=0xff
>
> A keymap.txt just containing the line...
> 180,13
> ... can thus fix this issue, since 13 (=0x0d) is the scancode of the
> corresponding key on the Atari keyboard.
Right, that entry was simply missing, fixed now.
> b) Scancode mapping: "<"/">" key and "#"/"'" key map to the same Atari
> key. Pressing "<"/">" (left of the Y key on the German keyboard)...
> key down: sym=60 scan=100 mod=0x0 name='<'
> key map: sym=0x3c to ST-scan=0x60
> Pressing "#"/"'"...
> key down: sym=35 scan=49 mod=0x0 name='#'
> key map: sym=0x23 to ST-scan=0x60
>
> The latter should probably be mapped to ST-scan 0x29 (= "#" on the
> German keyboard).
That one is a little bit more complicated. The scancode is called
SDL_SCANCODE_BACKSLASH and I've seen also some pictures where the
backslash seems to be on the key with the scancode 0x60 on US key-
boards. However, we also already map SDL_SCANCODE_NONUSBACKSLASH
to that key, and do not have any entry for 0x29 yet. So I think
it's likely ok to map BACKSLASH to 0x29 and use NONUSBACKSLASH for
0x60, thus I also included now that change. I'd appreciate some
testing from folks with a US keyboard now to see whether they
still can type all keys or whether they miss something in the
scancode mapping mode...
Thomas