I have another feature request: could you make it possible to have atomic masses with 4 digits, i mean this:
H=     1.008
Ca=  40.08
Xe=131.3

etc. so that I can also use the molar mass calculator in class?
thanks!

Well, I'm going to leave it at 2 decimals. That's what my friends and I who are in AP chem need.

Personally I use calcutil for that, but the possibility to run it using zStart would be cool for some.
Maybe, you could choose whether to recall a certain token or run an app/prog?

Yes, for handling the custom keys, that's probably what I'll do. I just wonder how I'll run programs that need Mirage/DCS.

Every thread needs a creative title.

Lately, between track and homework for the AP tests, I have had almost no time to program. So I decided to start programming during school in Mimas. I decided to do Conway's Game of Life because I saw the demo for the Prizm and it looked like it would be fun to use. So I've been working on this during school for about two weeks now and finally today, it actually worked. Although, I probably would have finished this way sooner if I could have used a debugger. It's pretty frustrating to just make changes and hope the program doesn't crash.

If you don't know what Conway's game of life is, here is the general idea: Every pixel is a cell acting independently, whether the cell lives or dies is decided by a set of rules:
1. If three of the eight cells surrounding a dead cell are living, it is born
2. If there are 0 or 1 cells surrounding a living cell, it dies of loneliness
3. If there are 2 or 3 cells surrounding a living cell, it lives on
4. If there are 4 or more cells surrounding a living cell, it dies of overpopulation

To make all this happen, I use most of the extra ram page (13,608 bytes) as well as about 900 bytes of hard-coded routines to do all the checks for every bit. I use the concept of active and not active cells to speed up my simulation (if none of the cells around a cell are alive, it won't do anything next round either). I also make extensive use if IX.

Some stats:

• 160 x 160 board
• goal 16 fps (it typically does this until about 200 active cells)

Controls:

• 2nd - toggle pixel
• Y= - clear board and recenter
• Zoom - step
• Graph - start/stop
• Clear - quit

Here is the game, I've been using it all day, so it works. I'll get the source later, it was written in Mimas after all. And I think my favorite part of this game is that while the actual game is only 1,042 bytes, it expands to about 1,900 bytes of code and uses 14,000 bytes of ram.

Ironically, my name makes a pretty awesome design.

hey, midis are music just no lyrics, but you get a lot more on there.

Sorry, I didn't say that right. I had to get the post in quick though because I was getting ninja'd left and right.

Ok, so I got the headphone thing working, it was a pain but it works.

Updates:

• ON + [Y=] - Toggle between head phone/normal mode (you can't link in headphone mode)
• Whenever my texts are displayed to the homescreen, it refreshes the cursor hook which Mirage destroys for no reason
• On + [COS] - now does nothing (you can find Asm( yourself lol)

About the headphone thing. During the monitor, (the context that flashes the cursor and handles keys), the OS runs a loop that is based on 3 interrupt cycles. 1 and 2 display the clock in the Mode menu, and 3 handles linking and keys. What happens is when headphones are in, the calculator sees that the link port is not normal, clears the getCSC value (why?), spends 1 sec waiting for link response, then checks the getCSC value it just cleared and restarts the GetKey loop.

The problem comes from 1) the getCSC value is killed, 2) the calculator waits a second, and 3) the calculator resets the GetKey loop ever single time. This means 1) unless you are really lucky, the keys won't be detected, 2) it's slow as crap, and 3) the cursor doesn't blink.

So my solution was to install a silentLinkHook that runs bcall(_kdbScan) (scan for keys), resets the silentLinking flag, and kills all silent linking. I didn't want to kill the silent linking, but the stupid one second delay left me no choice. Also, the cursor doesn't blink, but I can't make it without OS mods.

Axe installed automatically on ram clear (and calcutil functionality as an option, like omnicalc would be awesome)

Quote from: Darl181 on April 28, 2011, 12:35:25 am

might it be possible to custom-assign the on+sin/cos/tan key combos with a token in the catalog?

* Darl181 walks away whistling

For the Axe thing, I believe that Quigibo is trying to add an entry point for me. For calcutil, I'll look into that.

And custom-assigning the on+sin/cos/tan keys, I can probably do that. Although it might be more useful if I made it the number keys rather than the trig functions.

Boo! Sort of a necro but I have a possible feature request? Could you possibly add something that would make the os not freeze when something is plugged into the headphone jack? (Is that possible?)

There will never be a necro post in this topic. I've been doing this app for over a year, it's basically just my flash page where I can put hooks, so each update is more or less an individual project. This topic won't die until I do , or maybe when i reach 16kb of code.


I like the idea of not freezing with headphones. However, I don't even have the slightest clue as to why it freezes, let alone stopping it. I do see serious potential there though, so I'll see if I can fix that.

Stop making epic programs. Give someone else a chance

Now's your chance. Track and AP homework have me tied down for a while so you can get ahead of me with some crazy program.

But after the AP tests and track are done...

Edit2:
    Nvm, I lose. I didn't realize that we want to stop when we hit the walls, not loop. So just use this post as a learning exercise.

You're on runer. If we assume that the only requirements are that you are able to move the letter I around the screen, and quit, then this wins. I got it done in 40 bytes.

So "features" of this one: it shows a trail of 'I's, any key besides the arrows quits, 'I' starts at a random location (how fun!)

;de = xy


loop:
bcall(_getCSC) ;a = key
dec a ;down is 1, we just keep decreasing
jr nz, notDown ;a because the keys are really nicely
;numbered for this
inc e ;e is y
notDown:
dec a ;left is 2
jr nz, notLeft
dec d ;d is x
notLeft:
dec a ;right is 3
jr nz, notRight
inc d ;d is x
notRight:
dec a ;up is 4
jr nz, notUp
dec e ;e is y
notUp:
dec a ;only things we are interested in
;0 = null, 1, 2, 3, 4
;all of these will be negative by this point
ret p ;return if it's positive

ld a, e
and 7 ;loop y at 7
ld e, a
ld a, d
and 15 ;loop x at 15
ld d, a


ld (curRow), de ;set the xy
ld a, 'I' ;set the char
bcall(_putMap) ;display it
jr loop

Too bad ld (xxxx), de is 4 bytes. I didn't know that until just now.

Edit:
    Lol, runer, mine is so much more readable than yours. I'm still not exactly sure how it works.