update doc for reordered GameInfoDialog

This commit is contained in:
Thomas Jentzsch 2019-08-11 15:56:48 +02:00
parent 1d9aafbd60
commit cbbc40aa0e
6 changed files with 171 additions and 176 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.7 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.0 KiB

After

Width:  |  Height:  |  Size: 4.5 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.9 KiB

View File

@ -2890,7 +2890,7 @@
<p><b>Game Properties</b> dialog:</p> <p><b>Game Properties</b> dialog:</p>
<table border="5" cellpadding="2" frame="box" rules="none"> <table border="5" cellpadding="2" frame="box" rules="none">
<tr> <tr>
<td><img src="graphics/options_gameinfo.png"></td> <td><img src="graphics/options_gameinfo_emulation.png"></td>
<td>&nbsp;&nbsp;&nbsp;&nbsp;</td> <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
<td valign="top"><br>This dialog allows you to change all ROM properties <td valign="top"><br>This dialog allows you to change all ROM properties
as described in <b>Advanced Configuration - <a href="#Properties">Game Properties</a></b>. as described in <b>Advanced Configuration - <a href="#Properties">Game Properties</a></b>.
@ -3676,58 +3676,8 @@ Ms Pac-Man (Stella extended codes):
<p>Each block in a property file consists of a set of properties for a single <p>Each block in a property file consists of a set of properties for a single
game. Stella supports the properties described below:</p> game. Stella supports the properties described below:</p>
<a><img src="graphics/options_gameinfo.png"></a> <a><img src="graphics/options_gameinfo_emulation.png"></a>
<table CELLSPACING="10"> <table CELLSPACING="10">
<tr>
<td VALIGN="TOP"><i>Cartridge.MD5:</i></td>
<td>Indicates the MD5 checksum of the ROM image as a
string of hexadecimal digits. Stella uses this property while
attempting to match a game with its block of properties. If the
value of the property matches the MD5 checksum of the ROM image then
Stella uses that block of properties for the game. You can use the
GNU md5sum program, which is included with most Linux distributions,
to calculate the MD5 checksum of a ROM image.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.Manufacturer:</i></td>
<td>Indicates the game's manufacturer.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.ModelNo:</i></td>
<td>Indicates the manufacturer's model number for the game.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.Name:</i></td>
<td>Indicates the actual name of the game. When you save snapshots,
load/save state files, or use the <a href="#ROMAudit"><b>ROM Audit Mode</b></a> functionality,
this is the name that will be used for the respective file(s).</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.Note:</i></td>
<td>Contains any special notes about playing the game.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.Rarity:</i></td>
<td>Indicates how rare a cartridge is, based on the scale described on AtariAge.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.Sound:</i></td>
<td>Indicates if the game should use 1 or 2 channels for sound output.
All original Atari 2600 machines supported 1 channel only,
but some homebrew games have been written to take advantage of stereo
sound mods. The value must be <b>Mono</b> or <b>Stereo</b>.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.StartBank:</i></td>
<td>Indicates which bank to use for reading the reset vector.</td>
</tr>
<tr> <tr>
<td VALIGN="TOP"><a name="PropertiesCartType"><i>Cartridge.Type:</i></a></td> <td VALIGN="TOP"><a name="PropertiesCartType"><i>Cartridge.Type:</i></a></td>
@ -3791,8 +3741,45 @@ Ms Pac-Man (Stella extended codes):
<tr><td>X07 &#185;</td><td>64K AtariAge </td><td>.X07 </td></tr> <tr><td>X07 &#185;</td><td>64K AtariAge </td><td>.X07 </td></tr>
</table></td> </table></td>
</tr> </tr>
</table>
<tr>
<td VALIGN="TOP"><i>Cartridge.StartBank:</i></td>
<td>Indicates which bank to use for reading the reset vector.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Display.Format:</i></td>
<td>Indicates the television format the game was designed for. The value
must be <b>Auto</b>, <b>NTSC</b>, <b>PAL</b>, <b>SECAM</b>, <b>NTSC50</b>,
<b>PAL60</b> or <b>SECAM60</b>.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Display.Phosphor:</i></td>
<td>Indicates whether the phosphor effect should be emulated or not.
The value must be <b>Yes</b> or <b>No</b>.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Display.PPBlend:</i></td>
<td>Indicates the amount of blending which will occur while using the
phosphor effect. The value must be <i>n</i> such that 0 &lt;= <i>n</i>
&lt;= 100. The default value is whatever is specified for tv.phosblend.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.Sound:</i></td>
<td>Indicates if the game should use 1 or 2 channels for sound output.
All original Atari 2600 machines supported 1 channel only,
but some homebrew games have been written to take advantage of stereo
sound mods. The value must be <b>Mono</b> or <b>Stereo</b>.</td>
</tr>
</table>
<!--
<p><b>Note:</b> Items marked as '*' are deprecated, and will probably be
removed in a future release.</p>
-->
<a><img src="graphics/options_gameinfo_console.png"></a> <a><img src="graphics/options_gameinfo_console.png"></a>
<table CELLSPACING="10"> <table CELLSPACING="10">
<tr> <tr>
@ -3888,40 +3875,48 @@ Ms Pac-Man (Stella extended codes):
--> -->
</table> </table>
<a><img src="graphics/options_gameinfo_display.png"></a> <a><img src="graphics/options_gameinfo_cartridge.png"></a>
<table CELLSPACING="10"> <table CELLSPACING="10">
<tr> <tr>
<td VALIGN="TOP"><i>Display.Format:</i></td> <td VALIGN="TOP"><i>Cartridge.MD5:</i></td>
<td>Indicates the television format the game was designed for. The value <td>Indicates the MD5 checksum of the ROM image as a
must be <b>Auto</b>, <b>NTSC</b>, <b>PAL</b>, <b>SECAM</b>, <b>NTSC50</b>, string of hexadecimal digits. Stella uses this property while
<b>PAL60</b> or <b>SECAM60</b>.</td> attempting to match a game with its block of properties. If the
value of the property matches the MD5 checksum of the ROM image then
Stella uses that block of properties for the game. You can use the
GNU md5sum program, which is included with most Linux distributions,
to calculate the MD5 checksum of a ROM image.</td>
</tr> </tr>
<tr> <tr>
<td VALIGN="TOP"><i>Display.YStart:</i></td> <td VALIGN="TOP"><i>Cartridge.Manufacturer:</i></td>
<td>Indicates the scan-line to start displaying at. <td>Indicates the game's manufacturer.</td>
The value must be <i>n</i> such that 0 &lt;= <i>n</i> &lt;= 64.
Setting <i>n</i> to zero will enable ystart autodetection, which
should work fine for the vast majority of ROMs.</td>
</tr> </tr>
<tr> <tr>
<td VALIGN="TOP"><i>Display.Phosphor:</i></td> <td VALIGN="TOP"><i>Cartridge.ModelNo:</i></td>
<td>Indicates whether the phosphor effect should be emulated or not. <td>Indicates the manufacturer's model number for the game.</td>
The value must be <b>Yes</b> or <b>No</b>.</td>
</tr> </tr>
<tr> <tr>
<td VALIGN="TOP"><i>Display.PPBlend:</i></td> <td VALIGN="TOP"><i>Cartridge.Name:</i></td>
<td>Indicates the amount of blending which will occur while using the <td>Indicates the actual name of the game. When you save snapshots,
phosphor effect. The value must be <i>n</i> such that 0 &lt;= <i>n</i> load/save state files, or use the <a href="#ROMAudit"><b>ROM Audit Mode</b></a> functionality,
&lt;= 100. The default value is whatever is specified for tv.phosblend.</td> this is the name that will be used for the respective file(s).</td>
</tr> </tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.Note:</i></td>
<td>Contains any special notes about playing the game.</td>
</tr>
<tr>
<td VALIGN="TOP"><i>Cartridge.Rarity:</i></td>
<td>Indicates how rare a cartridge is, based on the scale described on AtariAge.</td>
</tr>
</table> </table>
<!--
<p><b>Note:</b> Items marked as '*' are deprecated, and will probably be
removed in a future release.</p>
-->
<p>The name of the properties file is configurable through the <p>The name of the properties file is configurable through the
'<i>-propsfile</i>' commandline argument and within the application itself '<i>-propsfile</i>' commandline argument and within the application itself
(see <b>Advanced Configuration - <a href="#ConfigPaths">Configure Paths</a></b>). If the (see <b>Advanced Configuration - <a href="#ConfigPaths">Configure Paths</a></b>). If the