×
Namespaces

Variants
Actions
(Difference between revisions)

Enter key as an alternative to navigation select key

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot change of template (Template:KnowledgeBase) - now using Template:ArticleMetaData)
hamishwillee (Talk | contribs)
 
(4 intermediate revisions by one user not shown)
Line 1: Line 1:
 
[[Category:Symbian C++]]
 
[[Category:Symbian C++]]
[[Category:Technical Solution]]
+
 
[[Category:S60 3rd Edition]]
+
[[Category:S60 3rd Edition (initial release)]]
 
[[Category:S60 5th Edition]]
 
[[Category:S60 5th Edition]]
 
[[Category:UI]]
 
[[Category:UI]]
 
[[Category:Usability]]
 
[[Category:Usability]]
__NOTOC__
+
{{ArticleMetaData <!-- v1.2 -->
__NOEDITSECTION__
+
{{KBTS}}
+
{{ArticleMetaData
+
|id=TSS001207
+
|platform=S60 3rd Edition, S60 5th Edition
+
|devices=All (S60)
+
|category=Symbian C++
+
|subcategory=UI, Usability
+
|creationdate=December 11, 2008
+
|keywords=EKeyOk, EKeyEnter
+
 
+
 
|sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) -->
 
|sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) -->
 
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
|sdk=<!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Nokia Qt SDK 1.1]) -->
+
|devices= All (S60)
|devicecompatability=<!-- Compatible devices (e.g.: All* (must have GPS) ) -->
+
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Nokia Qt SDK 1.1]) -->
|signing=<!-- Empty or one of Self-Signed, DevCert, Manufacturer -->
+
|platform= S60 3rd Edition, S60 5th Edition
|capabilities=<!-- Capabilities required (e.g. Location, NetworkServices.) -->
+
|devicecompatability= <!-- Compatible devices (e.g.: All* (must have GPS) ) -->
|author=[[User:Technical writer 1]]
+
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 +
|signing= <!-- Empty or one of Self-Signed, DevCert, Manufacturer -->
 +
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 +
|keywords= EKeyOk, EKeyEnter
 +
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 +
|translated-by= <!-- [[User:XXXX]] -->
 +
|translated-from-title= <!-- Title only -->
 +
|translated-from-id= <!-- Id of translated revision -->
 +
|review-by= <!-- After re-review: [[User:username]] -->
 +
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20081211
 +
|author= [[User:Technical writer 1]]
 +
<!-- The following are not in current metadata -->
 +
|subcategory= UI, Usability
 +
|id= TSS001207
 
}}
 
}}
  
Line 32: Line 37:
 
==Detailed description==
 
==Detailed description==
  
In most situations, Avkon UI components react to both navigation select key (<tt>EKeyOk</tt>) and enter key (<tt>EKeyEnter</tt>) 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.
+
In most situations, Avkon UI components react to both navigation select key ({{Icode|EKeyOk}}) and enter key ({{Icode|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.
 
Custom UI controls used in 3rd party applications should have the same kind of functionality.
Line 38: Line 43:
 
==Solution==
 
==Solution==
  
Handle <tt>EKeyOk</tt> and <tt>EKeyEnter</tt> events in the same way whenever suitable (in <tt>OfferKeyEventL()</tt> function for classes derived from <tt>CCoeControl</tt>). Test the UI in the emulator and use the PC keyboard to control the application.
+
Handle {{Icode|EKeyOk}} and {{Icode|EKeyEnter}} events in the same way whenever suitable (in {{Icode|OfferKeyEventL()}} function for classes derived from {{Icode|CCoeControl}}). Test the UI in the emulator and use the PC keyboard to control the application.
 +
<!-- Translation --> [[zh-hans:作为输入键之一的导航选择键]]

Latest revision as of 07:40, 1 August 2012

Article Metadata
Tested with
Devices(s): All (S60)
Compatibility
Platform(s): S60 3rd Edition, S60 5th Edition
S60 5th Edition
S60 3rd Edition (initial release)
Article
Keywords: EKeyOk, EKeyEnter
Created: User:Technical writer 1 (11 Dec 2008)
Last edited: hamishwillee (01 Aug 2012)

[edit] Overview

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

[edit] 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.

[edit] 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.

This page was last modified on 1 August 2012, at 07:40.
118 page views in the last 30 days.
×