# \[BUG\] Hex Color Gradient Stop Points **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [January 26, 2022, 3:16pm UTC](https://forum.inductiveautomation.com/t/bug-hex-color-gradient-stop-points/55403 "2022-01-26T15:16:57Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [January 26, 2022, 3:16pm UTC](https://forum.inductiveautomation.com/t/bug-hex-color-gradient-stop-points/55403/1 "2022-01-26T15:16:57Z")
Editing a gradient for a shape and I have found that I cannot edit the hex color value in the color picker directly. The hex value does update as I change the color on the wheel, select a new color on the palette, or change RGB/HSL values, but I cannot edit it or copy it. I am also not able to type in the RGB/HSL values, but must use the wheel and/or slider. Not able to type in the alpha value either. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 28, 2022, 12:00am UTC](https://forum.inductiveautomation.com/t/bug-hex-color-gradient-stop-points/55403/2 "2022-01-28T00:00:06Z")
Can you take a screenshot of exactly what you mean? You’re talking about this editor, correct? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/5/b5daf250545c221c6a8cc7a7d8fd38adbe0c4a7c.png) I suspect you might be running into a long-standing problem, where the bottom is actually cut off due to some bad math on our part; if you drag the designer window far enough from the bottom/taskbar you should see a plain hex field like this: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/a/ca4c23950e975468d3515fe31172aa1a633021e1.png) ---
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [January 28, 2022, 5:16pm UTC](https://forum.inductiveautomation.com/t/bug-hex-color-gradient-stop-points/55403/3 "2022-01-28T17:16:29Z")
I have run into that issue as well, but that is not the issue I’m having here. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/7/b720e6a6a801855ba80c179a402630b7b20faf1e.png) I’m not able to click into any of the text fields to enter values. I can only use the color picker, the color sliders, or the adjustment wheels. As I’m playing with it more here, it seems to be somewhat intermittent. It looks like when I initially open a window and select a shape that already has a gradient applied and try to edit the gradient, it doesn’t work. But then if I deselect and reselect the shape, it works. So no real issue here, just a couple of extra clicks. Thanks for your help. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 28, 2022, 6:11pm UTC](https://forum.inductiveautomation.com/t/bug-hex-color-gradient-stop-points/55403/4 "2022-01-28T18:11:26Z")
Gotcha. Judging by the aliasing on your screenshot, it looks like you're using the designer on a screen with a partial DPI scale (i.e. 125% or 150%). Historically all DPI scaling has been a problem for Java; it's better now than it was, but still has issues with fractional scale factors. If you're able to, I'd recommend either disabling the scale factor or disabling it for the designer via a JVM argument: > [@Issue with Designer/Vision Client Launchers on Linux with HiDPI displays](https://forum.inductiveautomation.com/t/issue-with-designer-vision-client-launchers-on-linux-with-hidpi-displays/53712/2): > > I think I resolved this myself, I noticed in the log it was still using the 1.5 value that I had given it initially, I removed the .ignition folder and launched again and then added my "jvm.arguments": ["-Dsun.java2d.uiScale=2.0"], And it looks correct now, it seems that not every element in swing respects a decimal scaling value.