Touch Tiles is a fast paced game of memorization, you race against the clock in an effort to complete each increasingly difficult level by touching matching tiles. Play for a high score by matching tiles before time runs out.

Each level begins with a sneak peek at where all the tiles are located, when the timer starts you must touch – the game utilizes the touch screen of the Blackberry Storm and recognizes both the user touching or clicking – each matching tile. If you correctly touch two matching tiles then you score points. If you make an incorrect match you suffer a penalty and the tiles flip back over.

Some levels feature twists on the basic rules for more difficult game play. Standard levels have a sneak peek of all the tiles before the timer starts, only the game tiles are shown, and when you make a correct match the tiles remain face up. Hidden levels play like standard levels but when you make a correct match the tiles are turned face down. All Tiles on Board levels have all 20 tiles on the board but only some of the tiles are matching pairs. No sneak peek levels are the most difficult as they play like normal levels but you don’t receive a sneak peek at the beginning.

You gain more points for getting more matches in a row as well as completing a level without making any mistakes. You can also earn Awards by meeting specific criteria; i.e. getting seven matches in a row, finishing a level perfectly, getting an incredibly high score. The Awards system allows for re-playability as you try again and again to unlock more and more awards.

You high scores are tracked over multiple games as well as your overall total score, total play time, and total number of games played. These numbers factor in to earned some of the toughest Awards the game has to offer.

Features:
40 levels of increasingly difficultly
Track your high score for each level
Earn awards for beating specific criteria
Numerous rules makes each level different from the last
Challenging but easy to play

A peek at the latest program that I've written for the Blackberry Storm.

Touch Tile is the latest piece of software I’ve written and my first real release for the Blackberry Storm. It utilizes the touch screen to create a quick paced memory style game.

If you are interested in giving me some feedback and doing some light beta testing please contact me and I’ll send you over a copy. I plan on releasing it in the next two weeks once I’ve finished up some loose ends.

Very simple game; it’s a knock-off of the old board game memory. Race against the clock in increasingly difficult levels matching tiles to clear the board. I’m working on adding alternate play conditions to add something new to the genre.

Having problems setting up a timed action in your Blackberry program when using Timer() and schedule. Let me take a few moments to break down how to setup a recurring task utilizing TimerTask.

A TimerTask is a set of actions that are called from a Timer that is running on a schedule.

Timer theTimer = new Timer();

TimerTask tt = new TimerTask() {

public void run ()

{

System.out.println(“1 Second”);

}

}

theTimer.schedule(tt,1000,1000);

I’ve created a Timer object and a TimerTask and set the TimerTask to a scchedule that begins 1000 milliseconds after the initial call and will repeat every 1000 milliseconds until it is cancelled.

The problem I had was I couldn’t figure out how to stop and start the schedule. You have three options.

Cancel the Timer. Using theTimer.cancel() you will stop the schedule, stop the TimerTask and destroy the Timer. The problem is you can’t recreate it on the Blackberry. Every time you do you get an error message.

Cancel the TimerTask. Using tt.cancel() you will stop the TimerTask and destoy the TimerTask. The problem is you can’t call on the TimerTask again since it no longer exisits, so you can’t start the TimerTask, then cancel the TimerTask, and then start another schedule that uses the TimerTask because it no longer exists.

Cancel the TimerTask and recreate the TimerTask before setting up a new schedule. The Timer doesn’t need to be cancelled, just the task. If you cancel the task then it ceases to exist. So to start, stop, start, stop, etc. a task you must recreate the TimerTask. So you must ensure that somewhere between the TimerTask cancel – tt.cancel() – and the next scheudle call – theTimer.schedule(tt,1000,1000).

I wasn’t able to find a clear reason for the problems I was facing using TimerTask and thought I would write something up for future generations. You will be able to see this in action in the source code for Comedy Timing in the near future.