# \[BUG\] Hex Color Gradient Stop Points

**URL:** <https://forum.inductiveautomation.com/t/bug-hex-color-gradient-stop-points/55403>\
**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:** 1\
**Showing post:** 4

<div class="post-metadata">

**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")

</div>

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.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-hex-color-gradient-stop-points/55403)._