One recurring problem we get is incorrectly entered times

e.g. 79.15 is 79 hours 19 minutes - when the pro wanted 79 minutes

entering 0:79:19 is fine or entering 0.79.19 is also fine for a race time of 1 hour 19 minutes 19 seconds

but if you enter 0.79:19 you get 79 hours …

Ideally is we could reduce the risk of making timing typos, that would help massively.

One simple solutionI thought of is have a maximum race time field somewhere
so we could set that as say 3 hours and if you accidentally have entered 79 hours you get a big warning notice

Also, for the typos between : and. ( and any other delimiter ) could the time parse just no accept any non numeric as a delimiter and this is would matter if you type 1-12#19 or 1.12-19 or 1,12.19

One recurring problem we get is incorrectly entered times

e.g. 79.15 is 79 hours 19 minutes - when the pro wanted 79 minutes

entering 0:79:19 is fine or entering 0.79.19 is also fine for a race time of 1 hour 19 minutes 19 seconds

but if you enter 0.79:19 you get 79 hours …

Ideally is we could reduce the risk of making timing typos, that would help massively.

One simple solutionI thought of is have a maximum race time field somewhere
so we could set that as say 3 hours and if you accidentally have entered 79 hours you get a big warning notice

Also, for the typos between : and. ( and any other delimiter ) could the time parse just no accept any non numeric as a delimiter and this is would matter if you type 1-12#19 or 1.12-19 or 1,12.19

Sailwave was designed to accept times in HHMMSS format with or

without separator. It most reliably works with this format. Using
no separator in fact speeds up data entry considerably if one uses
a numeric pad. For events that go over 24 hours it is possible to
add a date before the time but for dinghy racing that is unlikely!

What happens with different numeric data strings for time is

documented at .

I would recommend not using a : as a time separator as one needs

to hold down the shift key to get this ‘character’, which slows
down data entry, especially if using a numeric pad.

I have just tested entering elapsed times of up to 99 minutes and

59 seconds without a time separator and I get get the
times consistently interpreted. I also entered 89.19 meaning 89
minutes and 19 seconds and when I scored the corrected time
worked out correctly.

Hi Alan,
I don’t understand how entering 79.15 gets 79 hours - It gives you 79 mins 15 seconds which is what you say you want.

My preferred way is to enter the elapsed times through the Sailnumber wizard and this way you don’t need to enter any separators characters and they get inserted automatically for clear reading and it is much quicker and easier for entry.