Method for transferring data between modules by utilizing event mechanism in flex

Abstract

The invention provides a method for transferring data between modules of a flex application program, which comprises the steps of utilizing an event propagation mechanism of the flex to encapsulate the data into a customized event, and then transferring the event carrying the data from a source module to a target module and separating the data which is contained in the event from the target module for the target module to use, thereby achieving the purpose of transferring the data between the modules. The method has simple operation and easy maintenance, and eliminates the dependence between the modules. Because the event propagation mechanism of the flex is utilized by the method, the data transferring efficiency is high, and errors do not easily occur.

Description

technical field [0001] The invention relates to a method for transferring data between modules in flex development. The method is fast and reliable, can conveniently realize the interaction between modules, is easy to use, is convenient to maintain, and greatly reduces the coupling degree between modules, making each module more independent. Background technique [0002] At present, the method of transferring data between modules in flex is mainly realized by calling the method attribute between two modules, for example, accessing the attribute or method of module B in module A, so that the data of module A is transferred to module B middle. Since the modules in flex are not loaded with the startup of the program, but are loaded dynamically during the running of the program, if module B has not been loaded, then module A will throw an exception when accessing the properties or methods of module B, only in the module Only when B has been loaded, module A can run normally, s...

AI Technical Summary

Problems solved by technology

Since the modules in flex are not loaded with the startup of the program, but are loaded dynamically during the running of the program, if module B has not been loaded, then module A will throw an exception when accessing the properties or methods of module B, only in the module Only when B has been loaded, module A can run normally, so that module A has a certain dependence on module B, thus increasing the coupling between modules

In addition, when transferring data from one module to multiple modules, it is necessary to repeatedly access the properties or methods of the external modules. If more data needs to be transferred, the code will look messy, which is not conducive to later maintenance and modification.