This adds the ability for SplitsBrowser to load files containing relay results.
Notes;
Team results are only supported for IOF XML formats, both versions 2.0.3 and 3.0.
Team sizes must be at least 2. No upper limit is imposed.
Team results are only supported if all variations (gaffles) of each leg have the same number of controls. (It's not clear how to plot a graph otherwise, or whether such a graph would make sense.)
Teams are expected to be of the same size within a class, but they do not have to be the same across different classes. (E.g. you could have one class with teams of three and another class with teams of four.) Results files can also contain a combination of team classes and individual classes.
Within a team, team members other than the first are expected to start at the same time as the previous runner finishes.
Controls within legs are expected to vary between teams (e.g. due to gaffling). Graphs and the results table therefore do not show control codes, and the popup that shows you nearby runners at controls does not appear.
A different pair of background colours are used for alternate legs of a team event.
There is a UI control to switch between legs, allowing the user to focus on one specific leg or view all legs.
Viewing an individual leg is intended to be a zoomed-in view of that leg of the race. Competitors will still be shown in the order that the team finished, not the order that competitor finished among other competitors in that leg.
Viewing an individual leg in the results table will allow you to see that person's times.
This adds the ability for SplitsBrowser to load files containing relay results.
Notes;