13 (71)
Copyright © Nokia Mobile Phones 2000. All rights reserved.
4. INTERACTION
The communicator UI is based on CBA, Menu and keyboard usage. Keep in mind that there is no generic pointing
device in the UI, so the controls should not be ’clickable.‘ The user should be able to use the device by keyboard and
the Menu without the CBA, if he or she so wishes.
Button
Functionality
Tab Changes the focus between windows
Tab -> focus to right
Shift+Tab -> focus to left
Enter Default command (Button1 underlined) in CBA or
Carriage Return (CR) in editors
Esc Application specific
Up/Down Arrows key Application specific
Right/Left Arrows key Application specific
Views
Tab Opens a control (e.g. choice list -> text list box)
Enter (when control not
opened, e.g. choice list)
Opens a control (e.g. choice list -> text list box)
Enter (when control opened,
e.g. text list box)
Optional default command = Button1 underlined (e.g.
OK in text list box)
Esc Cancels (clears a dialog box and any changes made)
Up/Down Arrows key Changes the focus from the one control to another
Right/Left Arrows key Focuses on the active control
Dialogs
Table 3: Recommendations for interaction.
4.1 Enter key
In editors, the Enter key inserts a new line. Elsewhere, Enter performs the action described by the underlined default
command (Button1).
4.2 Menu button
The Menu button activates and deactivates the Menu (see chapter 7).
4.3 Esc Key
The Esc key always allows the user to cancel the current action. This is important, because the Cancel command is
often unavailable in the CBA.
When in a dialog, the dialog and any changes made can be cleared using the Esc key.
4.4 Tab key
The Tab key should move the focus between the windows, but there should always be some other way of moving
between views, ideally using the Arrows key, e.g. the left and right keys may change the window.
If the Arrows key cannot be used for navigating between windows, a command should be available in the CBA.
To Next Page
Loading...
