Good point, Don. However, there were times this weekend where I wasn't sure
whether a station gave me a "300" report or whether that was still there
from before. I ended up chacking the Check Call window for every QSO
because I couldn't trust the current QSO window. If I click on a packet
spot, I expect to see either no report or the report from the previous QSO,
but not an incorrect report.
Suggestion to Ron and Wayne: is it possible to make this an option so
everyone will get what they prefer? Options:
1. Pull up report from previous QSO with this station on another band (I
think that was what was supposed to happen). If no previous QSO, leave
blank.
2. Keep it the way it is now, per Don's request. Personally, I'd definitely
like to have the option to not have it like this. But Don has a good point,
too, so it's worth being able to select it like that.
3. Always have a blank report field. This would be my personal preference
(I understand I'm alone with this) because it prevents Writelog from
accepting the QSO until I enter a report. I have the Check Call window open
anyway, so it's easy enough to look there. I always listen for the report
and then compare it to the previous QSO's, so this would not slow me down
one bit. Also, last weekend there was one station who gave me a serial
number in the first QSO and a power of 100 later (and I logged what he
sent).
IMO, having to hit alt-W to accomplish option 3 is not desirable because it
makes it an awkward two-handed operation (alt-W, mouse, alt-W, mouse...).
I don't know whether this can be done, but Ron and Wayne have done some
other magic before.
Michael, K1JE
On Sunday, March 05, 2000 11:02 PM, Don Hill [SMTP:aa5au@msn.com] wrote:
>
> > 3. If there was something in the power field from a previous spot of a
> > station I worked before on an other band, and I clicked on a different
> > spot, the power remained that of the first spot, i.e. the new spot did
not
> > overwrite or blank the information --> here's the problem.
>
> I think there is a good explanation for this. I think it's been
discussed
> here
> before and it may not be a problem on SSB but it has saved me on RTTY
> before. Here it is:
>
> Say you work a station and forget to log him. Then you click on the next
> station and it cleared out the other station's report. Then you have a
> problem,
> especially if it is a new station that you haven't worked before and you
> don't
> remember what report the previous station gave you.
>
> The solution is to train yourself to wipe out (CTRL-W) stations out of
the
> entry field that you don't want to work or are dupes. This works for me.
> However, most contests I run single op without the packetcluster so there
> is no such problem unless it's a station I've mapped manually.
>
> It's not a bug, it's a protection device.
>
> 73, Don AA5AU
>
>
>
>
>
>
>
> --
> WWW: http://www.contesting.com/writelog
> Submissions: writelog@contesting.com
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: owner-writelog@contesting.com
>
--
WWW: http://www.contesting.com/writelog
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|