Enter key as an alternative to navigation select key

Comments

There is a small typo in the TSS001207 text. This typo may cause troubles, if someone does a copy & paste from the text (as I did).

eikon.hrh defines the symbol as EKeyOK. Note the capital letter K!

If the application source file contains the symbol as EKeyOk, it won't be accepted by the compiler. The case is significant!

Cheers,

Jyrki

Log in or Join to leave comments.

Article Metadata

---

Tested with

Devices(s): All (S60)

---

Compatibility

Platform(s): S60 3rd Edition, S60 5th Edition

---

Article

Keywords: EKeyOk, EKeyEnter

Created: User:Technical writer 1 (11 Dec 2008)

Last edited: hamishwillee (01 Aug 2012)

Overview

UI components that handle keyboard events should consider handling enter key events as an alternative to events from the navigation select key.

Detailed description

In most situations, Avkon UI components react to both navigation select key (EKeyOk) and enter key (EKeyEnter) events in the same way. This makes it possible to have consistent UI controls, whether the application is running on a device with conventional ITU-T keys or a device with a full QWERTY keyboard, or controlled via an external (bluetooth) keyboard.

Custom UI controls used in 3rd party applications should have the same kind of functionality.

Solution

Handle EKeyOk and EKeyEnter events in the same way whenever suitable (in OfferKeyEventL() function for classes derived from CCoeControl). Test the UI in the emulator and use the PC keyboard to control the application.