Color Picker in Component Inspector

Question

I want to add a parameter to a custom component which uses
the Color Picker in the Component Inspector. I would prefer to be
able to define the component parameters with the class(rather than
manually adding/subtracting the parameters).
However, there seems to be a conflict between the parameter
type 'Color' and the Color class.
To replicate this problem:
1. Define a symbol's class with the attached 'test' class.
2. Define the component parameters in the 'Component
Definition' for the class with the same 'test' class.
3. Drag the symbol to the stage.
4. Click on the symbol, and adjust the color parameter in the
Component Inspector(important step, otherwise it doesn't try and
set the color)
5. Run - receive "1067: Implicit coercion of a value of type
int to an unrelated type fl.motion:Color." error.
The only way I can see of resolving this seems more like a
hack - to remove the "test" class from the Component definition,
but leave the color parameter there. Now, to adjust the color
variable in the 'test' class to expect an int, rather than Color.
However, I would much prefer to keep the test class in the
Component definition, rather than manually changing the parameters.
Feels like this area of component parameters is on the
fringes of documentation, and even maintaining (this apparent
conflict between Color class and Color parameter type a case in
point).
Anyone any ideas/comments?

Answer 1

i would hope that defining a parameter as an int wouldn't
default to a color picker!
You're seeing a color picker because you initially defined
the parameter as Color. If you go back into Component definition
and hit OK, the parameter input type will update. (so long as you
have 'test' set up as the Definition class)
Alternatively, if you were to go through the 'replicate this
problem' steps above, but with your class, you won't see the Color
Picker.
As i said earlier, I'm aware that if i was to remove test as
Definition class, and either set up an alternative class as
definition class, or manage the parameter definitions manually, i
could fudge a solution to this problem.
I would like to know - is this hack necessary, or is there a
more conventional solution? I think it would make the most sense if
my component parameters could be defined by my class.
And I'm curious to know - what are we seeing here? Am I right
in thinking that there appears to be a conflict between the
parameter definition type 'Color' and the fl.motion.Color
class?