Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>activate</code> event is inherited from EventDispatcher (the default implementation of event dispatching class present in the player runtime). This class is usually extended by other classes if they want to be able to dispatch events. This particular event is dispatched <a href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/events/EventDispatcher.html#event%3aactivate" rel="nofollow"><em>"when the Flash Player or AIR application gains operating system focus and becomes active"</em></a> Note that it is a broadcast type event, which means that you don't need to listen to any particular dispatcher, it is invoked on any existing listener.</p> <p><code>addedToStage</code> is dispatched <a href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/display/DisplayObject.html#event%3aaddedToStage" rel="nofollow">when the listener is added to display list</a> (it's properties such as <code>stage</code>, <code>parent</code> and <code>loaderInfo</code> are populated and, potentially, it can start receiving interaction events, such as mouse events, touch events etc.) This is one of the basis events available to all display objects.</p> <p><code>viewActivate</code> is a specific to mobile devices event dispatched by classes inheriting from <code>spark.components.View</code>. So far I understand, it is dispatched once the view (which dispatches it) becomes visible to the user.</p> <p><code>creationComplete</code> is a specific to Flex framework event. It will be dispatched by View class mentioned above, because it is an extension of UIComponent, which is the core component of the Flex framework. This event is dispatched <a href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/core/UIComponent.html#event%3acreationComplete" rel="nofollow">once all of the components properties declared in MXML template were set</a>, the component finished it's validation cycle, being laid out etc.</p> <p>Most unfortunately, according to Adobe design you must use Flex framework in order to access certain features on mobile devices. This is why you have that lot of initialization events - the Flex framework is bloated with redundant or very similar classes, functions etc.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload