InspectorMessage

Remarks

⚠ The values are written down and must not be renumbered. The two ends of this protocol are different processes and, on a device, different builds — an editor talking to a player from last week's install is the ordinary case, not the exceptional one. An enum whose members moved when somebody inserted one in the middle would make that a silent misinterpretation rather than an error.

Fields and properties (9)

• Hello

  Editor → build: who are you, and what version of this protocol do you speak?

• Welcome

  Build → editor: the answer, carrying the build's name and its protocol version.

• RequestTree

  Editor → build: send me the entity tree.

• Entity

  Build → editor: one entity, with its parent and its components.

• TreeComplete

  Build → editor: that is the whole tree.

• SetValue

  Editor → build: set this component member to this value.

• Counter

  Build → editor: a counter's current reading.

• Command

  Editor → build: do the named thing — capture a frame, collect, reload.

• Result

  Build → editor: what happened to the last request.

Used by (4)

• FakeBuildVixen.Editor.Debugger.Tests
• InspectorProtocolVixen.Editor.Debugger
• InspectorProtocolTestsVixen.Editor.Debugger.Tests
• RemoteInspectorClientVixen.Editor.Debugger