I'm preparing to push out an updated Omnom with the new level selector. I think there still might be some kinks in it, so please let me know what I broke
The campaign selection button is highlighted before you even press it
The default campaign's levels don't automatically show up
Exiting a level with backspace puts you back in it again. Next backspace pulls you out
I've not played with task switching
I think somethings not quite right about lives count
Weird box characters in the display
I forgot to mention, "r" restarts a level and "n" skips the level and lets you move onto the next.
When I made the game I had 2 seperate lives counters. playerLives was 2, and refered to the amount of attempts you have left before you lose a life. So getting hit by an enemy returns you to your spawn but does not reset the level, but getting hit again causes you to lose a life from the deathCount variable.
Not sure if these are still used but just thought I'd mention it as its kind of confusing
omnom is available for diablo but is not installable due to inability of HAM to find python-pygame.
ETA apparently because the package is called python2.5-pygame on Diablo. Since it built on Diablo's autobuiler I'm guessing build-depends is correct but depends is wrong for Diablo?
omnom is available for diablo but is not installable due to inability of HAM to find python-pygame.
ETA apparently because the package is called python2.5-pygame on Diablo. Since it built on Diablo's autobuiler I'm guessing build-depends is correct but depends is wrong for Diablo?
Yeah, I was awaiting getting more done before doing any serious Maemp 4.1 testing. I'm going ahead and prepping a build with the dep fix. Performance is going to be a killer though. We'll need to learn some lessons from projects like SolarWolf to figure out how to handle this or look to see if it is easier to get good performance with some Qt stuff.
I've been jumping around between projects too much to give this too much attention lately.
It is possible to add a support for non qwerty keyboard?
On azerty keyboard for exemple, we can only do left/right, up and down are done with fn+left and fn+right.
It is possible to add a support for non qwerty keyboard?
On azerty keyboard for exemple, we can only do left/right, up and down are done with fn+left and fn+right.
There is plans to add configurable key bindings. I need to find my post for what my roadmap is.
@FRuMMaGe I'm requesting a spot on bugs.maemo.org to pass off the bug tracker extras requirement. Do you have an account on it? Would you like to have rights to edit bugs?
