The site is currently in read-only mode for maintenance. Posting of new items will be available again shortly.
Bubbles is a board game designed for use on the Pocket PC. The game starts with a board full of colored balls (called bubbles). Adjacent bubbles with the same color can be removed from the board. The more bubbles you remove in a turn, the more points you score. When you clear the entire board you get bonus points.
Bubbles was my first try to create a Windows CE program for the Pocket PC. It first used MFC, but I switched to ATL pretty early during the project. The game demonstrates how ATL can be used to create Windows CE programs with a small memory footprint.
Infrared support is one of the most appealing features of Windows CE, so I wanted to enable IrDA support as well. High scores can be transferred between CE devices (or Windows 2000) using IrSockets. It's relatively easy to use and the project contains some wrapper classes to enable IrDA sockets (nonblocking to avoid lockups).
During the development of this game I noticed that the CE environment isn't as mature as the desktop Win32 environment. STL and WTL are both missing. ATL for Pocket PC isn't as stable as its Win32 counterpart. The emulator locks up when you play several wave files after each other.
The most annoying bug is in the ATL handling of
WM_INITDIALOG. Due to a very trivial error in this piece of code you are forced to override this method (otherwise
SHInitDialog won't be called). If you want to call
SHInitDialog yourself, then you need to override the method and pretend that you never did (otherwise ATL will call it again with it's own set of arguments). Very annoying and it took me a while, before I figured out that this was wrong.
Most Pocket PC applications allow only one single instance. If the application is started again it reactivates the first instance of the application. Despite 95% of the Pocket PC programs need this functionality there is no support in the API (or ATL) to accomplish it in an easy way. You need to register your own window class and when the application starts, you need to look for that window class. If it exists, then you need to bring the window to the foreground to activate the application again. Unfortunately, this doesn't work good when your main window wasn't the active window when you deactivated the application (i.e. a dialog was on screen). In that case the main window is activated and this causes some problems. The OK button of the dialog isn't visible. The dialog's
OnActivate isn't called, so the SIP (soft input panel) isn't disabled, etc...
Despite these problems this game can serve as a good starting point for your own games. Game logic is separated from UI and highscore, options and about screens can be easily reused. I started writing a Tetris clone using this template and I hope it can be useful for you as well.