IEditorPlugin

Remarks

Two methods, and the second is usually empty. Everything registered through PluginContext is undone for the plugin when it is unloaded, so a plugin that only adds commands, panels and menu entries needs no teardown at all. Deactivate is for what the context cannot know about: a file watcher, a socket, a background thread.

⚠ The constructor runs before Activate and should do nothing. A plugin whose constructor throws is a plugin the loader cannot report against as precisely, and one whose constructor touches the editor is one that ran before its dependencies did.

Methods (2)

• void Activate(PluginContext context)

  Adds everything the plugin contributes.

• void Deactivate()

  Releases what the registration scope does not know about.

Used by (32)

• AssetEditorsModuleVixen.Editor.AssetEditors
• BlockoutModuleVixen.Editor.Blockout
• DeliveryModuleVixen.Editor.App
• DiagnosticsModuleVixen.Editor.Diagnostics
• EditorAddingModuleVixen.Editor.AssetEditors.Tests
• EditorApplicationVixen.Editor.App
• EditorModulesVixen.Editor.Host
• FramerVixen.Editor.App.Tests
• HalfModuleVixen.Editor.App.Tests
• HelpModuleVixen.Editor.App
• HolderVixen.Editor.App.Tests
• LibraryModuleVixen.Editor.App
• LoadedPluginVixen.Editor.Plugin
• LoadingTestsVixen.Editor.Plugin.Tests
• ModuleVixen.Editor.Plugin.Tests
• ModuleVixen.Editor.Plugin.Tests
• ModuleVixen.Editor.Plugin.Tests
• ModuleVixen.Editor.App.Tests
• PlayModuleVixen.Editor.App
• PluginHostVixen.Editor.Plugin
• SceneModuleVixen.Editor.App
• ScriptModuleVixen.Editor.Scripts
• ScriptsModuleVixen.Editor.Scripts
• SourceControlModuleVixen.Editor.App
• TerrainModuleVixen.Editor.Terrain
• TerrainModuleReachTestsVixen.Editor.App.Tests
• TerrainPhysicsModuleVixen.Editor.Terrain.Physics
• TexturingCollectionTestsVixen.Editor.Texturing.Tests
• TexturingModuleVixen.Editor.Texturing
• ThrowerVixen.Editor.App.Tests
• WaterModuleVixen.Editor.Water
• WorkspaceModuleVixen.Editor.App