Repository navigation
GTFO
Pre-release
Pre-release
·
14 commits
to 2.0.2
since this release
Pika 2.0.2-beta1 makes picked colours match their source. Colours now read in sRGB by default, so a hex you pick matches the one in your CSS or Figma, and a new Colors don't match? window works out which colour space a value came from when they differ. Updates now show in a bar inside Pika instead of separate windows, and Help explains the basics, from contrast to colour spaces.
As always, cheers for the support, and if you have any issues or feedback, let me know on GitHub.
New features
- Colors don't match?: pick a colour, enter the value you expected in any format (hex, RGB, HSL, HSB, OpenGL, Lab or OKLCH), and Pika shows which colour space reads it back and offers to switch to it. It's in the Help menu and in Settings.
- Inline updates: a slim bar in the window and the popover offers Update or Ignore, shows download progress, then Restart to update, with What's new linking to the right changelog entry.
- Help basics: short explanations of foreground and background, why contrast matters, WCAG and APCA, the pickers, editing values and colour spaces (#282).
Updates and bug fixes
- sRGB by default: picked hex values now match CSS, Figma and most design tools. If you'd chosen your display's own profile, it becomes Match display, which follows the display you pick on. Your history keeps its colours.
- Colour space setting: now its own section in Settings, with a short note on what each choice is for.
- Display P3 copies: in Display P3, CSS hex and RGB copy as
color(display-p3 …), because browsers read a plain hex as sRGB. The copy example in Settings shows what you'll get. - Pro picker accuracy: on displays in HDR mode, picks no longer read about 10% dark (macOS 15 and later), and colours at the edge of your display's range read the same as the system picker.
- History: keeps its colours when you change colour space, and clearing it keeps the colours you're working with.