AssetEditorsModule

Remarks

Four documents, four hooks, one place. A proxy shape set needs the rig it hangs off, a move set needs the sets it overlays, a clip needs the scene it was marked up against, and a harness plan needs everything it names by path. Each of them deliberately refuses to go looking — a document that knew how a project is laid out would be a document no test could open — so each declares the shape of the answer and somebody with a project supplies it. This module is that somebody.

⚠ The panels are inert without it, which is what makes this the last mile rather than a nicety. Unbound, the shape viewport draws nothing, Run says it has no project and Propose Contacts says it has no scene — all three honest, all three useless.

⚠ It was a line in the editor's application, and that is the finding. Doc 36 § F2: binding a freshly-opened document to the project it belongs to was EditorApplication.Bound, which meant a second feature with resolvers would have been a second line in a class that already had too many. `AssetEditorRegistry.Opened` is the seam that replaces it — and it is on the registry rather than on the project, because EditorProject.Register runs from a document's base constructor and would hand a subscriber a half-built one.

Fields and properties (2)

• public const string ModuleId

  What the host activates it under, and what a plugin depending on it names.

• public const string ModuleName

  What a plugin-management panel calls it.

Methods (1)

• public void Activate(PluginContext context)

  Adds everything the plugin contributes.

Used by (1)

• EditorModulesVixen.Editor.Host