if you want to take single frame screenshots, then an easy method would be to copy the contents of the screen buffer into a Pic variable (or into two, if you want greyscale). if you want animated screenshots on calc, then both limitations of storage and the amount of processing power required would make it not feasible.

for the +→ idea, that might actually be nice =)

two request :

-a Zadd() command, for change the z-adress (I know axiom can do it, but I prefer an axe command)

-an rect command who can draw in buffer and back buffer in same time (if possible  )

A sign(foo) command that returns -1 if foo is less than 0, 1 if greater, and 0 if equal. And perhaps sign(foo,bar), which would compare it to bar instead of 0. And while I'm on the topic, perhaps sign()^r could be the 8bit version?
Also, I know it'd have to be named something other than sign(), because there's already a sign{}, but I don't know what to call it.

I think more something like foo-bar?(ee0?-1,1),0

I wonder what's the use of Z-addressing ...

A sign(foo) command that returns -1 if foo is less than 0, 1 if greater, and 0 if equal. And perhaps sign(foo,bar), which would compare it to bar instead of 0. And while I'm on the topic, perhaps sign()^r could be the 8bit version?
Also, I know it'd have to be named something other than sign(), because there's already a sign{}, but I don't know what to call it.

You know, you can build a pretty optimized sign routine in pure Axe. In fact... I don't think it's even think it's possible to produce a more optimized sign routine for Axe using assembly.

Lbl Sign
Return!If
Return //32768*2+1

As for the other variations, the compare seems that it's a little specific and could easily just be thrown into the sign routine above like Sign(foo-bar) anyways. As for the 8-bit sign function, you should really always be working with 16-bit signed values in Axe because every signed operator expects them. There are a few operators for which you can get away with not sign-extending 8-bit signed values, such as +, -, and *. But for using other operations, it's a good idea to sign-extend any 8-bit signed numbers using sign{} when loading them from memory.

---

about axe being thight on space, I understand that it can give problems for some people if axe would exceed the size of about 16kb,
but it wouldn't be a problem to me and I would find it a bit sad if axe couldn't expand only for that reason,
so would it be practically possible to add 2 axe versions in the zip file, a lite and a pro version of axe,
where one has a low size and the other has all kind of possible features?

Axe has already exceeded 16kb (1 flash page); it's currently just about filling 32kb (2 pages). Right now the first page is more or less entirely code and the second page is more or less entirely data. The next step up would be 48kb (3 pages), but really the size increase itself isn't the issue. More of an issue is that there would then be code split across pages. Producing and maintaining assembly code that spans multiple pages introduces a lot more complexity over code that fits on one page. And Axe is already fairly complicated, so for now I'd like to keep it restricted to 32kb so my head doesn't explode. I think I can still add a fair amount of code/features, I just need to optimize existing code to the max as I add new code.

---

I wonder what's the use of Z-addressing ...

I used z-addressing with a bit of assembly in this Axe program I made for a mini competition a while ago. The screenshot demonstrates that this game quickly becomes a bit of an insane use of z-addressing, but it definitely showcases the potential power of it by "shifting" what would otherwise be a simple tunnel game at nauseating speeds with no program speed loss.

Oh, so that's what the multi page feature means? being able to make apps larger than 16kb with axe.
I don't really understand what the complications are that come with multiple pages,
I tried to search, but found few information about it.
I would love to have the multi page feature, since I'm working on a big project,
not knowing I can't exceed 16kb and I've almost reached the limits (about 15.5kb).
also, could it be that there comes problems if I try to upload big axe made applications to my pc through ti connect?
for some reason he wouldn't download it, no matter what I did, while everything else was being uploaded perfectly.
it always throws up the error: packet length not valid