JayKayAce
commented
4 months ago An alternative way would be to limit the color pallette in the Icon editor to the websafe colors. This would be less intrusive to the LabVIEW VI Format, until the VI Format supports 24bit Icons.
I have cursed this feature multiple times because I was drawing some iconography for VIs using the TestStand green, which then was compressed into another green, that did not look anything like the amount of work I had put in for finding the right green.
crossrulz
You can go for a long time as an advanced LabVIEW user without realizing that while the LabVIEW Icon Editor is 24-bit, LabVIEW icons are 8-bit (the web-safe colors, to be precise, along with some extra grays). For instance, these gradients:
are crushed into:
And you have no feedback in the Icon Editor that this is about to happen, until you click OK. (Fortunately, the Icon Editor data model is also 24-bit, so you can open it back up to fix any issues that arise.)
The most annoying situation for this sort of thing is when you want to apply a slight tint to white, or perhaps some shade of gray. You're only going to be specifically doing that (and caring about the result) with an area fill. And that's precisely where any color differences will be most notable. Perhaps the worst-case scenario is in the light violets, with significantly more blue than red, in order to maximize the misalignment with the 6x6x6 color cube of the web-safe palette: #f7efff is crushed to white, while the only slightly-darker #f2e5ff goes off in a completely-different-yet-equally-unacceptable direction.
This can also lead to trouble when you want to apply some sort of overlay with a light alpha: at the high transparency settings you tend to want, only some of the pixels will actually be any different.
Ways to potentially solve this: