Streetwalker, an app *has* to take up at least 16,384 bytes (and in $4000 byte multiples after that) even if your code is just 3 bytes! There's no way of getting around it, so I might as well include whatever I can fit in. Oh yeah, and thanks for the heads up DJ! I knew there was a problem yesterday, but I thought it would have worked itself out. I'll make a quick program to enable and disable low color mode so you can see low color mode for yourself. By basic I just mean 8 basic colors, enough to plot and use the calc as a calc, but probably not enough for game graphics. A light blue would appear just white or blue depending on which color it is closer to.

However, I could make it into an asm program and use self modifying code to reduce the code size to next to nothing! There's a lot of copying and pasting going on for each separate column. But then it wouldn't have the perks of an app.

i guess smc could be used to make it harder to lose your highscores.

Yeah at least on the Nspire when the calc crashes, you don't lose anything and on Casio calcs I think you only lose stuff updated after the last time you turned the calc OFF.

Also thanks for the program, I'll check it out later

Buttonz v1.5 is released.

Updates:
    Screen flashes if you hit the center of a block
    High scores are auto archived on app exit
    Bug fix during unarchiving
    HW2 int changed to HW1
    2nd button increases level up to 10
    Increased points at higher levels
    Low color mode used to conserve battery
    Levels increase faster
    Max speed at level 15
    Highest level reached displayed with high score

Thanks adriweb, Sorunome, Keoni29, Hayleia, DrDnar, DJ Omnimaga, Xeda112358, Streetwalker, tr1p1ea and Runer112 for your comments and suggestions actually...

Modified the first screen:

Thanks! I couldn't find exactly how much power is saved using low color mode, but it is labeled as a power saving function. I'm assuming it bypasses the fine tuning resistors, not exactly sure though, the datasheet (or my reading!) isn't too precise.

 I'm just hoping no one gets upset!

Ha Ha! Oh man Omni! I really hope your still using the old version! I probably should have pointed out that it still hasn't been accepted on ticalc yet, right now you can get it from my blog http://briandm82.com/?ddownload=265

Hopefully that should fix most of the problems I will fix the contrast bug (it's because I turn off the backlight and it resets and I don't pay attention, never change my contrast, and do a very poor/lazy job at bug testing)



When you run v1.5 it will delete the old high score table (because this calculates points different along with level) and you will see the screen I posted above. The high score table will now display the level you made it up to.

It's definitely better than the old version, the levels use to drag on and if you lost you probably didn't want to restart from the beginning. I would have to watch the bonus level to see when it went up. Now you can skip levels to try to get back where you were.

The low color mode in the game only exists during the game, on exit the LCD settings are reverted to exactly the way they were before the game started. If you were referring to that low color program I made, run it again to turn low color mode off. With the low color mode, edit a basic program and go to colors to see exactly how they change. It's really a toss up between colors and some extra battery life. Maybe keep low color mode on while your adding numbers and stuff but if your going to play a game be sure to shut if off unless the game looks good with a lower color count. Again, I don't know how much battery life it saves, but if you want maximum run time per charge, enable low color mode and cut off or turn down the contrast. In Buttonz, low color mode doesn't take away any colors so I might as well enable it. The screen flashing part of the game is just the colors being reversed temporarily.

Thanks for pointing the contrast reset out!!!!!!!!! Will be fixed immediately!!!!!! So far you found three bugs!!! One you probably didn't know, but your suggestion on archiving the variable pointed it out! From now on, I'll probably send you versions privately first

HW1 and HW2 are two different interrupts, HW2 runs faster but when I was testing it on the oscilloscope I noticed sometimes it would run erratically. That's just my calc though, it goes through a lot of abuse like random values being thrown at a port. (But a reset always fixes everything, nobody should be afraid to do some testing ) Hw1 goes slower but fast enough. Here's what it looks like when I pulse a line with it:

Oh no, what happens is it caches the page when someone visits, I need to reset that I think. Im going to do it right now and I just uploaded v1.5.1 which will address the contrast reset. It basically just skips turning the backlight off. Sorry DJ, that caching sucks, but it helps the pages load faster. I'll keep that in mind when I update from now on. I hope it works, open Buttonz.asm with a text editor and verify it reads Buttonz v1.5.1 if possible.