Nice, LGTM. You can also check how it feels to have the cursor change to a hand before you start to drag, on drag-area hover.

@Julian Eisel (Severin) nice improvement. Just one issue so far as I see. Based on the text cursor behavior I feel the same behavior should be used for the drag widgets. In other words, the cursor should change on both hover and click+drag. Right now it only shows the hand on click+drag.

Beyond providing more context to the user this will also make the behavior more consistent.

Dont think text cursor over buttons is great.

Typically when you have an editable text area, clicking and dragging will select the text, where as this allows dragging too at the moment, the text cursor is set once you click on it, so think its OK as-is.

Using grab hand is fine for panels though.

Typically when you have an editable text area, clicking and dragging will select the text, where as this allows dragging too at the moment, the text cursor is set once you click on it, so think its OK as-is.

Yeah, that makes sense. Blender's number inputs are a bit more upgraded than in other software. But we can have the text cursor over text field, like the object's name.

Looks good. Where is this hand cursor from? Was it already used for something in Blender?

Hehe, the cursor was already included in Blender, it just wasn't used afaik. It might be useful to add an open-hand-cursor which could be used for hovering. The closed-hand-cursor could be used while dragging. We might also add a hand-with-raised-index-finger-cursor, which could be shown while hovering operator buttons, menus, checkboxes, etc.

Nice!

I don't think Blender has such a thing as open-hand/closed-hand? At least looking at the code doesn't seem to.

EnumPropertyItem window_cursor_items[] = {
	{CURSOR_STD, "DEFAULT", 0, "Default", ""},
	{CURSOR_NONE, "NONE", 0, "None", ""},
	{CURSOR_WAIT, "WAIT", 0, "Wait", ""},
	{CURSOR_EDIT, "CROSSHAIR", 0, "Crosshair", ""},
	{CURSOR_X_MOVE, "MOVE_X", 0, "Move-X", ""},
	{CURSOR_Y_MOVE, "MOVE_Y", 0, "Move-Y", ""},

	{BC_KNIFECURSOR, "KNIFE", 0, "Knife", ""},
	{BC_TEXTEDITCURSOR, "TEXT", 0, "Text", ""},
	{BC_PAINTBRUSHCURSOR, "PAINT_BRUSH", 0, "Paint Brush", ""},
	{BC_HANDCURSOR, "HAND", 0, "Hand", ""},
	{BC_EW_SCROLLCURSOR, "SCROLL_X", 0, "Scroll-X", ""},
	{BC_NS_SCROLLCURSOR, "SCROLL_Y", 0, "Scroll-Y", ""},
	{BC_NSEW_SCROLLCURSOR, "SCROLL_XY", 0, "Scroll-XY", ""},
	{BC_EYEDROPPER_CURSOR, "EYEDROPPER", 0, "Eyedropper", ""},
	{0, NULL, 0, NULL, NULL}
};

I agree with only having Text cursor for mouse hover on text fields. Even though it doesn't behave exactly like in other apps where you can directly select text, is a welcome hint (unless the Text field is not editable, like for linked datablocks).

Besides that, looks fine to me!

No it doesn't have an open-hand/index-finger-hand, but looking at the code, they should be easy to add (we even have a make_cursor_gui in the developer tools :P ). So, if you agree, I'll include them and play a bit with them?!
I forgot to add the not editable case. But I'll add that soon. Thx for the reminder :)

Great!

How would you go about adding them? I guess you can just point to the local system ones. Don't need to actually design them, right?

The easiest way would be to take and modify the current closed hand cursor, i guess.

@Julian Eisel (Severin) If you need a GUI element, let me know.

Popups are another case where we need the hand/grab cursor (since they can now be moved around).

Examples include the "Save Over?", or the F6 popup:

Cheers!

Hey, here are the hand cursors that @Julian Eisel (Severin) asked for. They are 16x16 - If they pass initial review, I will also provide 32x32.