For example, old PB3 used to have it's color setup in RGB meaning that you could specify RGB values alas PB4 just has it's simple color picker. I was wondering if anyone might know what code PB4 is using as I couldn't really figure that part out.
And if you know, whats the proper way to convert it from RGB/hex to PB4 standards?
Through Hex, with PB4 (using the above addon recommended by Seerah). And with PB3 compared to PB4. Am I inserting the values correctly? Currently I'm using a manually picked/added color to reassemble the original one (see target frame) or well at least I tried..
It's entirely possible that the Rock framework used by PB3 is "translating" colors entered through its inline color sliders config widget differently from how the Blizzard color picker (as extended by EnhancedCoulourPicker) is "translating" the colors sent back to PB4.
But to be honest, unless one of those is doing transformations in an extremely wrong way (which I doubt), the difference should not be perceptible, unless they are large areas of color side-by-side.
There is a good reason why color matching in the real world doesn't rely solely on inputted numbers to confirm a visual match. Even in supposedly "device independent" color spaces, the transformations that are performed to arrive at a displayed or printed or painted color can be done slightly differently and at different levels of precision. With enough rounding in various steps, the resulting colors can be visually distinct from each other. (Compare Photoshop's wildly different conversions when quantizing color data from 16-bit to 8-bit versus the same integer data going from 8-bit to 16-bit.)
Anyways, I'm back on and I finally figured out that the embedded color picker is somehow broken, because even Photoshop's version (which is also used by most font/sub/text editing tools, see aegisub for example) works without fault. So If I could somehow use DogTag's "translation" method with the code handling... (yes it handles hex I figured)
For example, I insert the value w/ code: Color('26466D') and I get the result I've been trying to get so far. So why is Blizzard's tool so buggy when it comes to picking colors? Could it be that EnhancedColourPicker addon is somehow writing results incorrectly to how blizzards handles it? Anyways I'm no expert when it comes to lua nor am gonna try to blame the author(s) if this or that isn't properly working, so have a nice day and thanks for all help so far.
Could you give an example of a specific color you're trying to use, along with a screenshot showing the difference between that color as shown by PitBull3 and the color as shown by PitBull4? I've never encountered any such error in color entry in WoW...