Andy McFadden 0dfa2326dd Fix L1/L2 ASCII string editing ... The data operand editor determines low vs. high ASCII formatting by examining the first byte of string data. Unfortunately the test was broken, and for strings with a 1- or 2-byte length, was testing the length byte instead of the character data. This is now fixed. This also changes the way empty strings are handled. Before, they were allowed but not counted, so you couldn't create an empty string by itself, but could do it if it were part of a larger group. This was unnecessarily restrictive. Empty L1/L2/null-term strings are now allowed. This means that a buffer full of $00 can be formatted as a big pile of empty strings, which seems a bit ridiculous but there's no good reason to obstruct it. (issue #110)		2021-09-12 09:46:55 -07:00
..
advanced.html	Improve OMF feature docs	2021-06-15 08:57:00 -07:00
analysis.html
codegen.html	Update 64tass code gen	2021-08-09 14:26:25 -07:00
editors.html	Fix L1/L2 ASCII string editing	2021-09-12 09:46:55 -07:00
end-notes.html
index.html	Update ACME generator for v0.97	2021-07-31 14:42:36 -07:00
intro.html
main.css
mainwin.html
settings.html
tools.html	Improve OMF feature docs	2021-06-15 08:57:00 -07:00
tutorials.html	Update docs to point to new tutorial	2021-06-07 17:55:51 -07:00
visualization.html