Skip to content

Lifecycle

Purpose

Owns editor-window lifecycle coordination systems used by Snap Studio Pro.

This territory handles editor reload behaviour, window auto-closing, and layout-default initialization workflows.

Owns

  • Window auto-close behaviour
  • Assembly reload handling
  • Play-mode transition handling
  • Layout default loading
  • Editor lifecycle coordination

Does NOT Own

  • Workflow orchestration
  • Rendering implementation
  • Preview lifecycle ownership
  • Export execution
  • Feature-domain behaviour

Allowed Dependencies

Lifecycle may depend on:

  • Unity Editor lifecycle APIs
  • Diagnostics/logging
  • Lightweight layout/default systems

Lifecycle should avoid depending on:

  • rendering systems
  • preview systems
  • export systems
  • feature orchestration systems

Notes

Lifecycle systems exist to keep the editor shell stable during: - assembly reloads - play mode transitions - editor restarts

These systems intentionally own editor-window lifecycle safety behaviour rather than scattering it across the main editor window.

Future Candidates

  • Keep lifecycle coordination isolated and conservative.
  • Avoid moving feature workflow behaviour into lifecycle systems.
  • Maintain explicit editor-window cleanup ownership.