writing to a static pointer would be the only way to safely write to your own program data, and that's as simple as, well, writing to the static pointer! Just know that programs don't always get written back.  Homescreen games do not get written back, and Mirage/Doors games only get written back based on a user setting.  Appvars would be my way to go, any reason you don't want to use them?

Not sure, runer made a topic somewhere about the size/speed of the commands tho.
http://ourl.ca/8693 (attached pdfs)


When using Disp or Text, is there a command to have it display negative numbers properly?  Ie instead of displaying 32768 (or 32767?) it would display -1, etc.

Also is there a way to get the current pen location?  How about on the homescreen?

Darl, if you really wanted to do smc, you'd have to put some extra space in your program, GetCalc("prgmSMC")->N and then look for the last C9h in the file.

If the shell doesn't support writeback or if the user is running from the home screen (and the program isn't archived), you can ensure SMC by saving once to the pointer and then to the same pointer relative to the original copy of the program (the one not being run).

To do that, you'd first have to find the original copy. It's best to do it at the very beginning of your program, because there you can take advantage of the fact that the program name is stored at an address called OP1 ($8478), so this will work regardless of whether the user renames it. Use this as the first line of your program:

GetCalc(E8478)-E9D93→P

This finds the original copy of the currently running program, then subtracts $9D93; this number is where the running copy of the program is located, so P now holds the difference in address between the two programs.

Then, where you want SMC, you save to the local pointer (in the running copy, so it works with shells with writeback enabled) and to the appropriate spot in the original copy. For example, if you wanted to save 256 to a POINTER, you'd use something like this:

256→{POINTER}r
256→{POINTER+GDB1)r

All this works only if the program isn't being run from archive though, correct?

That's true, but in that case you can check if GetCalc() fails.

In general though, it's good to let the user decide through the settings of their shell whether or not they want writeback in their own programs right?

My post is actually to make it work when people run the program from the homescreen, which would never write anything back otherwise since it makes a copy of the program to run. Shells almost always write back any program that's in RAM, anyway, and whether it writes back when the program's archived is still up to the user.

Quote from: Builderboy on February 02, 2012, 07:40:00 pm

All this works only if the program isn't being run from archive though, correct?

That's true, but in that case you can check if GetCalc() fails.

I never check for that because unless the program's over 32 KB long, it would do anything since it's probably not writing to RAM. I guess it would help to tell the user that the modification failed, though.

How would you get the size of an appvar?
such as:
GetCalc("appvSTUFF",Y0)
[see what the size of the appvar is]


O.o I never thought it would be so easy. Thanks!