Features Wishlist

[Darl181]

What I mean is instead of Pt-Mask only looking 8 bytes forward, you would be able to tell it where the second sprite is.

[Runer112]

The Pt-Mask() routine is already really tight on register usage. Keeping track of another 16-bit value would be difficult and would require a pretty fair amount of restructuring and added size/slowness to the routine. And I feel that using non-sequential front and back sprites is not a common occurrence, so doesn't warrant this restructuring.

If you really need functionality like this, you could implement it yourself with a subroutine that copies the two 8-byte sprites to a sequential 16-byte section of RAM and then calls Pt-Mask() routine.

[Darl181]

Ok, how about this...
Two (sort of, more like 4) requests

1) a signed Disp, so numbers >32768 would display the respective negative number.  Ie instead of 65472 it would print  -   64 , prolly requiring six spaces to work in instead of the normal five.  Or maybe even have the negative sign next to the topmost digit, if it's smaller code-wise
1a) something similar for Text()
1b) support for one-byte numbers, maybe check the syntax at compile-time?

2) a Disp that advances only as many digits as the number needs

They would all be optional, so the existing commands aren't changed.

E: changed "bit" to "byte" >.<

[Hayleia]

Why not adding in the Commands.html the size of each routine and the size of each routine call ?

[Runer112]

Why not adding in the Commands.html the size of each routine and the size of each routine call ?

That actually might be a pretty good idea, since people always ask about this information and it's nowhere to be found. Perhaps speed data could be added as well? My only concern is that theses would complicate the otherwise fairly clean and simple command list.

[Hayleia]

Perhaps speed data could be added as well?

Yes, I thought about it but forgot to post it >.<

My only concern is that theses would complicate the otherwise fairly clean and simple command list.

For now there are two columns: "Command" and "Description". Maybe three little columns could be added, like "routine size", "call size" and "cycles" ?

[MGOS]

Maybe add that programs compiled to Axe Fusion won't crash when axe isn't installed. E. g. let it return to homescreen when the axe app can't be found.

[Runer112]

Maybe add that programs compiled to Axe Fusion won't crash when axe isn't installed. E. g. let it return to homescreen when the axe app can't be found.

This is semi-supported. If Axe is not found, the program should display a message that Axe was not found and exit cleanly. However, programs compiled as Axe Fusion currently don't check that the version of Axe found actually supports Axe Fusion, which will result in a crash when the program tries to reference nonexistent command vectors in Axe.

If the program crashes and Axe 1.1.2 exists on the calculator, then you should mosey on over to the Bug Reports thread.

[MGOS]

No, it only wasn't the latest version of axe on that calc and he accidentally ran an axe fusion program.

[Runer112]

Okay, that's a known issue. Hopefully that will be fixed in the next version of Axe.

[Hayleia]

I am quoting what I asked in the wrong topic so my feature request is actually in the Features Wishlist.

Would it be possible to have equates ?
I mean that for example if I write this
   test equ {V+17}
each time the parser hits the word "test", it replaces it with "{V+17}" before translating it into asm.

(note that here, V+17→°test would not work since V+17 is not constant)

EDIT: Oh, I see, that way if FOO translated to {V+17}, you could do something like 23→FOO and FOO→X and both would be valid statements.

It would still be no different than using {V+17} everywhere though, since FOO wouldn't actually exist. It'd be more like a macro than anything.

Yes that's it. It would not save space in any way. It is just so I can easily see who is who in my appvar. Because I have wood, stone and apples (among others) and having this
   {V+17}^^r equ wood
   {V+19}^^r equ stone
   {V+21}^^r equ apple
would be of a great help for me to understand my code easier. So would it be possible ?

[Hayleia]

Double posting, with another feature request:
Could the possibility to declare constants as follow be added ?
  18→°Var1+1→°Var2+5→°Var3

[Freyaday]

Could the UnArchive command be modified to return the address of the unarchived var if it was successful, and 0 if unsuccessful?

[Freyaday]

Ability to display a string of tokens?

[pimathbrainiac]

How about a larger app max compile size