Add position_changed signal for Node2D and Node3D

[CsloudX]

Describe the project you are working on

NO-GAME App

Describe the problem or limitation you are having in your project

I want listen some node's position but I don't want add script for this nodes.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Add position_changed or transform_changed signal for Node2D and Node3D

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

/

If this enhancement will not be used often, can it be worked around with a few lines of script?

I must add script for all this nodes. I'm lazy.

Is there a reason why this should be core and not an add-on in the asset library?

No, It's core.

[Calinou]

I must add script for all this nodes. I'm lazy.

This is not a sufficient reason for a feature to be added to core.

[CsloudX]

I must add script for all this nodes. I'm lazy.

This is not a sufficient reason for a feature to be added to core.

^V^, I think position_changed was used often, IMO, add the signal make GODOT better.

[Mickeon]

Signals are typically decently fast, but I'm honestly concerned about every existing Node2D and Node3D potentially emitting this signal every frame, even if not connected to anything. If a parent Node2D's position changes, the signal would have to propagate down the tree, and every child Node2D would also subsequently emit the signal.

[KoBeWi]

We have NOTIFICATION_TRANSFORM_CHANGED, which needs to be explicitly enabled with set_notify_transform(). Maaybe the signal could be emitted together with that notification.

It's not very common though, not sure why would you need it as frequently as you claim.

[smix8]

Transform changed is already disabled by default because it wreaks havoc on performance if enabled on to many nodes but it costs nearly nothing and is very fast compared to signals. Sending by default a signal for every slightest transform change is the next best thing for crashing the Engine with the MessageQueue.

[Mickeon]

What's the use-case? What's the actual necessity to implement this natively without using a script (which is possible to accomplish currently)?

[YuriSizov]

I want listen some node's position but I don't want add script for this nodes.

As Calinou stated, this is not a valid justification for a proposal. And as mentioned by others, performance ramifications is something that must be investigated before discussing this feature. So closing as not a valid proposal. Please use the Discussions section or our social and community platforms to look for a solution that works for you. Then a proper proposal may be born, if there is a good legitimate need for an improvement.