I find myself using executeBindings() more and more.  The pattern is usually when I use an AS object, that I developed, as the underlying model of a component and the binding is a method call on this object.  Not really sure how to "reorganize" my objects as I am not doing anything convoluted.  Is there a better pattern?
 
I also found that executeChildBindings() doesn't seem to do anything, but it may be justmy use of it.   What is the difference between the two methods?
 
 
-S

You shouldn't need to call executeBindings() except in extreme
circumstances.

During compilation, Flex creates watchers for each object (including
parameters to function calls) in each binding _expression_.  If you are making
changes internal to Arrays of objects in the Repeater's dataProvider and the
watchers aren't catching changes, you can probably reorganize objects in
your binding expressions rather than call executeBindings() manually.

Please file a bug and we'll check out the problem.  It sounds like we just
need to improve the Repeater/Binding documentation a little. 

We prefer when things work automagically to having folks stumble around
blindly.  :)

Thanks,
-e



-----Original Message-----
From: jeff tapper [mailto:[EMAIL PROTECTED]
Sent: Monday, May 03, 2004 8:54 AM
To: [email protected]
Subject: [flexcoders] When to use executeBindings() ?

Has anyone discovered a pattern as to when a repeater needs to be
manually told to "executeBindings()" and when it will happen auto-
magically?  I haven't found the pattern yet, I'm stumbling around
blindly by calling it manually if it doesn't seem to work.  I'd love
to know more definitively exactly when it should be needed, as I
can't tell whats a bug which should be reported, and what is my own
addle mindedness.


any advice?


thanks, as always

jeff





Yahoo! Groups Links





Reply via email to