Author Topic: Bug Reports  (Read 158887 times)

0 Members and 1 Guest are viewing this topic.

Offline Freyaday

  • The One And Only Serial Time Killing Catboy-Capoeirista-Ballerino
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1970
  • Rating: +128/-15
  • I put on my robe and pixel hat...
    • View Profile
Re: Bug Reports
« Reply #1500 on: September 27, 2011, 10:38:14 am »
Hi i just downloaded Axe 1.0.4 and wanted to compile a code i made with 1.0.2 into an app.
After backupping an unknown error appears :
A429958

If you close it the app still works normally
You might want to try with the new 1.0.5b that Quigibo just released today.
Gah, another new Axe :P

Nymless again.
To do a quicksave, I create the appvar NYMSAVE and then copy L3 to it, followed by all the predefined AxeVars (I have yet to code in saving for the three extra vars).
Unfortunately, something goes REALLY screwy with r3, which points to the start of the data for the mines. when you load form that save (copying the beginning to L3 and the rest to oA) all the mines are rotated 90 degrees to the left!
In other news, Frey continues kicking unprecedented levels of ass.
Proud member of LF#N--Lolis For #9678B6 Names


I'm a performer at heart; I stole it last week.
My Artwork!

Offline p2

  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 848
  • Rating: +51/-11
  • I'm back :)
    • View Profile
Re: Bug Reports
« Reply #1501 on: September 28, 2011, 11:16:48 am »
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?
*insert supercool signature*

Offline calc84maniac

  • eZ80 Guru
  • Coder Of Tomorrow
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2896
  • Rating: +467/-17
    • View Profile
    • TI-Boy CE
Re: Bug Reports
« Reply #1502 on: September 28, 2011, 12:05:17 pm »
So if I understand correctly, you're trying to compare to a character value? Try using '5' in the code (i.e. surround the character with single quotes), that will convert a character directly to a usable value without needing to use a string.
"Most people ask, 'What does a thing do?' Hackers ask, 'What can I make it do?'" - Pablos Holman

Offline p2

  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 848
  • Rating: +51/-11
  • I'm back :)
    • View Profile
Re: Bug Reports
« Reply #1503 on: September 28, 2011, 12:07:52 pm »
But how to check for a Var (X) or a Letter ("B")
*insert supercool signature*

Offline calc84maniac

  • eZ80 Guru
  • Coder Of Tomorrow
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2896
  • Rating: +467/-17
    • View Profile
    • TI-Boy CE
Re: Bug Reports
« Reply #1504 on: September 28, 2011, 12:11:49 pm »
Converting a variable X (0-9) to a number character can be done with (X+'0'). You can do letter characters the same way as number characters, for example, 'B'. Similarly, if you have a letter index L (1 to 26), you can create a character A-Z by doing (L-1+'A')
"Most people ask, 'What does a thing do?' Hackers ask, 'What can I make it do?'" - Pablos Holman

Offline Darl181

  • Vy'o'us pleorsdti thl'e gjaemue
  • CoT Emeritus
  • LV12 Extreme Poster (Next: 5000)
  • *
  • Posts: 3408
  • Rating: +305/-13
  • VGhlIEdhbWU=
    • View Profile
    • darl181.webuda.com
Re: Bug Reports
« Reply #1505 on: September 30, 2011, 10:32:32 am »
Horizontal (BUFF)- makes the calculator freeze.  No other variation of Horizontal has this problem.

Offline Freyaday

  • The One And Only Serial Time Killing Catboy-Capoeirista-Ballerino
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1970
  • Rating: +128/-15
  • I put on my robe and pixel hat...
    • View Profile
Re: Bug Reports
« Reply #1506 on: October 03, 2011, 03:07:00 pm »
While and Repeat loops that are empty
:While getkey(54)
:End
:Repeat 0
:1
:End!If getkey(54)
Stop looping before their condition is up.
« Last Edit: October 03, 2011, 03:07:19 pm by Freyaday »
In other news, Frey continues kicking unprecedented levels of ass.
Proud member of LF#N--Lolis For #9678B6 Names


I'm a performer at heart; I stole it last week.
My Artwork!

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Bug Reports
« Reply #1507 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.

Offline Freyaday

  • The One And Only Serial Time Killing Catboy-Capoeirista-Ballerino
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1970
  • Rating: +128/-15
  • I put on my robe and pixel hat...
    • View Profile
Re: Bug Reports
« Reply #1508 on: October 03, 2011, 03:13:05 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?
In other news, Frey continues kicking unprecedented levels of ass.
Proud member of LF#N--Lolis For #9678B6 Names


I'm a performer at heart; I stole it last week.
My Artwork!

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Bug Reports
« Reply #1509 on: October 03, 2011, 03:37:49 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:




Offline mrmprog

  • LV7 Elite (Next: 700)
  • *******
  • Posts: 559
  • Rating: +35/-1
    • View Profile
Re: Bug Reports
« Reply #1510 on: October 03, 2011, 05:15:23 pm »
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.

Offline Eeems

  • Mr. Dictator
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 6161
  • Rating: +318/-36
  • C'est la vie
    • View Profile
    • Eeems
Re: Bug Reports
« Reply #1511 on: October 03, 2011, 05:26:41 pm »
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.
/e

Offline NecroBumpist

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 130
  • Rating: +14/-5
  • Master of Lua
    • View Profile
Re: Bug Reports
« Reply #1512 on: October 03, 2011, 05:55:52 pm »
What's up with all the last line bugs anyway?

Lol, in the numerous parsers I've written, there has always been some fucking last line bug or another. The simplest answer I find that usually works is to append a newline character to input before processing begins.
Developing Lua scripts for the NSpire ?
Check out the Necrotorium
Need a few routines to run faster ? Checkout the MODS Lua Assembly Toolkit.
Need to save space for your scripts ? Checkout LuaSrcDiet

Offline Builderboy

  • Physics Guru
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 5673
  • Rating: +613/-9
  • Would you kindly?
    • View Profile
Re: Bug Reports
« Reply #1513 on: October 03, 2011, 06:08:55 pm »
{CONST} or {CONST + Var} produces a 'Wrong # of Args' error D:

Offline Quigibo

  • The Executioner
  • CoT Emeritus
  • LV11 Super Veteran (Next: 3000)
  • *
  • Posts: 2031
  • Rating: +1075/-24
  • I wish real life had a "Save" and "Load" button...
    • View Profile
Re: Bug Reports
« Reply #1514 on: October 04, 2011, 05:36:39 am »
{CONST} or {CONST + Var} produces a 'Wrong # of Args' error D:
Thanks, I just caught that.  A workaround for now is to just add the constant after the variable: Var + CONST, which is more optimized anyway.
___Axe_Parser___
Today the calculator, tomorrow the world!