This addresses an issue particularly with nDisplay nodes where the client can receive
the Sequencer state sync event before it has finished processing transactions from
the activity stream. If a sequence open on another client was created or saved by a
transaction in that stream, the nDisplay node may not be ready to open or sync a
Sequencer/player for it until its workspace is finalized.
In addition, a Sequencer/player is opened for any sequence not already open on the
client when the Sequencer state sync event is received. Since the client may have
been launched some time after other clients, it would not have received Sequencer
open events that occurred before it was launched.
This also includes some minor cleanup to event handling and delegate registration and
unregistration, as well as a few small corrections to some docstrings.
#jira UE-144128
#rb jason.walter
#preflight 623511e448746817f140bec1
[CL 19454582 by matt johnson in ue5-main branch]
- Master will now send its settings to the cluster so all nodes use the same setup
#jira UEENT-3208
#rb francis.hurteau
[CL 10465755 by Simon Therriault in Dev-VirtualProduction branch]
#jira UE-79947
#rb Patrick.Boutot
#lockdown cristina.riveron
#ROBOMERGE-SOURCE: CL 8573014 in //UE4/Release-4.23/...
#ROBOMERGE-BOT: RELEASE (Release-4.23 -> Main) (v407-8568993)
[CL 8573015 by francis hurteau in Main branch]
#jira none
#rb none
#ROBOMERGE-SOURCE: CL 7710407 in //UE4/Release-4.23/...
#ROBOMERGE-BOT: RELEASE (Release-4.23 -> Main) (v385-7708028)
[CL 7710410 by francis hurteau in Main branch]
Merged from CL 7437705, CL 7438413
#jira UE-78280
#rb none
#ROBOMERGE-SOURCE: CL 7708214 in //UE4/Release-4.23/...
#ROBOMERGE-BOT: RELEASE (Release-4.23 -> Main) (v385-7708028)
[CL 7708216 by francis hurteau in Main branch]
