I believe there is a bug in Android's implementation of Color.colorToHSV(). If you pass it fully desaturated color, it assigns all three HSV components to the same value, that value being the "value" component of the color. While hue is arguably arbitrary in such an instance could be assigned any value at random, saturation should unambiguously be assigned zero in such a case...at least, that's how I see it. I have circumvented this bug in my code by testing the individual bytes of the input color against each other to detect desaturation, and when it occurs, explicitly overwriting the resulting HSV color's saturation component with zero, but this bug, assuming I'm interpreting it correctly as a bug, should be fixed.
BTW, is there an official channel to file such a bug report? I don't see anything jumping out at me when I explore developer.android.com, but maybe I missed it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
