From ef131019238fca628ab8b830ec83bfa0f8abfe58 Mon Sep 17 00:00:00 2001
From: Andy McFadden
diff --git a/docs/sgmanual/settings.html b/docs/sgmanual/settings.html
index e7d3f2d..f2e0f73 100644
--- a/docs/sgmanual/settings.html
+++ b/docs/sgmanual/settings.html
@@ -30,7 +30,7 @@ you prefer hexadecimal values to be shown in upper case. None of them
affect the way the project analyzes code and data, though they may affect
the way generated assembly sources look.
The settings editor is divided into four tabs. Changes don't take +
The settings editor is divided into five tabs. Changes don't take effect until you hit Apply or OK.
@@ -84,6 +84,10 @@ controls.)These options change the way the code list looks on screen. They +do not affect generated code, which must use the delimiter characters +specified by the chosen assembler.
+Character and string operands are shown surrounded by quotes, e.g.
LDA #'*'
or .STR "Hello, world!"
. It's
handy to be able to tell at a glance how characters are encoded, so
@@ -92,8 +96,8 @@ supported character encoding.
String operands may contain a mixture of text and hexadecimal values. For example, in ASCII data, the control characters for linefeed and carriage return ($0a and $0d) are considered part of the string, but -don't have a printable symbol. (Unicode defines some glpyhs, but they -don't look very good at smaller font sizes.)
+don't have a printable symbol. (Unicode defines some "control picture" +glyphs, but they don't look very good at smaller font sizes.)If one of the delimiter characters appears in the string itself, the character will be output as hex to avoid confusion. For this reason, it's generally wise to use delimiter characters that aren't @@ -104,9 +108,6 @@ copy and paste (with Ctrl+C /
For character operands, the prefix and suffix are added to the start and end of the operand. For string operands, the prefix is added to the start of the first line, and suffixes aren't allowed.
-These options change the way the code list looks on screen. They -do not affect generated code, which must use the delimiter characters -specified by the chosen assembler.
The "quick set" pop-up can be used to set the fields for a few common configurations. The default set uses curly quotes with a few @@ -189,9 +190,9 @@ in the combo box to set the fields. The setting automatically switches to
These settings configure cross-assemblers and modify assembly source generation in various ways.
To configure an assembler, select it in the pop-up menu. The fields -will initially contain assembler-specific default values. All of -the values in the Assembler Configuration box may be configured -differently for each assembler.
+will initially contain assembler-specific default values. The values +in the Assembler-Specific Configuration box may be configured +independently for each assembler.The "executable" box holds the full path to the cross-assembler executable.
The Code Generation Settings affect all assemblers.
+When show cycle counts in comments is checked, cycle counts are inserted into end-of-line comments. This works the same as the option in the Code View tab, but applies to generated @@ -328,8 +331,9 @@ character encoding (e.g. you can default string operands to PETSCII), this setting will determine which encoding is preferred in generated sources.
The min chars for string detection setting determines how -many ASCII characters need to appear consecutively for the data analyzer to -declare it a string. Shorter values are prone to false-positive +many printable characters (based on the default text encoding setting) +need to appear consecutively for the data analyzer to +decide it's a string. Shorter values are prone to false-positive identifications, longer values miss out on short strings. You can also set it to "none" to disable automatic string identification.
The auto-label style setting determines the format for