1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
# This is an example for a keyboard mapping file that can be used in Hatari
# by loading it from the keyboard setup dialog.
#
# Lines starting with a '#' or with a ';' are comments. All other lines
# should contain exactly one key name and a scancode, separated by a comma.
# Comment characters can be quoted with '\#' and '\;'.
#
# The key name is the libSDL symbolic name of the key, see the following
# URL for a list: https://wiki.libsdl.org/SDL_Keycode
# You can also use the symbolic keycode value instead of the name, which
# you can get with the "--trace keymap" output from Hatari, for example.
#
# The given host key will be mapped to the ST key which is specified by
# second number - the ST scan code of the key. "--trace keymap" output
# shows the already mapped scan code.
#
# All numbers should be given as decimals (not hexadecimals).
#
# Note that using keyboard mapping file causes Hatari to use symbolic
# key mapping. Symbolic key mapping does not work with so called "dead"
# keys.
#
# Scan codes for Atari keyboard key positions in different TOS versions
# are documented here:
# http://tho-otto.de/keyboards/
#
# tests/keymap/ directory contains programs to discover/test the PC SDL
# and Atari scan code values. Hatari's default PC key code -> ST scan
# code mappings are in src/keymap.c source file.
#
# Example: If you want to get the 'y' and 'z' keys right with a german TOS
# ROM, you can use the following two lines to map the PC keys to the right
# ST scan codes:
Y,44
Z,21
|
