Hi Miyako, I take the point that the representation of a given RGB value (whatever it may be) will differ depending on the color space and the capabilities of the device that's displaying it. That's why we calibrate our monitors. But I don't see how that's relevant here. I think we're talking about setting and retrieving a mathematical value - whatever happens in the display is based on that value and will go where it may. But at the core that value is what it is.
I looked at the color picker on Mac Sierra and it doesn't offer the 'device' choice when viewing the web safe color panel - which is where the HEX values also appear. I tried changing it to device on the CMYK panel but the results returned by Object get rgb colors still don't agree with the web safe ones. The issue here isn't about what the color looks like (another discussion) but why the selected RGB value differs from the one 4D reports. I would expect a form object that has it's RGB value set on a Mac to have that same RGB value on a Windows machine, for instance, even though I know they will look very different viewed side by side. That's exactly why some of us like to work with specific RGB values - though that's beyond the scope of what we're dealing with here. One place something like this could come up is converting between different color representations. So if RGB colors are stored in CMYK (just for discussion - no idea if that's true) switching between the two could introduce some small variations and that could produce the variances I'm seeing. I suspect 4D doesn't store RGB natively based on the fact it was years before we got the choice of using RGB colors but that's just speculation. This isn't a big deal but I know some users are going to notice it in this particular situation. On Fri, Sep 29, 2017 at 6:17 PM, Keisuke Miyako via 4D_Tech < [email protected]> wrote: > on the color picker panel you should find a cogwheel icon, > which allows you to pick a color space. > > after all, > RGB is not an absolute definition unless you also specify the color space. > > when you use the picker tool, > it will always return the RGB in the generic (NSCalibratedRGBColorSpace) > space, > which is not the same as HTML (sRGB) or device (4D). > > when you open the picker, > the device space is selected by default, so all is fine. > but when you use the picker tool, it switches to generic, > so the RGB representation differs to that used in 4D. > you need to manually switch the space to device, > or use the value returned by the command (which is converted to device). > > > 2017/09/30 0:50、Kirk Brooks via 4D_Tech <[email protected]> のメール： > > Anyone else seen this? Any ideas? Worth filing a bug report? > > This is v16.2 (32 bit) on macos Sierra. > > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
