EditorProperty built in subclass signals don't seem to bind in gdscript.

dotted

In gd-script I added an editor plugin with the idea of hooking into property changes made by the inspector in order to take an action on the changes as a 'design time' action of the plugin.

I traversed the scene tree of the inspector instance and found the relevant elements (EditorPropertyFloat and Enum) and connected to them. However, no property_changed signal propagated back to the editor plugin script.

Indeed _bind_methods() for the above classes do not bind list any signals. (I've gotten around this by adding a signal to the edited class' setters)

Would it be harmful to add that binding to the property editors themselves? Seems like it would be useful for plugins in general.

--edit--

the parent class has the signal but it does not propagate (and of course adding ADD_SIGNAL results in a duplicate).

So the question becomes why is the signal not propagating and how to find out why.

dotted

On further poking around, if plugin's node type is added to the scene, inspector signaling works

so the following happens: load project that has plugin targeted node in a scene: signals attached upon node selection in the editor do not work add a node: signals work

this might suggest that the inspector editing the node at first is not the one operating on the node and that the actual inspector is created after on _selection_changed