Going crazy wondering why the breakpoints in your setter method are getting called? Think there is a ghost in your CPU or your compiler is drunk? Maybe Flex is way smarter than you. Or at least it thinks it is. Tony H at EffectiveUI.com figured out that Flex 3 beta 4 rocks some behind-the-scenes logic that can prevent your setters from being called. Apparently, if you make a getter [Bindable], the associated setter will NOT be called if the value passed into the setter is the same as the one that would be returned from the getter. Hmmm. Thanks Flex 3 beta 4.
Setter not getting called in flex 3?
Posted by nick.stielau
on February 01, 2008
