It does sound like you are describing the bug where the focus manager holds onto the reference of the combo box and stops the module unloading...
If you lose the combobox focus, does the module unload? Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk <blocked::http://www.inps.co.uk/> The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact is.helpd...@inps.co.uk ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Battershall, Jeff Sent: 23 April 2009 14:32 To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Unloading Modules - Binding is the Enemy? Thanks Pedro, I've seen what your describing in the docs - I'm looking at this via the profiler which is giving me feedback as to number of live instances, etc. Here's what I'm basing my statements on:. 1) I start up my app, which loads modules at runtime based upon user choice from a menu. 2) Module exectues Cairngorm Event/Command/Delegate to get array to populate a combo box. I'm passing a reference to the module's model in my Cairngorm event and the model is updated upon completion of the Command. 3) Combobox is bound (via MXML) to the model. 4) If I don't interact with the combobox, I can then logout and unload the module successfully. The profiler tells me there was previously 1 instance of the module and now there are zero instances. 5) If I make the combobox active (by interacting with it in any way), and then logout, the module remains in memory, with the profiler reporting one instance instead of zero. 6) If I then login again, the Profiler reports 2 active instances of the module. Note that any model objects are duplicated as well. For example, if my list of suppliers (used to popuate my combobox) (a strongly typed AS class) was previously 64, the profiler now reports there are 128 instances. There's my behavior. When my UI object (in this case ComboBox), becomes active, the binding becomes active and then the module will not unload, even if I set the modules model to null before attempting to unload. It would appear that I need to invalidate all outstanding bindings to any data object before the module will fully unload. This would seem to indicate that MXML binding (via curly braces) isn't going to allow this. Jeff
