Sun Microsystems Computer Accessories - page 44

30 Wireless Toolkit Basic Customization Guide • December 2003

■x: The x-coordinate of the left edge of the button image, in pixels relative to the

left edge of the device image

■y: The y-coordinate of the top edge of the button image, in pixels relative to the

top edge of the device image

■width: The width of the button image, in pixels

■height: The height of the button image, in pixels.

For example,

button.LEFT = 13, 197, 20, 20

For the second form (polygonal), the definitions for button_name, x, and yare the

sameas for the rectangular form. The polygonal form can consist of multiple points

definedby x and y coordinates. A minimum of three sets of x and y coordinates are

required to use this form.

For example, if the LEFT button were polygonal, it could have the following

values:

button.LEFT = 166, 420, 143, 432, 143, 406

The button location and dimensions are used for two purposes:

■Todefine the active region in which a mouse click is interpreted as a button

press.

■Todefine the region of the device image that is used to show graphic effects on

device buttons.

The region for each button should be defined to be large enough to cover the

button's area on all three device images. However,be careful not to allow the

buttons' regions to overlap each other.

The button coordinates are shown in FIGURE6.

Contents

Main Please Contents Page Page Page Figures Page Page Page Preface Who Should Use This Book How This Book Is Organized Using Operating System Commands Typographic Conventions Shell Prompts Related Documentation AaBbCc123 Accessing Sun Documentation Online Sun Welcomes Your Comments Customizing the Wireless Toolkit How to Customize the Wireless Toolkit Customization Steps Note Device Property Files and the Default Emulator Page Page Creating Device Property Files Make a Copy of an Existing Main Device Property File Note Obtain and Enter Image Files Obtain and Enter the Screen Properties Note Screen Location Total Screen Size Display Area Display Area in Full Screen Mode (screenPaintableRegion.x,screenPaintableRegion.y). Obtain and Enter the Button Properties 2. Enter the following measured values for the button properties in NewPhone.properties: Obtain and Enter Soft Button Label Areas Note Page Obtain and Enter Icon Properties Note Defining the Icon Location and States Page Enter Color Properties Screen Background RGB Color Run the Emulator for the New Device Examining Device Property Files Note Device Property Files Main Device Property File Fonts Fonts Used by the MIDP APIs Default Font System Fonts Bitmap Fonts Page Note Font Underlining The Device Image Image without Buttons Pressed Image with Buttons Pressed Image with Buttons Highlighted and Backlight On Scaling Screen Properties Screen Location Total Screen Size Display Area Note Display Area in Full Screen Mode Screen Pixel Ratio Note Screen Background Color Screen Border Color Touch Screen Note Screen Buffering Device Buttons Keyboard Handler Defining a Device Button Page Assigning a PC Keyboard Key to a Button Note Assigning a Game Action to a Button Specifying the Characters Generated by a Button Press Assigning Abstract Commands to Buttons Note Emulating Abstract Command Button Assignments Note Precedence of Assigning Commands to a Button Assigning an Abstract Command Type to a Button Secondary Button Assignments Restricting the List of Command Types for a Soft Button The Abstract Command Menu Customizing Menu Title and Soft Button Note Displayed Icons Defining the Icon Location and States Soft Button Label Display Color Sound Alerts Device Software Capabilities Locales Character Encodings Note Transparent Images Page Default Emulator Device Property Files Property Files The following property files are used. DefaultGrayPhone.properties Page Page Page Page Page Page Page Page Support for ByteCode Obfuscators Adding a ByteCode Obfuscator Example Page Page Connecting to the Wireless Toolkits WMA Emulation Environment Page Index A B C D G I K M N