Alternative controls for gradient masks

[asdkant]

Is your feature request related to a problem? Please describe.

I've recently had to work on some star wars cosplay photos I took, and I ended up coloring the lightsabers with colorize masked with two intersected gradients (this two times, one for the colored glow at the sides of the blade and one for the whiter center).

The edit was doable, but... placing the gradients was a bit of a pain. Especially if I have a very long blade that spans a large part of the image so that I can't zoom in on both ends.

I can see how this same issue can happen with horizons, or other straight lines in pictures that sometimes can't be easily masked with parametric masks (my go-to way of masking modules for stuff that'd be a pain to draw)

Describe the solution you'd like

An alternative way to control gradients, based on having two control points plus a "reverse" action instead of one and a directional arrow.

Alternatives

Being able to modify the angle of the gradient masks with a slider widget, like you have in the graduated density module, would help a bit. Moving things with the cursor can be unwieldy if you're trying to do fine work, so having sliders or some other way to fine-tune things is a big help. But it still doesn't solve the "two ends of the line can't be zoomed in at the same time" issue.

[dterrahe]

Being able to modify the angle of the gradient masks with a slider widget, like you have in the graduated density module, would help a bit.

There is a slider for the rotation in the "properties" collapsible section of the mask manager. Also #14157

[ralfbrown]

Also, when placing the gradient initially, you can drag the mouse to get two control points (the positions at start and end of drag).

[github-actions]

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.

[github-actions]

This issue was closed because it has been inactive for 300 days since being marked as stale. Please check if the newest release or nightly build has it fixed. Please, create a new issue if the issue is not fixed.