99 posts tagged with "legacy"

• Latest stable release.
• A new file, Boston.2013.tac, with qualifying times for the 2013 Boston Marathon has been added to the Common folder. You should use this for marathons run after September

• New command Continue used with Selected to allow you to mark a field and do another function, such as send an e-mail in one *.lst file.
• New command EMAIL PORT;
• At request of Steve Moland, “Announcers on the Run,” when doing an Import and you run into a field not recognized, in addition to Ignore and Cancel, have added “Ignore all remaining fields” button. When it is pressed, no more fields are processed and the file being imported is read but only up to the field being queried.
• Can now use Gmail, AOL and other SMTP servers for e-mail.
• Some people did not like being warned every time they went to delete a bib or time in Edit/Results. This can now be set in Preferences.
• At request of Marek BLAŽEK, made a change to the sort routine to handle diacritic symbols (R,Š,Ž,C,Š).
• Marek BLAŽEK requested that “Time difference” and “Total Time Difference” be added to allowed features of “Event to Database.” Done.
• Debbie Burke did not like the “I-beam” cursor on the main page which changed to a “pointer” cursor on the links. Was hard to see. Changed to “pointer” for bulk of screen and to “hand” on link. This is the more standard way to handle the cursor.
• It was pointed out that when tabbing across the Initial External Timers dialog box, that is was not possible to reach the TCP checkbox. It was only possible to get there with the mouse. Fixed.
• When using a device via TCP, baud does not matter. In order to reinforce that, when you check the TCP checkbox, the Baud drop-down disappears.
• Some people like to be in “insert” when editing and some but some like to be in “replace.” At request of Steve Scheidt, allow the editor to start in either “insert” or “replace” mode. Whatever mode you have it in when you leave the editor, it will be in that mode the next time you edit a file , even if you have closed RunScore in the interim.
• At request of Paul Williams, add alternate white and gray background lines on Instant Results to improve readability.

• At request of Steven Keith, add new system variable %race path%. This can be used in the System Command to copy files from the race directory.
• At request of Steven Keith, provide a way to execute a listing (*.lst) file on startup of a race. This is done by adding a parameter in the Properties/Target section of the RSServer or RSClient icon. The parameter is /startup=filename. In the example below, RSServer starts up the sample race and then starts the announcer.

c:\runscore\rsserver.exe sampleraces\sample\entries /startup=announce.lst

or

c:\runscore\client\rsclient.exe /startup=announce.lst

• You can also specify the IP Address and the port on the command line of RSClient. The parameters are /address=ipaddress and /port=number. For example:

c:\runscore\client\rsclient.exe /startup=announce.lst /address=MyDesktop /port=33000

• While we were at it, we decided to allow you to set the Login name for RSClient to log into RSServer. If you are not using login names, don’t worry about this feature. You can only use this feature if you are requiring a login name but not requiring a password. The parameter is /login=login_name. For example:

c:\runscore\client\rsclient.exe /startup=announce.lst /address=MyDesktop /port=33000 /login=Announcer

• At request of Craig Wilson, allow team members beyond the number scoring to advance. This is controlled by setting a negative number for Advance Maximum control
• You have always been able to specify a “scratch” event in RunScore by making the event name start with the letters “STA” or “SCR”. Now there is a third way. Just specify the event to be a “Start” event in “Misc/Edit list of events”. When a scratch event’s time is subtracted from another event’s time and there is not time for the scratch time, a time of zero is used. On the other hand, if it is not a scratch event, for example it might be the BIKE event in a triathlon, then when the BIKE time is subtracted from the next split and there is no BIKE time, the resulting split is a blank. That allows you to easily find someone who missed a split point.
• New team feature: Team Spread: Prints out, when using Team Format Columns, the spread in time between the first finisher and last scoring finisher on each team.
• New team command: Team Format Brief: Implemented at request of Pat Leone. With Team Format Brief, only the team place, team name, and team score are printed.
• At Steven Keith’s request, add “Starts with” (or “SW”) command to entries.ini. It had been added to *.lst processing some months ago.
• Fixed a problem in entries.ini where you needed to put in dummy data in the [data] area even if none was required.

• 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.

• Added support for Japanese language
• Fixed Chatsworth support.
• You can now set the lap difference in a lap race in Entries.ini. If two times, in a lap race are within the time, in seconds, the second time is eliminated. Command: “Lap Difference”. The default is 10 seconds.

• Jenna Ginsburg found that a Time Format of NONE was not working with the Announcer feature on RSClient. Fixed.
• Cleaned up and fixed some problems in the sample races. Made them available for download independent of the full install (RunScoreSetup.exe).
• At urging of Steven Keith, add red background text “ UNREGISTERED RUNNER NUMBER “ to Unregistered Runner Number (entry record 0) so that people realize that they are not editing an entry.

• The old *.tac files have been replaced with new ones based on the age-grade tables. These files are used to flag times that the USATF considers quality performances based on gender, age, and time. You can tell if you are using the new ones because they have a 2010 date.
• Unregistered Runner Number (URN) is now protected and is always in record number zero.
• You can now check for Updates via the Click for Updates link on the main page.
• Add support for TCP/IP link between timing systems and RunScore. This allows you to have your timing system farther away.
• And, as usual, a number of bug fixes which are documented in the LatestRevisions.html file.
• The logo in Live Results can now be a *.png file (Portable Network Graphics) or a *.bmp (Windows bitmap) file. Previously, RunScore only supported bitmaps.

• Made an improvement to the edit box when you edit a bib or a time (Right-click on a bib or time). Before the edit box had a thick border which had the effect (in Win XP) to hide the lower part of the characters being edited.
• Fred Dewsberry found that Look Up stopped working on the server once the RSClient is started. This has been a long-standing bug. Not sure why it took this long for someone to report it. Fixed.
• Sylvan Symth requested that when there are no finishers for a team score, that, instead of displaying an annoying error pop-up, just produce a page with no results , only the header. Done.
• John Lauces reported that bar codes were not printing correctly. The problem was introduced when the default monospaced font was added to Preferences. Fixed.
• Greg McFerren found that the BEST command was not working correctly. It was finding the worst performances instead of the best Fixed.

• More bug fixes as described in the LatestRevisions.html file.

• This version mainly fixes bugs that have been found in Version 7.2.1.0. There have been some additional improvements.
• At request of Andrés Alanon Vazquez, add two new commands for use with the Announce screen: “Last Lap Time” and “Average Lap Time.”
• Included a tip in the Help screens by Steven Keith about providing RSServer and a race folder on a thumb drive so that the race management people can do their own data entry without actually installing RunScore.

• This is the first version of RunScore produced with Microsoft Visual Studio VC++ tools built on top of OWLNEXT which is an independent development based on Borland OWL (Object Windows Library). Almost all development before this point was produced with Borland tools.
• NOTE: This version of RunScore will not run on older Windows operating systems: Windows 95, Windows 98, Windows ME, or Windows NT. It will run on Windows 2000, Windows XP, Vista, and Windows 7.
• What are the advantages?

• The largest advantage from the user’s point of view is that we have squashed the bug that produced those “Busy clipboard” pop-ups. The bug was traced to some Borland code. I reported this to the OWLNEXT developers who have fixed it. * There are no functional advantages and no perceived speed differences. * There are no longer DLLs that get installed in the Windows directory. Therefore, if you want to move RunScore from one computer to another, all you have to do is copy the RunScore folder to a thumb drive and then copy it into the new computer. For those technically inclined, this type of application is called a “static” application instead of the RSS/RSC which was a “dynamic” application since it depended on external DLL files. Note, however, that there are still some DLLs installed with RunScore (Summit timer DLL and Active.com DLL) but since they are in the RunScore directory, they will be copied to the new computer. * When I retire from supporting RunScore, it will be far easier to turn the development package over to another person since it will be using modern tools. * The Microsoft Visual Studio Interactive Development Environment (IDE) is far superior to the Borland IDE. It should be since it has had an additional 13 years of improvements. This helps me in development and in finding bugs. It is also much more fussy, warning me of possible problems. * For those Vista users that were having problems with the special functions of printers in Vista, like Back to Front printing, the VC version incorporates the new Printer Dialog box that works perfectly under Vista. Probably does the same under Windows 7.

• What are the disadvantages?

• While the install package will be about the same size, updates will be larger since they are static applications. But in this day of high-speed access, I don’t see this as a problem.

• Recent changes

• At the suggestion of Steven Keith, add support for monospace fonts other than “Courier New.” In Preferences you can specify what default monospace font you want. It will be used in all listings. These fonts make for much better looking listings. In Help/Index/Preferences are examples showing the difference between an Arial monospaced font and the Courier New font. * Another new control in Preferences allows you to specify if you want the page number at the top or the bottom of each page of the printout. * Jeff Glaze pointed out that a person with a birthdate of 01/01/2000 did not have their age updated. Fixed. * Version control. As before, for RSClient to connect to RSServer, the first three numbers in the version must agree. For example RSClient Version 7.1.0.1 can connect to RSServer Version 7.1.0.3. Before, if the first three did not agree, it was not possible to connect. Now that is only true if only the first two numbers agree. If the first two agree but the third does not, you can connect but you are given a warning. Things will probably work but there may be some functions that do not agree. * A RunScore API (Application Programming Interface) has been developed. The purpose of the API is to allow programmers to access the RunScore database and results. This could be used to add entrants, to develop new results listings, or many other uses. It is only useful for programmers who can program in C++. * At request of Art Stockman, make change to allow changing of event in Initialize External Timer so that data can be directed to a different event without having to shut RunScore down.