colorPickerChange fired on initialization.

[Adam Voliva]

The colorPickerChange event is being fired on initialization.

[Eric]

@avoliva I got the same problem, any solutions?

[Larry Chen]

+1

[Nicolas Rigaudière]

+1

[Nicolas Rigaudière]

@avoliva I have found a quick workaround for the moment. I'm using a boolean initialized at false and in my function I do the following :

public colorPickerChange(color: string) {
  if (this.isColorPickerInit) {
   //do something
  } else {
   this.isColorPickerInit = true;
  }
}

[Adam Voliva]

Ya I'm doing something similar to that too, but a real fix would be preferred.

[Scot S]

This is actually preventing me from using this package.
I'm running ajax calls using that Output when they select a color, and are running unnecessary ajax calls upon ngOnInit

[Christian Benseler]

Same here, still.
This workaround from @nrigaudiere works for a single colorpicket, but this approach doesn't scale if you have multiple pickers.