Академический Документы
Профессиональный Документы
Культура Документы
User Guide
AppLauncher
Users Guide
Rev.1
Nov 2015
ii
Copyright
The product described in this document may include copyrighted computer programs. Laws in the
United States and other countries preserve for certain exclusive rights for copyrighted computer
programs. Accordingly, any copyrighted computer programs contained in the product described in
this document may not be copied or reproduced in any manner without the express written
permission.
2015 Symbol Technologies LLC All Rights Reserved
No part of this document may be reproduced, transmitted, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without the prior
written permission.
Furthermore, the use of our products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications, except for
the normal non-exclusive, royalty-free license to use that arises by operation of law in the sale of a
product.
Trademarks
Zebra and the Zebra head graphic are registered trademarks of ZIH Corp. The Symbol logo is a
registered trademark of Symbol Technologies LLC, a Zebra Technologies company.
Table of Contents
Table of Contents
About This Guide
Introduction.................................................................................................................... v
Chapter Descriptions ..................................................................................................... v
Notational Conventions.................................................................................................. vi
Chapter 1: AppLauncher Introduction
Introduction ................................................................................................................... 1-1
Installation ..................................................................................................................... 1-1
Automated Deployment on Mobile Device .............................................................. 1-2
Manual Deployment on Mobile Device ................................................................... 1-2
Installing on Windows CE Devices ................................................................... 1-2
Installing on Window Mobile Devices ................................................................ 1-2
Un-installation ............................................................................................................... 1-3
For Windows CE Devices ................................................................................. 1-3
For Windows Mobile Devices ............................................................................ 1-3
Chapter 2: AppLauncher Screen
Introduction ................................................................................................................... 2-1
AppLauncher Screens .................................................................................................. 2-2
Default Screen ........................................................................................................ 2-2
Bitmap Area ...................................................................................................... 2-3
Menu Area ........................................................................................................ 2-4
Chapter 3: AppLauncher Registry Structure
Introduction ................................................................................................................... 3-1
Multiple Profile Mode .............................................................................................. 3-1
Profile ................................................................................................................ 3-1
Legacy Mode .......................................................................................................... 3-2
iv
Introduction
This guide provides information on the AppLauncher application, how to configure the AppLauncher via the registry
entries and also how to operate the application.
NOTE Screens and windows pictured in this guide are samples and can differ from actual screens.
Chapter Descriptions
Topics covered in this guide are as follows:
Appendix C, Special Notes provides additional information needed for configuring AppLauncher.
vi
Notational Conventions
The following conventions are used in this document:
bullets () indicate:
Action items
Lists of alternatives
Lists of required steps that are not necessarily sequential
Sequential lists (e.g., those that describe step-by-step procedures) appear as numbered lists.
NOTE This symbol indicates something of special interest or importance to the reader. Failure to read the note
will not result in physical harm to the reader, equipment or data.
CAUTION This symbol indicates that if this information is ignored, the possibility of data or material damage may
occur.
WARNING!
This symbol indicates that if this information is ignored the possibility that serious personal
injury may occur.
Installation
Download the installation of AppLauncher from the Symbol support website at http://support.symbol.com.
Install the downloaded package onto the host PC. Follow the installation wizard instructions.
NOTE The new installation package installs sample setting which contains one profile setting and with default
profile. However, it does not update the mobile device registry to set any value for registry value
"ActiveProfile".
Establish an ActiveSync connection between the mobile device and the host PC.
2.
On the host PC, go to Start - Program Files - AppLauncher - Install AppLauncher to mobile device to
initiate automatic installation process.
3.
Follow the installation instructions to successfully install the AppLauncher application to the mobile device.
The automatic deployment process checks the operating system of the mobile device and installs the necessary
files to the mobile device according to the system of mobile device.
NOTE If AppLauncher is already installed in the mobile device, a confirmation dialog will be displayed before
proceeding with the re-installation. Any existing configurations in registry or in .reg files in the \Application folder
will not be affected by the re-installation.
Establish an ActiveSync connection between the mobile device and the host PC.
2.
3.
4.
Establish an ActiveSync connection between the mobile device and the host PC.
2.
3.
4.
NOTE AppLauncher installation installs the application to persist the AppLauncher settings after a cold boot.
User can customize these settings by editing the .reg file located in the \Application folder.
Un-installation
If a cold/clean boot has not been performed on the mobile device, the following steps can be carried out on the
mobile device to uninstall AppLauncher
1.
2.
3.
If a cold/clean boot has been performed, AppLauncher will not appear in the Remove Programs list ; In this case
un-installation needs to be done manually. To manually uninstall AppLauncher perform the following steps on the
mobile device.
1.
2.
3.
2.
2.
Delete the AppLauncher shortcut file from the \Windows\Start Menu\Programs folder
NOTE
The AppLauncher screens differ according to the operating system of the mobile device.
AppLauncher Screens
The configurable settings that define the look and feel and the functionality of the AppLauncher screens are stored
in the AppLauncher registry.
To launch AppLauncher in the mobile device go to Start - AppLauncher.
Default Screen
The default screen (See Figure 2-1 on page 2-2) is displayed when AppLauncher is run for the first time on the
mobile device. This screen has the default settings associated with it and could be navigated using the scroll
buttons or the touch screen. The configurable settings for the default screen are stored in the registry location:
[HKEY_CURRENT_USER\Software\Symbol\Launcher\Default\Settings].
Bitmap Area
Menu Area
About Button
Exit Button
Figure2-1
Use the scroll buttons on the mobile device keyboard or the touch-sensitive screen to navigate through the menu
items. Use the Enter button to launch/access the selected menu item in non-touch-sensitive mobile devices.
By making a few modifications to the AppLauncher registry file, it is possible to display an additional icon and/or
quick launch key for each menu item (See Figure 2-2 on page 2-3).
Icons
Figure2-2
The quick launch keys are used for launching applications by pressing the corresponding key on the mobile device
keyboard.
The icons give more clarity to the menu items, enabling the user to clearly identify applications and program
groups. The default application icon is displayed alongside the description while a program group displays a folder
icon.
If an application does not have a default icon, AppLauncher displays the default icon for Windows applications
alongside the description.
The AppLauncher screen consists of two main components which are;
Bitmap area
Menu area
Bitmap Area
The default screen interface consists of a product specific bitmap on the top of the screen (bitmap area). By
manipulating registry, it is possible to change the look and feel of the screen.
The bitmap can be different for each screen and can be configured through BitmapFilePath registry entry.
The height of the bitmap area is set by the BitmapHeight registry entry.
(See Ranges and Limits on page A-5 for more information.)
NOTE The bitmap is not displayed if no bitmap is specified or if the bitmap file is missing or if BitmapHeight
registry setting is set to 0.
Menu Area
Below the bitmap area is the scrollable list of menu items (menu area).
The menu items can be accessed via the touch screen or using the scroll buttons or by pressing the corresponding
value on the numeric keyboard.
NOTE When there are not enough menu items to fill the menu area, the menu background color is displayed at
the bottom of the menu area.
Program icons for executable programs and a folder icon for items that have a Call registry setting (i.e. that
display sub-menus).
2.
A single digit prefix indicating the numeric key that can be pressed to launch the item. If the existing Number
registry entry is 0 then the numeric prefixes are not displayed.
3.
The description of the menu item is set in the Description registry entry.
4.
Figure2-3
Profile
A profile controls the menu that AppLauncher displays. At the top level, each profile comprises of the following two
main entries.
Settings -
Programs this contains the items which are displayed in the AppLauncher menu. The menu items can be
either executables or sub-menus
Executables
Define name, description and command line parameters.
Sub Menu
Define description and sub menu parameters. Sub menus must be defined within their own profile.
It is not possible to call a sub menu from a different profile.
Legacy Mode
When set, legacy mode provides backward compatibility with previous versions of AppLauncher thereby allowing
existing AppLauncher configurations to be used without modification.
Default Profile
Figure3-1
Screenshot of [HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\]
Profiles allow storing different configurations of AppLauncher in a single device. Each profile has a unique name
and configuration and can access submenus under that profile only. Accessing other profiles is restricted.
Active profile
The active profile is the profile which loads when AppLauncher is invoked. A profile name can be passed as a
command line parameter to AppLauncher.exe to load that profile. Alternatively, using a remote registry editor, enter
the name of a profile to ActiveProfile in the [HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher] registry.
If a profile is not specified, AppLauncher looks for registry key
[HKEY_CURRENT_USER\Software\Symbol\Launcher] to load that configuration. If
[HKEY_CURRENT_USER\Software\Symbol\Launcher] is not available, then the default profile stored in
[HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\Profiles\DefaultProf] registry is loaded to
AppLauncher screen.
Default Profile
The default profile is the profile which loads if there is no profile specified as the active profile. Default profile
settings are found in registry path
[HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\Profiles\DefaultProf].
Command Line - If a profile name is passed on the command line and a matching profile is found in the
registry, then the menu associated with that profile is loaded. If the defined profile is not found, AppLauncher
displays an error and exits. This method gets the highest priority.
2.
Active Profile - If no profile is passed on the command line and an active profile is set in the registry, the menu
described by the active profile registry key is displayed. If the defined profile is not found, AppLauncher
displays an error and exit.
3.
Legacy Launcher - If no profile is passed on the command line and an active profile is not set, AppLauncher
displays the menus as described by the legacy Launcher registry key.
4.
Default Profile - If no profile is passed on the command line, an active profile is not set, and the legacy
Launcher key is not set, then AppLauncher displays menus as described by the default profile key.
When there is no defined profile, and the legacy Launcher key is not set, and the default profile key is not set,
AppLauncher displays an error and exits.
NOTE A Profile is loaded when AppLauncher is launching. To change the profile exit and restart AppLauncher.
Default Key
Programs key for holding key
information of applications
and program groups.
Program information must be
entered in ProgN sub menu.
Configuration settings
for menu.
Figure3-2
Screenshot of [HKEY_CURRENT_USER\Software\Symbol\Launcher]
Default Settings
The Default key is required by AppLauncher to run and contains two registry settings that are essential for the
application.
The Default registry key is located at
[HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\Profiles\<Profile_Name>\Default]
Programs - Contains registry keys of programs/sub menus which are in the main interface.
Settings - Contains configuration information of default screens.
NOTE The Default registry keys should be placed directly under the Launcher key for the AppLauncher to run.
The Default key holds registry entries that configure the main screen of AppLauncher. It has the special registry
entry Exit for the purpose of terminating AppLauncher. The registry settings for sub menus do not contain the Exit
key. Instead, the sub menus hold the special registry entry Return to exit from the current screen and return to the
previous screen.
Programs
The Programs key contains the registry settings of the menu items displayed by AppLauncher.
NOTE The registry key holding program information should be named as Programs as it is required by
AppLauncher to run properly.
The entries for the main screen menu items are found in
[HKEY_CURRENT_USER\Software\Symbol\Launcher\Default\Programs]. Each menu item is depicted using a
ProgN key where ProgN could either be a key for an application or a Program Group (sub menu).
Definitions of the registry keys entered in ProgN are given in Table 3-1.
Table3-1
Key
Type
Description
Name
String
Command
String
Description
String
Call
String
HotKey
DWORD
HotKeyModifier
DWORD
ProgN denotes a menu item in AppLauncher. The menu item can be an application or a program group. If ProgN
Key is for calling an executable then Name, Description and Command value should be available under the ProgN
Key. If ProgN Key is for a Program Group then Call and Description should be available under the ProgN keys.
NOTE Menu item keys should be named in ProgN format (i.e. Prog1, Prog2, Prog3, etc.) as this is required for
AppLauncher to run smoothly.
Settings
The Settings key contains User Interface (UI) configuration information for the AppLauncher screens.
The registry settings for the Default key contain the special key "Exit" which is used to terminate the AppLauncher
application on the mobile device. The keys for program groups have the special key "Return" to exit from the sub
menu and return to the previous screen.
AppLauncher uses the values set for the default settings to configure the screen display of both the main screen
and the sub menu screens. However, the settings defined within a sub menu can override the default settings. For
example the sub menu can display a different image in the bitmap area or have background color only for that
screen. This allows the user to have multiple screen configurations for the AppLauncher screens.
NOTE If the user defined configuration settings contain out of range values, AppLauncher displays an error
message and runs with default settings.
See Appendix A-3, Screen Configuration Settings for information of the settings.
Program Groups
The applications that are not set in the default main screen of AppLauncher are listed in the Program Group. Icons
are displayed on the default screen to provide access to these program groups. Access a particular program group
by clicking on the representing icon.
Use program groups to store a group of applications such as sample applications, utilities, etc.
Program groups are placed at the same level in the registry as Default key, i.e. directly under the Launcher key.
They have a similar registry structure to the Default key. The only difference between the Default registry key and
the registry key of a program group is that it has a special key titled 'Return'. The Return key allows users to return
to the originating screen once they enter the program group.
Adding a Program
Follow the steps given below to add a new program to the AppLauncher.
1.
Locate the registry key holding the key information of the programs residing on the mobile device.
HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\Profiles\<Profile_Name>\Default\Programs\
2.
In the registry, make a new key entry and enter the program information. Make sure the new key is in the same
registry hierarchy as the other program keys.
3.
4.
Enter the registry information (i.e. Name, Command, Description, Call, HotKey, etc.) into the new program key.
See Programs on page 3-6 and Program Key Settings on page A-2 for more information.
Description value under ProgN key has a length limitation of 260 characters and if one exceeds that amount a
warning message is raised saying that the allowed limit has being exceeded or valid value for description was
not found.
5.
To provide access to a Program Group, set the exact name of the program group in the Call key. Also enter
the description text string in the Description key.
NOTE ProgN key can be configured to invoke an application or a sub folder. However if by mistake if the ProgN
key contains literals for both Call and Name registry values then AppLauncher gives higher priority to
Name registry value ignoring the Call Registry value.
Adding a SubMenu
Programs can be categorized into different groups such as Test Applications or Demo Applications. AppLauncher
can then display a menu item to access these program groups in the default screen.
See Program Groups on page 3-7 for more information.
Follow the steps given below to add a new sub menu to the AppLauncher screen.
1.
2.
Create and name the new registry entry for the sub menu.
Example - Test Apps
Make sure that the sub menu key is at the same registry level as the other sub menus and the Default key.
3.
Within the newly created sub menu registry key store the key information for any programs that are stored
within the sub menu (Refer Adding a Program on page 4-2).
4.
Create a key for storing sub menu screen settings. Make sure to name this folder as Settings.
5.
Store the Call and Description key information to access sub menu within the Default key.
NOTE Make sure to set the Return key to return to the originating screen. See Settings on page 3-7 for more
information.
First create Prog1 key within the Default registry key to set up the sub menu for TestApps.
[HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\Profiles\<Profile_Name>\Default\Programs\Prog1
]
Within the Prog1 key enter the key settings to navigate to the TestApps sub menu screen from the
AppLauncher main screen, i.e. enter the name of the sub menu, in this case TestApps into the Call key.
Also, enter the text string Test Applications into the Description key.
Table4-1
Key
Description
Value
Call
Description
TestApps
Test Applications
The menu item for accessing the TestApps sub menu is now created and is displayed on the AppLauncher
main screen.
2.
Create a new key titled TestApps within the Launcher key. Make sure that the TestApps key is on the same
level of the Default key.
Within the newly created TestApps key, create a key Programs for storing the key information of Test
Applications.
[HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\Profiles\<Profile_Name>\TestApps\Programs]
Also, create the Settings key for storing the UI key information for the Test Apps sub menu.
[HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\Profiles\<Profile_Name>\TestApps\Settings]
3.
Create Prog1 key to enter the registry information for the SelfTest program.
Table4-2
Key
Description
Name
Command
Description
Value
\Application\SelfTest.exe
SelfTest
Table4-2
Key
Description
Value
Call
HotKey
HotKeyModifier
4.
After entering the above given information, it is necessary to enter the key information for the UI of the
TestApps sub menu.
Table4-3
Name
About
Description
Value
BitmapFilePath
BitmapHeight
CommandWidth
DescriptionWidth
DetailColumns
Headings
MenuAreaBackgroundColor
MenuItemBackgroundColor
16777215
MenuItemFont
Arial
MenuItemFontSize
70
Auto-compute
Table4-3
Name
Description
Value
MenuItemHeight
50
MenuItemIconWidth
50
MenuItemTextColor
Menu Bars
Mode
NameWidth
Number
QuitAfterLaunch
Return
14658924
SelectedMenuItemTextColor
16777215
SeparatorColor
12745728
Table4-3
Name
Description
TitleBar
TitleBarContext
UseProgramIcons
Value
AppLauncher screen is displayed in the full display area of the mobile device.
This is the default screen setting.
Set the value of FullScreen key to 1 to enable full screen mode.
Partial Screen Mode - AppLauncher screen is partially displayed in the mobile device.
Set the value of FullScreen key to 0 to enable this mode.
Figure4-1
Defines the location of the AppLauncher screen in relation to the display area
of the mobile device. The ForceScreen registry settings are stored in this key.
The functionality of the ForceScreen registry settings is to display the AppLauncher
screen at the defined X and Y coordinates.
NOTE If ForceScreen coordinates are zero or if the coordinates are not within the allowed range, AppLauncher
screen would be displayed in the default FullScreen mode.
Details
In Detail mode, only three columns are supported. This is because having more columns does not provide
additional benefit to the functionality or usage of AppLauncher.
Report
List
Small Icons
Large Icons
Menu Bars (Default mode)
BitmapFilePath
BitmapHeight
Setting Bitmap File Path
Set the full file path and name of the bitmap image to
HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher\Profiles\User1\Default\Settings\BitmapFilePath
registry key.
Example - \Application\app_launch.bmp
To change the image being displayed, replace the image file with a preferred image file. Also, make sure to define
the correct path of the image file within the mobile device.
Change the value of this setting to alter the bitmap area height. Make sure that the defined value is within the
allowed range for this setting. Also ensure that the height of the image used in the bitmap area is the same value of
the set value to correctly display the image.
The bitmap display may change according to the height and width of the bitmap (See Bitmap Display States).
Therefore, use a bitmap with the same pixel height as BitmapHeight value and width of the mobile device screen to
correctly display the image in the bitmap area.
Table4-4
Height oftheBitmap
Width oftheBitmap
Same
SeparatorColor -
MenuItemFont -
MenuItemFontSize -
MenuItemHeight -
MenuItemIconWidth -
MenuItemBackgroundColor MenuItemTextColor -
SelectedMenuItemTextColor UseProgramIcons -
Number -
Key
ExitOnESC
Type
dword
Description
Provides a keyboard shortcut (ESC
key)to exit AppLauncher from the
main menu screen.
Default
0
The valid value for the registry entry is {1, 2, and 0}. Other values are considered as invalid and will cause
an error message to be displayed and the default value to be used. If the registry entry does not exist or
the value is empty then the default value will be assumed.
[HKEY_CURRENT_USER\Software\SymbolLLC\AppLauncher]
Table4-6
Key
BackOnZero
Type
dword
Description
Sets the keyboard shortcut to the 0
key rather than the last sequential
number in the menu list.
Default
0
Key
Type
Description
Default
FullScreen
dword
ForceScreenLeft
dword
ForceScreenTop
dword
ForceScreenRight
dword
ForceScreenBottom dword
Name
Type
Description
Name
string
Specifies the file name of the program item. This can be the
name of an executable program file or the name of any file with
a registered associated to an application that allows it to be
launched.
See Note below
Description
String
Command
string
HotKey
Dword
HotKeyModifier
dword
Call
string
NOTE Any single program item must have only one of the following values "Name" or "Call".
TableA-3
Name
About
Type
Description
Default
string
Specifies that an about option is to be added to the button matrix or list view and specifies the
text to be used for the about option.
string
dword
Dword
DescriptionWidth
dword
DetailColumns
dword
Exit
string
Headings
dword
BitmapFilePath
BitmapHeight
CommandWidth
\Windows\app_launch.bmp
70
Auto-compute
Auto-compute
Exit
MenuAreaBackground dword
Color
16777215
(R-255, G-255, B-255)
MenuItemBackground
Color
dword
16777215
(R-255, G-255, B-255)
MenuItemFont
string
Arial
MenuItemFontSize
dword
12
MenuItemHeight
dword
50
MenuItemIconWidth
dword
50
TableA-3
Name
MenuItemTextColor
Mode
NameWidth
Number
QuitAfterLaunch
Return
Type
Description
Default
dword
0
(R-0, G-0, B-0)
string
Menu Bars
dword
Auto-compute
dword
dword
string
SelectedMenuItemBac dword
kgroundColor
14658924
(R-0, G-173, B-223)
SelectedMenuItemTex dword
tColor
16777215
(R-255, G-255, B-255)
12745728
(R-0, G-124, B-194)
SeparatorColor
dword
TableA-3
Name
Type
Description
Default
TitleBar
string
TitleBarContext
Dword
UseProgramIcons
dword
TableA-4
Setting
Upper Limit
Lower Limit
BitmapHeight
100
CommandWidth
100
DescriptionWidth
100
DetailColumns
Difference between
ForceScreenRight and
ForceScreenLeft
150**
Difference between
ForceScreenBottom and
ForceScreenTop
(2 x MenuItemHeight) +
BitmapHeight
(This value is invalid if all
ForceScreen settings are
set to 0)
Headings
MenuItemFontSize
20
Default
TableA-4
Setting
Upper Limit
Lower Limit
Default
MenuItemHeight
120
Mode
NameWidth
100
Number
QuitAfterLaunch
TitleBarContext
UseProgramIcons
Menu Bars
Error Messages
Message
Description
BitmapHeight registry key contains a value greater than 100 or less than 0.
DescriptionWidth registry key contains a value greater than 100 or less than
0.
MenuItemHeight must be between MenuItemHeight registry key contains a value greater that 120 or less than
10/33 and 120
33 if UseProgramIcons set as 1, or less than 10 if UseProgramIcons set as 0.
MenuItemIconWidth must be
between 30 and 100
CommandWidth must be between CommandWidth registry key contains a value greater than 100 or less than 0.
0 and 100
Non-Symbol device
TableB-1
Error Messages
Message
Description
Number must be 1 or 0
TitleBarContext must be 1 or 0
QuitAfterLaunch must be 1 or 0
UseProgramIcons must be 1 or 0
ExitOnESC must be 1, 2 or 0
Warning Messages
TableB-2
Warning Messages
Message
Description
Hotkey registration is
Same key pair is assigned to registry values Hotkey and HotkeyModifier, for
unsuccessful. You may have used more than one program.
same key pair for more than one
program
Program Key <N> - Either
Description key is empty or
exceeds limit
TableB-2
Warning Messages
Message
Description
Program Key <N> - No Description In registry key Prog<N> key, registry value Description is missing and neither
and Name or Call found
registry values Name or Call exist.
Program Key <N> - No Name or
Call found
In registry key Prog<N> key, neither registry values Name nor Call exist.
Sequence is missing in Prog keys Number sequence is beak in middle of Prog<N> keys.
in Registry
Set the appropriate values for Blue, Green and Red channels.
Example B-99/G-66/R-FF
2.
3.
Invoke the Calculator utility which comes with Windows on the PC. Select View - Scientific from the menu.
4.
Make sure mode is selected as Hex in the radio button and then copy and paste the concatenated value to
the calculator edit box.
5.
Select the "Dec" radio button to convert the hex value to decimal.
Zebra and the Zebra head graphic are registered trademarks of ZIH Corp. The Symbol logo is a registered trademark of
Symbol Technologies LLC, a Zebra Technologies company.
2015 Symbol Technologies LLC
Revision1-Nov 2015