I was just wondering what was going on with this project, glad to see you working on it again!

It's a hook It just sets the key delay counter ($8442) to one.

I kinda like the name. If you want to change it go for it, but i think Source is nice.

I doubt keypresses will be causing your crash unless you don't handle "other" keys. Generally that just means jumping back to the main loop if no keys were pressed. The key value in a getting modified would just cause your character to move left instead of down, for example, not crash. I would put everything after the title screen (which looks much better now in my opinion!) and pick one thing to work with. For example, get your grayscale stuff set up and running and then draw a sprite. Then use that sprite routine to render a predefined list of objects to the screen. Once that's done and working correctly, create another routine to populate the objects list. And so on. One part at a time, with testing and debugging at each stage. You can use the code you've written as a basis for what to do next, but you really need to go one routine at a time.

The first post in this thread was almost two months ago and you still haven't been able to debug it past the title screen Anyway, if there's anything i/we can do to help, don't hesitate to ask. I've even installed Mono!

I guess "touched" means when you poke the screen with your finger. I don't know anything about webdev though. I'll happily help you figure out what's crashing after the title screen, i'll even try setting Brass up (though i'd much rather use spasm ).

So... pimath, are you an asm guru yet? Ask us some questions!

You'll need to use direct input to read the keys. Though you will probably need to at least use some ion calls, like ionFastCopy to draw the graph buffer and ionPutSprite to draw a sprite to the screen. You could write your own sprite routine that wouldn't be too hard if you kept it aligned (meaning you can only draw to x multiples of . Writing your own fastcopy routine isn't too hard if you know how the LCD ports work, but it's probably beyond the scope of this project.

You can use direct input to either read the numbers 0-9, if the number is correct, display a check sprite or something, if in correct, display an x sprite. You can also use the up and down arrows to increase and or decrease the number you want to choose.

Doing this without any external routines makes this program much more complicated. That or much more boring, as nothing will get drawn to the screen. The screen will be blank until you guess the correct number and then exit.