Team timer resets to previous game end on split button click

[MLSTRM]

Click split button: splitClick(): updateSplits(): TimerLabel.Text = current (resolved time span from teamSplits[splitNum]-teamGameEnd[game])

Next timer tick: updateTimerEvent(): teamSplits[splitNum] = current updateSplits() TimerLabel.Text = current (resolved in the same way)

time to resolve hasn't been updated immediately after we move on so it doesn't exist - then the resolved timeSpan flattens out to -1*(previous game time). - since we don't show the sign it doesn't appear that way, so it jumps "back" to the previous game time until the next timer update.

Possible solutions:

• Don't run updateSplits as part of splitClick()
• Get current timer on split click and force an update
• Move things along behind the scenes but just don't visually update until the timer cycle

[MLSTRM]

Cause confirmed as theorised above, shows much more prevalently if over an hour difference since the first 2 digits swap over.

[MLSTRM]

Appears to happen to game end times also.

[MLSTRM]

Fixed under bfc8df1