Greentea published a summary and research of her hidden events in the Flash MX 2004 she found in her blog (http://www.yc-liren.com/green_tea/blog/). Original address: http://www.yc-liren.com/green_tea/blog/showlog.asp? Cat_id = 35 & log_id = 378 This mention: "Construct event is the component used to pass parameters, when we are in the Component Definition Set good parameters (or use inspectable), we modify the value of this parameter in the production tool, then this value is passed back through the Construct event. "My first reflection is that this event may only be debugging in Flash. In the development environment, I added some tests on the basis of the original text. I use the TextArea component to receive the value that the event is executed, not TRACE (). The code is as follows: OnClipEvent (construct) {_root.tomato.text = "construct / n";} onclipevent (inTIAALIZE) {_root.tomato.text = "iniyislize / n";}
OnClipevent (LOAD) {_root.tomato.text = "LOAD / N"; Use trace () can be displayed normally. That is to say, from the debugging and development of Flash, the incident fails! Before combined with the construct event to pass the parameters of the component before initializing the component, my guess: These are the events used when Flash execute some operations, and does not provide for development. So, it is a hidden event. It is also a reason, Macromedia does not need to open these incidents that are not available for Flash development.
