7 - 22 CA50/UCA Client & Server Developer & User Guide
Menu States
Defines the menus applicable for different menu states. For each state of the device (AppCallActive, indicates that
the device is in a call is active and an application is open in the browser state) menu states define what is shown as
the menu for the left soft key and the right soft key.
Following is a sample code snippet for the menu state AppCAllActive:
<MenuStates>
<State ID="4" Name="AppCallActive" LSKey="Options:M:L:AppCallActive"
RSKey="End:S:L:PhoneHangUp" LPHKey="" RPHKey="" FPTTKey="default" SPTTKey="default" />
</MenuStates>
The format for representing a menu for LSKey and RSKey use is: [title to display]:M:L:[menu name]
In this example, the LSKey refers to the menu titled Options and the menu name is AppCallActive.
State = "AppCallActive"
Left Soft key (LSKey) displays options as a menu and the actual menu referenced is AppCallActive.
Right Soft key (RSKey) displays end as a command and the actual command referenced is PhoneHangUp.
The name attribute identifies the client state as follows:
•
DesktopNoCall
- The user is at the desktop and not on a phone call.
•
AppNoCall
- The user is running a Web application and is not on a phone call.
•
DesktopCallActive - The user is at the desktop and is on a phone call.
•
AppCallActive
- The user is running a Web application and is on a phone call.
•
DesktopQuietMode- The user has entered quiet mode from the desktop.
•
AppQuietMode
- The user has entered quiet mode while running a Web application.
•
DesktopCallOnHold-The user is on a call at the desktop and is on hold.
•
AppCallOnHold
- The user is on a call on hold while running a Web application.
Menus and actions can be assigned to keys for each of the client states. These menus are accessible to the user
through the keys while the device is in that client state. Key and menu assignments must be thought through a bit.
For example, for the "AppCallActive" client state is recommended to assign a menu to a key that presents a "Hang
up" menu option.
As mentioned earlier, keys defined by the Web application take precedence over keys defined in the
<MenuStates> area of the profile. The CA50 is a dual purpose device (communication and Web browser). The
UCA Web developer must consider the <MenuStates> key assignments when designing a Web application for the
CA50.
NOTE
Examples of base profiles are found in the following directory in the default UCA server software
installation: \Program Files\Motorola\UCA Server\Profiles.
Summary of Contents for CA50
Page 1: ...CA50 UCA Client Server Developer User Guide ...
Page 2: ......
Page 3: ...CA50 UCA Client Server Developer User Guide 72E 93914 02 Revision A November 2009 ...
Page 18: ...xvi CA50 UCA Client Server Developer User Guide ...
Page 24: ...xxii CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 30: ...1 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 34: ...2 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 48: ...3 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 106: ...4 58 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 109: ...UCA Client Application on the CA50 5 3 Page intentionally blank ...
Page 110: ...5 4 CA50 UCA Client Server Developer User Guide ...
Page 135: ...UCA Server 6 25 Figure 6 30 Installing Prerequisites Figure 6 31 SQL Server Setup ...
Page 200: ...7 32 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 284: ...9 56 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 302: ...10 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 350: ...11 48 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 358: ...12 8 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 418: ...A 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 436: ...B 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 478: ...E 12 CA50 UCA Client Server Developer User Guide 6 7 8 9 10 11 ...
Page 488: ...F 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 492: ...G 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 510: ...I 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 538: ...Index 12 CA50 UCA Client Server Developer User Guide ...
Page 540: ......
Page 541: ......