I was in search for a nice syntax highlighter for this blog and found this. Let’s see how it works:
|
1 2 3 4 |
public void onTouch( MotionEvent event ) { processMultitouch( event ); } |
Well, i guess that does it for my purposes 🙂
Last weekend i started integrating the desktop editor for Newton into the android version (yes, there’s a desktop version of Newton too, using the same exact code). I was initially a bit afraid that the editor is to fiddly to work on the small screen of say the hero or G1 (didn’t test on tattoo). However, my fears have vanished. The editor is now in a fully functional state along with a dead simple way to upload and share your levels with others. I recorded a small video showing of the editor in action:
Sorry for the bad video quality, i need to get a new webcam. This one hasn’t been in action for a bout 3 years :p.
The video shows of the intuitive interface of the editor (at least i think it is intuitive). Just drag and drop any item on screen. To create a new obstacle select the respective button at the bottom (the green one) and draw the corner points of the obstacle. You can also easily animate obstacles via a time slider shown at the top of the screen. Once you feel like the level is ready for some testing you can do a try run of it via pressing the run button. Pressing the back button in the run screen brings you back to the editor and the map you just edited. If you feel confident enough that your level is awesome you can either save it to your local sd card or directly upload it to the server from where other users can download, play and score points on your map.
To get to play maps created by others you simply go to the level selection menu, chose online levels and start playing any map you like. Highscores are of course also recorded for user generated maps.
Now we are busy creating the levels for the final version. Stefanie will (hopefully! /me shakes fist!) do most of that work, so blame here if a level really pisses you off :). We will probably not make the planned release date this sunday and instead aim at some time next week. The levels should be worth the small amount of money you’ll hopefully spent.
Leave your thoughts in the comments!
I was fooling around with multitouch the last weekend a bit and arrived at the conclusion that at least my android screen fucks up a lot of the events very often. I searched quite some time for a fix, read all the available documentation very carefully but couldn’t come up with a solution.
The problem is also visible in some android framework tests and all the multitouch games i tried on my droid. You can find a couple of videos here and here. I also found this thread over on the android groups but there’s been no helpful reply yet.
Just for fun i was googling around a bit today and found this nice site. It features a helper class that cleans up the multitouch event stream and should clean up the mess a bit. It’s used in the eclair version of cyanogen’s mod at the moment. I only tested it briefly but so far it seems to work. Cudos to Luke Hutchison who devised this nice little class.
I will report progress on this issue in the near future.
Edit: Luke Hutchison kindly replied to the android group thread over here and confirmed my suspicions. I’d love to get some comments on this from google framework engineers. Thanks Luke for helping us all out on this matter!
Edit2: Well, and he replied here as well. Thanks again! I also wanted to note that the problems Luke mentioned and i experienced are not inherent to only the G1 but also occur on my hero as well as my droid. I don’t know how the Nexus one performs in that regard, let alone other less widely spread devices. I will try to come up with some template code you all can use for your game programming needs in the near future and share it here.
