Global / Sandbox.SerializedObject

PropertyFinishEditDelegate

Sandbox.SerializedObject.PropertyFinishEditDelegate

Overview

Declared type and relationship surface; behavioural intent is not inferred from the metadata alone.

Type relationships

Base type

System.MulticastDelegate

Interfaces

—

Declarations owned by this type

• Sandbox.SerializedObject.PropertyFinishEditDelegate..ctor(System.Object,System.IntPtr) constructor
• Sandbox.SerializedObject.PropertyFinishEditDelegate.BeginInvoke(Sandbox.SerializedProperty,System.AsyncCallback,System.Object) method
• Sandbox.SerializedObject.PropertyFinishEditDelegate.EndInvoke(System.IAsyncResult) method
• Sandbox.SerializedObject.PropertyFinishEditDelegate.Invoke(Sandbox.SerializedProperty) method

Inherited members

Direct inherited members are not expanded here because the pinned record does not establish a complete inheritance closure.

Flow

The diagram separates the declared inputs, operation and result. Connections describe the recorded relationship; they do not establish execution order or lifecycle behaviour.

Open this operation in the flow explorer →

Examples

No reviewed code example or workflow covers this declaration. Use the exact declaration and inputs/outputs flow as the available local teaching surface, then run a bounded installed-build probe before relying on behaviour. Open the exact declaration flow.

Constraints and pitfalls

• Execution context: game-or-shared-unknown
• A public declaration is not proof of sandbox allowlisting.
• No compile/runtime verification was run.

Prerequisites and limits

• Resolve the type identity in the pinned release before relying on its declaration.

Still unknown

• Installed-build callability, compile behaviour and runtime effects are not established by this snapshot.
• No indexed implementation-source chunk is linked to this declaration; the entry is declaration-only.

declaration-onlymetadata-only

Evidence and verification

Related workflows

None selected.

Related diagrams

None selected.