I've been poking around sanity-checking some code I'm working on for my DI
package, and posted my conclusions and thoughts here: http://is.gd/2tAu
-Josh
On Thu, Aug 21, 2008 at 8:28 AM, Josh McDonald <[EMAIL PROTECTED]> wrote:
> I'd say if A is long-lived you'd definitely want to keep a referenc
I'd say if A is long-lived you'd definitely want to keep a reference to the
watcher so you can unwatch it, or at least re-use it :)
Just thinking of the best way to have an editor component have the VO
injected but still be able to know when the entire object is replaced behind
its back. I think I
When u create a binding from object A to B, a reference is added to A.
(A keeps a reference to B).
It will not be garbage collected until you unwatch the changeWatcher it
or delete A.
So if your concern is whether u need to keep a reference to
ChangeWatcher object returned by
mx.binding.utils
I think you have to call unwatch otherwise the CW may not get GC'd
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Josh McDonald
Sent: Tuesday, August 19, 2008 10:57 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Question about
4 matches
Mail list logo