0 Members and 7 Guests are viewing this topic.
Quote from: Oninoni on September 27, 2011, 02:28:54 amHi 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 :A429958If you close it the app still works normallyYou might want to try with the new 1.0.5b that Quigibo just released today.
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 :A429958If you close it the app still works normally
In other news, Frey continues kicking unprecedented levels of ass.
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 pmFreyaday, 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?
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.
What's up with all the last line bugs anyway?
{CONST} or {CONST + Var} produces a 'Wrong # of Args' error