Event Handler not Unsubscribing

[Unsuitable]

Hello,

Upon refreshing the chart F5, the indicator is supposed to unsub the event, and when it loads back in, re-subscribe. For some reason, it's not unsubbing so it keeps duplicating the event handler. I tried using Dispatcher, but IIRC that has to do with custom buttons which this indicator does not have. Also tried to print "Unsubbing" to confirm it unsubbed but that print never occurs. Doesn't the indicator go to the temporary state of Terminated when refreshing the chart thus it should run through that bit of code?

else if (State == State.Historical)
{
  if (ChartControl != null )
  {
    lock (Account.All)
    userAccount = Account.All.FirstOrDefault(a => a.Name == AccountName);

    count = 0;
    intrumentName = InstrumentInput.FullName;

    ChartControl.Dispatcher.InvokeAsync((Action)(() => {
      InitialOrderTransfer(); --> userAccount.ExecutionUpdate += OnExecutionUpdate;
    }));
  }
else if (State == State.Terminated)
{
  if (ChartControl == null)
    return;
  // Unsubscribe to events
  ChartControl.Dispatcher.InvokeAsync((() =>
  {
    userAccount.ExecutionUpdate -= OnExecutionUpdate;
    Print("Unsubing");
  }));
}

[NinjaTrader_Jim]

Hello Unsuitable,

Thanks for your post.

You may wish to close the platform and restart to ensure everything is cleared and there are not any leftover event handlers that are subscribed.

What you have set up looks fine, but the dispatcher is not necessary. I have an example attached that demonstrates subscribing to various account level events.

Let us know if you experience any issues with the example or setting up in the same fashion after restarting the platform.

We look forward to assisting.

[Unsuitable]

Hello Jim,

Turns out the terminated state was within the state.DataLoaded if statement. I notice the code uses DataLoaded while I use Historical, does it matter?

[NinjaTrader_Jim]

Hello Unsuitable,

DataLoaded and Historical are good states for subscribing events and resource creation. It doesn't really matter between the two of these. State.Configure would be less advised, especially for strategies since State.Configure would be processed when clicking OK in a Strategies dialog, without enabling the strategy.