Category Archives: Bug

Two Big Fixes Tonight

I made two big fixes last Saturday night. The next release will be beta 2.2 and it will be available to the general public right away. If you have using GFX please consider making a donation.

The first bug fix was with how the “Next Race” feature works. The second fix was with the “Call It” functionality. Let’s start with the “Next Race” feature. If you have not been following along with the latest development progress you might not be aware that you can now progress through races from the winner screen. See this screen shot to the left. When there is more than one race entered the next race button will be active on the winner screen. As you cycle through each race the previous race will be removed from the schedule, the racers times will be save back to the roster, and the next race will be loaded up ready to go. There was a small bug in the logic to get the next racers and what racers were loaded next. It should now be fixed. I can’t seem to break it anyway. So, I am pretty confident that the next race logic and the racers on deck is solid. One thing I have not figured out yet is where to put the next racer display when four bikes are raced. It fits nice when two racers a but not with four. I will try a few things to get it all on the screen and that will allow me to release beta 2.2.

The way the next racers come up is that GFX always grabs the next race below the current race unless you are on the last race. So there are three possibilities.

  1. Iif you select the first race on the race list and start things off, GFX will go in order from top to bottom.
  2. If you select the last racer on the race list it will move its way up the list from the bottom.
  3. If you select a race in the middle of the race list the system will keep grabbing the race below the current race until it reaches the end of the race list and then move its way up the race list.

It is also important to note that the last race in the list is not deleted when there is only one left. This is because the Next Button is disabled when there are no more races to load. So you only have the Race Again button available. By design the Race Again button is meant to be used to either race the same group again or if you are not using names and just Racer One, Racer Two and so on. You shouldn’t have to keep loading races to the race list so the last one is kept.

The Race Again button is a big time saver if you are only running colors and not racer names. Just delete the last race from the race list when you have gone through the entire race roster and start adding more if needed. I hope that is easy to understand. If not play with it and let me know what questions you have.

The second big update was with the “Call It” functionality. It was not working as expected. I was trying to make it much more complicated that it was. I ended up check if a racer has completed the distance. If they have then great, save then record the time. If a racer has not completed the distance then GFX will enter 99:99:999 into their time and save that. So 99:99:999 is essential a DNF. But they still get on the board of the final time. I am pretty happy with the way this worked out.

When released give these updates a really good test. Don’t assume they are fixed until you test them yourself when beta 2.2 hits the downloads page. If you are visual person like myself the follwing video will demonstrate these updates in action.

Goldsprints FX beta 2.1 is Released

Goldsprints FX beta 2.1Goldsprints FX beta 2.1. is out for members that have made a donation. Fixes and a few new features are included. Bugs were pretty minor if you knew how to work around them. I developed the delete functionality a little goofy. Thanks to the testers for finding the bug in the delete process. I have lots of ideas going off in my head after this 2.1 release. I wish I had more time to do some coding but this week is crazy busy for me with an event coming up on Saturday and my regular 9-5. Spending these late nights is wearing me down a little. Here are the four fixes and new features added.

  1. The Race button has been disables. Start all races from the Events button. The Race button will get removed entirely in next beta release.
  2. Fixed the issue with deleting racers when more than one was checked. This bug put the current checked counter out of sync. Now all racers checked will be deleted with the confirmation.
  3. Fixed a bug when adding new racers to the roster and you have some already checked. This put the current check count out of sync. Now the checked counter is reset and all checks removed.
  4. On the winners screen you can now race the same ones again or go right to the next race. No need to go back to the Events screen to get next race. Better presentation to the audience.

I have a few more features to add into beta 2 yet. Expecting public beta 2 release to be in about 2 weeks. Donating will get you into the beta testing sooner. Thanks again to everyone that has already donated.

I will get a video up as soon as I have more time that will show the new features in action.

Speed Calculation Bug

I am pretty sure my speed calculation is not correct. After looking at a few screen shots and video from Saturday’s event I decided to manually calculate the speed based on some of the racers display. Have a look at this screen shot.

The blue time was 19.078 over 400 meter. His speed was 74.77. That doesn’t seem right so I just broke down the calculation and if this is right then it is a bug that needs to be fixed.

400 Meters = 0.2485484768949336 Miles

19.078 Seconds = .005299444444444444 hours

0.2485484768949336 / .005299444444444444 = 46.900855268988417813259693384079 MPH

So assuming that is correct above his speed should be about 46.90 MPH not 74.77 MPH. This should be pretty easy to track down and fix. I have not tested the kilometer per hour to see if that is off as well.

I have gotten emails from several of you biting at the bit to start testing GFX. Sorry I have not replied. I have just been busy setting up my first event under Capital City Sprints for most of the last week.

Look for an update this week on the speed bug. After that I just need to get the beta to you guys. I am sure you will find more bugs or features you want to add.

Beta To-Do List is Complete, Almost!

If you have been checking the beta to-do list you should have noticed that I have everything crossed off as of about 5 minutes ago. Check the original post and list here: http://www.goldsprintsfx.org/2010/01/26/goldsprints-fx-beta-release-to-dos/.

Everything went pretty good with just a minor code change here and there. One of the items on the list was to display the time when a race is complete. Here are a few screens of the new display with the time added.

If you have not noticed, the color of the box and the text matches the racer color that is set on the Settings screen. In these three screen shots you can see what I mean. Also, note the winning time is shown now.

These first two examples show two racers in two races. the first is a race using the bar display. The second is using the clock display. The winner is the blue bike and text is set to white in both cases. In future updates, when the race management is done, the racer’s name will be displayed as well.

This example shows four racers. The winner is the yellow racer who has black text.

Other updates include fixing the way the Reset and Call It work. But I just noticed one bug. When the Call It is clicked the correct rider is shown as the winner, but for some reason the race bar are flip flopped so visually the bars are incorrect.

So there is still work to be done. Beta is close. Just a few things left that seems to only surface when I fix something else. I promise to not add anything new. Just bug fixes so everyone else can find these bugs!

Bug Fix: Distance & Time Display

I fixed a bug tonight around the way the distance and time was displayed when they ended with a double 00 in the decimal place. I love it! People are finding bugs and they don’t even have the beta in their hands yet!

Basically something like 23.00 was showing at 23. Visually it made the numbers jump and shift. Thanks to eLBy for pointing this out. It was a pretty easy fix but I did not do it in the way I was expecting in the end. Just the same, here is a video of the time and distance fix. It should not always show full two digit decimals.

Watch this video on Vimeo. Video created by Ed Husar.