EasyManua.ls Logo

MACROMEDIA FLASH 8-USING FLASH - Page 577

MACROMEDIA FLASH 8-USING FLASH
678 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Adding, naming, and registering assets 577
If you have experience handling and naming graphics, you can enter your own instance names
for the graphic assets on the Stage. You do not need to use the movie clip containers or the
templates—instead, you can add your own assets to the Stage, add a Learning Interaction
component to the Stage, and then register the assets’ instance names in the Component
inspector for the interaction.
Remember the following aspects about naming assets:
Interaction components do not need to be named.
UI components need to have unique names for similar interaction types.
Each graphic distractor (Drag object, Target object, hot spot, and hot object) must have a
unique instance name.
Text fields can share the same instance names across multiple interactions.
After you name the assets on the Stage, it’s important to register those names in the
Component inspector for the learning interaction so that the scripts can control the assets.
About naming Learning Interaction component
instances
Every interaction has an interaction component associated with it to configure its unique
parameters. These components do not need to be named.
Naming UI components (RadioButton, CheckBox,
Button, and TextInput)
When you use similar interaction types, you need to give each UI component a unique name.
For example, if you create two Multiple Choice interactions, the second interaction requires
unique instance names for the CheckBox and the Button components. These new instance
names need to be registered in the Component inspector for the learning interaction.
To name a UI component:
1. Select the UI component instance on the Stage.
2. In the Property inspector, type a name in the Instance Name text box.
3. Register the name in the Component inspector for the interaction (see “Registering
dynamic text fields and UI components” on page 578).

Table of Contents

Related product manuals