| 1 |
Keyboard related settings in hardwareconfig.xml |
| 2 |
|
| 3 |
In section <PPI>...</PPI>: |
| 4 |
|
| 5 |
Setting name: key_ghosting |
| 6 |
Default value: true |
| 7 |
Description: |
| 8 |
If true, the emulator will press 'ghost' keys when user presses multiple keys |
| 9 |
at once on crossing rows/columns of the keyboard matrix. |
| 10 |
It must be set to true for all MSX models that suffer from this hardware problem |
| 11 |
|
| 12 |
Setting name: key_ghosting_sgc_protected |
| 13 |
Default value: true |
| 14 |
Description: |
| 15 |
If true, the key ghosting routine in the emulator will protect Shift, Graph |
| 16 |
and Code keys from key-ghosting. According to schematics and tests, several |
| 17 |
European machines have such a protection but some Japanese machines don't have it. |
| 18 |
In the protected machines, those three keys are connected to the keyboard matrix |
| 19 |
via a Diode, which prevents that pressing those two or more of those three |
| 20 |
keys together would ghost to other rows/columns via the 'character key' that you press |
| 21 |
in combination with them. |
| 22 |
|
| 23 |
|
| 24 |
Setting name: keyboard_type |
| 25 |
Default value: int |
| 26 |
Description: |
| 27 |
Indicates which type of keyboard the MSX has. It is used to load a file that |
| 28 |
maps unicode characters to the appropriate key-combinations on the MSX. |
| 29 |
The file-name will be: unicodemaps/unicode.<keyboard_type> |
| 30 |
|
| 31 |
Setting name: has_keypad |
| 32 |
Default value: true |
| 33 |
Description: |
| 34 |
Indicates if the emulated MSX model has a numeric keypad. If true, key-presses |
| 35 |
on the host numeric keypad will be mapped to corresponding key-presses on |
| 36 |
the MSX's numeric keypad. |
| 37 |
If false, key-presses on the host numeric keypad will be ignored. User can |
| 38 |
overrule this with a setting in the settings.xml file. |
| 39 |
|
| 40 |
Setting name: code_kana_locks |
| 41 |
Default value: false |
| 42 |
Description: |
| 43 |
When true, the the CODE/KANA key locks on the emulated machine. Is in practice the |
| 44 |
behaviour of all Japanese MSX models and of the VG8010. |
| 45 |
If false, CODE/KANA key does not lock (e.g. it is only active as long as the key is |
| 46 |
pressed) |
| 47 |
|
| 48 |
In section <PSG>...</PSG>: |
| 49 |
Setting name: keyboardlayout |
| 50 |
Default value: <empty> |
| 51 |
Description: |
| 52 |
Indicates if the "keyboard mode" flag (bit 6 on PSG register 14) must be set. |
| 53 |
It will be set to "1" if keyboardlayout is JIS. Otherwise it will be 0. |
| 54 |
In practice, this bit is only read by the Japanese ROM-BIOS to determine |
| 55 |
the keyboard layout; Japanese-JIS or Japanese-ANSI |
| 56 |
See http://map.tni.nl/articles/keymatrix.php for further details about |
| 57 |
Japanese keyboard layouts. |
| 58 |
Note that this setting is ignored by the keyboard driver of openMSX. The |
| 59 |
keyboard driver only looks at the keyboard_type parameter in the PPI |
| 60 |
section to determine which unicode to keycombination mapping to apply. |
| 61 |
|
| 62 |
|
| 63 |
Keyboard related settings are described in doc/commands.html |