Archived:Applications should not capture events from numeric keys (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}}.
RWindowGroup::CaptureKey() can be used for capturing key events when the application is not on the foreground. However, this should not be done for numeric key events, as it will cause problems with the idle view of the phone application.
Article Metadata
Compatibility
Platform(s): S60 3rd Edition (initial release), FP1
Platform Security
Signing Required: DevCert
Capabilities: SwEvent
Article
Created: User:Technical writer 1
(04 Jul 2007)
Last edited: hamishwillee
(15 Jun 2012)
Description
When an application tries to capture events from numeric keys [0..9,*,#] with RWindowGroup::CaptureKey(), the capture process will fail when the phone application (in idle view) is on the foreground. Furthermore, capturing events from these keys will prevent the phone application from handling them properly.
Note that SwEvent capability is required for RWindowGroup::CaptureKey().
Solution
No known solution. Applications should not try to capture events from keys 0..9, '*' or '#'.
(no comments yet)