When any of these occur, the system will queue additional timing events until the system is able to process them. The number of queued times is configurable (In the Timer Settings with values of 5,10,15,20). A warning will be displayed once the threshold approaches. Note: this queue mechanism will not be used or encountered very often since most functions (including background) processes run very quickly. If the warning does pop up, please take appropriate actions. No processes should execute for any persistent times so it is expected you may never see this warning.
Visually, the iterating stop watch buttons, normally iterate for the number of cars on course. If the queue mechanism kicks in, all of the buttons may start to, and you will see 'T-1, T-2',..etc., in the respective Staging rows, for running timers. This indicator will not display more than the configured number of timers. If you have 3 Stop Watches configured, only 3 will be indicated in the staging grid.
Once the 'busy state' is ended, the times will automatically sequence into the staging grid and the appropriate number of running running stop watches will be displayed, along with the 'T-x' timing indicators.
- If the Auto-Save Interval was executed in very short intervals, timing occurred VERY rapidly (seconds apart), and if data entry was occurring at the same time. Hard case to reproduce in normal circumstances
- Movement keys are continually pressed while timing is occurring very rapidly (with a few seconds with multiple timers running).
The solution was to improve and isolate the save processes from other running processes, and thus saving after each car in the staging grid works as expected. This is still not recommended since it will thrash the processor excessively, especially for very large events. Slow machines will see this impact.
Prior Version Release notes:
v5.3x Release Notes (2006)
v5.2x Release Notes (2005)
Copyright © 2007, AXWare Systems, All Rights Reserved.