... most people in my math class who dont' program (which is all but me) who have calculators bought the fanciest ones possible: ti84+ SE's in cool colors like blue or pink -- and even I don't have that! Of course, their archive will never shoot down below 1500K, ...
Actually those with 84+SE's who don't use them have calcs with archive space that is often horrendously low due to all the bloatware apps that come with 84+SEs...because they will never even bother to delete those apps
Progress moves along... I found another bug with the move learning engine...but it shouldn't take too long to fix at all: I think I just need to add a +5 somewhere... Meanwhile I'm working on transferring the project over to axe 0.4.8 which involves...some messiness (By how much was L1 moved between 0.4.6 and 0.4.7? Was it 54 or 56 bytes?) . Also I've begun to tile the next area shown in the screenie:
Looking great, the physics seem awesome. As for the for to while loop Runer112 has a version of that in the optimization compilation...wait here it is:
Ticalc.org has started hiring to fill their position for primary news editor-the office responsible for featuring programs and posting news. The only qualifications are a love of calcs (which I think we all have ), a time commitment, high availability, and an eye for news, so if you think you've got what it takes, submit an application by Sunday February 13th 2011.
Lol, that guy looks like the one from Pokemon. The graphics look great, but is the gray as flickery on calc as in the screenie? Also, do you think that 16x16 gives you too narrow of a view? (although I guess it's too late to change that...)
Sometimes objects are hard to interact with: if you're standing right in front of a door you have to move back a bit before you can open it; the same goes for the flashlight; I spent about 20 seconds running around that room trying to pick it up (But it wasn't that bad once you got used to it) Also, is it possible to change the font of the text on the bottom of the screen? Or maybe make it fade in as well as out..that would be cool.
Grammar nazi: You spelled proceed as procede, one of the I's isn't capitalized, and "alright" should be "all right."
Also, I really like how
Spoiler For Spoiler:
the guy gets killed after the earthquake that one really took me by surprise. And also how the flashlight just spazzes when it runs out of power. And also how I could've actually written a new post to say this stuff but I didn't lol
Aaaaaahhh so good! I take it where it says "to be continued" is the end of the first level? This is amazing Builderboy, great job! I love the sound effects, they really added to the atmosphere of the game
Axe Memory Mapper v1.1 allows you to look at every address (0000 through FFFF) of your calculator's RAM and their contents. (Like Calcsys' hex editor, but more Axe user friendly)-The useful part is that it shows you the offset of the bytes you are viewing from common saferam areas.
It shows both the decimal and hex value of the highlighted byte, along with the binary translation and the 8x8 sprite of the 8 bytes following the highlighted position. The pointer is displayed in decimal, hex, and L*+offset format. Navigation features include membank switching, a goto function, and a comprehensive search function for programs/appvars as well as strings of up to 8 bytes in ASCII or hex. See readme for full features list and controls
Oh, no I mean removing the memory menu completely from the OS and then making a separate app that handles the same stuff as the memory menu (obviously with an updated/upgraded look and ability). Then they couldn't even access the memory menu to begin with. You could even protect your app with a password...
Actually this wouldn't even be that hard in Axe. Archive, UnArchive, Delvar, all you need is a menu interface and knowledge of how to sort the VAT and you're good
You can't use file pointers the same way you use regular ones . The getcalc operation with file pointers doesn't return a pointer to the appvar like with appvars that are in RAM because objects in archive need three bytes, not two to access them. You need a byte for the page that the object is on and two bytes for its position within the page. Because of this, the GetCalc() operation doesn't return a pointer that you can store to a variable like with objects in RAM. So instead of using the value returned by the getCalc operation, you just use the file name (eg Y1, Y2, etc). Note that (i think) you can't do any math besides addition or subtraction with them- no Y1*2 or anything like that. Anyway, the correct (and optimized) way to do what you are trying to do is
Anyway, of course there would be another bug. Here's demo 3.1 If you already loaded v3 on your calc, the only files you need to resend are Ash.8xk and thetaAshTD.8kv
Show Posts
(although I guess it's too late to change that...)
(But it wasn't that bad once you got used to it) 
that one really took me by surprise. And also how the flashlight just spazzes when it runs out of power. And also how I could've actually written a new post to say this stuff but I didn't lol
)
