Board Logo
« Race Timing Program »

Welcome Guest. Please Login or Register.
Oct 17th, 2017, 3:13pm


Conforums Terms of Service | Membership Rules | Home | Search | Recent Posts | Notification | Format Your Message | Installation FAQ

Please use the forums Search feature before asking.
Please post code using the code box described in Format Your Messages.
This will keep indentation, separate it better form the message and prevent gibberish.
If the code is too long for one post or additional files are needed, upload a ZIP archive to the Just BASIC Files Archive Site.

« Previous Topic | Next Topic »
Pages: 1  Notify Send Topic Print
 thread  Author  Topic: Race Timing Program  (Read 259 times)
oxcart
New Member
Image


member is offline

Avatar




PM


Posts: 13
xx Race Timing Program
« Thread started on: Jul 6th, 2017, 04:31am »

I time road races and have been working on a program to help me do this since late 2015. As people want it to do more, faster and different things, it has become a little big. I have loaded the main and supporting programs to my homepage below as text files.

http://webpages.charter.net/lwagner905/

Main program : ResTiming.txt
Data file : GetFind17.txt
Timing device file : RTFix.txt
Gender checkers : FMasci.txt and FFasci.txt

If you select Click-In Results, it will generate an "Overall.txt" file that is used after the Click-In phase. After "clicking in entrants in finish order from the right 3 columns, close the main screen and the reports options appear. Choose Ultrak first to generate a times file. To add times as you go, just hit a blank enter. Click on an entrant in the far left reverse order screen to remove them. Add runners not in the database by typing info into dialog box.

I will be greatful for any observations that will speed up execution during the Click-In phase.

http://webpages.charter.net/lwagner905/
User IP Logged

Rod
Administrator
ImageImageImageImageImage


member is offline

Avatar

Graphics = Goosebumps!


PM

Gender: Male
Posts: 3100
xx Re: Race Timing Program
« Reply #1 on: Jul 6th, 2017, 06:18am »

Interesting, not sure if my experiments are going to help. First off I thought you had a lot of code between clicks. I set off to show you that the listboxes manage themselves by eliminating empty strings and that all you might need is a status file.

Code:
  'nomainwin
  'maintain a ststus file for each runner
  dim status(100,4)
  'index names for look upo
  bib=1
  status=2
  starttime=3
  endtime=4
  sync=time$("ms")
  status(1,bib)=1
  status(1,status)=1'running
  status(1,starttime)=sync
  status(2,bib)=2
  status(2,status)=1'running
  status(2,starttime)=sync
  status(3,bib)=3
  status(3,status)=1'running
  status(3,starttime)=sync
  status(4,bib)=4
  status(4,status)=1'running
  status(4,starttime)=sync
  status(5,bib)=5
  status(5,status)=1'running
  status(5,starttime)=sync

  'set up name array for listbox
  running$(1) = "001 Rod Bird "
  running$(2) = "002 Dan Teal"
  running$(3) = "003 Liz Moody"
  running$(4) = "004 Ian First"
  running$(5) = "005 Tom Last"
  listbox #race.lbr, running$(), [selectionMade],255, 35, 250, 90
  listbox #race.lbf, finnish$(), [edit], 5, 35, 250, 90
  finnished=1

  WindowWidth = 600 : WindowHeight = 180
  open "Time in Runners" for window as #race
  #race.lbr "singleclickselect"
  wait

[selectionMade]
    #race.lbr "selection? runner$"
    racenumber=val(left$(runner$,3))
    running$(racenumber)=""
    finnish$(finnished)=runner$
    finnished=finnished+1
    status(racenumber,status)=0
    status(racenumber,endtime)=time$("ms")
    #race.lbr "reload"
    #race.lbf "reload"
    #race.lbr "selectindex 0"

    if finnished=6 then [quit]
    wait

[quit]
    for n= 1 to 5
        print status(n,bib),status(n,status),status(n,starttime),status(n,endtime),status(n,endtime)-status(n,starttime)
    next
    end

 



However what it shows me is that the mouse click itself is the source of most of the delay This is a Windows feature and it is all about eliminating "bounce". The switch needs closed for a certain amount of time before it is considered really closed and not bouncing.

If you have a series of close together runners I recon it is going to be really hard to get them clicked in fairly. :(

When I run we get radio fobs that are logged on a mat as we finish. Perhaps a new input scheme is required?
User IP Logged

Pages: 1  Notify Send Topic Print
« Previous Topic | Next Topic »

Conforums Terms of Service | Membership Rules | Home | Search | Recent Posts | Notification | Format Your Message | Installation FAQ

Donate $6.99 for 50,000 Ad-Free Pageviews!

| |

This forum powered for FREE by Conforums ©
Sign up for your own Free Message Board today!
Terms of Service | Privacy Policy | Conforums Support | Parental Controls