In previous versions the cursor resets once the mouse leave the node, which is also not quite right as the cursor should be kept when dragging. I would like to open a PR to fix that. However, I don't know how can I fix it if we can not get when exactly the mouse leave the node.

I think we can reset the cursor on when transform is finished. The PR is very welcome. If with the test, it is another level of awesomeness.

Resetting the cursor is not sufficient, as the cursor may still stay on the cursor when the transformation is finished. We need the accurate hover information for a good implementation, which is why I opened the issue.

Actually I want to fully transform the cursor setting logic:

• Every control node has two types of cursor: hovering and dragging
• dragging cursor overrides the hovering cursor
• Every time we need to update the cursor, find the first node with active cursor that is on the top and apply the cursor. If none, reset the cursor.

With this we can implement a rotator that has grab as its hovering cursor and grabbing as its dragging cursor. When rotating the cursor is always dragging, whether its being hovered or not.

Maybe, but it sounds like an overkill for me.

as the cursor may still stay on the cursor when the transformation is finished

I don't see that is a large issue. We can enable hover back in that case.