_onMainColorSelected calls both onMainColorChange and onColorChange about flutter_material_color_picker HOT 6 CLOSED

Hey that makes sense. And your English is fine, never apologize.

Actually, what do you think about adding a property allowShades: bool so that the material_color_picker can be used with only the main colors if needed. We can then use the flag to determine the behavior of the callbacks too.

from flutter_material_color_picker.

I understand but, when you choose the main color, a shade color is automatically selected. Calling the onColorChange is useful when you use this color picker in a dialog, if the user choose the main color and after submit the dialog without select the shade color.

You can wrap it, store the current shade color and if the dialog is submit (and not canceled), return the color. You can check how I use it here: https://github.com/Pyozer/MyAgenda_Flutter/blob/master/lib/widgets/settings/list_tile_color.dart

Instead of remove the call of onColorChange when mainColor is chosen, we can add a parameter to call it or not.

If the onColorChange is not calling after the mainColor and the user just submit the dialog after chosen the mainColor, the color will be lost.

(Sorry if my english is not good 😆)

from flutter_material_color_picker.

Yeah it's a great idea, I will merge your PR ;)

from flutter_material_color_picker.

Awesome, I've updated the docs and change list. Let me know if there's any issues with it.

from flutter_material_color_picker.

Thank you for your PR, I merged it and publish new version to pub ;)
I also made a small fix for mainColor with selectedColor parameter.
Also, I add an example project with the package ;)

from flutter_material_color_picker.

Awesome. I can't wait to use it.

from flutter_material_color_picker.