MACROMEDIA FLASH 8-DEVELOPING FLASH LITE 2.X User manual

Developing Flash Lite Applications

Trademarks
1 Step RoboPDF, ActiveEdit, ActiveTest, Authorware, Blue Sky Software, Blue Sky, Breeze, Breezo, Captivate, Central,
ColdFusion, Contribute, Database Explorer, Director, Dreamweaver, Fireworks, Flash, FlashCast, FlashHelp, Flash Lite,
FlashPaper, Flash Video Endocer, Flex, Flex Builder, Fontographer, FreeHand, Generator, HomeSite, JRun, MacRecorder,
Macromedia, MXML, RoboEngine, RoboHelp, RoboInfo, RoboPDF, Roundtrip, Roundtrip HTML, Shockwave, SoundEdit,
Studio MX, UltraDev, and WebHelp are either registered trademarks or trademarks of Macromedia, Inc. and may be registered in
the United States or in other jurisdictions including internationally. Other product names, logos, designs, titles, words, or phrases
mentioned within this publication may be trademarks, service marks, or trade names of Macromedia, Inc. or other entities and
may be registered in certain jurisdictions including internationally.
Third-Party Information
This guide contains links to third-party websites that are not under the control of Macromedia, and Macromedia is not
responsible for the content on any linked site. If you access a third-party website mentioned in this guide, then you do so at your
own risk. Macromedia provides these links only as a convenience, and the inclusion of the link does not imply that Macromedia
endorses or accepts any responsibility for the content on those third-party sites.
Speech compression and decompression technology licensed from Nellymoser, Inc. (www.nellymoser.com).
Sorenson™ Spark™ video compression and decompression technology licensed from
Sorenson Media, Inc.
Opera ® browser Copyright © 1995-2002 Opera Software ASA and its suppliers. All rights reserved.
Macromedia Flash 8 video is powered by On2 TrueMotion video technology. © 1992-2005 On2 Technologies, Inc. All Rights
Reserved. http://www.on2.com.
Visual SourceSafe is a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.
Copyright © 2005 Macromedia, Inc. All rights reserved. This manual may not be copied, photocopied, reproduced,
translated, or converted to any electronic or machine-readable form in whole or in part without written approval from
Macromedia, Inc. Notwithstanding the foregoing, the owner or authorized user of a valid copy of the software with which
this manual was provided may print out one copy of this manual from an electronic version of this manual for the sole
purpose of such owner or authorized user learning to use such software, provided that no part of this manual may be
printed out, reproduced, distributed, resold, or transmitted for any other purposes, including, without limitation,
commercial purposes, such as selling copies of this documentation or providing paid-for support services.
Acknowledgments
Project Management: Mary Leigh Burke
Writing: Tim Statler
Managing Editor: Rosana Francescato
Editing: Linda Adler, Mary Kraemer, Lisa Stanziano, Anne Szabla
Production Management: Patrice O’Neill, Kristin Conradi, Yuko Yagi
Media Design and Production: Adam Barnett, Aaron Begley, Paul Benkman. John Francis, Geeta Karmarkar, Masayo Noda,
Paul Rangel, Arena Reed, Mario Reynoso
Special thanks to Lisa Friendly, Bonnie Loo, Erick Vera, the beta testers, and the entire Flash Lite engineering and QA teams.
First Edition: September 2005
Macromedia, Inc.
601 Townsend St.
San Francisco, CA 94103

3
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
What’s new in Flash Lite authoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Guide to instructional media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Typographical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 1: Creating Interactivity and Navigation. . . . . . . . . . . . . . . 7
Keys supported by Flash Lite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using tab navigation in Flash Lite. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Handling key events (Flash Professional Only) . . . . . . . . . . . . . . . . . . . . 13
Handling button events (Flash Professional Only) . . . . . . . . . . . . . . . . 20
Using the soft keys (Flash Professional Only) . . . . . . . . . . . . . . . . . . . . 26
Chapter 2: Working with Text and Fonts . . . . . . . . . . . . . . . . . . . . 31
About text in Flash Lite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Using input text fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Font rendering methods in Flash Lite . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Flash Lite rendering quality and anti-aliased text . . . . . . . . . . . . . . . . . 39
Embedding font outlines in SWF files . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Text field example application (Flash Professional Only) . . . . . . . . . . 42
Creating scrolling text (Flash Professional Only). . . . . . . . . . . . . . . . . . 45
Chapter 3: Working with Sound . . . . . . . . . . . . . . . . . . . . . . . . . . 49
About sound in Flash Lite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Using device sound (Flash Professional Only). . . . . . . . . . . . . . . . . . . . 50
Using native Flash sounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Chapter 4: Optimizing content for performance and file size . . .57
SWF file size and memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Performance optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Device speed and frames per second . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4Contents
Chapter 5: Testing Flash Lite Content
(Flash Professional Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Overview of Flash Lite testing features (Flash Professional Only) . . . 63
Using the Flash Lite emulator (Flash Professional Only) . . . . . . . . . . . 66
Flash Lite error and warning messages (Flash Professional Only) . . 74
Selecting test devices and Flash Lite content type
(Flash Professional Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Flash Lite content types (Flash Professional Only) . . . . . . . . . . . . . . . . 78
Determining platform capabilities (Flash Professional Only). . . . . . . . 81
Appendix: Warning and Error Messages
(Flash Professional Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Flash Lite emulator error and information messages
(Flash Professional Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

5
Introduction
This manual describes how to develop applications for mobile devices using Macromedia
Flash Lite. You can use various modes of navigation for different devices and how to work
with text and fonts. This manual also describes how to manage the runtime memory available
to Flash Lite applications running on various models of mobile phones. Using a Flash Lite
emulator that is included with Macromedia Flash Professional 8, you can test and debug your
application in the authoring tool before you test it on an actual device.
What’s new in Flash Lite authoring
Flash Professional 8 includes the following new features to help developers create
Flash Lite applications:
Flash Lite emulator The Flash Lite emulator lets you preview your content as it will
function on an actual device. The emulator can configure itself to mimic the features available
on any supported device. The emulator also provides debugging information that alerts you to
potential problems and incompatibilities on the target device.
Device Settings dialog box You use the Device Settings dialog box to select your test
devices and Flash Lite content type. When you test your content in the Flash Lite emulator,
you can choose the test device you want the emulator to mimic.
Device document templates Flash Professional 8 includes document templates to let you
quickly start creating content for specific devices and content types.

6Introduction
Guide to instructional media
The Flash Lite documentation package includes the following media to help you learn how to
create Flash Lite applications:
■Getting Started with Flash Lite provides an overview of Flash Lite technology and
developing Flash Lite content for mobile devices. It also includes a step-by-step tutorial
for creating a Flash Lite application.
■Developing Flash Lite Applications is a comprehensive guide to creating Flash Lite
content, and includes instructions for testing your applications in the integrated
Flash Lite emulator.
■Flash Lite 1.x ActionScript Language Reference describes all the ActionScript language
features available to Flash Lite developers, and provides example code.
■Learning Flash Lite 1.x ActionScript complements the language reference and provides
additional code examples and an introduction to writing Flash 4 ActionScript, upon
which Flash Lite 1.x ActionScript is based.
■The Flash Lite sample applications demonstrate key concepts and best practices discussed
or mentioned in the written documentation.
Additional resources
For the latest information on developing Flash Lite applications, plus advice from expert
users, advanced topics, examples, tips, and other updates, see the Mobile and Devices
Developer Center at www.macromedia.com/devnet/devices/.
For TechNotes, documentation updates, and links to additional resources in the Flash Lite
developer community, see the Macromedia Flash Lite Support Center at
www.macromedia.com/support/flashlite/.
Typographical conventions
The following typographical conventions are used in this manual:
■Italic font indicates a value that should be replaced (for example, in a folder path).
■Code font indicates ActionScript code.
■Code font italic indicates an ActionScript parameter.
■Bold font indicates a verbatim entry.
■Double quotation marks ("") in code examples indicate delimited strings. However,
programmers can also use single quotation marks.

7
1
CHAPTER 1
Creating Interactivity and
Navigation
Macromedia Flash Lite 1.0 and Flash Lite 1.1 support user interaction through the device’s
keypad, or through a stylus or touch-screen interface on devices that provide one.
There are two ways to add key-based interactivity to a Flash Lite application. You can use the
Flash Lite default tab navigation, or you can create a custom key-based navigation system.
Tab navigation functions the same way in Flash Lite as it does in Flash desktop applications,
where the Tab and Shift+Tab keys let users navigate between objects on the screen. In Flash
Lite, the device’s four-way arrow keys serve the same purpose as the Tab and Shift+Tab keys.
Tab navigation in Flash Lite works only with buttons and input text fields; it is typically best
used for simple user interactions, such as menus. For more information, see “Using tab
navigation in Flash Lite” on page 9.
Instead of using tab navigation, you can use custom key navigation. In this case, your
application handles keypress events that Flash Lite generates in response to a user pressing a
key on their device, and then takes the appropriate action. You would use this type of
navigation, for example, if you’re creating a Flash Lite game or other application whose
interaction model is more complex than that of a simple menu.
This chapter contains the following topics:
Keys supported by Flash Lite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using tab navigation in Flash Lite. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Handling key events (Flash Professional Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Handling button events (Flash Professional Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Using the soft keys (Flash Professional Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

8 Creating Interactivity and Navigation
Keys supported by Flash Lite
In addition to the alphanumeric keys available on standard telephones, most mobile devices
feature a five-way keypad, which let users navigate and select items on the device’s display as
well as the Left and Right soft keys. A device’s soft keys are multifunctional keys that use the
device’s display to identify their purpose at any moment.
The five-way keypad has four arrow keys (Up, Down, Left, and Right) and a Select key, which
are typically located at the center of the keypad. Different applications can use these keys as
they choose. For example, in a Flash Lite game, the user might press the arrow keys to move a
character on the screen, and then press the Select key to perform another action, such as make
the character jump.
Flash Lite supports the following keys on mobile devices:
■Five-way keypad keys (Up, Down, Left, Right, and Select)
■Left and Right soft keys
■0-9, *, and # keys
The following images show these keys on a generic keypad and on an actual phone:
Not all devices and Flash Lite content types support all these keys. For example, on some
devices, a Flash Lite application can access only the Up and Down arrow keys, not the Left
and Right arrow keys. Also, not all devices and content types allow Flash applications to access
the Left and Right soft keys. When you test your application in the Flash Lite emulator, the
emulator generates warning messages when you press keys that aren’t available on the target
device and content type.
Soft keys
5-way keypad
Numeric, #, and
* keys

Using tab navigation in Flash Lite 9
Using tab navigation in Flash Lite
On desktop Flash applications, the Tab and Shift+Tab keys let users switch keyboard focus
among objects on the screen. The object that has focus responds to further keypresses. In
Flash Lite, the arrow keys on the device’s five-way keypad serve the same purpose as the Tab
and Shift+Tab keys.
Flash Lite supports three different modes of tab navigation: two-way, four-way, and four-way
with wrap-around. Different devices and Flash Lite content types support different navigation
modes. In two-way navigation, users can For more information, see “Modes of tab navigation”
on page 9.
Tab navigation in Flash Lite works with buttons and text fields. When an input text field has
focus and the user presses the Select key, Flash Lite opens the device’s generic text input dialog
box, in which the user can enter text. For an example of using input text fields to get user
input, see “Text field example application (Flash Professional Only)” on page 42.
This section contains the following topics:
Modes of tab navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About the focus rectangle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Guidelines for using tab navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Modes of tab navigation
Flash Lite supports three modes of tab navigation: two-way, four-way, and four-way with
wrap-around. Different devices and Flash Lite content types support different navigation
modes. For information on determining the navigation mode for a specific device and content
type, see “Determining platform capabilities (Flash Professional Only)” on page 81.

10 Creating Interactivity and Navigation
Each navigation mode discussed in the following sections references a sample file that you can
view in the Flash Lite emulator. Each sample file consists of the same three-by-three grid of
buttons, as shown below. The only difference between the sample files is that each is
configured to target a device and Flash Lite content type that support the navigation mode
in question.
f
To use each sample file, open it in Flash and test it in the emulator (select Control > Test
Movie). Click the arrow keys on the emulator’s keypad (or press the arrow keys on your
keyboard) to see how each navigation mode affects user navigation.
Two-way navigation In two-way navigation, the device’s Up and Down arrow keys move
focus from one object (button or input text field) to another; the Left and Right arrow keys
have no effect. The Down key moves the focus to the next object on the right. If there are no
objects positioned to the right of the current object with focus, focus moves to the leftmost
object below the current object with focus. If there are no objects below the rightmost object
with focus, focus moves to the top and leftmost object. The Up key moves focus to the next
object on the left. If there are no objects to the left of the current object with focus, focus
moves to the rightmost object above the object.
For an example of two-way navigation, see the sample file named 2_way_nav.fla, located in
the Samples and Tutorials/Samples/Flash Lite folder in the Flash installation folder.
Four-way navigation In four-way navigation, the user can move focus from one object to
another with the device’s Left, Right, Up, and Down keys. Pressing the Left key moves the
focus from the current object with focus to the object to the left of the button with focus. The
Right key moves the focus to the next button to the right of the button with focus. The Up
and Down keys similarly move focus to the button above and below the button with focus.
For an example that uses four-way navigation, see the sample file named 4_way_nav.fla
located in the Samples and Tutorials/Samples/Flash Lite folder in the Flash installation folder.
Four-way navigation with wrap-around This mode is the same as four-way navigation,
except that when there are no buttons below the rightmost button with focus, focus moves to
the top and leftmost button.
Array of buttons in sample file

Using tab navigation in Flash Lite 11
About the focus rectangle
By default, Flash Lite draws a yellow rectangle around the button or input text field that has
focus. The focus rectangle lets the user know which object on the screen will respond when
the user presses the device’s Select key. For example, the following image shows the focus
rectangle drawn around a button that has the current keypad focus:
For buttons, the focus rectangle’s bounding box is determined by the button’s hit area—
the invisible region that (in Flash desktop applications) defines the part of the button that
responds to mouse clicks. For input text fields, the focus rectangle’s bounding box is
determined by the text field’s dimensions.
You can disable the default focus rectangle behavior by setting the _focusRect property to
false. If you’re using buttons that define over states, Flash Lite displays those states when the
button receives focus. For this reason, the focus rectangle is often not necessary when using
buttons. For example, the following image shows the same application as in the preceding
image, but with the focus rectangle disabled; the button that has focus is displaying its
over state:
Button with current focus and
default focus rectangle
Button with current focus (focus
rectangle disabled)

12 Creating Interactivity and Navigation
If your application contains input text fields, Macromedia recommends that you do not
disable the focus rectangle, as it provides the only visual clue that an input text field has focus.
For example, the following image shows an input text field that has the current focus:
If your application contains buttons (with defined over states) and input text fields on the
same screen, you can set the _focusRect property to false in each button’s on(rollOver)
event handler and set it to true in each button’s on(rollOut) handler, as shown in the
following code example. This causes the focus rectangle to appear when an input text field has
focus, but not when a button has focus.
// Attach this code to each button on the Stage.
on(rollOver) {
_focusRect = false;
}
on(rollOut) {
_focusRect = true;
}
For more information about using input text fields, see “Using input text fields” on page 34.
Guidelines for using tab navigation
When using tab navigation to create interactivity, you should place at least two objects (input
text fields, buttons, or a combination) on the screen at the same time. If the screen only
contains a single button or input text field, the user can’t change the focus and may feel stuck
in the user interface.
If a screen in your application contains only a single button for user interaction, consider
detecting a keypress event rather than using button events. For more information, see
“Handling key events (Flash Professional Only)” on page 13.
Input text field with current focus

Handling key events (Flash Professional Only) 13
Handling key events (Flash Professional
Only)
In addition to using tab navigation between buttons and input text fields, a Flash Lite
application can also respond to arbitrary keypress events.
Not all devices and content types support all device keys. For example, on a device that
supports two-way navigation (see “Modes of tab navigation” on page 9) Flash Lite doesn’t
generate keypress events for the Left and Right Arrow keys.
On all devices, Flash Lite supports the following keys:
■0-9, *, and # keys
■Select key
On devices that support two-way navigation, Flash Lite also supports the Up and Down
Arrow keys on the 5-way keypad. On devices that support four-way navigation, Flash Lite
supports the Up, Down, Left, and Right Arrow keys.
On devices that support the SetSoftKeys command, Flash Lite also supports the Left and
Right soft keys.
This section contains the following topics:
Writing a key handler script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Creating a key catcher button (Flash Professional Only) . . . . . . . . . . . . . . . . . . . . . . 14
Creating a simple menu using movie clips (Flash Professional Only). . . . . . . . . . . . 16
Writing a key handler script
To handle a keypress event, you attach an on(keyPress "key") handler to a button instance,
where key is a supported key event name. For example, the following code, attached to a
button instance on the Stage, executes when the user presses the Right Arrow key on
their device:
on(keyPress "<Right>") {
trace("You pressed the right arrow key");
}

14 Creating Interactivity and Navigation
The following table lists the ActionScript keypress event that Flash Lite generates in response
to the user pressing a key on the device:
Creating a key catcher button (Flash Professional
Only)
If your application must handle several different keypress events you could either create a
single button for each keypress event, or use a single button to handle all keypress events.
This type of button is commonly called a key catcher (or key listener) button. Because the
key catcher button isn’t supposed to be visible to the user, it usually sits off the Stage (in the
work area).
The following procedures demonstrate how to use a key catcher button to handle keypress
events in a simple application. The application lets the user move a circle around the Stage by
pressing the four arrow keys on their device.
You can find a completed version of this application, key_catcher.fla, in the Samples folder on
your hard disk:
■In Windows, browse to boot drive\Program Files\Macromedia\Flash 8\
Samples and Tutorials\Samples\FlashLite.
■On the Macintosh, browse to Macintosh HD/Applications/Macromedia Flash 8/
Samples and Tutorials/Samples/FlashLite.
Device key ActionScript key event Availability
0-9, *, # 0, 1, 2, 3, 4, 5, 6, 7, 8,
-9, *, #All devices
Select key <Enter> All devices
Left Arrow key <Left> Devices that support four-way
navigation, only.
Right Arrow key <Right> Devices that support four-way
navigation, only.
Up Arrow key <Up> Devices that support four-way
navigation, only.
Down Arrow key <Down> Devices that support four-way
navigation, only.
Left soft key <PageUp> Devices that support the SetSoftKeys
command, only.
Right soft key <PageDown> Devices that support the SetSoftKeys
command, only.

Handling key events (Flash Professional Only) 15
To create and use a key catcher button:
1. Create a new document from the Flash Lite 1.1 Series 60 template, and save it as
keycatcher.fla.
For more information on creating documents from the Flash Lite templates, see “Using
Flash Lite document templates (Flash Professional Only)” in Getting Started with
Flash Lite.
2. Select the layer in the Timeline named Content.
3. Using the Oval tool, create a oval or circle on the Stage and convert it to a movie clip.
4. With the new movie clip selected, in the Property inspector, type circle in the Instance
Name text box.
5. Using the Text tool, create a text field that contains the text key catcher, and convert it to
a button symbol.
6. Position the new button symbol in the work area around the Stage. To view the work area
around the Stage, select View > Work Area.
7. Select the key catcher button instance, and open the Actions panel (Window > Actions).
8. Enter the following code in the Actions panel:
on(keyPress "<Left>") {
circle._x -= 10;
}
on(keyPress "<Right>") {
circle._x += 10;
}
on(keyPress "<Up>") {
circle._y -= 10;
}
on(keyPress "<Down>") {
circle._y += 10;
}
Key catcher button
Movie clip instance circle

16 Creating Interactivity and Navigation
9. Test the application by selecting Control > Test Movie.
Press the four arrow keys on the emulator’s keypad to make the circle move around
the Stage.
For another example of using a key catcher button, see “Creating a simple menu using movie
clips (Flash Professional Only)” on page 16.
Creating a simple menu using movie clips (Flash
Professional Only)
In this section you’ll learn how to create a simple menu using movie clips. In this method,
rather than relying on the default tab navigation between buttons—and attaching code to
each button—you use a key catcher button to listen for keypress events and update the user
interface as needed. This technique does involve more development work than the button
menu approach (see “Handling key events (Flash Professional Only)” on page 13), but it
offers some advantages:
■Control over tab order. Rather than tab order being determined by the Flash Lite player
(as with buttons), you (the developer) can decide what object has focus and how it
responds to keypress events.
■Maintain menu selection between application states. For example, suppose you want your
application to “remember” the last menu item the user selected so you can return the focus
to the same item at a later time. This isn’t possible using a button menu because you can’t
assign button focus using ActionScript.
In the following procedure, you start with a partially completed Flash document. You can find
a completed version of the application (movieclip_menu_complete.fla) in the /Tutorials and
Samples/Samples/Flash Lite/ folder in the Flash installation folder.
To create a simple menu using movie clips:
1. Open the file named movieclip_menu.fla located in the /Tutorials and Samples/Samples/
Flash Lite/ folder in the Flash installation folder.
2. In the Timeline, select the layer named Menu Items.

Handling key events (Flash Professional Only) 17
3. Open the Library panel (Window > Library) and drag an instance of the movie clip symbol
named Menu Item Clip from the Library panel to the Stage.
This movie clip contains two keyframes, or visual states: one for the menu item’s initial,
unselected state, and the other for its selected state, which appears when the menu item
receives focus. The following image shows the first keyframe of the movie clip’s timeline.
It contains a dynamic text field to display the menu item’s label, and a red background
graphic. The text field and background graphic extend across all frames in the movie
clip’s Timeline.
The following image shows Frame 5 in the movie clip’s Timeline. The only visual
difference between this frame and the first one is the yellow border highlight that
surrounds the menu item’s red background.
4. Drag two more instances of the menu item movie clip to the Stage and align them vertically
in a column.
5. Select the upper movie clip and, in the Property inspector, type menu_1 in the Instance
Name text box.
Dynamic text field with variable
name label.
Frame labels

18 Creating Interactivity and Navigation
6. Assign the instance names of menu_2 and menu_3 to the middle and lower movie
clips, respectively.
The numeric suffix appended to each instance name lets you dynamically refer to each
movie clip in code, which you’ll add shortly.
7. Using the Text tool, create a text field along the lower edge of the Stage.
8. In the Property inspector, select Dynamic from the Text Type pop-up menu, and type
status in the Var text box.
As in the simple menu example, this text field displays a status message about the menu
item that is currently selected.
9. In the Timeline, select the first frame on the layer named Actions.
10. Open the Actions panel (Window > Actions), and enter the following code:
// Initialize menu item labels:
menu_1.label = "News";
menu_2.label = "Sports";
menu_3.label = "Weather";
// Initialize variable that specifies number of menu items
numItems = 3;
// Initialize selectedItem variable, which contains
// the index of the current menu selection
selectedItem = 1;
// Initialize status text field
currentLabel = eval("menu_" add selectedItem add ":label");
status = "Press to select " add currentLabel;
// Send the first menu item to its "over" state
tellTarget("menu_1") {
gotoAndStop("over");
}
11. In the Timeline, select the layer named Key Catcher.
menu_1
menu_2
menu_3

Handling key events (Flash Professional Only) 19
12. Open the Library and drag an instance of the button named key catcher to the Stage.
Next you’ll attach event handler code to this button that handles user keypress events and
update the user interface.
13. With the button selected on the Stage, open the Actions panel.
14. Type (or copy and paste) the following code into the Actions panel:
on(keyPress "<Down>") {
if(selectedItem < numItems) {
// Turn off highlight on previously selected menu item:
tellTarget("menu_" add selectedItem) {
gotoAndStop("off");
}
// Increment selectedItem variable
// and turn on highlight for new selection
selectedItem++;
tellTarget("menu_" add selectedItem) {
gotoAndStop("over");
}
// Update status text field with label of selected item:
currentLabel = eval("menu_" add selectedItem add ":label");
status = "Press to select " add currentLabel;
}
}
on(keyPress "<Up>") {
if(selectedItem > 1) {
// Turn off highlight on previously selected item:
tellTarget("menu_" add selectedItem) {
gotoAndStop("off");
}
// Increment selectedItem and turn on highlight for new selection
selectedItem--;
tellTarget("menu_" add selectedItem) {
gotoAndStop("over");
}
// Update status text field with label of selected item:
currentLabel = eval("menu_" add selectedItem add ":label");
status = "Press to select " add currentLabel;
}
}
on(keyPress "<Enter>") {
// Update status field with selected item
status = "You selected " add currentLabel;
}

20 Creating Interactivity and Navigation
15. Select Control > Test Movie to test the application in the emulator.
To interact with the menu, click the Up and Down Arrow keys on the emulator with your
mouse, or press the corresponding arrow keys on your keyboard.
Handling button events (Flash
Professional Only)
Flash Lite supports the following ActionScript button events: press, release, rollOver, and
rollOut. To handle these events, you attach an on(event)handler to a button instance,
where event is one of the supported button events listed in the following table:
The following procedure demonstrates how to create a simple application that handles button
events. For an example of using buttons to create a menu, see “Creating a simple menu using
buttons and tab navigation (Flash Professional Only)” on page 22.
To create a button event handler script:
1. Create a new document from the Flash Lite 1.1 Series 60 device template and save it as
button_handler.fla.
For more information on creating documents from the Flash Lite templates, see “Using
Flash Lite document templates (Flash Professional Only)” in Getting Started with
Flash Lite.
2. Select Window > Common Libraries > Buttons to open an external library of prebuilt
button symbols.
3. In the Library panel, double-click the Circle Buttons folder to open it.
4. Drag an instance of the Menu button symbol to the Stage.
5. Select the button and open the Actions panel (Window > Actions).
Button event When event is generated
press User presses the Select key on device when button has focus.
release User releases the Select key on device when button has focus.
rollOver Button receives focus.
rollOut Button loses focus.