"<tt/OS/".
The names are the usual ones you can find in system reference manuals. Example:
-<verb>
+<tscreen><verb>
...
OS.savmsc = ScreenMemory;
OS.color4 = 14; // white frame
if (OS.stick0 != 15 || OS.ch != 255) // key or stick input?
...
-</verb>
+</verb></tscreen>
Please note that memory location 762/$2FA is called "<tt/char_/" while the orignal name "<tt/char/" conflicts with the C keyword.
for the instructions. In conjunction with the "void"-variable extension
of cc65, display lists can be created quite comfortable:
-<verb>
+<tscreen><verb>
...
unsigned char ScreenMemory[100];
DL_BLK4,
DL_CHR20x8x2,
DL_JVB,
- &DisplayList
+ &DisplayList
};
...
OS.sdlst = &DisplayList;
...
-</verb>
+</verb></tscreen>
Please inspect the <tt/_antic.h/ header file to detemine the supported
instruction names. Modifiers on instructions can be nested without need
under different mappings, defining remapped strings works only flawlessly
with static array initialization:
-<verb>
+<tscreen><verb>
#include <atari_screen_charmap.h>
char pcScreenMappingString[] = "Hello Atari!";
#include <atari_atascii_charmap.h>
char pcAtasciiMappingString[] = "Hello Atari!";
-</verb>
+</verb></tscreen>
delivers correct results, while
-<verb>
+<tscreen><verb>
#include <atari_screen_charmap.h>
char* pcScreenMappingString = "Hello Atari!";
#include <atari_atascii_charmap.h>
char* pcAtasciiMappingString = "Hello Atari!";
-</verb>
+</verb></tscreen>
does not.
all keyboard codes are available as defined values on C and assembler side.
Example:
-<verb>
+<tscreen><verb>
...
while (!kbhit());
switch (OS.ch)
...
}
...
-</verb>
+</verb></tscreen>
You can find the C defines in the file "<tt/atari.h/" or "<tt/atari.inc/" for the assembler variant.