summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
author Vas Crabb <vas@vastheman.com>2020-12-31 02:46:10 +1100
committer Vas Crabb <vas@vastheman.com>2020-12-31 02:46:10 +1100
commitd85735634cd7baca5fdf9f15ebb61baa0703c71a (patch)
tree82da58d821cb1957f86b2c7b797ddbd29b35a18f
parentf429695d4f007c1670d5920c91690fc09ea186f6 (diff)
version bump for 0.227, some documentation clean-upmame0227
-rw-r--r--android-project/app/src/main/AndroidManifest.xml4
-rw-r--r--docs/source/conf.py4
-rw-r--r--docs/source/techspecs/luaengine.rst4
-rw-r--r--docs/source/techspecs/luareference.rst5
-rw-r--r--docs/source/usingmame/commonissues.rst30
-rw-r--r--makefile4
6 files changed, 32 insertions, 19 deletions
diff --git a/android-project/app/src/main/AndroidManifest.xml b/android-project/app/src/main/AndroidManifest.xml
index d0afb50b5aa..d23fa226f49 100644
--- a/android-project/app/src/main/AndroidManifest.xml
+++ b/android-project/app/src/main/AndroidManifest.xml
@@ -4,8 +4,8 @@
-->
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="org.mamedev.mame"
- android:versionCode="226"
- android:versionName="0.226"
+ android:versionCode="227"
+ android:versionName="0.227"
android:installLocation="auto">
<!-- OpenGL ES 2.0 -->
diff --git a/docs/source/conf.py b/docs/source/conf.py
index 1a9730e288f..4cb7ff4b3aa 100644
--- a/docs/source/conf.py
+++ b/docs/source/conf.py
@@ -63,9 +63,9 @@ copyright = u'2020, MAMEdev Team'
# built documents.
#
# The short X.Y version.
-version = '0.217'
+version = '0.227'
# The full version, including alpha/beta/rc tags.
-release = '0.217'
+release = '0.227'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
diff --git a/docs/source/techspecs/luaengine.rst b/docs/source/techspecs/luaengine.rst
index 5d3565af214..5e97d4e3885 100644
--- a/docs/source/techspecs/luaengine.rst
+++ b/docs/source/techspecs/luaengine.rst
@@ -90,7 +90,7 @@ Let’s first run MAME in a terminal to reach the Lua console:
/ /
/ _/
- mame 0.226
+ mame 0.227
Copyright (C) Nicola Salmoria and the MAME team
Lua 5.3
@@ -113,7 +113,7 @@ You can check at runtime which version of MAME you are running, with:
::
[MAME]> print(emu.app_name() .. " " .. emu.app_version())
- mame 0.226
+ mame 0.227
We now start exploring screen related methods. First, let's enumerate available
screens:
diff --git a/docs/source/techspecs/luareference.rst b/docs/source/techspecs/luareference.rst
index d15c74efe0b..0dd14ef45cf 100644
--- a/docs/source/techspecs/luareference.rst
+++ b/docs/source/techspecs/luareference.rst
@@ -47,9 +47,6 @@ c:at(i)
Returns the value at the 1-based index ``i``, or ``nil`` if it is out of
range.
c:find(v)
- Returns the key for item ``v``, or ``nil`` if it is not in the collection.
- The key is what you would pass to the index operator to get the value.
-c:find(v)
Returns the key for item ``v``, or ``nil`` if it is not in the container.
The key is what you would pass to the index operator to get the value.
c:index_of(v)
@@ -1317,7 +1314,7 @@ Properties
^^^^^^^^^^
map.spacenum (read-only)
- The address space number of the address space the map is associated with
+ The address space number of the address space the map is associated with.
map.device (read-only)
The device that owns the address space the map is associated with.
map.unmap_value (read-only)
diff --git a/docs/source/usingmame/commonissues.rst b/docs/source/usingmame/commonissues.rst
index 7fba001d86b..8249979aa91 100644
--- a/docs/source/usingmame/commonissues.rst
+++ b/docs/source/usingmame/commonissues.rst
@@ -70,7 +70,7 @@ There's still room for improvements in MAME's speed, but chances are that if you
Why do my Neo Geo ROMs no longer work? How do I get the Humble Bundle Neo Geo sets working?
-------------------------------------------------------------------------------------------
-Recently the Neo Geo BIOS was updated to add a new version of the Universal BIOS. This was done between 0.171 and 0.172, and results in an error trying to load Neo Geo games with an un-updated **neogeo.zip** set.
+Recently the Neo Geo BIOS was updated to add a new version of the Universe BIOS. This was done between 0.171 and 0.172, and results in an error trying to load Neo Geo games with an un-updated **neogeo.zip** set.
This also affects the Humble Bundle set: the games themselves are correct and up to date as of MAME 0.173 (and most likely will remain so) though you'll have to pull the ROM set .ZIP files out of the package somehow yourself. However, the Neo Geo BIOS set (**neogeo.zip**) included in the Humble Bundle set is incomplete as of the 0.172 release of MAME.
@@ -252,7 +252,11 @@ Unofficial builds of MAME may have supported it for varying amounts of time as w
What happened to the MAME support for autofire?
-----------------------------------------------
-A Lua plugin with providing enhanced autofire support was added in MAME 0.210; the old built-in autofire functionality was removed in MAME 0.216. This new plugin has more functionality than the previous built-in autofire in older MAME revisions; for instance, you can specify an alternate button for the autofire.
+A Lua plugin with providing enhanced autofire support was added in MAME 0.210,
+and the old built-in autofire functionality was removed in MAME 0.216. This
+new plugin has more functionality than the built-in autofire feature in older
+version of MAME; for example, you can configure an alternate buttons for
+different for autofire rates.
You can enable and configure the new autofire system with the following steps:
@@ -262,13 +266,25 @@ You can enable and configure the new autofire system with the following steps:
The setting will be automatically saved for future use.
-Once you're inside a system of your choice, bring up the MAME menu (typically the **tab** key) and go into *plugin options*. From there, depending on whether you have an existing autofire button set up or not, it will either show the existing entry/entries or it will ask you to select the input for the autofire.
+Once you’re running a system of your choice, bring up the MAME menu (using the
+**Tab** key by default), select *Plugin Options* and then select *Autofire*.
+From there, depending on whether you have an existing autofire button set up or
+not, it will either show the existing entry/entries or it will ask you to select
+the input for the autofire.
-Typically you'll be choosing *P1 Button 1* for systems like Galaga, Alcon, or the like. The *Hotkey* is the button you press for the autofire effect. This can be any keyboard key or joystick button that you wish. As of 0.216, mouse buttons are not yet supported.
+Typically you’ll be choosing *P1 Button 1* for systems like Galaga, Alcon, and
+the like. The *Hotkey* is the button you press for the autofire effect. This
+can be any keyboard key or joystick button you wish. As of 0.216, mouse buttons
+are not yet supported.
-*On frames* and *Off frames* are how long to leave the button pressed and unpressed in number of frames. Some systems do not read the inputs fast enough for 1 and 1 to be usable. You may need to try 2 and 2 (e.g. Alcon) or other combinations. Try fine-tuning these to your taste.
+*On frames* and *Off frames* are how long to leave the button pressed and
+released in number of frames. Some systems do not read the inputs fast enough
+for 1 and 1 to be usable. You may need to try 2 and 2 (e.g. Alcon) or other
+combinations. Try fine-tuning these to your taste.
-The autofire configuration for that system will be saved in a ``systemname.cfg`` (e.g. ``alcon.cfg``) file inside the Autofire folder for future use. Each system will have its own configuration.
+The autofire configuration for that system will be saved in a ``systemname.cfg``
+file (e.g. ``alcon.cfg``) inside the Autofire folder for future use. Each
+system will have its own configuration.
Note that if you set the autofire button to an input button that's also defined in MAME's inputs for the running system, you may get unexpected results-- Using Gradius as an example:
@@ -292,4 +308,4 @@ MAME supports both G-Sync and FreeSync right out of the box for Windows and Linu
* Turning VSync on is suggested in general with G-Sync and FreeSync.
* Low Latency Mode will not affect MAME performance with G-Sync/FreeSync.
-The effects of G-Sync and FreeSync will be most noticeable in drivers that run at refresh rates that are very different from normal PC refresh rates. For instance, the first three *Mortal Kombat* titles run at 54.706841Hz. \ No newline at end of file
+The effects of G-Sync and FreeSync will be most noticeable in drivers that run at refresh rates that are very different from normal PC refresh rates. For instance, the first three *Mortal Kombat* titles run at 54.706841Hz.
diff --git a/makefile b/makefile
index a524d1d210f..765333c747d 100644
--- a/makefile
+++ b/makefile
@@ -1737,14 +1737,14 @@ endif
ifeq (posix,$(SHELLTYPE))
$(GENDIR)/version.cpp: makefile $(GENDIR)/git_desc | $(GEN_FOLDERS)
- @echo '#define BARE_BUILD_VERSION "0.226"' > $@
+ @echo '#define BARE_BUILD_VERSION "0.227"' > $@
@echo 'extern const char bare_build_version[];' >> $@
@echo 'extern const char build_version[];' >> $@
@echo 'const char bare_build_version[] = BARE_BUILD_VERSION;' >> $@
@echo 'const char build_version[] = BARE_BUILD_VERSION " ($(NEW_GIT_VERSION))";' >> $@
else
$(GENDIR)/version.cpp: makefile $(GENDIR)/git_desc | $(GEN_FOLDERS)
- @echo #define BARE_BUILD_VERSION "0.226" > $@
+ @echo #define BARE_BUILD_VERSION "0.227" > $@
@echo extern const char bare_build_version[]; >> $@
@echo extern const char build_version[]; >> $@
@echo const char bare_build_version[] = BARE_BUILD_VERSION; >> $@