Fixed an issue when printing race results – if the race results had already been printed, and the race had cycling enabled, and in the print dialog the option for how to print the details (i.e., information about individual laps) was set to something other than Only displayed, then when the race was changed to without cycling and the results were printed, nothing happened. A JavaScript error occurred but did not display visually – pressing the Confirm Print button had no effect.
Modified the setting for the master Hamachi device URL in the Basic Configuration tab under Uploading. Instead of the https protocol, the http protocol and port 5001 are now used. I found that some internet providers have issues with communication over https when using the Hamachi VPN.
Added the option to set which device, in a race with individual starts, will be used to trigger the start using the start button or laser sensor. Previously, this could only be done on the main (master) device.
When manually entering a chip log, a full recalculation of the racer’s result is now performed. Previously, only a message was sent about the chip entry, but if the chip log had a time that did not match the currently calculated results for that racer, it was not reflected in the results, and a manual recalculation of the entire race was required.
Fixed an introduced bug – in the Measurement detail function, it is possible to set an indeterminate value instead of a specific segment finish time for a racer. If this was set for a racer and a panel displaying events from this race was used, the indeterminate value for that racer would repeatedly appear in the panel when results for other racers changed. The problem was in comparing the indeterminate value and thus deciding where the changes in the results occurred.
Changed the way time differences between the client computer and the RaceMeter device are handled. On pages where races are started, or individual racers are started, or where time from the RaceMeter device is displayed (e.g., results or displayed panels), the possible time difference between the client computer and the RaceMeter device was handled by repeatedly (every minute) querying the RaceMeter time. The difference between the client time and the RaceMeter time was then calculated and used to correct the current client time, for example, when starting races or racers or displaying the time of an ongoing race, etc. Now, upon page start, the RaceMeter time is queried 5 times, and the difference used for time correction on the client is the one from the fastest response.
Adjusted the handling of individual racer starts. Now, after starting a racer or selected racers, the start time is immediately displayed, but grayed out, and an animation appears on the button that triggered the start, indicating that the start time is being saved to the RaceMeter device. If the operation fails – for example, due to a network issue – the button that initiated the start changes to allow resending the already recorded start time. If the operation succeeds, the start times for the given racer(s) are highlighted.
Individual starts. Now, for racers with no individual start time filled in, the empty start time is displayed even on the race start page, and these racers will not disappear from the list (as started racers do) when the Actual state mode is enabled, where the remaining time until the start is displayed for racers (typically used for planned individual starts), and started racers disappear from the list.
Individual starts. Racers can now be started up to 24 hours after the race start. Previously, this was only possible from the race start until 23:59:59 on the same day as the race start time.
Added the ability to start and stop multiple selected races at once. You just need to select multiple races and use the Start or Stop function. A page with the list of selected races and a button to start them all at the same time will be displayed.
New functions available in the context of reports – seconds_to_localized_string, get_boolean_string, and all functions from unit math, date_utils, and core_utils.
