User manual MACROMEDIA FLASH MX 2004-USING FLASH

[. . . ] Using Flash Trademarks Add Life to the Web, Afterburner, Aftershock, Andromedia, Allaire, Animation PowerPack, Aria, Attain, Authorware, Authorware Star, Backstage, Bright Tiger, Clustercats, ColdFusion, Contribute, Design In Motion, Director, Dream Templates, Dreamweaver, Drumbeat 2000, EDJE, EJIPT, Extreme 3D, Fireworks, Flash, Flash Lite, Flex, Fontographer, FreeHand, Generator, HomeSite, JFusion, JRun, Kawa, Know Your Site, Knowledge Objects, Knowledge Stream, Knowledge Track, LikeMinds, Lingo, Live Effects, MacRecorder Logo and Design, Macromedia, Macromedia Action!, Macromedia Breeze, Macromedia Flash, Macromedia M Logo and Design, Macromedia Spectra, Macromedia xRes Logo and Design, MacroModel, Made with Macromedia, Made with Macromedia Logo and Design, MAGIC Logo and Design, Mediamaker, Movie Critic, Open Sesame!, Roundtrip, Roundtrip HTML, Shockwave, Sitespring, SoundEdit, Titlemaker, UltraDev, Web Design 101, what the web can be, and Xtra 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. [. . . ] The type of document you select determines the type of default screen in the document. · A Flash Slide Presentation uses the slide screen as the default screen type. A slide screen has functionality designed for a sequential presentation. · A Flash Form Application uses the form screen as the default screen type. A form screen has functionality designed for a nonlinear, form-based application. Although each document has a default screen type, you can include both slide screens and form screens in any screen-based document. For information on slide and form screens, see "Slide screens and form screens (Flash Professional only)" on page 218. Document structure and hierarchy (Flash Professional only) Each document has a master screen at the top level. In a Flash Slide Presentation, the top-level screen is called Presentation by default. In a Flash Form Application, the top-level screen is called Application by default. The top-level screen is the container for everything that you add to the document, including other screens. Screens are similar to nested movie clips in some ways: Child screens inherit the behavior of their parents, and you use target paths in ActionScript to send messages from one screen to another. However, screens do not appear in the library, and you cannot create multiple instances of a screen. For information on using ActionScript with screens, see "About using ActionScript with screens (Flash Professional only)" on page 231. Understanding screen-based documents and the screen authoring environment (Flash Professional only) 217 You can add multiple screens to a document, and you can nest screens within other screens, in as many levels as you want. If a screen is nested several layers deep, all the screens above that screen are its ancestors. A child screen contains all the content of its ancestor screens. Top-level slide has three children, Slide 1, Slide 2, and Slide 3. Slide 5 is a child of Slide 4. The Screen Outline pane for a Flash Slide Presentation containing screens nested three levels deep. About using preloaders with screen-based documents If you want to include a preloader with your screen-based document, one way to do this is to create the preloader as a separate SWF file (non-screen-based), and load the SWF file for the screen-based document from within the preloader SWF. You cannot create a preloader within a screen-based document, because all screens in a document are located on the first frame of the root Timeline, so you cannot call or load other frames. Slide screens and form screens (Flash Professional only) You can create two types of screens in a document: slide screens and form screens. A Flash Slide Presentation uses the slide screen as the default screen type. A Flash Form Application uses the form screen as the default screen type. However, you can mix slide screens and form screens in any screen-based document to take advantage of the functionality of each type of screen and create more complex structure in a presentation or application. 218 Chapter 12: Working with Screens (Flash Professional Only) You can set parameters for slide or form screens in the Property inspector. For more information, see "Setting parameters for a screen (Flash Professional only)" on page 225. [. . . ] For the complete example, see <menulist>. <radiogroup id="type"> <radio label="Movie clip"/> <radio label="Button"/> <radio label="Graphic"/> </radiogroup> <targetlist> Availability Flash MX 2004. Usage <targetlist id="myLabel" class="myClass1[, myClass2][, . . . , myClassN]" required="true|false" pathtype="relative|absolute"/> Attributes id String; represents a unique identification string that is used by the extensibility features to identify the control and access the value it returns. class The class or classes for which to list instances. required Boolean value; if true, the OK button cannot function until a value is entered for this control; if false, the control has no effect on the OK button. String; the two possible values are relative and absolute. pathtype Child tags None. <targetlist> 467 Description Control tag; creates a control that lists all instances of a class and lets the user select an instance. Example The following example is excepted from the Load Graphic behavior definition file. The tags define a targetlist control that lets users select a movie clip into which a graphic will be loaded. For the complete dialog box definition, see the Graphic_load_graphic. xml file in the Behaviors folder. <vbox> <label value=""/> <label value="Select the movie clip into which to load the graphic:"/> <targetlist id="target" class="movieclip"/> </vbox> The control created by the <targetlist> tag is shown in the following figure: <textbox> Availability Flash MX 2004. Usage <textbox id = "myID" literal = "true|false" maxlength = "myLength" multiline = "true|false" size = "mySize" tabindex = "myIdx" value = "myValue"/> 468 Appendix B: XML to UI Attributes id String; represents a unique identification string that is used by the extensibility features to identify the control and access the value it returns. [. . . ]