Sun Microsystems Computer Accessories manual Secondary Button Assignments

Page 50

command.keys.BACK = SOFT1 command.keys.EXIT = SOFT1 command.keys.CANCEL = SOFT1 command.keys.STOP = SOFT1 command.keys.OK = SOFT2 command.keys.SCREEN = SOFT2 command.keys.ITEM = SOFT2 command.keys.HELP = SOFT2

In cases of conflict in the mapping of actual commands to keys, commands are mapped first by command type and then by priority.

Secondary Button Assignments

Secondary buttons may be defined for a command type. If a command is unable to be assigned to the preferred button for its type because another command with higher precedence (due to either its type or its priority) has taken the button, the command can be assigned to an alternative button.

This is done by specifying more than one button name in the property definition where the names are separated by spaces:

command.keys.<type> = <button_name> <button_name> .. <button_name>

Example

The first definition below assigns commands of type BACK to the END key and alternatively to the SOFT1 key. The second definition assigns commands of type OK to the SEND key and alternatively to the SOFT2 key.

command.keys.BACK = END SOFT1 command.keys.OK = SEND SOFT2

Restricting the List of Command Types for a Soft Button

Only certain command types might be allowed for a specific soft button, which means that other command types will not be assigned to that soft button in any case, even if that soft button is left unassigned.

You restrict command types to a button by specifying a list of one or more command types in the property definition:

command.exclusive.<button_name> = <type> <type> ... <type>

Example

The following definition allows only the command types BACK, EXIT, CANCEL, and STOP to be mapped to the SOFT1 key.

command.exclusive.SOFT1 = BACK EXIT CANCEL STOP

36 Wireless Toolkit Basic Customization Guide • December 2003

Image 50
Contents Basic Customization Guide Please Contents Examining Device Property Files Default Emulator Device Property Files Vi Wireless Toolkit Basic Customization Guide December Figures Viii Wireless Toolkit Basic Customization Guide December Tables Wireless Toolkit Basic Customization Guide December Who Should Use This Book How This Book Is OrganizedUsing Operating System Commands Related Documentation Typographic ConventionsShell Prompts Accessing Sun Documentation Online Sun Welcomes Your CommentsCustomizing the Wireless Toolkit How to Customize the Wireless ToolkitDevice Property Files and the Default Emulator Customization StepsCustomizing the Wireless Toolkit Wireless Toolkit Basic Customization Guide December Creating Device Property Files Make a Copy of an Existing Main Device Property FileObtain and Enter Image Files Obtain and Enter the Screen Properties Screen LocationTotal Screen Size Display AreaDisplay Area in Full Screen Mode Specifying Screen PropertiesObtain and Enter the Button Properties By measuring the image file, obtain the button propertiesHeight Width Obtain and Enter Soft Button Label Areas Soft button label display is defined by a line of the form Obtain and Enter Icon Properties Defining the Icon Location and StatesEnter the following measured values for the icons properties Screen Background RGB Color Enter Color PropertiesRun the Emulator for the New Device Examining Device Property Files Device Property Files Fonts Used by the Midp APIs Main Device Property FileFonts Bitmap Fonts Default FontSystem Fonts Ascii character Distance to character Font Underlining Device ImageImage with Buttons Highlighted and Backlight On Image without Buttons PressedImage with Buttons Pressed ScalingScreen Properties Screen Location Display Area Display Area in Full Screen ModeTotal Screen Size Screen Pixel Ratio Screen Background ColorScreen Buffering Screen Border ColorTouch Screen Defining a Device Button Device ButtonsKeyboard Handler Button.LEFT = 13, 197, 20 Assigning a PC Keyboard Key to a Button Assigning a Game Action to a Button Specifying the Characters Generated by a Button PressAssigning Abstract Commands to Buttons Abstract Command Types in Order of PrecedenceEmulating Abstract Command Button Assignments Precedence of Assigning Commands to a Button Secondary Button Assignments Abstract Command Menu Displayed Icons Defining the Icon Location and StatesSoft Button Label Display Soft Button Labels on the Emulated Device DisplayColor Sound AlertsDevice Software Capabilities Alert Type ValuesLocales Character EncodingsEnableAlphaChannel false Transparent ImagesWireless Toolkit Basic Customization Guide December Default Emulator Device Property Files Property FilesDefaultGrayPhone.properties Appendix a Default Emulator Device Property Files Wireless Toolkit Basic Customization Guide December Appendix a Default Emulator Device Property Files Wireless Toolkit Basic Customization Guide December # alert.alerttype.sound soundfile Wireless Toolkit Basic Customization Guide December Device Image Files Icon Image FilesIcon Image Files Support for ByteCode Obfuscators Adding a ByteCode ObfuscatorExample Appendix B Support for ByteCode Obfuscators Wireless Toolkit Basic Customization Guide December P E N D I X C Wireless Toolkit Basic Customization Guide December Index Keyboard.handler property Device property files, 1 WMA messages, customizing Wireless Toolkit Basic Customization Guide December