ld hl,1
ret
ld hl,address
and thats it?
.dw hInvT
.db 7
.db "Cn2.2id"
Yeah, that's because it's a "new" token and is sent to the token hook in a special manner that Axe doesn't handle. I didn't add handling for it because I wasn't entirely sure how to account for it without introducing other problems on calculators with older OSes, but I think I've found a way to fix it now.Do you mind explaining that a bit? I don't see anything in the code that would prevent new tokens from being used...
:.KEY
:AsmComp(GCNAXE)
:prgmGCNLIB
:CnOn
:
:For(A,0,255)
:Disp GetKey►Dec,i
:Pause 100
:End
:
:CnOff
:Stop
:Return
Generated by SourceCoder (http://sc.cemetech.net)
© 2005-2012 Cemetech (http://www.cemetech.net)
Hmm, so why didn't he just put it all in one place? D: Is it so that it can work around DCS? :/Only 547 bytes in "L1" is actually for CALCnet. The other 100-odd you only have to worry about if you're also using the Doors CS GUI API with CALCnet. Believe it or not, I actually use my brain when I design things. ;)
Hmm, so why didn't he just put it all in one place? D: Is it so that it can work around DCS? :/Only 547 bytes in "L1" is actually for CALCnet. The other 100-odd you only have to worry about if you're also using the Doors CS GUI API with CALCnet. Believe it or not, I actually use my brain when I design things. ;)
Edit: Oh yes, and the L3 stuff for interrupts, of course, but that's nothing extraordinary.
Isnt L3 appBackupScreen?
I thought L2 was for interrupts...
Btw since L3 is used for intterupts, this means that in CALCnet games written in Axe cannot be in grayscale, right? (Since grayscale uses all of L3) Or can we simply not make our game full screen and just use the rest of L3 for grayscale?
Oo i did not notice this thread. Would be cool to use :D