Omnimaga
Calculator Community => TI Calculators => Axe => Topic started by: Darl181 on April 28, 2011, 02:49:56 am
-
The code below is eventually going to be put in the Tio level editor.
The idea is to either insert or remove a level from the pack.
Str0T is temp string, something like "appvTEMPLVL"
Str0L is the real level set.
r6 is the pointer to start off the level var. getcalc(thing)→r6 then →P.
P is manipulated to change the level that's pointed to within the set.
Q is simply {r6-2}^r stored to a var
One level is 384 bytes large, one "level slot"
After INSERT
Inserts a level where the pointer is. One slot.
What it's *supposed* to do is copy all the data from the current pointer one slot forward, making the level larger and leaving a gap where the new level can be started.
After DELETE
Removes the level pointed to.
Pulls back the levels after the currently-pointed-to level, shrinking the pack and overwriting the current level.
The 31337 lets the game know, when it's reading through the level appvar, where the appvar ends.
So, the code.
Main editor program to an extent
PROGRAM:STIO10E
:.program start
:.header, sprites, strings, main menu, level select
:.more stuff
:Lbl E
:.Editor start
:.load level, start main loop
:.main loop starts
:.cursor movement code...
:If getKey(10):3→r1:Goto LVL:End
:If getKey(11):4→r1:Goto LVL:End
:If getKey(12):1→r1:Goto LVL:End
:If getKey(13):2→r1:Goto LVL:End
:.rest of main loop
:.main loop ends
:.subroutines
:Lbl LVL
:prgmLEVEL
:Goto ESub-programPROGRAM:LEVEL
:..
:{r6-2}^r→Q
:.^r is same as the result of [sup]r[/sup]
:!If r1-1
:.Q-1→Q
:.INSERT
:GetCalc(Str0T,Q)→B
:GetCalc(Str0L)→C
:copy(C,B,Q)
:GetCalc(Str0L,Q+384)→C
:copy(B,C,Q)
:31337→{Q+384→Q+C+1}^r
:End
:!If r1-2
:.DELETE
:If Q+385
:Q-384→Q
:GetCalc(Str0T,Q)→B
:GetCalc(Str0L)→C
:copy(C,B,Q)
:GetCalc(Str0L,Q)→C
:copy(B,C,Q)
:31337→{Q+r6}^r
:End
:End
:.manual switch
:!If r1-3
:.previous
:If P-r6
:P-384→P
:End
:!If r1-4
:If {P+383}^r-31337
:P+384→P
:End
:.Return
I've tried this code, and it led to a pretty epic RAM clear, even caused the BLOD somehow :P
On another try it made a gigantic overflow variable which on recall caused another crazy RAM clear.
Clearly, I'm going to need some help getting this to work properly...
1) is it plausible?
2) what's wrong with it? I've been coding for less than a year and make some pretty dumb mistakes sometimes, and I'm guessing this might be another one...
3) can it be fixed, or would it need to be completely re-written?
EDIT: this code, and the text almost verbatim, is in a kompispad (read:etherpad) at http://kompisen.se/tio and the "Tio Dev" link in my sig goes there as well.
-
So basically what you want is
first creating an appvar
then add and delete levels?
I recommend that you create an appvar for lets say 8 levels. then let the user choose the level to edit and save it in the appvar. I think the reason for the RAM clear is that you have overflown the appvar.
You can add/del levels by using a short list at the start of the appv, for example if level 1-3 are used would the data at the start be 1,1,1,0,0,0,0,0.
I hope this will help you!
-
Made a more graphic representation of what I'm going for.
-
The problem is most likely that you overflow the appvar.
I'll take a look at this later, better run to class now ;)
-
For this you'll need to use insertmem and delmem, so asm.
-
...or use MemKit. What you're describing is exactly what its there for. It gives you the ability to insert any number of bytes into an appvar at any location, or remove bytes from a location.
-
O.O didn't know that, thanks !
-
Cool!
-
Memkit! Completely forgot that...
:banghead:
-
But how does it (memkit) exactly work? Shifting the rest of the bytes? Or does it buy a new RAM-chip?
-
It's an axiom (external routines which can be called), which by the way I failed on figuring out how to use :P
Can't find the tokens anywhere...
/me starts looking for a tutorial
Or maybe one can tell how to use it precisely? I got the #Axiom line down but can't fine the tokens (ie New( Delete( )
EDIT: just re-read the memkit readme, a lot clearer after trying fsr :P
-
But how does it (memkit) exactly work? Shifting the rest of the bytes? Or does it buy a new RAM-chip?
It shifts bytes around. There are two bcalls (_InsertMem and _DelMem) for that very purpose, automatically shifting the appropriate bytes and updating all var pointers. MemKit is basically an Axe front-end for that, with some other useful features.
-
Can someone clarify what the offset argument in New( and Delete( is supposed to be? Is it the byte in ram at which it's located, or the bytes from the start of the var?
I tried it as # of bytes from the start of the var and it made a ~3kb y-var :P
TIA
-
Bump.
I tried it again last night, this time the y-var was 4kb :P
I just now went through the readme again.
New(PTR,OFS,SIZ) Arguments: PTR = Pointer to start of program/appvar (from getcalc).
OFS = Offset in program to add memory
SIZ = Size of memory to insert
Returns: 0 if it failed, non-zero if it succeeded.
Description: Attempts to inflate the size of a program/appvar
Delete(PTR,OFS,SIZ) Arguments: PTR = Pointer to start of program/appvar (from getcalc).
OFS = Offset in program to start deleting memory
SIZ = Size of memory to delete
Returns: 0 if it failed, non-zero if it succeeded.
Description: Attempts to shrink the size of a program/appvar
still not very clear, even in retrospect...
EDIT: is the two-byte r modifier needed?
EDIT2: attached problematic stuffs. uses memkit, and LEVEL is a sub-program
btw made with axe 0.5.0