We should start a statistic how often you guys upload a new, latest version!
One every week. Or was it every day??


But I have a question!
If I save the code of another program as "H" (for example)
Why can't I use this:
:if {H+4} =5
I always must save the numbers/letters I need to search for (in the code) saved in the code, too:
:"5"->Str1
:{Str1+0}->{H+0}
:if {H+4} = {H+0}
OR:
:if {H+4} = {Str1+0}

But That's so annoying (especially if you have to save 27 different things there!!
It would have been so much easier if I could have written:
:5->X
:if {H+4} =X

Can't you please add that or tell me where my mistake is?

But how to check for a Var (X) or a Letter ("B")

Horizontal (BUFF)- makes the calculator freeze.  No other variation of Horizontal has this problem.

Freyaday, I'm pretty sure loops work exactly like they're supposed to. Your problem might be key bouncing, meaning that for a small fraction of a second after depressing or letting go of a key, the key's state will bounce between pressed and not pressed. You probably don't see this when the loop contains code because the small amount of time it takes to execute that code is enough for the key's state to stop bouncing.

Quote from: Runer112 on October 03, 2011, 03:12:00 pm

Freyaday, I'm pretty sure loops work exactly like they're supposed to. Your problem might be key bouncing, meaning that for a small fraction of a second after depressing or letting go of a key, the key's state will bounce between pressed and not pressed. You probably don't see this when the loop contains code because the small amount of time it takes to execute that code is enough for the key's state to stop bouncing.

That is bizzare. Is it something physical that happens, or an electrical glitch?

I think it's just the nature of how metal contacts act when extremely close together, but not quite touching. I'm not 100% sure, but that's my best guess.

---

Anyway, here are some bugs that I think are actually the fault of Axe and not strange hardware quirks.

• If the last line of a program is CONST→, no error is thrown and no code is produced from it. (What's up with all the last line bugs anyway?)
  
  
• ᴇ and π don't throw errors if followed by no valid digits, they're just interpreted as zero. They should probably also throw an error if the digit field contains an invalid alphanumeric digit. For instance, no error is thrown at ᴇ86GC, which could cause great confusion to people who don't notice the invalid hexadecimal character G.
  
  
• I'm not 100% sure of this one, but I think Axe might use some bcalls that aren't present in older operating systems. In this case, Axe should either avoid those bcalls or check the OS version before running. This animated screenshot taken by ben_g is what lead me to believe this:
  
  
  
  

Another thing about loops appearing to quit early. If you have a menu, or something that checks for enter being pressed at the beginning of your game, sometimes it "picks up" the enter from the home screen to run the program. Sometimes this creates the illusion of quitting early.

That's an easy fix, just put a wait at the start of your program for until enter is no longer pressed.

{CONST} or {CONST + Var} produces a 'Wrong # of Args' error