I am focusing on my shell first, I think, but i'll continue it if I have time

sometimes that is not useful, Scout. For example when you want to explain something with the exponential E, or with the radians r.
And, Freyaday, I think you can better use this for storing your pictures:
////TO STORE////
... drawing things here...
GetCalc("appvNAMEOFYOURAPPVAR",768)->P
Copy(L6,P,768
////TO READ////
GetCalc("appvNAMEOFYOURAPPVAR")->P
Copy(P,L6,768
DispGraph
////TO STORE TO A PIC VAR////
Repeat the STORE part, but instead of
GetCalc("appvNAMEOFYOURAPPVAR",768
use
GetCalc("PicNUMBERFROM0-9",768
/////////////////////////////////
Maybe this is more convenient to use...
But it's all up to you!

Oh, that is rather easy. It won't work for numbers greater than 9999 but it is EFD74AEFEF4AEB

If you want a code to convert values up to 65535, that will require a larger opcode

(But I do have it >_>)

please give it, it would be useful for some things, like checking RAM
(You wrote a code for this that stores to Ans, maybe you can rewrite a part of it too, like the store to Ans part?
Isnt that replacing EFD74A with EF4AEB?)

I have a question: is there a hex code that copies the OS Ans var to the HL (Axe Ans) var? That would be useful!

Quote from: bluebl1 on March 01, 2011, 10:11:55 pm

stupid AI noob!!! it keeps cheating! Castling does NOT work that way!!! I found a way to beat it anyways. I put it in checkmate and had my queen on same horizontal line so even if it "castled" it wouldn't be safe. when i took out all of my opponents pieces including the king, the game didn't end.

I know he fixed the fake castling, but what happens when you win? I beat him and took every single piece but nothing happened...

I know, I did that on purpose. I figured that for now, it would be better if you could continue playing on the off chance that the game glitches and pulls a false checkmate. Plus, as soon as you get checkmate, you can just quit.

Quote from: graphmastur on March 01, 2011, 10:36:06 pm

Hey, for some reason the cursor was messing up pretty badly.  It was some random garbled thing.

OS 2.53 MP. (for integral function, and that's it)

This happens on my friends calculator also. He has 2.43. He said that a lot of other stuff was going horribly wrong too aside from the cursor. Tomorrow, I'm going to completely clear the calculator and see if that fixes it. If not, it must be related to hardware somehow. (Running the program from the homescreen didn't fix it either, so it's not specifically Mirage's fault. And it only uses 1 bcall the entire time, so it shouldn't be OS related either.)

Even weirder, the cursor graphic is not the very last thing in the program. All of the text comes after it. And the displaying routine isn't anything out of the ordinary.

That thing is auto-fix, it fixed itself in my case.

phew... I think 3: L3, L5,L6
L3: I think this is the backbuffer
L5: this is the buffer of the homescreen (where the chars are stored)
L6: this is the buffer for the screen.

You can call the buffers by using the list variables.

Xeda made this routine for running Basic progs:

Okay, so earlier I was asked by aeTIos for a hex code to run BASIC programs in Axe and I have heard that this was requested by others, so here goes my rendition... I am sorry in advance if my Axeing is horrible, this is only my second routine:

Code: [Select]

"prgmHELLO"→Str1                     ;Name of the var
Str1                                 ;To get the pointer to the string in HL (Ans)
Asm(E7FDCB08CEEF9B4AFDCB088E         ;
As a word of warning, do not use "Stop" in your BASIC programs... This seems to cause a crash
You can use "Return" and all the other commands, though, to my knowledge.

I hope this helps!

++ Xeda, well done!
And the Axe is okay

ARGHHHHHHH If that would happen to me, my motivation would be gone for >9000 years...