I've implemented that like this:
If the object is rotated, by dragging the node, by a rotation amount (in degrees, for this example), then the actual rotation would be equal to:
For example, if the input rotation is 67°, then the applied rotation would be 67 - 67 % 15 = 67 - 7 = 60.
And that works fine. However, this isn't the default behavior in 99% of the software I've used, but rather, it's freehand rotation, until you press a key (most likely Ctrl), and then the snapping is applied. And currently I don't know how to detect whether Ctrl is pressed or not, so I can't finish this feature on my own (if I figure it out, I will send in a PR).
I've implemented that like this:
If the object is rotated, by dragging the node, by a
rotationamount (in degrees, for this example), then the actual rotation would be equal to:For example, if the input rotation is 67°, then the applied rotation would be 67 - 67 % 15 = 67 - 7 = 60.
And that works fine. However, this isn't the default behavior in 99% of the software I've used, but rather, it's freehand rotation, until you press a key (most likely
Ctrl), and then the snapping is applied. And currently I don't know how to detect whetherCtrlis pressed or not, so I can't finish this feature on my own (if I figure it out, I will send in a PR).