You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first line holds the module file version. For this file, that's "1".
No decimal points or anything fancy.
The second line is the module description, which appears on the title
bar when the module is loaded.
The third line is the root address of the data table.
The fourth line is the number of table entries.
The fifth line is the length of a single entry.
The sixth line is a filename, indicating a list of names to be used by
the entry selector. If "NULL", the entry selector will only use
numbers. If names run out before numbers do, the selector will continue
with just numbers.
The seventh line is also a filename, indicating the table file to be used
by TEXT entries. Tables here can only be letter-matching, that is, of
the form XX=Y; multiple bytes or multiple characters, such as XXYY=Z,
or XX=yz, are not permitted. If "NULL", standard ASCII is assumed."
Translate value to macro according to 6th line automatically. It should be able to skip invalid string for macro or convert them, avoid redefinition, split bitfield and then output the definition file. An alternative is to load a predefined definition file.
Another solution is to make a script to convert all text files set in NMM files to required macro definition files. Rule conversion -> error correction log for macro -> human review.
The text was updated successfully, but these errors were encountered:
"THE MODULE FORMAT
The first line holds the module file version. For this file, that's "1".
No decimal points or anything fancy.
The second line is the module description, which appears on the title
bar when the module is loaded.
The third line is the root address of the data table.
The fourth line is the number of table entries.
The fifth line is the length of a single entry.
The sixth line is a filename, indicating a list of names to be used by
the entry selector. If "NULL", the entry selector will only use
numbers. If names run out before numbers do, the selector will continue
with just numbers.
The seventh line is also a filename, indicating the table file to be used
by TEXT entries. Tables here can only be letter-matching, that is, of
the form XX=Y; multiple bytes or multiple characters, such as XXYY=Z,
or XX=yz, are not permitted. If "NULL", standard ASCII is assumed."
Translate value to macro according to 6th line automatically. It should be able to skip invalid string for macro or convert them, avoid redefinition, split bitfield and then output the definition file. An alternative is to load a predefined definition file.
Another solution is to make a script to convert all text files set in NMM files to required macro definition files. Rule conversion -> error correction log for macro -> human review.
The text was updated successfully, but these errors were encountered: