I am wondering, why `Color` has 3 properties named...

# compose

[Grigorii Yurkov]

I am wondering, why Color has 3 properties named red green blue if Color can store non-RGB colors, for instance HSV. Isn't it confusing?

[caelum19]

https://developer.android.com/reference/kotlin/androidx/compose/ui/graphics/Color seems this answers a few questions

[caelum19]

Looks like the only things stored are 1 int packed with 4 values and which ColorSpace is used

[caelum19]

the red, green and blue vals have overridden getters and so don't actually store anything but provide a way of extracting those values from the int

[Grigorii Yurkov]

I don't care about internal implementation. I am wondering why they named properties as they named

[caelum19]

I suppose for convenience? Seems you can get the components used in the model without mentioning those colours with the component1...4 properties. It does seem a little less safe after looking into it, in case someone was unaware of the color space and expected "red" to mean it has an rgb color space and they got back a component from another model

[caelum19]

maybe an exception should be thrown if the model isn't rgb? Maybe I'm missing something

[Grigorii Yurkov]

maybe an exception should be thrown if the model isn't rgb?

No it should not

[Grigorii Yurkov]

* If this color's color model is not [RGB][ColorModel.Rgb],
* calling this is the first component of the ColorSpace.

This is red property documentation

[caelum19]

Yeah that's the part that seems too implicit to me, as it seems it doesn't actually derive what the red value would be from the actually used model and just returns the first component

[caelum19]

I think we agree the naming could lead to confusion