search

darktable-org / darktable

darktable is an open source photography workflow application and raw developer
https://www.darktable.org
GNU General Public License v3.0
9.88k stars 1.15k forks source link

Move masks with pixel-accuracy (using keys) #15746

Open rekcodocker opened 1 year ago

rekcodocker commented 1 year ago

Is your feature request related to a problem? Please describe. On retouching I often need to place a mask in a perfect position so features in the image line up. For example, straight lines should line up so they don't 'wobble'. The mouse is inaccurate for this work. Often it moves a little too far or it moves a little sideways, when all I need is vertical correction.

Describe the solution you'd like I would like to use keys to move the masks, one pixel at a time. That way I achieve two goals at once: I don't under/overshoot, and I don't move sideways when I need vertical movement or vice-versa.

Alternatives I don't see an alternative way. I am using the mouse but it's not pixel-accurate.

Additional context

This accuracy is needed in the retouch-module only - but masks are generic. It doesn't hurt if it works everywhere.

github-actions[bot] commented 10 months ago

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

rekcodocker commented 6 months ago

To add to this: 1) it would be nice if everything could move with pixel-accuracy. Also the crop window, for example. 2) An addition: In some programs when you hold SHIFT or CONTROL, things move strictly horizontal or vertical, with no motion on the other axis. This helps not to lose alignment.

rekcodocker commented 4 months ago

I would still like this. If it's impossible then close it, but it does not seem (to me)

github-actions[bot] commented 2 months ago

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.