What are the screen dimensions?

How do I display integers (with nRGBlib)?

A smarter way to debug values on the handled is to user sprintf and show_msgbox =)

Also, is there a way to save high scores?

Writting in a file ?

FILE * f = fopen("/documents/mygame_highscore.tns", "w+");
char buf[integerSize(highscore) + 2];
sprintf(buf, "%d", highscore);
fputs(buf, f);
fclose(f);
refresh_osscr(); // refresh OS screen so that we can see the created file when we exit the program

int integerSize(int n) {
  int i;
  for(i = 0; n > 0; n/= 10, i++);
  return n
}


I wonder... is self-modifying code possible in Ndless, as in highscores storing themselves inside their respective games rather than external files? I saw that happen often on the TI-83 Plus in the past.

Actually I do not remember what was the main use on the TI-83 Plus since external data was often in appvar form anyway and did not take any space in the PRGM/apps menu, but on the TI-Nspire I notice that external files often clutter the TI-Nspire document explorer, and I remember people ranting about having too many files on the TI-83 Plus before, which tells me some TI-Nspire users might not like it very much to see their menu cluttered. It is particularly bad when you got 50 gbc4nspire ROMs with savestates. Of course there are folders, though.

I wonder... is self-modifying code possible in Ndless, as in highscores storing themselves inside their respective games rather than external files? I saw that happen often on the TI-83 Plus in the past.

You can, but if the file size get modified, like if you recompile with extra stuff / updates, the highscore system will crash.

Levak, if you store the data on the end of the tns file, and you can get the size of it using Ndless there should not be any problem.

The fgets function seems to have a glitch:
char *fgets(char *str, int num, FILE *str2eam) {
char *str2 = str;
while (num--) {
char c = fgetc(str2eam); //THIS IS THE BUGGY LINE
if (c == EOF) {
*str2 = '\0';
return NULL;
}
*str2++ = c;
if (c == '\n')
break;
}
*str2 = '\0';
return str;
}
The c variable should be specified as an int, not a char -- it looks like the compiler treated the char as unsigned and optimized out the return NULL entirely! Plus, it is possible that an 0xFF character exists in the file, so signed char is not the way to go.