Skip to main content

7.2.9.0 (2010.11.19)

RunScore Team
  • At request of Jon Krupa, discard any line of an import file that will produce a record in which all fields are blank. This helps to eliminate those blank records in an Excel file that gets incorporated into a *.csv file.
  • Have you ever been working with results in a chip/tag race and were in “bibs and times” (F5) mode and pressed F2 to delete only to realize that you pressed F3 (numbers mode) by mistake and the next F2 ends up deleting a bib but not the time thus mis-aligning the bibs and times? Have you ever hit F2 by mistake and seen a finisher disappear? Some months ago a command “Edit Results (tab) BOTH” as suggested by Mike Richards was added so that you would always be in F5 mode. However, the user could, with a click of the mouse or by depressing F3, put the mode back to the Bibs mode. After many discussions with Steven Keith, Mike Proctor, and Jon Krupa, two significant changes have been made to help. Keep reading.
  • At request of Jon Krupa and Mike Proctor, provide a way to “lock” the Results screen in a “both” mode , bibs and times. This can be done using a new control in Preferences. The setting can be overridden for a race by setting “Edit Results” in entries.ini. It can be set to “bibs”, “times”, or “both”. Likewise, if you only want the “both” mode for a few races, you can use the “Edit Results” to use the “both” mode for those races and leave the “both” mode unchecked in Preferences.
  • At request of several users, provide protection for deleting bibs and times. It works just like the delete function in Browse. That is, when you first go to delete a finisher or a finisher’s time, you will be asked if you really want to. You will also be told that you can “arm” the deletion by using Ctrl-F2.
  • Steve Moland, of Announcers on the Run, requested a change to the Announce screen. He asked that a blank line be inserted if the user pressed enter with no bib number. This allows him to put in blank line if he makes an error , increasing readability.
  • Made improvements in the Initialize External Timers dialog box. Prevents you from having two devices connected to the same port. (This is allowed when RSServer is the client and is talking to chip controllers which are servers since the servers have different IP addresses.) Changes also allow you to stop a device while keeping others running. Now if you don’t change anything for a device (timer, port, baud, tcp), the device will not be stopped and started again. This is particularly useful when using the Summit timer.
  • If you have a device activated through Initialize External Timers, you can turn it off by blanking the port number or by setting the Start/Stop drop down to Stop.
  • It now tests if you are using the same port for two different devices but allows in the case of systems such as IPICO in which case it checks to see if the IP Addresses are the same.
  • Jason Biggs found that AccuChip data was not being handled correctly when coming through TCP/IP. Fixed.
  • Tony Newton asked for a change to the Live Results screen so that the most recent finisher stayed at the bottom of the screen and is highlighted in blue. To do this, set the Scroll Speed to zero and the Scroll Delay to, say, 1 second.
  • Working with Ron Larson, found that sometimes in an Event to Database operation, data is written that is longer than the field. RunScore was not protecting for this situation which, sometimes, caused crashes. This could be a very significant fix.