I'm using v10.21A. My F-key will send the %3 whether the SEQ number starts
out gray or blue, basically as Scot said. However, each time I start WL,
the Entry window starts out with NOTHING in the SEQ field, and it stays that
way until I log the QSO. Thus the %3 only sends ZERO ZERO ZERO, since
there's nothing in the SEQ field. This is true no matter what the serial
number is supposed to be - All SUBSEQUENT SEQ fields are filled immediately
with the correct number, and the F-key sends %3 just fine.
Surely some of you SSB contest guys have some comments on this? Thanks - 73
---------------------------------
WA9ALS - John
jfleming@shelbynet.net
http://www.qsl.net/wa9als
---------------------------------
----- Original Message -----
From: "Scot Herrick" <sherrick@ameritech.net>
To: <Writelog@contesting.com>
Sent: Thursday, November 02, 2000 10:50 PM
Subject: RE: [WriteLog] SSB soundcard serial numbers
>
> All,
>
> I've been working with John tonight as well. I'm not seeing what John is
> seeing with the first QSO number. I'm on version 10.19. Here is what I
see.
>
> On first opening up a contest, the serial number is blank. Upon putting in
a
> callsign (e.g., WA9ALS) the serial number '1' shows up as gray which is
what
> it is supposed to do. Upon hitting the space bar, the serial number turns
> blue which means it is ready to log this serial number if required. At
this
> point, you can hit your function key with the serial number in it and it
> will send serial number '1.'
>
> I also tested this without hitting the space bar. If just the call is in
the
> QSO Entry field and the serial number '1' is still gray, upon hitting the
> function key the serial number turns blue and the serial number '1' is
sent.
>
> Something's different. Comments appreciated...
>
> Thanks...Scot, K9JY
>
> PS K1VV sent EXCELLENT documentation regarding SSB recording of wave
files.
> I'm putting them into the web site as we speak; hopefully will get it
> updated yet this evening (if I can get off of email!!)
>
> See WriteLog's complete user manual at
> K9JY's WriteLog site www.k9jy.com
>
> mailto:scot@k9jy.com
>
>
> > -----Original Message-----
> > From: owner-writelog@contesting.com
> > [mailto:owner-writelog@contesting.com]On Behalf Of WA9ALS - John
> > Sent: Friday, November 03, 2000 03:15
> > To: Writelog@contesting.com
> > Subject: [WriteLog] SSB soundcard serial numbers
> >
> >
> >
> > Tiny bug/feature/op error... I've been working with the soundcard SSB
> > voice keyer this evening. Regarding %3 in an SSB message, I couldn't
> > get the FIRST QSO of a given session to send it's serial number - I just
> > got ZERO-ZERO-ZERO sent. Notice that the SEQ area is EMPTY for the
> > FIRST QSO of each session that you open Writelog. If I log a dummy QSO,
> > then the NEXT QSO's Entry window has the SEQ number in BLUE showing, and
> > the %3 in the SSB message works as expected.
> >
> > 1. Apparently the SEQ number has to be showing for the %3 to work. If
> > I log a dummy #1 QSO (with a SEQ field blank), and then delete it, the
> > SEQ field now shows "1" (or whatever the FIRST SEQ number of that
> > session is) and the %3 works as expected.
> >
> > 2. Why doesn't the very FIRST SEQ number of a given session show?
> >
> > 3. Is there a way to MAKE it show? Surely everyone's not logging a
> > dummy Q and then deleting it every time they open the log. Thanks
> > ------------------------------------------------------------
> > WA9ALS - John
> > email: jfleming@shelbynet.net
> > homepage: http://www.qsl.net/wa9als
> > logbook: http://www.qsl.net/wa9als/search.htm
> >
> >
> >
> >
> > --
> > WWW: http://www.writelog.com/
> > Submissions: writelog@contesting.com
> > Administrative requests: writelog-REQUEST@contesting.com
> > Problems: owner-writelog@contesting.com
> >
>
>
> --
> WWW: http://www.writelog.com/
> Submissions: writelog@contesting.com
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: owner-writelog@contesting.com
>
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|