Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Archived:Long key press problem for Java ME TextField on some Eseries devices (Known Issue)

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Java MIDlets on S60 3rd Edition FP2 devices with a QWERTY or half-QWERTY keyboard (Nokia E55, E72, E75) behave abnormally when the user tries to input a number in a Java MIDlet's password TextField component with a long key press.

Article Metadata
Tested with
Devices(s): Nokia E55, E72, E75
Compatibility
Platform(s):
S60 3rd Edition FP2
Article
Created: User:Kbwiki (28 Dec 2009)
Last edited: hamishwillee (09 Aug 2013)

Description

A long key press in a password-type TextField component causes the following:

  • On the Nokia E55, the Java application closes.
  • On the Nokia E72, two characters appear(letter + number).
  • On the Nokia E75, when the QWERTY keyboard is used, causes similar behaviour as on the E72.

Steps to reproduce

The following code creates a TextField which doesn't work properly:

  protected void startApp() {
display = Display.getDisplay(this);
//Creates a form for TextField input
mainForm = new Form("String Item Demo");
//Following line creates a TextField which doesn't work correctly
password = new TextField("Password:", "", 10, TextField.PASSWORD);
mainForm.append(password);
display.setCurrent(mainForm);
}

Solution

No solution or workaround is currently available. The problem is expected to be fixed in future firmware releases.

This page was last modified on 9 August 2013, at 04:20.
38 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×