Archived:TimerTask operation changes TextField focus (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: 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}}.

Article Metadata

---

Tested with

Devices(s): Tested on Nokia 6233 (Series 40), Nokia N70, Nokia N73, Nokia N93 (S60)

---

Compatibility

Platform(s): Series 40 and
S60 2nd Edition FP3
S60 3rd Edition, S60 3rd Edition, FP1

---

Article

Created: User:Technical writer 1 (13 Jun 2007)

Last edited: hamishwillee (28 Jun 2012)

Overview

TextField focus is changed and wrong TextField calculation is performed after each TimerTask operation.
After each TimerTask operation, focus always switches from the chosen TextField to the first TextField on the Form. This means that the content of the wrong TextField is calculated.

Description

Use case: An application consists of a Form with three TextFields, of which the first and the third can be modified with input by the user. The second TextField includes a calculation of input content from the third TextField.

Description: Two problems occur every time when the included TimerTask operation reaches the end and the total result of the second TextField on the Form is updated:

1. The application switches focus to the first, topmost TextField (notable with Nokia N70 where the first TextField becomes always visibly active), and as result,
2. The input of the first TextField is calculated instead of the intended third TextField (all phones).

The desired operation (that is, the third TextField is calculated and focus remains unchanged) can be reproduced with Sun's WTKs 2.2 and 2.5.