Archived:CustomItem extension using setClip() paints over Form components in Series 40 (Known Issue)
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}}.
The article is believed to be still valid for the original topic scope.
The article is believed to be still valid for the original topic scope.
Article Metadata
Tested with
Devices(s): All devices prior to Series 40 6th Edition
Compatibility
Platform(s): Series 40 platform editions prior to Series 40 6th Edition
Article
Created: User:Technical writer 1
(25 Aug 2008)
Last edited: lpvalente
(23 Apr 2012)
Contents |
Overview
The extension of the clipping area paints CustomItem over MIDP 2.0 and MIDP 2.1 high-level API items on Form in Series 40.
Description
When the clipping area of the y coordinate is extended (for example, y=80), the CustomItem object is painted over MIDP 2.0 and MIDP 2.1 high-level API items on Form.
How to reproduce
For example, implement a MIDlet using two TextField items and one CustomItem item. Include them on the Form in the following top-down order: TextField, CustomItem, TextField.
To test this issue, paint the CustomItem and set the clipping area using the following code snippet:
Solution
This issue has been fixed starting from Series 40 5th Edition Feature Pack 1.

