Data binding (Flash Professional only) 411
The following list describes the types of things reported:
■ Executing bindings
■ Calling web service methods
■ Fetching XML documents
■ Status and result events from WebService and XML components
■ Valid and invalid events from validated data fields
■ A variety of errors, invalid settings, and so on
By running your application and then examining the log, you can often find out why things
are not working as expected. Sometimes an error is explicitly reported—for example, a
missing web service parameter. Sometimes the data is bound to the wrong component or to
no component and so on. If you find that there is too much information in the log, clear the
Output window by selecting Clear from the context menu, to keep the log as short as
possible.
For more information, see the “Log class (Flash Professional only)” in the Components
Language Reference.
Data binding in Flash Player 7 versus Flash Player 6
Bindings between components are executed based on default component events (for example,
a binding between the
selectedIndex of a DataGrid and a DataSet is executed whenever a
new record is selected in the DataGrid or DataSet. After the event is generated, the binding is
queued to be executed as soon as possible. This action depends on your version of Flash
Player. If you publish to Flash Player 7, the binding happens immediately. If you publish to an
earlier version of Flash Player, the binding is queued to the beginning of the next frame.
However, the DataSet component works only in Flash Player 7. Queuing bindings to the next
frame can potentially cause issues with components, such as the DataSet, that provide their
own events for accessing data that may become out of sync with data binding. To avoid these
issues, Macromedia recommends that you publish to Flash Player 7 when using the DataSet
component.