In testing via the Profiler, binding UI objects in a module to a model (even if local to the module) appears to be causing a module's failure to unload. This happens as soon as the UI component becomes active. In fact, even if the source object (data provider) is set to null, the binding persists and will prevent a module from unloading. Does this issue have to be such a PITA? It appears that using curly braces for binding in MXML can create Modules that won't unload.
In FP 10, the Loader class has the new unloadAndStop() method. Would be extremely handy to have something similar for Modules. Basically you want to remove all listeners to a model and then unload the module. Seeking enlightenment - anyone got any? Jeff Battershall Application Architect Dow Jones Indexes jeff.battersh...@dowjones.com (609) 520-5637 (p) (484) 477-9900 (c)
