From 15ee292664c8487da9adaa8371b105b522d111b6 Mon Sep 17 00:00:00 2001
From: Markus Sauermann <6299227+Sauermann@users.noreply.github.com>
Date: Mon, 5 Jun 2023 10:04:08 +0200
Subject: [PATCH] Don't update mouse cursor state on child order changed

Partially Revert "Create a virtual mouse move event after moving child nodes"
This reverts parts of commit ce10ca69794900896a4162efc823386ce5bde3dd.

The problem was that the the mouse-move event interacted in unexpected ways.
---
 scene/main/node.cpp | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/scene/main/node.cpp b/scene/main/node.cpp
index 264a152392e..ad7e445b5cb 100644
--- a/scene/main/node.cpp
+++ b/scene/main/node.cpp
@@ -216,14 +216,6 @@ void Node::_notification(int p_notification) {
 				memdelete(child);
 			}
 		} break;
-
-		case NOTIFICATION_CHILD_ORDER_CHANGED: {
-			// The order, in which canvas items are drawn gets rearranged.
-			// This makes it necessary to update mouse cursor and send according mouse_enter/mouse_exit signals for Control nodes.
-			if (get_viewport()) {
-				get_viewport()->update_mouse_cursor_state();
-			}
-		} break;
 	}
 }