Alert after Alert in J2ME

I just discovered a very nasty restriction in J2ME concerning Alerts whilst developing a MIDP 2.0 application for a Nokia E70 Mobile Phone (running Symbian 60 3rd Edition). As has become common now, the code I had worked find in the Sun Wireless Toolkit emulator but not so on the E70. Anyway, here’s the deal …

If you display an Alert object (e.g. a Yes/No dialog), and then (as a result of the user selecting Yes or No) try to display another Alert object after that, the phone will generate an IllegalArgument exception. This is because of the default behaviour of the Display.setCurrent(Displayable) method which assumes that you want to return to the object that created the Alert after the new alert is dismissed. Now, in my view, this is a reaonable thing to want to do. However, the exception that is thrown suggests that an “Alert cannot return to an Alert” which is not documented anywhere that I’ve seen.

So, the solution was to use the Display.setCurrent(Alert,Displayable) method and ensure that the second parameter is never another Alert.

Thanks to Naomi and Brian for their help on this.

Deise Dictionary of Waterford Slang

I’m delighted to announce the publication of the second edition of The Deise Dictionary of Waterford Slang, brought to you by Wellboy and the team at www.UpTheDeise.com. This is truly a modern classic, filled with useful (and not-so-useful) phrases for all walks of life in Waterford, Ireland.

Priced at a mere €10.00, it would make an ideal stocking filler this Christmas. It’s available from The Book Centre in Waterford or online at www.UpTheDeise.com.

Best of luck Wellboy, boy!