summaryrefslogtreecommitdiffstatshomepage
path: root/docs/source/plugins
diff options
context:
space:
mode:
author Vas Crabb <vas@vastheman.com>2025-06-25 03:56:09 +1000
committer Vas Crabb <vas@vastheman.com>2025-06-25 03:56:09 +1000
commitaf10f3f21cc03a6dcbfde08850f640e26d9cbb9f (patch)
tree05895657ff111b3f0ad10640f6ad0cb253cdfadb /docs/source/plugins
parent72251989ad8df6f6a1f401c56a1b02ec60938e25 (diff)
Various fixes:
ui: The new menus were unusable with a touchscreen, and not conducive to localisation. It's still not possible to add sound routes with a touchscreen, but at least it's possible to configure routes that exist. emu/sound.cpp: Fixed localisation issues, less temporary objects. emu/audio_effects: Fixed some localisation issues. plugins/autofire, plugins/inputmacro: Allow deleting autofire buttons or input macros without needing to use the UI Clear input. ui/selmenu.cpp, ui/imgcntrl.cpp: Use terse messages for bad media. Making these messages longer hasn't reduced support burden. Adding the version will just perpetuate the myth that you need to redownload all your ROMs for every release. ui/ui.cpp: Allow info screens to be dismissed by mouse clicks or touches. ui/sliders.cpp: Hiding the menu should preserve state. This is a design choice. sound: Avoid anything that could possibly depend on static initialisation order across transaltion units. Allow speaker position names to be localised. sound/none.cpp: Don't pretend it can create output streams.
Diffstat (limited to 'docs/source/plugins')
-rw-r--r--docs/source/plugins/autofire.rst16
-rw-r--r--docs/source/plugins/inputmacro.rst10
2 files changed, 20 insertions, 6 deletions
diff --git a/docs/source/plugins/autofire.rst b/docs/source/plugins/autofire.rst
index 2cb974626d2..5dd8eb21cf0 100644
--- a/docs/source/plugins/autofire.rst
+++ b/docs/source/plugins/autofire.rst
@@ -44,11 +44,10 @@ The options for adding a new autofire button or modifying an existing autofire
button are the same.
Select **Input** to set the emulated button that you want to simulate pressing
-repeatedly. Currently, only player buttons are supported. Typically you’ll set
-this to the primary fire button for shooting games. This is most often *P1
-Button 1* or the equivalent for another player, but it might have a
-different name. On Konami’s Gradius games, *P1 Button 2* is the primary fire
-button.
+repeatedly. Only digital inputs are supported. Typically you’ll set this to
+the primary fire button for shooting games. This is most often *P1 Button 1*
+or the equivalent for another player, but it might have a different name. On
+Konami’s Gradius games, *P1 Button 2* is the primary fire button.
Select **Hotkey** to set the control (or combination of controls) you’ll use to
activate the autofire button. This can be any combination that MAME supports
@@ -75,6 +74,13 @@ When modifying an existing autofire button, select **Done** or press the UI
Cancel key to return to the list of autofire buttons. Changes take effect
immediately.
+When modifying an existing autofire button, select **Delete** to delete the
+autofire button. The autofire button will be deleted immediately when you
+select **Delete** without requiring additional confirmation. You can also
+delete an autofire button by highlighting it in the list of autofire buttons
+and pressing the UI Clear key (Del/Delete/Forward Delete on the keyboard by
+default).
+
.. _plugins-autofire-notes:
diff --git a/docs/source/plugins/inputmacro.rst b/docs/source/plugins/inputmacro.rst
index 959faa05fbe..c83e9e00de6 100644
--- a/docs/source/plugins/inputmacro.rst
+++ b/docs/source/plugins/inputmacro.rst
@@ -24,7 +24,9 @@ their activation sequences (initially there will be no input macros configured).
Select a macro to edit it, or choose **Add macro** to set up a new input macro.
See :ref:`plugins-inputmacro-settings` for details on editing input macros. You
can delete an input macro by highlighting it in the menu and pressing the UI
-Clear key (Del/Delete/Forward Delete on the keyboard by default).
+Clear key (Del/Delete/Forward Delete on the keyboard by default). You can also
+delete a macro by selecting the macro to edit it and then selecting **Delete
+macro** from the menu.
Input macros are saved in the **inputmacro** folder in the plugin data folder
(see the :ref:`homepath option <mame-commandline-homepath>`). A file is created
@@ -119,6 +121,12 @@ new macro.
When editing an existing macro, select **Done** or press the UI Back key to
return to the list of input macros. Changes take effect immediately.
+When editing an existing macro, select **Delete macro** to delete the macro.
+The macro will be deleted immediately when you select **Delete macro** without
+requiring additional confirmation. You can also delete a macro by highlighting
+it in the list of macros and pressing the UI Clear key (Del/Delete/Forward
+Delete on the keyboard by default).
+
.. _plugins-inputmacro-examples: