I think the editor should be separate. Some people may not want to create levels and will prefer a smaller file in that case. I don't think the play button will work, though.

You could always make it an app if you wanted, you get double the file size that way ^^

I've never worked with apps before. I have no idea what I can/can't do from one... etc. Never really looked into it. I don't even know how to compile to an app with Axe...

Its easy Just go to options, and select Application under 'shell'.  The only difference between apps and programs is you can't modify any data that you create in your program.  ie: you cant do this:

Code: [Select]

[000102030405]->Str1
9->{Str1+5}  //cant do that!
you have to do this instead

Code: [Select]

[000102030405]->Str1
Copy(Str1,L1,6)  //copy it to some free ram, but you cant copy back
9->{L1+5}

Well I'm sure I don't do that anywhere...
... Actually SMC is possible but not realistically I know that...

I'm not sure it's worth it yet.  If I hit the point where I can't keep it below the limit, yep, it's an app.
Until then, I'll settle for a prgm's faster compile speed.

well just so you know that the option is easy to convert and you don't have to worry about keeping compatibility for the most part   And this isn't even the hard SMC the tricky part is where you start to modify more than just data

You're giving me a headache just thinking about the debugging 

Are you talking about the epic amount of time it takes to compile an app? Yeah, me too.

Are you talking about how the calculator seems to not do what I tell it? Yeah, me too.

I think the editor should be separate. Some people may not want to create levels and will prefer a smaller file in that case. I don't think the play button will work, though.

Actually, do Axe programs initialize variables automatically?
If not, there's always:
GetCalc(prgmBREAKOUT)
Asm(jp hl)
... on second thought that won't work. It'll mess up all my pointers. :'(

Quote from: lookitsan00b on November 15, 2010, 09:49:03 pm

Well I'm sure I don't do that anywhere...
... Actually SMC is possible but not realistically I know that...

SMC is easier to write than you might think. It's debugging that's the pain

Im saying SMC in an app is unrealistic, except when you have it copy itself to RAM... but that's cheating

Ah glad to see you back. I was getting a bit worried that you kinda lost interest or something. (Some people starts calc programming then quit 3 weeks later ). Glad you got the bug fixed. I don't mind if it's an app or a program, by the way. I would go with a program if your game still compiles under 15 KB, though (and if you're below the 8192 bytes code limit present with programs)

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
 

I knew there was something I left out! I changed the winning and Game Over screens!
Sorry for forgetting to list that in the update list and readme.

Guess its about time to get me a ticalc account?