| Paquete | com.adobe.icc.vo |
| Clase | public class Statement |
| Herencia | Statement  Object |
| Implementa | IEventDispatcher |
| Versión del lenguaje: | ActionScript 3.0 |
| Versión de producto: | Bloque de construcción Asset Composer 9.5 |
| Versiones de motor de ejecución: | AIR (unsupported), Flash Player 9, Flash Player 10 |
Statements should be formed as ({attributeName} {operator} {attributeValue}).
Example 1: For, specifying (state = 1), set:
- attributeName = "state"
- operator = OP_EQUALS
- attributeValue = 1
For, specifiying 'name' begins that 'abc', i.e, name = 'abc, set:
- attributeName = "name"
- operator = OP_STARTS_WITH
- attributeValue = "abc"
Statements can also be chained together using the innerStatement and joinOperator properties. This allows one to build
compound statements.
Example 2: Consider the statement ((name = 'abc) OR name = 'yz'), i.e., either 'name' begins with 'abc' or ends with 'xyz'. For this, set:
- attributeName = "name"
- operator = OP_STARTS_WITH
- attributeValue = "abc"
Then make a new Statement object and set:
- attributeName = "name"
- operator = OP_ENDS_WITH
- attributeValue = "xyz"
Finally, set the xyz statement as the innerStatement of the abc statement and set abc statement's joinOperator = JOIN_OR.
Example 3: Searching for modules that either do use a Data Dictionary or use a specific Data Dictionary.
In this case, we take advantage of the fact that statements can search on nested properties. The path to the property is the same as that which you would
normally use to get at the property on the corresponding Value Object: If a DataModule object does not use a Data Dictionary, its
dataDictionaryRefs property will be null. If it uses one, however, its DataDictionaryRefs property will set to the
ID of the Data Dictionary used by the module.
The first statement will therefore check for a null dataDictionaryRefs property and the second (nested statement) will check for an existing
dataDictionaryRefs property set to a given Data Dictionary ID string (note that the server will take care of looking at the first item within
the dataDictionaryRefs list even if there are no items):
- attributeName = "dataDictionaryRefs"
- operator = OP_IS_NULL
- attributeValue = null
- joinOperator = JOIN_OR
-
innerStatement =
- attributeName = "dataDictionaryRefs"
- operator = OP_EQUALS
- attributeValue = {dataDictionaryId}
Ocultar propiedades públicas heredadas
Mostrar propiedades públicas heredadas| Propiedad | Definido por | ||
|---|---|---|---|
 | constructor : Object
Una referencia a la clase de objeto o función constructora para una instancia de objeto determinada. | Object | |
| Método | Definido por | ||
|---|---|---|---|
addEventListener(type:String, listener:Function, useCapture:Boolean = false, priority:int = 0, weakRef:Boolean = false):void
Registers an event listener object with an EventDispatcher object so that the listener
receives notification of an event. | Statement | ||
Dispatches an event into the event flow. | Statement | ||
Checks whether the EventDispatcher object has any listeners registered for a specific type
of event. | Statement | ||
|
Indica si un objeto tiene definida una propiedad especificada. | Object | |
|
Indica si hay una instancia de la clase Object en la cadena de prototipo del objeto especificado como parámetro. | Object | |
|
Indica si existe la propiedad especificada y si es enumerable. | Object | |
Removes a listener from the EventDispatcher object. | Statement | ||
|
Establece la disponibilidad de una propiedad dinámica para operaciones de bucle. | Object | |
|
Devuelve la representación de cadena de este objeto, con formato según las convenciones específicas de configuración regional. | Object | |
|
Devuelve la representación de cadena del objeto especificado. | Object | |
|
Devuelve el valor simple del objeto especificado. | Object | |
Checks whether an event listener is registered with this EventDispatcher object or any of its ancestors for the specified event type. | Statement | ||
| Constante | Definido por | ||
|---|---|---|---|
addEventListener | () | método |
public function addEventListener(type:String, listener:Function, useCapture:Boolean = false, priority:int = 0, weakRef:Boolean = false):voidRegisters an event listener object with an EventDispatcher object so that the listener receives notification of an event. You can register event listeners on all nodes in the display list for a specific type of event, phase, and priority.
After you successfully register an event listener, you cannot change its priority
through additional calls to addEventListener(). To change a listener's priority, you
must first call removeEventListener(). Then you can register the listener again with the new
priority level.
After the listener is registered, subsequent calls to
addEventListener() with a different value for either type or useCapture result in the
creation of a separate listener registration. For example, if you first register a
listener with useCapture set to true, it listens only during the capture phase. If you
call addEventListener() again using the same listener object, but with useCapture set to
false, you have two separate listeners: one that listens during the capture phase, and
another that listens during the target and bubbling phases.
You cannot register an event listener for only the target phase or the bubbling phase. Those phases are coupled during registration because bubbling applies only to the ancestors of the target node.
When you no longer need an event listener, remove it by calling EventDispatcher.removeEventListener(); otherwise, memory problems might result. Objects
with registered event listeners are not automatically removed from memory because the
garbage collector does not remove objects that still have references.
Copying an EventDispatcher instance does not copy the event listeners attached to it. (If your newly created node needs an event listener, you must attach the listener after creating the node.) However, if you move an EventDispatcher instance, the event listeners attached to it move along with it.
If the event listener is being registered on a node while an event is also being processed on this node, the event listener is not triggered during the current phase but may be triggered during a later phase in the event flow, such as the bubbling phase.
If an event listener is removed from a node while an event is being processed on the node, it is still triggered by the current actions. After it is removed, the event listener is never invoked again (unless it is registered again for future processing).
Parámetros
type:String — The type of event.
| |
listener:Function — The listener function that processes the event. This function must accept an event object
as its only parameter and must return nothing, as this example shows:
| |
useCapture:Boolean (default = false)useCapture is set to true, the
listener processes the event only during the capture phase and not in the target or
bubbling phase. If useCapture is false, the listener processes the event only
during the target or bubbling phase. To listen for the event in all three phases, call
addEventListener() twice, once with useCapture set to true,
then again with useCapture set to false.
| |
priority:int (default = 0) | |
weakRef:Boolean (default = false)Class-level member functions are not subject to garbage
collection, so you can set |
dispatchEvent | () | método |
public function dispatchEvent(event:Event):Boolean
Dispatches an event into the event flow. The event target is the
EventDispatcher object upon which dispatchEvent() is called.
Parámetros
event:Event — The event object dispatched into the event flow.
|
Boolean — A value of true unless preventDefault() is called on the event,
in which case it returns false.
|
hasEventListener | () | método |
public function hasEventListener(type:String):Boolean
Checks whether the EventDispatcher object has any listeners registered for a specific type
of event. This allows you to determine where an EventDispatcher object has altered handling of an event type in the event flow hierarchy. To determine whether
a specific event type will actually trigger an event listener, use IEventDispatcher.willTrigger().
The difference between hasEventListener() and willTrigger() is that hasEventListener() examines only the object to which it belongs, whereas willTrigger() examines the entire event flow for the event specified by the type parameter.
Parámetros
type:String — The type of event.
|
Boolean — A value of true if a listener of the specified type is registered; false otherwise.
|
removeEventListener | () | método |
public function removeEventListener(type:String, listener:Function, useCapture:Boolean = false):voidRemoves a listener from the EventDispatcher object. If there is no matching listener registered with the EventDispatcher object, a call to this method has no effect.
Parámetros
type:String — The type of event.
| |
listener:Function — The listener object to remove.
| |
useCapture:Boolean (default = false)removeEventListener() are required to remove both: one call with useCapture set to true, and another call with useCapture set to false.
|
willTrigger | () | método |
public function willTrigger(type:String):Boolean
Checks whether an event listener is registered with this EventDispatcher object or any of its ancestors for the specified event type. This method returns true if an event listener is triggered during any phase of the event flow when an event of the specified type is dispatched to this EventDispatcher object or any of its descendants.
The difference between hasEventListener() and willTrigger() is that hasEventListener() examines only the object to which it belongs, whereas willTrigger() examines the entire event flow for the event specified by the type parameter.
Parámetros
type:String — The type of event.
|
Boolean — A value of true if a listener of the specified type will be triggered; false otherwise.
|
Tue Jun 12 2018, 02:12 PM Z