Planning my new project I'm going to make in axe, I came across some questions about how to do stuff in axe (V 1.0.5)

1. How can you make it that a variable toggles from 0 to 1 and vice versa if you press a special key, but it doesn't keep toggling when you hold it?
It shouldn't influence the other getkeys for movement, etc. in the same loop.

2. Is it possible to display two buffers on top of each other (or / xor) without having greyscale?

3. Is there a short way of letting to user chose from a bunch of saved files (appvars) to reload or chose the file to save the data, without having that many If-statements?

Thanks Xeda for your attempt solving my problem, but I think it isn't exactly that what I'm looking for.

I will explain what I need:
Let's say D is our toggle variable (at the beginning 0), and Enter the key.
So if I press Enter, D toggles to 1.
If I hold down the button, nothing should happen.
If I release the button, nothing should happen.
If I press Enter again, D toggles back to 0.
If I hold down the button, nothing should happen.
If I release the button again, nothing should happen.

Edit:
This is the way I do not want it:
0->D
Repeat getkey(15)
If getkey(9)
  If D
    0->D
  Else
    1->D
  End
End
...
End


Thanks jacobly. I will try that out.

Has someone any idea to solve the other problems?

Ok, but then I cannot use the other keys the same time, right?

For(A,L₃,L₃+767)
 {A} or {A−L₃+L₆}➔{A}
End

This is much faster!
Edit: even faster!

3. Is there a short way of letting to user chose from a bunch of saved files (appvars) to reload or chose the file to save the data, without having that many If-statements?

You have two options - you can either use Memkit to get the names of all the appvars in memory, and then display them as a scrolling list, and have the user choose between them, or you can use or write a custom input function, like the one in Firefall, that one's pretty good.

[...] I calculated that the following loop runs about 40 times per second at 6MHz:

Code: [Select]

Repeat getKey(15)
For(A,0,383)
.That ﹢ symbol is the 16-bit OR operator
{A*2+L₆}ʳ﹢{A*2+L₃}ʳ→{A*2+L₆}ʳ
End
C+1→C
End

Yeah, I will try that.

Quote from: MGOS on October 30, 2011, 07:28:39 am

3. Is there a short way of letting to user chose from a bunch of saved files (appvars) to reload or chose the file to save the data, without having that many If-statements?

You have two options - you can either use Memkit to get the names of all the appvars in memory, and then display them as a scrolling list, and have the user choose between them, or you can use or write a custom input function, like the one in Firefall, that one's pretty good.

I think I'm going to make a custom menu with limited amout of Appvars - that's enough for the beginning - maybe I canm fix that later if Axe has new features to do that more easily.

Thanks a lot, guys!

1. jacobly's solution is what I would do too.

I did that and it works quite good.

2. You can do it even faster with the new speed loop:

Code: [Select]

L₆
For(383)
 {➔A}ʳ﹢{A+L₃-L₆}ʳ➔{A}ʳ+2
End


I just realized that there is this cool new loop. It might be useful for something, but for my problem I found another way avoiding drawing two buffers over each other.

3. If your saved data takes a standard form like "appvSAVE1", "appvSAVE2", "appvSAVE3", etc.  Then you can construct the first part of the string in some memory by doing copy("appvSAVE0",L₁,7) and then make the string the Nth file by doing N+'0'➔{L₁+5}.  Now all you have to do to load the file is just GetCalc(L₁) which uses the string you just constructed.  If you want to list all the appvars on the calculator that start with your custom header and choose from those, you'll have to use memkit.

Due to the big program size I reached I think it's better to use a simple way, so I will just have some default save files the user can choose from. But still thanks Quigibo.