Tomasz Chabora

It's emitted only for the main inspector object. > In GDScript "addon" plugins, you can't have more than one EditorPlugin in your cfg. IIRC there is a proposal for more...

I did a quick patch with 2 changes: [0001-makeshift-patch.patch](https://github.com/godotengine/godot/files/13693548/0001-makeshift-patch.patch) - makes sure that `handles()` does not return true if something is already edited - prevents toggling visibility in quick succession...

Can you check if this patch fixes your issue with `inspector_only`? [patch.txt](https://github.com/godotengine/godot/files/13902085/patch.txt) Though probably more changes to handle sub-resources. The limitation of one object per plugin/context can't be lifted, because...

> (which is good for me, but I don't know if that's by design in Godot or I'm accidentally exploiting a bug). This is likely result of the editing context...

I tested the graph in the newest version. Clicking a graph node will open it in the inspector, with no error printed. Not sure what's the problem. The Terrain button...

When you click GraphNode, it will be edited in the inspector. Any plugin that uses inspector will lose its editing context and receive `edit(null)`. If you want to keep graph...

These two methods are called together. At least in the case that affects your plugin. Also the API is not exposed, because it was added to fix an internal editor...

Well that error appears when you try to edit multiple objects by the same plugin within the same editor context, which is very likely to happen when your plugin handles...

Can't reproduce. Can you make a minimal reproduction project?

This seems a bit confusing, so maybe something can be improved here.