public static class PlaySystemOrderPuts the play-mode contributions in an order their declarations justify.
Remarks
⚠ Registration order is the tie-break and the default, deliberately. A sort that reordered contributions with nothing to say about each other would make the frame depend on a hash order and turn every existing comment about sequence into a lie. With no attributes anywhere this returns exactly what it was given, which is what every contribution in the tree got before the attributes existed.
⚠ It cannot move the snapshot. PlayModeController.Play captures the world and *then* calls Contribute; this runs inside that call, so everything a contribution creates is still outside the snapshot and still goes away with a Stop. An ordering mechanism that ran earlier — at registration, say — would be the one change that could move that boundary, which is why the sort is here and not in IEditorRegistry.Add.
Methods (2)
public static IReadOnlyList<T> Sort<T>(IReadOnlyList<T> contributions, out IReadOnlyList<string> notes) where T : classSorts contributions so that a provider attaches before anything that asked for it.
public static void Verify(object contribution, PlaySession session, IList<string> notes)Names what a contribution declared it provides and did not.
Used by (1)
- PlayModeControllerVixen.Editor.SceneView