1 Reply Latest reply on Aug 18, 2012 10:24 PM by Flex harUI

    Is overriding commitProperties neccessary when updating Spark components?


      I understand that when creating a custom component, it's normally best practice to defer any property changes to it by using setters/getters, setting a "dirty" flag, calling invalidateProperties(), and then letting commitProperties() handle the actual changes.

      But in the case where properties only affect Spark components, wouldn't this be redundant since Spark components already defer their property changes?

      For instance, say I have a custom UIComponent that contains a Spark Button and I want to expose a buttonLabel property for it that changes the label of the button:

      private var _buttonLabel:String;
      private var myBtn:Button;
      private var _buttonLabelChanged:Boolean = false;
      function set buttonLabel(lbl:String){
      = lbl;
      = true;

      So then setting the buttonLabel property will then eventually trigger:

      override protected function commitProperties(){
      .label = _buttonLabel;
      = false;

      But the setter for "label" in the Spark Button class is already using an invalidation process which makes the above code pointless, yes? Or am I missing something?