iPart( and int( have the same effect for positive numbers, so that's not it.

It looks to me like fPart( is not returning the right number.  Try this when it crashes:
Figure out which variable was being used (it's probably the bad one).
Go into the Solver ([Math] [0])
Type that variable into the equation
Scroll up or down (I forget which) and look at all the digits of precision the calc has.  Here you can see what's happening to these numbers.

Fix: put a round(......,0 around the statement with the fpart(.  (Ex: int(6fPart((B-1)/6)+1->S changes to round(6fPart((B-1)/6)+1,0->S)

and... what is the difference between int(...) and round(...,0)?  Also, int( did fix my crashing problems.

okay more info on what is going wrong:
 if one_number = 9
    that_number=8
    if the_other = 8
      the_other=7
    end
  else
    everything works
  end

and 7 can be a valid #. lulz fun.

PS: what does round(...,0) do? I've always avoided round...

Well I guess I must be doing something wrong (other than learning how to work with inString, closing parentheses omission, and 2d strings, and using 2.53MP all at once)

I've been getting very strange errors recently...

Where B=inString(str4,str2) (after modifications (including a couple fPart(s, but it's still a natural number))
sub(str4,B,1) ;ERR: DOMAIN, (B=7 and length(str4)=36)
  -----
sub(str4,7,1) ;works fine with no change to the string
  -----
7 -> B
sub(str4,B,1) ;works fine
  -----
int(B -> B
sub(str4,B,1) ;works fine

... And that only happens on the second time through the main loop. (the next line of code is the 'End' for the main loop)

Now, after much work to make my obviously corrupting variables work, (using 'int(', of course) I have hit a brick wall.


when inString( returns '9', which I then convert to (3,1) (I did say it was a 2d string) I try to do this to it:
X+1-6(X=6) -> X
... and nothing happens. (I'm not totally sure that's true, but I do know that there is no writeback if it DOES do something)

Anybody with the slightest idea why this is happening?  Any help will get a nice polyalphabetic encryption program! (btw, this is the only bug left)

new in v1.05:

Well it has version 1.00. 1.00 means it's finished, normally. (unless there are bugs)

Can't wait for next version! By the way, in case you only check the forums project/axe sections and not the front page news, I made a Youtube video of the endless mode.

Do you think I have enough space in my app (I've used 9000) for that soundtrack?
And, yes, there were bugs.

btw, why does it say it's a four page app, when 9k clearly fits in one page?

Really? Theres soo many B-calls and far too many have almost cryptic names that I never probably would've known...

Btw this was supposed to be an I-suggest-something-awesome-and-somebody-else-takes-it-and-makes-it situation, but I do suppose I could give it a shot, given links to the documentation...

Hooray for Mimas!

EDIT: whats an MD5 hash? And what do oversized tater-tots have to do with anything?

This is great.  Well done Lookit'san00b!

Quote from: DJ Omnimaga on November 23, 2010, 01:55:23 am

I got 9020.

What?!  But that's OVER my high score 9000!

You seem to be implying that it is done.
Nope. Found a saving bug, finally fixed that bug with the balls passing through the blocks occasionally, and realized that, unless Axe 0.4.5 automatically signs apps, I forgot to do that. Oops I'll probably want to add some sort of delay on the editor's keypresses too.

So I'll try to get v1.05 uploaded by tomorrow.

Quote from: lookitsan00b on November 16, 2010, 11:49:52 pm

If not, there's always:

Code: [Select]

GetCalc(prgmBREAKOUT)
Asm(jp hl)
... on second thought that won't work. It'll mess up all my pointers. :'(

There's a b_call(ExecProg) or something like that that does that ... you'll have to move the program name to a particular spot in memory before you do that, though.

I think I'll just make two versions: split programs, and an app.
On second thought, who wants a program when you can have an app? I'll just use the programs for debugging.
Then again, you can just push enter from the homescreen to re-run a program. not an app. I'll have to add in looping back to the menu. Not too hard.

So, new in v1.0
  semi-intelligent paddle size powerups
  removed caps on paddle size and ball number
  added good reason to look at the source (okay a mediocre reason) see readme
  extreme mode
  looping back to the menu with the app version
  both app and bi-program versions included
 

Just got out of classes and a Math Club meeting...
Let's see...
The commands should be seen as functions. They either take an input and output a result or they just output a result. The result they output is always (at the moment, anyway) the last converted value. When I add things like getKey, the result will obviously be based on that. So for example, Line(T,A,B,X,Y will output Y as a result. Disp Y,X,<<String>> will output X as the result, since X is the last calculated result. So, when you use Disp Y,X in place of T for the Line( command, you are actually only using the X from the Disp command.

So to lookitsan00b, yes, you are right, if you think of it that way. It took me a bit to understand how you were saying it, but yes.

@Qwerty.55: I have not added any ability to work with number bases other than ten, but I do have 16-bit addition, subtraction, and multiplication ready. I just finished a 16 bit divide routine during Calc III, so now I have to add that in...

That's not exactly what I was saying, but yes that answers my question.

I was thinking that when it sees the line
Line(1,1,1,Pause Text(33,10,"HI"))

It parses it to a list like this

Arguments:
{1,1,1,33,10,"HI"}

Commands:
Line at an index of 0
Pause 3
Text 3

Line would then grab the first five parameters starting at an index of 0,
Pause would grab the first parameter starting at an index of 3, and
Text would grab the first three parameters starting at an index of 3.

Now that I think about it, it seems a little idiotic, since it wouldn't allow for addition and subtraction in parameters...

But that's what I meant.  You're doing it so much better