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/techspecs | |
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/techspecs')
-rw-r--r-- | docs/source/techspecs/memory.rst | 18 |
1 files changed, 12 insertions, 6 deletions
diff --git a/docs/source/techspecs/memory.rst b/docs/source/techspecs/memory.rst index 260e39e566e..9d7eb3c1b29 100644 --- a/docs/source/techspecs/memory.rst +++ b/docs/source/techspecs/memory.rst @@ -126,7 +126,8 @@ A memory share can be created if it doesn’t exist in a memory map through that creator class. If it already exists it is just retrieved. That class behaves like a pointer but also has the ``target()``, ``length()``, ``bytes()``, ``endianness()``, -``bitwidth()`` and ``bytewidth()`` methods for share information. +``bitwidth()`` and ``bytewidth()`` methods for share information. The +desired size is specified in bytes. .. code-block:: C++ @@ -154,12 +155,17 @@ A memory bank is a named memory zone indirection that can be mapped in address spaces. It points to ``nullptr`` when created. ``configure_entry`` associates an entry number and a base pointer. ``configure_entries`` does the same for multiple consecutive entries -spanning a memory zone. Alternatively ``set_base`` sets the base for -entry 0 and selects it. +spanning a memory zone. -``set_entry`` allows to dynamically and efficiently select the current -active entry, ``entry()`` gets that selection back, and ``base()`` gets -the associated base pointer. +``set_base`` sets the base address for the active entry. If there are +no entries, entry 0 (zero) is automatically created and selected. Use +of ``set_base`` should be avoided in favour of pre-configured entries +unless there are an impractically large number of possible base +addresses. + +``set_entry`` dynamically and efficiently selects the active entry, +``entry()`` returns the active entry number, and ``base()`` gets the +associated base pointer. .. code-block:: C++ |