-
-
Notifications
You must be signed in to change notification settings - Fork 54
-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Richer color picker experience #22
Comments
Yup, all of these are good suggestions and already planned. However, it requires making the color loupe from scratch, which is quite a lot of work. Related issue: #16 Note to self: Should be possible to use the arrow keys to move the color loupe via keyboard arrows 1px at a time. Also, shift key + arrow to move in increments of 10px. |
Tip: You can press Space to show the RGB color in the picker. It's not configurable though. |
Nice! That improves the tool a lot for me. |
Another vote for the close-up mode. This feature is vital for those who use a graphic tablet like me. The reason is that a click with a tablet is most of the time a short stroke, which means that with a tablet it's really difficult to "pick a pixel," so to say. So the ability to slow down the mouse cursor is indispensable. |
I've just moved away from using ColorSnapper2, and I think this app should implement some of the extra features that ColorSnapper2 provides for its color picker, as they improve the user experience significantly.
Features
ctrl
on ColorSnapper2 the loupe sort of zooms in into the screen, showing a bigger loupe, much bigger pixels, a pixels grid and importantly also the loupe moves more slowly. Those are pretty useful features IMO as picking a precise pixel currently with the app is not a smooth as it should be, it's just too easy to move the cursor accidentally to a neighbor pixel and I find that I physically get closer to the screen just to have a better view of the pixels.Demo
Screen.Recording.2021-11-11.at.11.50.54.mov
The text was updated successfully, but these errors were encountered: