perhaps you should seperate the data in the AppVar with zero's? then you could use the length( command to see how long the nam is, and then add that to a pointer to the current program-name. here is some code which should do it:
.READPRGS

GetCalc("apvrDATA")->D->P             .get the pointer to the appvar DATA
"prgm"->Str0ZZ                        .initialize Str0ZZ

While P<{D-2}rr-9                     .check for reaching the end of the AppVar
length(P)->L                          .store the length of the string at P to L, because it will be used more than once
Copy(P,Str0ZZ,L)                      .annex data at current position to Str0ZZ
P+L+1->P                              .add the length of the string at P to P to move P to the start of the next string
.Code to do whatever you want with the program...
End


this code is not tested, use at your own risk

I don't know wheter Str0ZZ should be Str09 or not, because I thought only Str00 till Str99 were supported, but I'm not sure about that.

I think that is doesn't work because you use Pt-Off, and not Pt-On. Pt-Off will just only turn off the pixels which are black on the sprite, nad not turn on the pixels that are white on the sprite. perhaps u could use the combination of Pt-On( and RectI( ? like this:
:.TEST
:<data>
:1->A->B
:ClrDraw
:Repeat getKey(15)
:Pt-On(B/12,A/12,Pic1
:RectI(B/12,A/12,8,8
:Pt-On(B/18,A/18,Pic1+8
:RectI(B/18,A/18,8,8
:Pt-On(B/24,A/24,Pic1+16
:RectI(B/24,A/24,8,8
:DispGraph
:ClrDraw
:C-getKey(2)+getKey(3)->C
:D-getKey(4)+getKey(1)->D
:B+C->B
:A+D->A
:End


well, I got this error earlier, but right now it isn't happening. I'll try to replicate it, but I'm not sure if I will succeed before the contest ends

Can't you do that with the Euler's constant 'e'?

ow yes, youre right! thanks!

could a command be added for changing the screen intensity? perhaps lcm( could be renamed to lcd(EXPR) with expr a value from 0 to 24 or something?

iPart( would be a nice token for nib{ I think. could you also add a bit{ command? min( could be replaced by it. the following syntax could be used:
.bit{byteaddress, bitnumber}:

[0B->GDB1            .00001011
If bit{GDB1,1}=1    .true
Disp "last bit on!"
End
If bit{GDB1,8}       .false
Disp "First bit on"
End


Do you mean the first time you compile the error show up and the second attempt it won't? Do you need to do something inbetween (such as Garbage Collecting, archiving/unarchiving)?

yes, that's exactly what I mean. I do nothing in between, and then it suddenly compiles without any errors.

ninja'd? or double post? was the site acting weird, or is this message that important to you, so you posted it twice?

or perhaps EXPR[ # ], like arrays? EXPR would be the pointer to the data, and # could be any number/variable with any value. and when that's unrealizable, just constant 0 - 3.

a feature request: when I currently want to draw an Inverted Rectangle, I have to do:
Rect(X,Y,W,H
RectI(X,Y,W,H
could you change invT( in the 2nd DISTR menu to Inv, so that we can type InvRect(X,Y,W,H)? or would this be too much work?

another thing I suddenly thought of: could DelVar perhaps be changed to DelCalc(, since it is a member of the Calc var handling system? IMO it would be nice to have GetCalc( and DelCalc( look similar, because of the same Syntax and use.

and the PTR in the documentation used in the External Variables part for GetCalc(PTR) is not the same PTR as for float{PTR}, or am I wrong at this point? Else it would perhaps be more consistent to use EXPR in stead of PTR.

one last note: in the documentation it says: Sub(, but in the editor it is sub( with a lower case S.