« previous next »
Pages: [1]   Go Down

Author Topic: How do you know when your App is getting too big for 1 page?  (Read 14475 times)

0 Members and 2 Guests are viewing this topic.

Offline Jerros

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 137
  • Rating: +9/-0
    • View Profile
How do you know when your App is getting too big for 1 page?
« on: August 16, 2010, 10:51:10 am »
So I've been working on an App, making it larger each day, but now I get the feeling random bugs pop up out of nowhere.
It's kind of similar to what happened when my programm breached the 8kB limit and had to be turned into an App.
Thus the next step would be to add another page to the App, although I dont know wether that's needed or not.
Any way to check that?
Logged


79% of all statistics are made up randomly.

Offline thepenguin77

  • z80 Assembly Master
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1594
  • Rating: +823/-5
  • The game in my avatar is bit.ly/p0zPWu
    • View Profile
Re: How do you know when your App is getting too big for 1 page?
« Reply #1 on: August 16, 2010, 11:14:27 am »
It's when it gets over 16,384 bytes that it requires two pages. There are two ways to check for this.

1. compile your app as a program and check it's size on the computer. This will give you a rough estimate of how bit it is.

2. Download Omnicalc run it and press 6, 1, 3. Then find your app, when you have it selected, press Alpha H. Your are now looking at your app as it is in calculator memory. Alpha G is goto, so by using that, you can look for the end of your file. You'll know you found the end because it will go from random bytes to all FF's. The max size for a one page app is $4000 bytes, so if the end is around $7800, you'll be needing two pages soon.
Logged
zStart v1.3.013 9-20-2013 
All of my utilities
TI-Connect Help
You can build a statue out of either 1'x1' blocks or 12'x12' blocks. The 1'x1' blocks will take a lot longer, but the final product is worth it.
       -Runer112

souvik1997

  • Guest
Re: How do you know when your App is getting too big for 1 page?
« Reply #2 on: August 16, 2010, 11:22:33 am »
Quote from: thepenguin77 on August 16, 2010, 11:14:27 am
It's when it gets over 16,384 bytes that it requires two pages. There are two ways to check for this.

1. compile your app as a program and check it's size on the computer. This will give you a rough estimate of how bit it is.

2. Download Omnicalc run it and press 6, 1, 3. Then find your app, when you have it selected, press Alpha H. Your are now looking at your app as it is in calculator memory. Alpha G is goto, so by using that, you can look for the end of your file. You'll know you found the end because it will go from random bytes to all FF's. The max size for a one page app is $4000 bytes, so if the end is around $7800, you'll be needing two pages soon.

I think you meant Calcsys, not Omnicalc.

Logged

Offline Happybobjr

  • James Oldiges
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2325
  • Rating: +128/-20
  • Howdy :)
    • View Profile
Re: How do you know when your App is getting too big for 1 page?
« Reply #3 on: August 16, 2010, 11:28:10 am »
its like 16,0000,  a little bigger than that actually.

go to your memory on the calc.  look at the amount of memory your smallest app takes. if it is about 16000 then thats it.  now subtract about 150 from it, just because of ummm, well i dont remember why
Logged
+0/-1 karm for this message
School: East Central High School
 
Axe: １.０.0
TI-84 +SE  ||| OS: 2.53 MP (patched) ||| Version: "M"
TI-Nspire    |||  Lent out, and never returned
____________________________________________________________

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: How do you know when your App is getting too big for 1 page?
« Reply #4 on: August 16, 2010, 01:51:24 pm »
You don't need to check because I doubt your app signer will sign an app that's too large.  But I use this:

Code: [Select]
#define VALIDATE(last) #if ($+0 > (last)) \ .echo "ERROR: MEMORY: " \ .echo ($+0 - (last)) \ .echo " bytes too large\n" \ ld q,q \ #endif
So then I just do VALIDATE($7FBD) at the end of the program.  The lower size is to give enough room for the signature.  Its great to use for any self modifying code that you copy to ram to make sure you don't overflow the buffer.  Spasm has many of these macros built in as well.  The ld q,q is just there to generate an error by the way.
« Last Edit: August 16, 2010, 01:53:18 pm by Quigibo »
Logged
___Axe_Parser___
Today the calculator, tomorrow the world!

Offline thepenguin77

  • z80 Assembly Master
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1594
  • Rating: +823/-5
  • The game in my avatar is bit.ly/p0zPWu
    • View Profile
Re: How do you know when your App is getting too big for 1 page?
« Reply #5 on: August 16, 2010, 08:35:33 pm »
Quote from: souvik1997 on August 16, 2010, 11:22:33 am
Quote from: thepenguin77 on August 16, 2010, 11:14:27 am
It's when it gets over 16,384 bytes that it requires two pages. There are two ways to check for this.

1. compile your app as a program and check it's size on the computer. This will give you a rough estimate of how bit it is.

2. Download Omnicalc run it and press 6, 1, 3. Then find your app, when you have it selected, press Alpha H. Your are now looking at your app as it is in calculator memory. Alpha G is goto, so by using that, you can look for the end of your file. You'll know you found the end because it will go from random bytes to all FF's. The max size for a one page app is $4000 bytes, so if the end is around $7800, you'll be needing two pages soon.
I think you meant Calcsys, not Omnicalc.

Good thing you caught that, he would have been really confused. Calcsys is what you're after.

Calcsys Omnicalc, sp pc, they're all the same thing.  :)




Logged
zStart v1.3.013 9-20-2013 
All of my utilities
TI-Connect Help
You can build a statue out of either 1'x1' blocks or 12'x12' blocks. The 1'x1' blocks will take a lot longer, but the final product is worth it.
       -Runer112

Offline Jerros

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 137
  • Rating: +9/-0
    • View Profile
Re: How do you know when your App is getting too big for 1 page?
« Reply #6 on: August 17, 2010, 04:17:06 am »
Okay, I'll check it with your tips, thanks.
The programm is currently ~6000 lines, but I guess that what Quigibo said is right, my compiler will probably error if I'm exeeding the limit.
Thanks all.
Logged


79% of all statistics are made up randomly.

Offline ACagliano

  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 919
  • Rating: +32/-2
    • View Profile
    • ClrHome Productions
Re: How do you know when your App is getting too big for 1 page?
« Reply #7 on: August 17, 2010, 07:21:30 am »
Can Axe compile to a second page, or are we limited to 16,000 bytes?
Logged

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55943
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: How do you know when your App is getting too big for 1 page?
« Reply #8 on: August 17, 2010, 07:51:06 am »
Well, he's using ASM, not Axe, so Axe is out of the question here.
Logged

Offline Jerros

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 137
  • Rating: +9/-0
    • View Profile
Re: How do you know when your App is getting too big for 1 page?
« Reply #9 on: August 17, 2010, 08:49:47 am »
News-flash:
My compiler just said my header is "invalid". (while I havent touched the header in months)
I guess I just hit the limit.
I don't hope adding another page will be alot of work though...
Logged


79% of all statistics are made up randomly.
Pages: [1]   Go Up
« previous next »