Hi Derrick, In my opinion, due to the release of Cairnorm 2.2, see explanation here:
http://weblogs.macromedia.com/amcleod/archives/2007/05/cairngorm_22_-_1.cfm ... unbinding should'nt be necessary any more. Regards, masu On 7/9/07, Derrick Grigg <[EMAIL PROTECTED]> wrote: > > You can use the mx.Modules approach. I have used them in large Flex > applications and they worked quite well. The only cavet is that you > should not use the easy databinding (ie dataProvider="{model.cart"} ) > since those bindings can not be removed when a Module is unloaded. > Instead use the ChangeWatcher > (http://livedocs.adobe.com/flex/201/langref/mx/binding/utils/ChangeWat > cher.html) to accomplish the quasi binding. Using that allowed me > to 'unbind' when I needed to. In the class file I would declare a > variable as type ChangeWatcher, and then use the ChangeWather.watch > method to create an instance of the ChangeWatcher and set it to my > variable. When I needed to unbind I would use the > ChangeWatcher.unwatch method to remove the binding. Overall it's a > little more code but it works well. I didn't use the BindingUtils > because there was no way to remove them after the fact. > > With the mx.Modules you can dispatch an event before you unload the > module to getting the 'binding' removed and also remove any event > listeners etc. to ensure the module is fully unloaded. With a bit of > work you can get it working properly. > > Hope that helps, > > Derrick > > -------------- > www.dgrigg.com > > >
