When you are developing an application with your own graphic framework in a full screen mode, it is necessary catch the key codes from the user press action.

We have already seen that it is important to catch the events from the left and right soft key (which can have different values in different devices).

Sometimes it is necessary handle the other button codes which are not defined in the default codes of the MIDP Canvas class. One of those codes is the Clear (or Delete). You might have a your own TextField where you handle the key events from the letters (digits from 1 to 9) and there you might catch also that code to delete the character already in the field.

The code you have to manage (for example in the keyClicked method of the Canvas class) in that case is the -8 for the Nokia Series60, Sony-Ericsson and Samsung devices. The Nokia Series40 doesn't have a Clear (Delete) button.

If someone know other values for other devices, he can post a comment!

Three minutes of a Premier League game, Brimingham-Arsenal: Martin Taylor, Birmingham defender, tackles the Arsenal forward Da Silva Eduardo. But the tackle is not like many other tackles: the tackle is very late and dangerous, Eduardo have already passed the ball and the Taylor's foot hits Eduardo right leg. The big weight of Taylor push on the leg and breaks it.

The images of the accident are very vicious, the English TV doesn't show the replay. You can feel the pain only listen to the narration of the match commentators describing the condition of the Eduardo leg and his foot.

Probably he'll need 11 months to come back and play again. We want wish to Eduardo to come back stronger than ever and to score goal like this:

The problem happens sending several SMSs (5-10 or more) to a series60 device (all S60 2nd and 3rd Edition devices). The WMA unsinged midlets using PushRegistry acts wrongly when launching. We can have:

• Slow queuing of received SMSs;
• Symbian OS Error;
• Launching fails;
• Crash of application without message or error.

The solution claimed by the Forum Nokia is the signing of the Midlet with the Third Party Protection Domain and change the permissions for the autostart to "always allowed".

It is not a easy solution (the sign process is always a pain) and also it is a pity that the affected feature is one of the most interesting for J2ME developers.

Link to the Forum Nokia Knowledge Base article.

The Nokia N96 is the new high level Nokia device. Beyond the nice design, it presents also a lot of features among which the DVB-H support that make the user able to see tv programs in high definition.

It supports WIFI and A-GPS, it has a 5 MegaPixels Carl-Zeiss camera. The screen resolution is 240x320  and the color depth is 24 bit.

The operating system is the Symbian 9.3 and the Nokia family is the Serie 60 3rd Edition Feature Pack 2.

The Java platform supports the following JSRs:

• CLDC 1.1
• eSWT UI API
• JSR 135 Mobile Media API
• JSR 172 Web Services API
• JSR 177 Security and Trust Services API
• JSR 179 Location API
• JSR 180 SIP API
• JSR 184 Mobile 3D Graphics API
• JSR 185 JTWI
• JSR 205 Wireless Messaging API
• JSR 226 Scalable 2D Vector Graphics API
• JSR 234 Advanced Multimedia Supplements
• JSR 248 Mobile Service Architecture for CLDC
• JSR 75 FileConnection and PIM API
• JSR 82 Bluetooth API
• MIDP 2.1
• Nokia UI API

eSWT is a subset of the cross-platform SWT and give to the developer a finer control over the UI or a greater variety of UI components (called widgets in eSWT) than what the LCDUI API can offer. The drawbak of the eSWT is that it is supported only by the series 60 3rd edition FP2 or newer