Annotation of hatari/doc/keymap-sample.txt, revision 1.1.1.6

1.1       root        1: # This is an example for a keyboard mapping file that can be used in Hatari
                      2: # by loading it from the keyboard setup dialog.
                      3: #
1.1.1.6 ! root        4: # Lines starting with a '#' or with a ';' are comments. All other lines
        !             5: # should contain exactly one key name and a scancode, separated by a comma.
        !             6: # Comment characters can be quoted with '\#' and '\;'.
1.1.1.4   root        7: #
1.1.1.6 ! root        8: # The key name is the libSDL symbolic name of the key, see the following
        !             9: # URL for a list: https://wiki.libsdl.org/SDL_Keycode
        !            10: # You can also use the symbolic keycode value instead of the name,
        !            11: # which you can get with the "--trace keymap" output from Hatari, for
        !            12: # example, but note that the values are different between SDL1 and SDL2
        !            13: # and thus they are not portable.
1.1.1.4   root       14: #
1.1.1.6 ! root       15: # The given host key will be mapped to the ST key which is specified by
1.1.1.5   root       16: # second number - the ST scan code of the key.  "--trace keymap" output
                     17: # shows the already mapped scan code.
1.1       root       18: #
1.1.1.4   root       19: # tests/keymap/ directory contains programs to discover/test the PC SDL
1.1.1.5   root       20: # and Atari scan code values.  Hatari's default PC key code -> ST scan
                     21: # code mappings are in src/keymap.c source file.
1.1.1.4   root       22: #
1.1       root       23: # Example: If you want to get the 'y' and 'z' keys right with a german TOS
                     24: # ROM, you can use the following two lines to map the PC keys to the right
                     25: # ST scan codes:
1.1.1.6 ! root       26: Y,44
        !            27: Z,21

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.