This doesn’t make sense.
First there is no standard thing called “WebHex” colors (best I can tell it’s the name of one of the default palettes in Inkscape, which I’ve never used). There isn’t even really a think called “hex colors”. There are 24-bit RGB colors which can be represented in hex, which is how you specify colors on the web. But they can also be represented in other ways such as rgb(0,102,51) a nice evergreenish color, also rgb(0%,40%,20%). There are 2^24 24-bit colors or about 16.8 million of them and that’s not counting 256 levels of opacity. Colors outside the 24-bit range can be specified with rgb() but let’s ignore that.
Second, there is no canonical order of colors, not surprising since RGB colors occupy a 3-dimensional space. There isn’t even a canonical order of the 216 “web safe” colors that are almost completely irrelevant these days — for example, these pages present the web safe palette in three different orders (https://htmlcolorcodes.com/color-chart/, https://websafecolors.info/color-chart, https://en.wikipedia.org/wiki/Web_colors). Also, since the 216 web safe colors all have names, some sites present them in alphabetical order.
I find it hard to believe that Glowforge would implement an algorithm that only works for the 216 web safe colors or relies on the colors in a particular “WebHex” palette in a particular application.
I could believe one of these:
- It’s random (seems pretty unlikely to me)
- It’s based on colors as first encountered in the file
- It’s sorted by intensity (e.g., R + G + B maybe + A)
- It’s sorted by R, then G, then B (etc.)
Has anyone done a large enough test to know for sure or does anybody from @glowforge want to enlighten us? Thanks.
I believe I’ve seen this too. Given that the Glowforge people are pretty smart and have done a lot of things right, I can’t believe it’s random. Perhaps another variable is head speed? Or material?