I am having an issue with the TimeBar throwing an exception. I will attach a screen shot of the error. I have traced it down in the source and it seems to be a race condition when you update the TimeBar multiple times in a short period of time.
Here is the code that is throwing the exception, it is line 10 in LabelMapper.cs.
MapLabels(IEnumerable<PeriodSpan> periods, Func<DateTime,
So whats happening is, by the time this code is run, periods is null.
The only place this is being called is on line 351 in ViewManager.cs. Before it calls it checks for null but then it invokes the call on the dispatcher. I think the problem is the value is changing before the function gets run. It seems like this can happen if you make multiple updates in a row.
Action(() => LabelMapper.MapLabels(intervalDescriptor.Periods, bestlabelFormatter)));
I am using version 2013.1.403.1050.