|
Version 23.40 - August 2023 |
|
New Features |
|
|
Enhancements |
|
| Network Services |
Networking framework has been improved substantially to manage conditions where Network Clients are started late into the event and lots of data has been managed. Note: saving data on the timing server, refreshes the amount of data in the network cache for new Network Clients. This provides a very quick synchronization when new Clients connect. Without the Save, all pending networked data is cached and send to any new Network Client during the Synchronization - the amount of data will dictate how long it will take the new Network Client to receive and process all data. This also includes when switching a Network Client to another Network Client (ex: from Registration Client to Announcer Client). Hint: Save data on the Timing Server from time to time.
|
| Network - Registration Clients | Since Registration Clients do no interact with the Staging Grid, the splitter window is now maximized on the screen. |
|
Fixes |
|
| Network Services | Prior to this version - it was possible for networking data on a client to be consumed by a client, then if that client was shut-down, killed or restarted, there was a potential for some data to be skipped after a re-synchronization. As of this version, improved cache management eliminates that potential and forces data to the Q cache, then for consumed. |
| Registration - Staging Windows - splitter | The Splitter location was not being reset if it was changed. This forces the user to resize based on their preferences each time an event is loaded. |
|
Re-Class Registration Entry |
If a Member # was entered that already existed and you exited the Edit Entry dialog, it would inadvertently pop up an error that would not clear. |
|
Edit/Copy + Insert Registrations and Membership entries with Bar Codes |
When Bar Code values = Membership Numbers, the Memberships Numbers where not always unique across all entries. |
|
Version 23.30 - July 2023 |
|
New Features |
|
|
Enhancements |
|
| NCCC Staging Grid |
Since NCCC does not use Pax based results, forced the Pax based columns to
be hidden from view in the Staging Grid automatically. Prior versions would show them but could be hidden manually. |
| Staging Consolidation | When data is recovered, it is possible for the last line of the recover to be ignored. Usually that is a blank line but in some cases it may not be. As such it may be ignored by the Re-Consolidation process. This is usually evident if the last row is missing a Run Number associated with that driver. |
|
Edit/Copy + Insert Registrations and Membership entries with Bar Codes |
Behavior for bar code value generation has been changed when bar
code value = Member #'s. In order to reduce duplicates and conflicts for the membership numbers and bar codes, when duplicates are encountered, the membership # and bar code will be cleared and must be re-entered and unique. This also affects editing entries in-place in the Registration Grid and Membership Grid respectively. Hint: If the same driver has multiple vehicles (thus entries) we recommend added _2, _3 etc. to the end of a normal membership number to force unique Membership #'s and thus provide a unique bar code for all entries. Non-Membership # barcodes are not affected (class + number, number or unique membership values across all entries). |
| Networking - Clients |
The Networking Clients managed disconnecting and reconnecting by popping up
dialog boxes for user interaction when necessary. The intend was to
specifically indicate the Networking status. However in order to make
the interactions quiet, actions are now logged in the Network Status log
and the Network indicator is used to indicate the health of the connection.
A dialog is no longer introduced and you are only required to click on the
Timing Server button to disconnect or reconnect as necessary. If Networking/Auto-connect is active, reconnections are tried continuously until it connects or the user cancels the auto-connect, or closes the event. This includes updated connection management for AXWareDM. Once connected, dropped connections are managed automatically. |
| Networking Cleanup | During Networking shutdown, cleaned up cache management messages in the Network Status Log. |
| AXWareDM |
The penalty manager was updated to provide car color and Notes field from
the Timing Server. Removed redundant/repeated data exchanges that occur depending on how the penalties were being entered in AXWareDM. |
|
Fixes |
|
| Class Definitions | If All classes are deleted, Save is ignored (since the grid was not edited). Now if any rows are delete, or all rows are deleted, the Save and SaveAs function as expected. |
| Export Tab Delimited Results |
Update the target folder to be the data folder - prior to this the
announcer folder was used inadvertently. NOTE: we do not recommend exporting results that are to be tweaked by 3rd party software as this is no longer an official result set. |
| Check For Update | The Check for Update has been out of commission for some time due to a parsing issue with the License. We were not aware of this condition until now. The Check for Updates worked as expected, however when selecting to download the license, base or update versions did not work properly and resulted in 404 HTTP error. |
| Bar Code Scanning | Some Scanning Setup options were not being saved. |
| Export Registrations to Membership |
When the Export Dialog is first loaded the Update flag was set ON even for
existing matching drivers between Registrations and Membership Data.
Now the Update Base Entry or Export Extended Data Columns must be checked for the table to automatically check the Update for matching drivers, respective to the Skip or Modify settings. Note: to auto-select entries, select the criteria and press the Refresh Button. That will automatically re-display the table with the Update check box properly selected based on Skip and Modify settings. You can override any entry as necessary. |
| Re-classing Registration Entries - screen refresh | Following a Re-Class in the Registration Grid may show a paint problem and display incorrect vehicles when scrolling up and down via arrow keys. The screen was lacking a re-paint after re-positioning on the newly re-classed entry. |
|
Version 23.20 - Mar 2023 |
|
New Features |
|
| COM Ports |
In order to support 'strange' device name registrations, a small update to
the PORT lookup was necessary. This affects newer Prolific USB-RS232
adaptors (which we do not recommend) and fixes a lookup issue for their
port name/assignments. Prior versions of AXWareTS would allow the selection of a port but failed to assign the port number affectively resulting in COM port errors. |
|
Enhancements |
|
|
ORM Upload Raw Timing |
For File/AXWare ORM/Upload Results/Raw Timing Data
the process may not finish for large events.
Usually the results were posted but the history of the runs may be cut
short. In ORM under Club Results/Results link the history may be incomplete and statistics for the event may not be 100% updated respectively. This version manages larger data sets and lets the server process complete. Prior to this, the History Link and statistics for the event may not be completed. The upload and processing may vary in time depending on the number of entries and number of runs recorded. Work around: Execute the Import from the Admin Controls/Events Page in ORM and select the export files from the event explicitly. This requires generating the export files first, them using Import like to process those files. |
|
Fixes |
|
| Time Slips | Notes field was not being printed when selected for a customized Time Slip. |
|
Version 23.10 - Jan 2023 |
|
New Features |
|
| Framework update | Maintenance Release for 2023. |
| Class Definitions |
2023 SCCA Class definition updates - including pax factors 2023 NCCC based on 2022 class definitions. |