a users's experiences this weekend

Imported from Yahoo
1

Some experiences as a user this weekend

···

=======================================

Topper nationwide.

http://www.mumblesyachtclub.co.uk/results/2007/2007toppers.htm

Further to the recent message about entered results going AWOL, I entered
177 sail numbers on Saturday only to see them disappear a few minutes later!
Extremely unpleasant. I think I know the scenario:-

- start sailwave (has no results)
- enter sailnos but have not saved file yet
- start sailwave again by mistake (2nd instance now running)
- save the file containing the set of results
- some time later and by mistake save the send instance which has no
results.

The (asked-for) warning that Sailwave is already running would have helped.

When entering a long list of sail numbers, especially for a split start
scenario (flights) you need to be able to go back and review the entered
list and reapply it - it's almost impossible to check things if the
finishing boat has recorded the finishes across both starts (interleaved in
the list) - Sailwave sorts it out (it knows flight/fleet from sailno) -
that's great - but - it's hard to review later (comp says "i was third" and
shs's about 120 in the list). It needs (again asked for) another type of
sailno wiz that essentially allows you to replicate the sheet of paper
results in front of you and edit/reapply it after review - probably easier
than using the reposition tool.

Ambiguous sailnos are a pain - I came to a grinding halt each time i.e. 23
when 230 and 233 exist. The down arrow tweak didnt work cos it didnt enable
the OK Next button (I'll fix it) but a better solution is needed. I also
agree about a single Enter hit for each SailNo as well. And Sailwave should
speak the numbers back to you for feedback.

The existing sailno wiz needs a list of the last N numbers entered so it
you're interrupted you can restart sensibly.

Essentially data entry needs to be slicker.

We had the results on the website a 20 minutes after each race finish
(mostly waiting for them to come ashore) but it could have been faster.

It was no proboem doing this size event single handed - just had to grab a
parent to read out the sailnos - I quickly discivered it was *slow* to read
and type them.

Interesting :slight_smile:

One more thing - when scoring race 2 and onwards it'd be better to assume
DNF not DNC even though they may not have officially retired.

I know - you've been telling me all this for years... :slight_smile:

Regards,
Colin
www.sailwave.com

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.472 / Virus Database: 269.9.6/865 - Release Date: 24/06/2007
08:33

2

Colin,

When you say:

One more thing - when scoring race 2 and
onwards it’d be better to assume

DNF not DNC even though they may not have officially retired.
This is true for Open meetings, Nationals etc. but not for long club
series. For these series we score DNF as starters +1 and DNC as entries
+1, encouraging members to come down for more weekends. The two can be
significantly different, particularly for evening series.

Would it be possible to select between DNC and DNF for auto-complete
depending upon type of series please?

Thank you,

Rhys Lankester

BCYC

Colin Jenkins wrote:

···

www.sailwavecom

No virus found in this outgoing message.

Checked by AVG Free Edition.

Version: 7.5.472 / Virus Database: 269.9.6/865 - Release Date:
24/06/2007

08:33

3

Yes - I would never hardwire something like that. Probably envisage something in series or global options specifiy the code to use.

CJ

···

-----Original Message-----
From: sailwave@yahoogroups.com [mailto:sailwave@yahoogroups.com]On Behalf Of Rhys LANKESTER
Sent: 25 June 2007 09:21
To:
sailwave@yahoogroups.com
Subject: Re: [sailwave] a users’s experiences this weekend

Colin,

When you say:

One more thing - when scoring race 2 and onwards it'd be better to assume
DNF not DNC even though they may not have officially retired.

This is true for Open meetings, Nationals etc. but not for long club series. For these series we score DNF as starters +1 and DNC as entries +1, encouraging members to come down for more weekends. The two can be significantly different, particularly for evening series.

Would it be possible to select between DNC and DNF for auto-complete depending upon type of series please?

Thank you,
Rhys Lankester
BCYC

Colin Jenkins wrote:

Some experiences as a user this weekend

=======================================

Topper nationwide.

http://www.mumblesyachtclub.co.uk/results/2007/2007toppers.htm

Further to the recent message about entered results going AWOL, I entered
177 sail numbers on Saturday only to see them disappear a few minutes later!

Extremely unpleasant. I think I know the scenario:-

- start sailwave (has no results)
- enter sailnos but have not saved file yet

  • start sailwave again by mistake (2nd instance now running)

    • save the file containing the set of results
    • some time later and by mistake save the send instance which has no
      results.

    The (asked-for) warning that Sailwave is already running would have helped.

    When entering a long list of sail numbers, especially for a split start
    scenario (flights) you need to be able to go back and review the entered
    list and reapply it - it’s almost impossible to check things if the
    finishing boat has recorded the finishes across both starts (interleaved in
    the list) - Sailwave sorts it out (it knows flight/fleet from sailno) -
    that’s great - but - it’s hard to review later (comp says “i was third” and
    shs’s about 120 in the list). It needs (again asked for) another type of
    sailno wiz that essentially allows you to replicate the sheet of paper
    results in front of you and edit/reapply it after review - probably easier
    than using the reposition tool.

    Ambiguous sailnos are a pain - I came to a grinding halt each time i.e. 23
    when 230 and 233 exist. The down arrow tweak didnt work cos it didnt enable
    the OK Next button (I’ll fix it) but a better solution is needed. I also
    agree about a single Enter hit for each SailNo as well. And Sailwave should
    speak the numbers back to you for feedback.

    The existing sailno wiz needs a list of the last N numbers entered so it
    you’re interrupted you can restart sensibly.

    Essentially data entry needs to be slicker.

    We had the results on the website a 20 minutes after each race finish
    (mostly waiting for them to come ashore) but it could have been faster.

    It was no proboem doing this size event single handed - just had to grab a
    parent to read out the sailnos - I quickly discivered it was slow to read
    and type them.

Interesting :slight_smile:

One more thing - when scoring race 2 and onwards it'd be better to assume
DNF not DNC even though they may not have officially retired.

I know - you've been telling me all this for years... :-)

Regards,
Colin
www.sailwave.com

No virus found in this outgoing message.

Checked by AVG Free Edition.
Version: 7.5.472 / Virus Database: 269.9.6/865 - Release Date: 24/06/2007
08:33

4

Another minor point - when entering a new competitor boat type like,
lets say, a Topper, if you type 'top' and click the drop-down list it
goes to that part of the list where Toppers start. Windows convention
is that F4 is a keyboard shortcut to bring up the drop-down. It would
be helpful to have this function in Sailwave (anything that saves
mouse-clicks can speed things up)

Alan

Some experiences as a user this weekend

Topper nationwide.

http://www.mumblesyachtclub.co.uk/results/2007/2007toppers.htm

Further to the recent message about entered results going AWOL, I

entered

177 sail numbers on Saturday only to see them disappear a few

minutes later!

Extremely unpleasant. I think I know the scenario:-

- start sailwave (has no results)
- enter sailnos but have not saved file yet
- start sailwave again by mistake (2nd instance now running)
- save the file containing the set of results
- some time later and by mistake save the send instance which has no
results.

The (asked-for) warning that Sailwave is already running would have

helped.

When entering a long list of sail numbers, especially for a split

start

scenario (flights) you need to be able to go back and review the

entered

list and reapply it - it's almost impossible to check things if the
finishing boat has recorded the finishes across both starts

(interleaved in

the list) - Sailwave sorts it out (it knows flight/fleet from

sailno) -

that's great - but - it's hard to review later (comp says "i was

third" and

shs's about 120 in the list). It needs (again asked for) another

type of

sailno wiz that essentially allows you to replicate the sheet of

paper

results in front of you and edit/reapply it after review - probably

easier

than using the reposition tool.

Ambiguous sailnos are a pain - I came to a grinding halt each time

i.e. 23

when 230 and 233 exist. The down arrow tweak didnt work cos it

didnt enable

the OK Next button (I'll fix it) but a better solution is needed.

I also

agree about a single Enter hit for each SailNo as well. And

Sailwave should

speak the numbers back to you for feedback.

The existing sailno wiz needs a list of the last N numbers entered

so it

you're interrupted you can restart sensibly.

Essentially data entry needs to be slicker.

We had the results on the website a 20 minutes after each race

finish

(mostly waiting for them to come ashore) but it could have been

faster.

It was no proboem doing this size event single handed - just had to

grab a

parent to read out the sailnos - I quickly discivered it was *slow*

to read

and type them.

Interesting :slight_smile:

One more thing - when scoring race 2 and onwards it'd be better to

assume

DNF not DNC even though they may not have officially retired.

I know - you've been telling me all this for years... :slight_smile:

Regards,
Colin
www.sailwave.com

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.472 / Virus Database: 269.9.6/865 - Release Date:

24/06/2007

···

--- In sailwave@yahoogroups.com, "Colin Jenkins" <colin@...> wrote:

08:33