diff options
author | 2022-06-11 21:47:19 +1000 | |
---|---|---|
committer | 2022-06-11 21:47:19 +1000 | |
commit | f47f9c3db3c7d20bea0526425cdbc469d5a10868 (patch) | |
tree | 4dd7ac860eb10169b511521eecb31b8760011434 /docs/source/advanced | |
parent | 5214d7f31c6e682315a7803484ade265130cfb6b (diff) |
ui, docs: Added menus to fill a couple of gaps, improved consistency. (#9915)
Added menus for controlling toggle inputs, and showing recognised input
devices and control state. Moved input menu options off main menu to a
submenu, as there are a lot of them now.
Moved menu heading drawing into base class, added headings to more
menus, and made headings more consistent with the menu items used to
reach them. Also made terminology more consistent.
Changed the default names for buttons and hat switches/D-pads to use
1-based numbering. DirectInput still returns 0-based button numbers for
some devices.
Removed local copy of MinGW xaudio2.h as it’s now included in the MSYS2
package. Also fixed building the DirectSound sound output module with
the SDL OSD on Windows - the Windows headers are sensitive to include
order.
Started adding documentation for menus, to hopefully help people find
menus they remember seeing but can't recall how to access.
For translators, this makes terminology more consistent. In particular:
* "Settings" is preferred over "configuration" in a number of places, as
the latter can be construed as referring specifically to settings
stored in .cfg files in the cfg_directory folder. Also, references to
saving machine configuration could be interpreted as relating to the
settings on the "Machine Configuration" menu.
* The controls on host input devices (e.g. keys, buttons, joystick axes)
are referred to as "controls", while emulated inputs are referred to
as "inputs".
* The menus for assigning host controls to emulated inputs are called
"input assignments" menus to distinguish them from other input
settings menus.
* Combinations of controls that can be assigned to emulated inputs are
referred to as "combinations" rather than "sequences".
* The potentially confusing term "ROM set" has been removed altogether.
Use "short name" to refer to a device or system's identifier.
* "System" is used in almost places to refer to a complete, runnable
system rather than "Machine".
* "Driver" is now only used to refer to source files where systems or
devices are defined - it is no longer used to refer to individual
systems.
* A few more menus have message context for the messages. This makes it
a bit easier to guess where the messages are used. It also means you
can use different translations in different places if necessary (e.g.
if the same English text should be translated differently as an item
in one menu and as a heading in another).
Diffstat (limited to 'docs/source/advanced')
-rw-r--r-- | docs/source/advanced/ctrlr_config.rst | 47 |
1 files changed, 24 insertions, 23 deletions
diff --git a/docs/source/advanced/ctrlr_config.rst b/docs/source/advanced/ctrlr_config.rst index f05a3d164b7..6fdeddc8a8a 100644 --- a/docs/source/advanced/ctrlr_config.rst +++ b/docs/source/advanced/ctrlr_config.rst @@ -41,8 +41,9 @@ Basic structure Controller configuration files follow a similar format to the system configuration files that MAME uses to save things like input settings and -bookkeeping data. This example shows the overall structure of a controller -configuration file: +bookkeeping data (created in the folder specified using the +:ref:`cfg_directory option <mame-commandline-cfgdirectory>`). This example +shows the overall structure of a controller configuration file: .. code-block:: XML @@ -127,21 +128,21 @@ left and right arrows will be replaced with the numeric 8, 2, 4 and 6 keys on the numeric keypad, respectively. Note that substitutions specified using ``remap`` elements only apply to inputs -that use MAME’s default assignment for the control type. That is, they only -apply to default assignments for control types set in the “Inputs (general)” -menu. They *do not* apply to default input assignments set in driver/device I/O -port definitions (using the ``PORT_CODE`` macro). +that use MAME’s default assignment for the input type. That is, they only apply +to default assignments for control types set in the “Input Assignments +(general)” menus. They *do not* apply to default control assignments set in +driver/device I/O port definitions (using the ``PORT_CODE`` macro). MAME applies ``remap`` elements found inside any applicable ``system`` element. .. _ctrlrcfg-typeoverride: -Overriding defaults by control type ------------------------------------ +Overriding defaults by input type +--------------------------------- Use ``port`` elements with ``type`` attributes but without ``tag`` attributes to -override the default host input assignments for a controls: +override the default control assignments for emulated inputs by type: .. code-block:: XML @@ -183,10 +184,10 @@ P1 Button 4 (Player 1 Controls) X key, or joystick 1 button 4 Note that this will only apply for inputs that use MAME’s default assignment for -the control type. That is, ``port`` elements without ``tag`` attributes only -override default assignments for control types set in the “Inputs (general)” -menu. They *do not* override default input assignments set in driver/device I/O -port definitions (using the ``PORT_CODE`` macro). +the input type. That is, ``port`` elements without ``tag`` attributes only +override default assignments for control types set in the “Input Assignments +(general)” menus. They *do not* override default control assignments set in +driver/device I/O port definitions (using the ``PORT_CODE`` macro). MAME applies ``port`` elements without ``tag`` attributes found inside any applicable ``system`` element. @@ -194,22 +195,22 @@ applicable ``system`` element. .. _ctrlrcfg-ctrloverride: -Overriding defaults for specific controls ------------------------------------------ +Overriding defaults for specific inputs +--------------------------------------- Use ``port`` elements with ``tag``, ``type``, ``mask`` and ``defvalue`` -attributes to override defaults for specific controls. These ``port`` elements +attributes to override defaults for specific inputs. These ``port`` elements should only occur inside ``system`` elements that apply to particular systems or source files (i.e. they should not occur inside ``system`` elements where the -``name`` attribute has the value ``default``). The default host input -assignments can be overridden, as well as the toggle setting for digital -controls. +``name`` attribute has the value ``default``). The default control assignments +can be overridden, as well as the toggle setting for digital inputs. The ``tag``, ``type``, ``mask`` and ``defvalue`` are used to identify the affected input. You can find out the values to use for a particular input by -changing its assigned host input, exiting MAME, and checking the values in the -system configuration file. Note that these values are not guaranteed to be -stable, and may change between MAME versions. +changing its control assignment, exiting MAME, and checking the values in the +system configuration file (created in the folder specified using the +:ref:`cfg_directory option <mame-commandline-cfgdirectory>`). Note that these +values are not guaranteed to be stable, and may change between MAME versions. Here’s an example that overrides defaults for 280-ZZZAP: @@ -225,5 +226,5 @@ Here’s an example that overrides defaults for 280-ZZZAP: </input> </system> -This sets the host inputs to steer left and right to the K and J keys, +This sets the controls to steer left and right to the K and J keys, respectively, and disables the toggle setting for the gear shift input. |