diff --git a/docs/sgmanual/settings.html b/docs/sgmanual/settings.html index 05a21c8..54bc06f 100644 --- a/docs/sgmanual/settings.html +++ b/docs/sgmanual/settings.html @@ -209,12 +209,6 @@ counts are inserted into end-of-line comments. This works the same as the option in the Code View tab, but applies to generated source code rather than the on-screen display.

-

If put long labels on separate line is checked, labels -that are longer than the label column are placed on their own line. This -looks a bit nicer because otherwise the opcode gets pushed out of alignment. -(Some assemblers get bent out of shape if you split an equate -directive, so those might stay on one line.)

-

If you enable identify assembler in output, a comment will be added to the top of the generated assembly output that identifies the target assembler and version. It also shows the command-line options @@ -223,6 +217,22 @@ file is sent to other people, since it may not otherwise be obvious from the source file what the intended target assembler is, or what options are required to process the file correctly.

+

Labels can generally be placed either on the same line as a code or data +operand, or on the line before it. Placing them on the same line makes +the output a bit more compact, but if the label is longer than the label +column is wide, the subsequent fields can be pushed out of alignment. +The placement is configurable. Labels can be output on their own line:

+
    +
  1. Only when required - labels will not be placed on a separate line + unless the assembler requires them to be.
    2. +
  2. When the label is wider than the field - labels will only be + placed on a separate line when they don't fit in the label column.
    3. +
  3. Whenever possible - labels are always placed on a separate line + when they are allowed to be. Most assemblers require that the label + be on the same line as assignment pseudo-ops, + e.g. "FOO = $1000".
    4. +
+

Project Properties