On several occasions I have run into the problem of the scorer inadvertently publishing results for a new series that over wrote the results of a prior series. This is a result of using a prior series .blw as the basis for the new series
and not always checking the full path name to ensure that it is published in the proper place. Is there a way to have Sailwave notify the user that a prior file will be over written prior to the actual writing of the file and allow the user to cancel the
write? That checking could also be used to help in inadvertent overwriting existing .blw files as well. For most Windows applications, this type of checking is performed.
have run into the problem of the scorer
inadvertently publishing results for a new
series that over wrote the results of a
prior series. This is a result of using a
prior series .blw as the basis for the new
series and not always checking the full path
name to ensure that it is published in the
proper place. Is there a way to have
Sailwave notify the user that a prior file
will be over written prior to the actual
writing of the file and allow the user to
cancel the write? That checking could also
be used to help in inadvertent overwriting
existing .blw files as well. For most
Windows applications, this type of checking
is performed.
Thanks for the feedback. I completely understand the “SaveAs” for the blw, but the issue is with “Publish” results to a file. There is no notice of a potential
overwrite. There is just the “Browse” for destination file which most do not use when publishing new results as the series unfolds; they would use the previously set file location. The main problem is that using a prior blw to form the beginning of a new
series, the publishing file location and name is remembered. Therefore, if the scorer forgets to check the actual file location, he or she may overwrite previous valid results with a new set of results that are most likely empty. Another possible solution
would be have the publish address be relative to the blw. In this case it would be easy to ensure that any published results would most likely not overwrite previous results as the blw would most likely be in separate folders. Just a thought.
On several occasions I have run into the problem of the scorer inadvertently publishing results for a new series that over wrote the results of a prior series. This is a result of using a prior series .blw as the basis for the new series and not always checking
the full path name to ensure that it is published in the proper place. Is there a way to have Sailwave notify the user that a prior file will be over written prior to the actual writing of the file and allow the user to cancel the write? That checking could
also be used to help in inadvertent overwriting existing .blw files as well. For most Windows applications, this type of checking is performed.
Hi Tom,
So I misunderstood you but generally the prompt for overwrite applies to one time operations in the case of publish to a file that happens many many times. I personally would find it rather annoying to the extent that it would be ignored and just another dialogue box to answer.
Possibly you could get clever and only prompt the first time after a file is opened or a filename is changed but would have to disable it also for automation.
Will think about it if I working in that area of the program.
But if you always write to a Dropbox or pCloud folder you would have a backup anyway
Hi Tom,
So I misunderstood you but generally the prompt for
overwrite applies to one time operations in the case of
publish to a file that happens many many times. I
personally would find it rather annoying to the extent
that it would be ignored and just another dialogue box
to answer.
Possibly you could get clever and only prompt the
first time after a file is opened or a filename is
changed but would have to disable it also for
automation.
Will think about it if I working in that area of the
program.
But if you always write to a Dropbox or pCloud folder
for the feedback. I completely understand
the “SaveAs” for the blw, but the issue is
with “Publish” results to a file. There
is no notice of a potential overwrite.
There is just the “Browse” for destination
file which most do not use when publishing
new results as the series unfolds; they
would use the previously set file
location. The main problem is that using
a prior blw to form the beginning of a new
series, the publishing file location and
name is remembered. Therefore, if the
scorer forgets to check the actual file
location, he or she may overwrite previous
valid results with a new set of results
that are most likely empty. Another
possible solution would be have the
publish address be relative to the blw. In
this case it would be easy to ensure that
any published results would most likely
not overwrite previous results as the blw
would most likely be in separate folders.
Just a thought.
have run into the
problem of the scorer
inadvertently publishing
results for a new series
that over wrote the
results of a prior
series. This is a
result of using a prior
series .blw as the basis
for the new series and
not always checking the
full path name to ensure
that it is published in
the proper place. Is
there a way to have
Sailwave notify the user
that a prior file will
be over written prior to
the actual writing of
the file and allow the
user to cancel the
write? That checking
could also be used to
help in inadvertent
overwriting existing
.blw files as well. For
most Windows
applications, this type
of checking is
performed.
Thanks for the feedback and all of the work that you do to make Sailwave what it is. We all benefit immensely from your efforts and willingness to consider new
ways to use the application as well as new features. As a prior software developer myself, I understand your reasoning for not informing the user of the overwrite as well as the potential complexity (and latent defects) that may be introduced in the code in
trying to be “clever”.
As a thought for potential future consideration, I have seen some applications with a user selectable “sticky” option to check for or not check for overwrites.
Maybe that could be a future option for publish file.
So I misunderstood you but generally the prompt for overwrite applies to one time operations in the case of publish to a file that happens many many times. I personally would find it rather annoying to the extent that it would be ignored
and just another dialogue box to answer.
Possibly you could get clever and only prompt the first time after a file is opened or a filename is changed but would have to disable it also for automation.
Will think about it if I working in that area of the program.
But if you always write to a Dropbox or pCloud folder you would have a backup anyway
Jon
Jon
Jon Eskdale
03333 443377
07530 112233
On Sat, 9 Mar 2019 at 19:45, Tom OWEN
towen999@msn…com [sailwave] sailwave@yahoogroups.com wrote:
Jon,
Thanks for the feedback. I completely understand the “SaveAs” for the blw, but the issue is with “Publish” results to a file. There is no notice of a potential overwrite. There is
just the “Browse” for destination file which most do not use when publishing new results as the series unfolds; they would use the previously set file location. The main problem is that using a prior blw to form the beginning of a new series, the publishing
file location and name is remembered. Therefore, if the scorer forgets to check the actual file location, he or she may overwrite previous valid results with a new set of results that are most likely empty. Another possible solution would be have the publish
address be relative to the blw. In this case it would be easy to ensure that any published results would most likely not overwrite previous results as the blw would most likely be in separate folders. Just a thought.
On several occasions I have run into the problem of the scorer inadvertently publishing results for a new series that over wrote the results of a prior series. This is a result of using a prior series .blw as the basis for the new series and not always checking
the full path name to ensure that it is published in the proper place. Is there a way to have Sailwave notify the user that a prior file will be over written prior to the actual writing of the file and allow the user to cancel the write? That checking could
also be used to help in inadvertent overwriting existing .blw files as well. For most Windows applications, this type of checking is performed.
