Keymaps: Difference between revisions
Jump to navigation
Jump to search
m (Created page with 'this page is under construction ~~~~ * host (pc) keyboards have a "machine" and "locale" type. the "machine" type is defined by the port (windows, x11, sdl etc) and the "locale"…') |
mNo edit summary |
||
| Line 1: | Line 1: | ||
this page is under construction [[User:Gpz|Gpz]] 22:39, 24 June 2012 (UTC) | this page is under construction [[User:Gpz|Gpz]] 22:39, 24 June 2012 (UTC) | ||
=== considerations === | |||
* host (pc) keyboards have a "machine" and "locale" type. the "machine" type is defined by the port (windows, x11, sdl etc) and the "locale" type by what type of keyboard the user has connected (we currently have different maps for US and DE keyboards) | * host (pc) keyboards have a "machine" and "locale" type. the "machine" type is defined by the port (windows, x11, sdl etc) and the "locale" type by what type of keyboard the user has connected (we currently have different maps for US and DE keyboards) | ||
* emulated keyboards have a "positional" and a "symbolic" type. the former referring to the actual hardware (keyboard matrix and key positions) and the later referring to what is actually written on the keycaps. (for example the localized c128 keyboards would all have the same "positional" type, but different "symbolic" types. | * emulated keyboards have a "positional" and a "symbolic" type. the former referring to the actual hardware (keyboard matrix and key positions) and the later referring to what is actually written on the keycaps. (for example the localized c128 keyboards would all have the same "positional" type, but different "symbolic" types. | ||
* we support two fundamentally different type of keyboard mappings, "symbolic" and "positional". | |||
==implementation== | |||
=== resources === | |||
* "KeymapIndex" - selects active keymap (0: symbolic, 1: positional, 2: user defined symbolic, 3: user defined positional) | |||
* "KeymapSymFile" - name of the keymap to use for symbolic mapping (automatically set) | |||
* "KeymapPosFile" - name of the keymap to use for positional mapping (automatically set) | |||
* "KeymapUserSymFile" - name of user defined symbolic keymap | |||
* "KeymapUserPosFile" - name of user defined positional keymap | |||
---- | |||
=== remove === | === remove === | ||
resources: KeymapSymDeFile | resources: KeymapSymDeFile | ||
options: -symdekeymap, -buksymkeymap, -bukposkeymap, -grsymkeymap, -grposkeymap, -bdesymkeymap, -bdeposkeymap | options: -symdekeymap, -buksymkeymap, -bukposkeymap, -grsymkeymap, -grposkeymap, -bdesymkeymap, -bdeposkeymap | ||
Revision as of 00:53, 25 June 2012
this page is under construction Gpz 22:39, 24 June 2012 (UTC)
considerations
- host (pc) keyboards have a "machine" and "locale" type. the "machine" type is defined by the port (windows, x11, sdl etc) and the "locale" type by what type of keyboard the user has connected (we currently have different maps for US and DE keyboards)
- emulated keyboards have a "positional" and a "symbolic" type. the former referring to the actual hardware (keyboard matrix and key positions) and the later referring to what is actually written on the keycaps. (for example the localized c128 keyboards would all have the same "positional" type, but different "symbolic" types.
- we support two fundamentally different type of keyboard mappings, "symbolic" and "positional".
implementation
resources
- "KeymapIndex" - selects active keymap (0: symbolic, 1: positional, 2: user defined symbolic, 3: user defined positional)
- "KeymapSymFile" - name of the keymap to use for symbolic mapping (automatically set)
- "KeymapPosFile" - name of the keymap to use for positional mapping (automatically set)
- "KeymapUserSymFile" - name of user defined symbolic keymap
- "KeymapUserPosFile" - name of user defined positional keymap
remove
resources: KeymapSymDeFile
options: -symdekeymap, -buksymkeymap, -bukposkeymap, -grsymkeymap, -grposkeymap, -bdesymkeymap, -bdeposkeymap