I've noticed that when I use the color picker in BBEdit and use the magnifying glass to grab a color from the screen, the color that it inserts into my document is different from what I've grabbed. I think this is because BBEdit is converting the color from its "literal" value to its "calibrated" value based on the ColorSync profile for my monitor. For example, let's say I have a web page preview window open, and there's a background color I want to copy into another document. The CSS for the web page specifies that color as hex value #242226, but when I use the color picker magnifying glass and insert the color back into BBEdit, it changes it to #1B191C, which is what OS X has decided is the "Device RGB" value.
I should say that this isn't specific to BBEdit, but it does make it harder to keep color consistent. I have one color picker called Hex Color Picker <http://wafflesoftware.net/hexpicker/> which has an option called "Don't generate calibrated colors". With this enabled, the hex value that appears in the color picker is consistent with the CSS for the web page (which is good!), but if I simply accept that value, BBEdit still inserts the wrong one. The only way to get around this is to manually copy the hex numbers from the color picker and paste them into BBEdit, but that's a lot slower than just plucking with the magnifying glass. Is there any way around this? Some hidden preference I'm missing? While I'm on the topic, is there any way to have BBEdit insert color values into CSS in the decimal rgb(r, g, b) format? Better still, I'd love to be able to insert colors using the CSS3 rgba notation: rgba(r, g, b, a) where a is the alpha (transparency) value. -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group.
