The Loupe isn't displaying the color values that I set correctly. What's going on?

In version 4.1, the Loupe tool has gained the ability to work with different color spaces using the Working Color Space item in the menubar. Many apps and development environments use color management, but unfortunately there's no standardization on the color space that's used. If you need accuracy when sampling, you'll need to pay attention to which space is being used by the app that's displaying the color. You can find out more about Working Color Spaces in the Loupe section of xScope's Help window.

If you're using a version of xScope prior to 4.1, the Loupe tool displays the color that is actually being shown on screen, not the color that you set in your design. You'll have to take your monitor calibrations into account when selecting colors. For example, while you may know the color of an element in your design is #ffffff, that may not be what your screen is currently displaying. Since xScope reports what color is actually being shown on-screen, there may be a discrepancy between what you set as the color and what shows up in the Loupe.

version 4.7.1 added color space warnings in Loupe:

• A warning icon is placed over the color sample
• A short message is displayed next to the formatted color name
• Invalid color values are displayed with an exclamation mark (!)
• If you sample an on-screen color that can't be displayed correctly in the current color space, an "Out of gamut" warning is displayed
• For example, if you set the Loupe to display hex colors while working in sRGB, and sample a bright red on a Display P3 image
• If you use an output format that is incompatible with the current color space, a "Format unavailable" warning is displayed
• For example, if you use hex colors while working in a Display P3 color space
• Can be disabled in Loupe settings