-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Holo Color Picker fails to give exact color #31
Comments
If you want to return the exact same color you send, you need to have both
This is because HSV colors consist of these three values. I'm not sure what is @LarsWerkman Very nice design, thank you for putting it on maven central. |
Oh. I translated your colors to hex ( |
@mg6maciej yes that is exactly what is happening. the reason for this is when setting a color in the color picker you have to translate this to a radial value for the colorpicker and a value for the bars. |
I'm not sure this should be closed without resolving. When using It's even more important if you use Relevant code:
I have made a quick fix for this case: mg6maciej@6f8dd87. It's not a complete solution, but works well with saturation + value bars. Ideally |
here is my version of the quickfix from mg6maciej https://github.com/mreinerth/HoloColorPicker/compare/hotfix/SetColor_GetColor_consistency. Works perfect for me to fix the problem that u dont get the right color u set before. I use the Colorpicker in a dialog and have additionally a gridview under the picker and bars with predefined colors where a click set the color of the picker and the ok button of the dialog save the color (obtained by getColor) to use as a draw color. When i open the Dialog with the picker i set the oldCentercolor and the color to my saved color value. |
Hi, I have issue with this holo color picker, I set the old color with int -6697984 but when I get the color from the picker, it returns -6632448. I have added saturation, value, opacity and even sv bar, but it still does not give exact color int as I set before.
Do you know what is the problem and what probably could be the solution?
The text was updated successfully, but these errors were encountered: