"safer" is a misnomer here, because there's no harm in running the setter. If we define the change event to mean that the reference changed, then this is the right check. We don't use logical equals() in our comparison of other component model objects (like list data), so a reference equality check is more consistent with checks like "if previousListData != listData".
-T On Mon, Aug 3, 2009 at 6:57 AM, Sandro Martini <[email protected]>wrote: > HI Niclas, > good point :-) i agree with you, I'm for safer tests, or to avoid them > and assign always the new value ... > > And what other say ?? > > > Than, what default value should we set in the patch for the > isCloseable of TabPane (and there are others like this in sources, but > i can get more details on others) ? > > Thanks, > Sandro >
