Your pictures take up 768 bytes, right? Why not store all your pics consecutively, so having a 768 byte appvar for one pic, a 1536 for two pics, etc. If you have, say, 35 pics to store, you'd need an appvar that's 26,880 bytes, and obviously it'd need to be in the user archive. If you have it loaded in Y1, you could load the first pic into a RAM location (say, GDB1) like so: Copy(Y1,GDB1,768) . You could then load, say the twenty-seventh picture like so: Copy(26*768+Y1,GDB1,768) . The pseudo code for this would be something like:
Copy(number_of_pic_to_load_counting_from_zero * 768 + Y1, RAM_location_to_load_to, 768)

Quote from: buttsfredkin on September 19, 2011, 09:59:18 am

Your pictures take up 768 bytes, right? Why not store all your pics consecutively, so having a 768 byte appvar for one pic, a 1536 for two pics, etc. If you have, say, 35 pics to store, you'd need an appvar that's 26,880 bytes, and obviously it'd need to be in the user archive. If you have it loaded in Y1, you could load the first pic into a RAM location (say, GDB1) like so: Copy(Y1,GDB1,768) . You could then load, say the twenty-seventh picture like so: Copy(26*768+Y1,GDB1,768) . The pseudo code for this would be something like:
Copy(number_of_pic_to_load_counting_from_zero * 768 + Y1, RAM_location_to_load_to, 768)

OK thnkx
It'll be helpful for making a second one.
EDIT: OK. So how do I store it?

Just like you read it. You'll have to draw your pictures (on the buffer, aka L6) and copy them step by step in an appvar created for this (with the correct size) with 768 bytes steps. Like Copy(L6,APPVAR+1536,768).

I suppose you could use the bcalls that archive and unarchive variables in hex. That shouldn't be too horrible.

Or you could write an axiom and use that with UnArchive/Archive for the tokens

Suppose you have three appvars. Each of these is 768 bytes in size. One is called "AppVarOne" (yeah, I know it's too long of a name. whatever ). Another is "AppVarTwo" and the third is "AppVarThree". You want to combine them into a 2304 byte appvar that you're going to call "Really_Big_AppVar". I would use the following code: (keep in mind that this code has no user interface, it just does it's thing). Oh, and AppVarOne, AppVarTwo, and AppVarThree are all in the archive.

.MAKE Make big appvars out of little ones

.load the smaller appvars, the 768 byte ones
.make sure these are in the archive, or this won't work
GetCalc("appvAppVarOne",Y1)
GetCalc("appvAppVarTwo",Y2)
GetCalc("appvAppVarThree",Y3)

.make a new, bigger appvar (make sure this appvar doesn't already exist. if it does, delete it.)
GetCalc("appvReally_Big_Appvar",2304)->W
.let's store the pointer to Really_Big_Appvar in variable W
.and make Really_Big_Appvar 2304 bytes in size.

.Now start copying the small appvars into the big one.
Copy(Y1,W,768)
Copy(Y2,W+768,768)
Copy(Y3,W+1536,768)

.archive Really_Big_Archive (optional) and you're all done!
Archive "appvReally_Big_Archive"


Ta-da! Let me know if that doesn't make any sense.