[DogParkList] Re: MacLoggerDX Contest Log Fields
Anthony Rodgers
arodgers@mac.com
Sat, 31 May 2003 22:00:56 -0700
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--B_3137263258_203592
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Well, what can I say? You guys are astonishing!
Scott =AD many thanks for your excellent advice on using MacLoggerDX in
contests. I knew it could be done =AD I just didn=B9t want to reinvent the whee=
l
and your real-world advice is invaluable. Please keep up your work on the
Cabrillo converter =AD I will give whatever limited help that I can (with bet=
a
testing etc.).
On another topic, I posted a question to the Ham-Mac list about using a Mac
to auto send CQ and other common things using sound recordings triggered by
function keys, much the same way that TRLog does. Do you have any
suggestions from your contesting experience?
Don =AD once again, you are faster than light at implementing suggestions fro=
m
your faithful users. I am a web developer, and have no idea how you do it s=
o
fast! I can=B9t wait to start using MacLoggerDX in anger, and beating some of
the TRLog boys at their own game :-)
Kinda proves our point about Mac users, doesn=B9t it? :-)
73 de VA7IRL,
--=20
Anthony Rodgers
Email: VA7IRL@rac.ca
Cell: 604-340-8295
Numeric Pager: 1-800-331-6351
Text Pager: arodgers@txt.bellmobility.ca
MSN Messenger ID: arodgers@mac.com
On 5/31/03 6:52 PM, "B. Scott Andersen" <bsandersen@mac.com> wrote:
> Dear Don,
>=20
> My goodness. I went into the office for a few hours to catch up on
> some things and look what you've done. I can't leave you alone for
> a minute! :-)
>=20
> You were exactly right to check the ADIF standard and the LOTW stuff. I
> was going to suggest that (but, of course, you're right on the ball with
> this stuff). Actually, putting "Logbook of the World Ready" on your
> product
> description would be a nice bragging point.
>=20
> By the way, the ARRL doesn't have a digital signature client
> for the Macintosh yet. Did you have any interest in checking that
> out once
> they release the source? They claim they are "looking for
> volunteers".
>=20
> <minirant>Of course, it makes me wonder what my ARRL dues are for
> if me
> and my Macintosh are 2nd class citizens. They've got a LINUX
> client but
> no Macintosh client. Sheesh!</minirant>
>=20
> The SRX (received serial number--numeric only) and the SRXString
> (received exchange data) can only be entered manual at the time of the
> QSO. Leaving that as a simple editable field seems fine to me.
>=20
> The STX (transmitted serial number) is the one field that "must" have
> the auto-increment capability. Let's ignore the STXString field for a
> moment.
> Let me make a suggestion about how the implement this (just a draft)
> and we
> can see how much (if any) of my musings are useful.
>=20
> ----
> First, the upper panel (above the tabs) looks really nice right now. I'm
> reluctant to add anything up there for any of this unless we really
> can't
> think of another way.
>=20
> I think we actually talked about this once (back in December) but one
> option
> is to create a tab for control of contest behavior and to setup and
> spawn the
> Cabrillo processor. I'm going to assume that that's not what is going
> to happen.
> [If you do decide to create a "contest" tab, then things get even
> easier.]
>=20
> In the "Prefs" tab there is some open area below the DX Alarms
> checkboxes.
> I might suggest two new controls in this small area: a checkbox and a
> text
> field with a label.
>=20
> +------ Contesting -----------+
> | |
> | Autogen serial #'s [ ] |
> | Next serial # [ ] |
> | |
> +-----------------------------+
>=20
> IF the checkbox is in the unchecked state THEN
> IF the next serial number field is empty THEN
> when the user puts an X there the next serial # is set to 1
> ELSE
> when the user puts an X there the number appear in the field is
> unaltered
> FI
> ELSE
> when the user unchecks the box any value in the box is left unchanged
> FI
>=20
> The next serial number value is NOT persistent between application
> restarts.
> (You don't need to write it to disk).
>=20
> The next serial number value is a editable text area but only natural
> numbers
> are allowed. No signs (+/-). No decimal point (.). Only digits. Leading
> zeros
> are suppressed/eliminated. [If a user enters "001" you can, at your
> option,
> convert that to simply "1".]
>=20
> When a QSO is logged:
> If the checkbox "autogen serial #'s" is checked, then the current
> value of the
> associated text box is written into the serial number sent field of
> the QSO.
> Also, the value in the "Next serial #" text field is incremented by
> 1. That is,
> if a user were to click on the "Prefs" panel again and look at that
> text area
> they would see a "2" in that field after the first QSO had been
> logged.
>=20
> If the checkbox "autogen serial #'s" is NOT checked, no value is
> stamped
> into the serial number sent field. The value in the "Next serial #",
> if any,
> is left unaltered. (This behavior allows people to "drop out of a
> contest"
> temporarily and make some QSOs that won't apply toward the contest
> score.
> When they wish to "return to the contest" the numbers pick right up
> where
> they left off.]
> ----
>> > (I made all the new fields Str31, but perhaps SRX and STX can be 15
>> > chars and SRX_STRING and STX_STRING could be 63).
> As for field sizes, I think 15 is more than adequate for the STX and
> SRX fields.
> You might think that the other fields would be OK at Str31 but consider
> this nightmarish exchange for the ARRL November sweeps:
>=20
> W4/KB1AAA/MM 1234 B W1/KC8ZZZ/MM 71 EMA
> 111111111122222222223333333333
> 123456789012345678901234567890123456789
>=20
> Some nerd operating portable, on a boat, away from his home state, talks
> to another nerd doing the same thing off the coast of Massachusetts. I
> actually have no idea if this is a legal call setup or if this exchange
> would ever happen. But, it is plausible enough that you should probably
> allow it.
>=20
> So, reluctantly, I guess the Str63 is probably a better choice. Then
> again, if
> I had to do this exchange, I'd turn the radio off, get a beer, and read
> the
> paper for a while. :-)
>=20
> I downloaded b16 before I left work tonight. Then, apparently, you
> posted
> b17. Man, you work FAST! :-) I'll check out the new one in the morning.
>=20
> =3D=3D> I should reiterate: what a fantastic job you do with this stuff!
> =3D=3D> It is my pleasure to drop whatever ideas I can to help out. Please
> =3D=3D> feel free to use some, most, all, or none of what I suggest.
> =3D=3D> You're the developer; I'm just the nutty user. :-)
>=20
> -- Scott
>=20
> PS Regarding:
>>> >> 6) document including revised "B. Scott Andersen's Contesting Tips"
>>> >> for the manual.
> I'd be honored to be included. Of course, now that you've got all these
> changes
> in place, I'll need to revise my suggestions!
>=20
>=20
> On Saturday, May 31, 2003, at 04:49 PM, Don Agro wrote:
>=20
>> > Hi Scott,
>> >
>> > On Saturday, May 31, 2003, at 07:13 AM, Don Agro wrote:
>> >
>>> >> 1) review ADIF 2.1.1 and LOTW to finalize spec (above).
>>> >> 2) Add new fields to database.
>>> >> 3) add new fields to log table (display and edit).
>>> >> 4) add new fields to ADIF import/export.
>>> >> 5) add UI support, auto increment etc.
>>> >> 6) document including revised "B. Scott Andersen's Contesting Tips"
>>> >> for the manual.
>> >
>> > I have done steps 1-5 with the following exception -
>> >
>> > There is UI support for SRX autoincrement, and SRX_STRING
>> > The only way to enter STX or STX_STRING is by editing the actual log
>> > entry.
>> > I still need to think about how to do this. Your suggestions are
>> > welcome.
>> >
>> > (I may have mixed up SRX and STX - I made SRX the self generated auto
>> > increment field).
>> >
>> > (I made all the new fields Str31, but perhaps SRX and STX can be 15
>> > chars and SRX_STRING and STX_STRING could be 63).
>> >
>> > <ftp://dogparksoftware.com/MacLoggerDX2.9b17.sit>
>> >
>> > Give it a try and let me know what you think.
>> >
>> >
>> > Best Regards,
>> > Don Agro
>> >
>> > D o g P a r k S o f t w a r e L t d .
>> >
>> > email: dagro@dogparksoftware.com
>> > www: http://www.dogparksoftware.com
>> >
>> > _______________________________________________
>> > DogParkList mailing list
>> > DogParkList@dogparksoftware.com
>> > http://two.pairlist.net/mailman/listinfo/dogparklist
>> >
>> >
> B. Scott Andersen | "Magic is real, unless declared integer."
> bsandersen@mac.com | -- The collected sayings of Wiz Zumwalt
> Acton, Massachusetts | Amateur Radio =3D=3D> ne1rd
>=20
> _______________________________________________
> DogParkList mailing list
> DogParkList@dogparksoftware.com
> http://two.pairlist.net/mailman/listinfo/dogparklist
>=20
--B_3137263258_203592
Content-type: text/html; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: [DogParkList] Re: MacLoggerDX Contest Log Fields</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana">Well, what can I say? You guys are astonishing!<BR>
<BR>
Scott – many thanks for your excellent advice on using MacLoggerDX in=
contests. I knew it could be done – I just didn’t want to reinv=
ent the wheel and your real-world advice is invaluable. Please keep up your =
work on the Cabrillo converter – I will give whatever limited help tha=
t I can (with beta testing etc.).<BR>
<BR>
On another topic, I posted a question to the Ham-Mac list about using a Mac=
to auto send CQ and other common things using sound recordings triggered by=
function keys, much the same way that TRLog does. Do you have any suggestio=
ns from your contesting experience?<BR>
<BR>
Don – once again, you are faster than light at implementing suggestio=
ns from your faithful users. I am a web developer, and have no idea how you =
do it so fast! I can’t wait to start using MacLoggerDX in anger, and b=
eating some of the TRLog boys at their own game :-)<BR>
<BR>
Kinda proves our point about Mac users, doesn’t it? :-)<BR>
<BR>
73 de VA7IRL,<BR>
-- <BR>
Anthony Rodgers<BR>
Email: <FONT COLOR=3D"#0000FF"><U>VA7IRL@rac.ca<BR>
</U></FONT>Cell: 604-340-8295<BR>
Numeric Pager: 1-800-331-6351<BR>
Text Pager: <FONT COLOR=3D"#0000FF"><U>arodgers@txt.bellmobility.ca<BR>
</U></FONT>MSN Messenger ID: <FONT COLOR=3D"#0000FF"><U>arodgers@mac.com<BR>
</U></FONT><BR>
On 5/31/03 6:52 PM, "B. Scott Andersen" <bsandersen@mac.com>=
; wrote:<BR>
<BR>
</FONT><BLOCKQUOTE><FONT FACE=3D"Monaco"><TT>Dear Don,<BR>
<BR>
My goodness. I went into the office for a few hours to catch up on<BR>
some things and look what you've done. I can't leave you alone for<BR>
a minute! :-)<BR>
<BR>
You were exactly right to check the ADIF standard and the LOTW stuff. I<BR>
was going to suggest that (but, of course, you're right on the ball with<BR=
>
this stuff). Actually, putting "Logbook of the World Ready" on yo=
ur <BR>
product<BR>
description would be a nice bragging point.<BR>
<BR>
By the way, the ARRL doesn't have a digital signatu=
re client<BR>
for the Macintosh yet. Did you have any interest in=
checking that <BR>
out once<BR>
they release the source? They claim they are "=
looking for <BR>
volunteers".<BR>
<BR>
<minirant>Of course, it mak=
es me wonder what my ARRL dues are for <BR>
if me<BR>
and my Macintosh are 2nd class ci=
tizens. They've got a LINUX <BR>
client but<BR>
no Macintosh client. Sheesh!</=
minirant><BR>
<BR>
The SRX (received serial number--numeric only) and the SRXString<BR>
(received exchange data) can only be entered manual at the time of the<BR>
QSO. Leaving that as a simple editable field seems fine to me.<BR>
<BR>
The STX (transmitted serial number) is the one field that "must" =
have<BR>
the auto-increment capability. Let's ignore the STXString field for a <BR>
moment.<BR>
Let me make a suggestion about how the implement this (just a draft) <BR>
and we<BR>
can see how much (if any) of my musings are useful.<BR>
<BR>
----<BR>
First, the upper panel (above the tabs) looks really nice right now. I'm<BR=
>
reluctant to add anything up there for any of this unless we really <BR>
can't<BR>
think of another way.<BR>
<BR>
I think we actually talked about this once (back in December) but one <BR>
option<BR>
is to create a tab for control of contest behavior and to setup and <BR>
spawn the<BR>
Cabrillo processor. I'm going to assume that that's not what is going <BR>
to happen.<BR>
[If you do decide to create a "contest" tab, then things get even=
<BR>
easier.]<BR>
<BR>
In the "Prefs" tab there is some open area below the DX Alarms <B=
R>
checkboxes.<BR>
I might suggest two new controls in this small area: a checkbox and a <BR>
text<BR>
field with a label.<BR>
<BR>
+------ Contesting -----------+<BR>
| &=
nbsp;  =
; |<BR>
| Autogen serial #'s [ ] |<BR>
| Next serial # [ ] &=
nbsp;|<BR>
| &=
nbsp;  =
; |<BR>
+-----------------------------+<BR>
<BR>
IF the checkbox is in the unchecked state THEN<BR>
IF the next serial number field is empty THEN<BR>
when the user puts an X there the=
next serial # is set to 1<BR>
ELSE<BR>
when the user puts an X there the=
number appear in the field is <BR>
unaltered<BR>
FI<BR>
ELSE<BR>
when the user unchecks the box any value in the box=
is left unchanged<BR>
FI<BR>
<BR>
The next serial number value is NOT persistent between application <BR>
restarts.<BR>
(You don't need to write it to disk).<BR>
<BR>
The next serial number value is a editable text area but only natural <BR>
numbers<BR>
are allowed. No signs (+/-). No decimal point (.). Only digits. Leading <BR=
>
zeros<BR>
are suppressed/eliminated. [If a user enters "001" you can, at yo=
ur <BR>
option,<BR>
convert that to simply "1".]<BR>
<BR>
When a QSO is logged:<BR>
If the checkbox "autogen serial #'s" is checked=
, then the current <BR>
value of the<BR>
associated text box is written into the serial number sen=
t field of <BR>
the QSO.<BR>
Also, the value in the "Next serial #" text fie=
ld is incremented by <BR>
1. That is,<BR>
if a user were to click on the "Prefs" panel ag=
ain and look at that <BR>
text area<BR>
they would see a "2" in that field after the fi=
rst QSO had been <BR>
logged.<BR>
<BR>
If the checkbox "autogen serial #'s" is NOT che=
cked, no value is <BR>
stamped<BR>
into the serial number sent field. The value in the "=
;Next serial #", <BR>
if any,<BR>
is left unaltered. (This behavior allows people to "=
drop out of a <BR>
contest"<BR>
temporarily and make some QSOs that won't apply toward th=
e contest <BR>
score.<BR>
When they wish to "return to the contest" the n=
umbers pick right up <BR>
where<BR>
they left off.]<BR>
----<BR>
> (I made all the new fields Str31, but perhaps SRX and STX can be 15 <B=
R>
> chars and SRX_STRING and STX_STRING could be 63).<BR>
As for field sizes, I think 15 is more than adequate for the STX and <BR>
SRX fields.<BR>
You might think that the other fields would be OK at Str31 but consider <BR=
>
this nightmarish exchange for the ARRL November sweeps:<BR>
<BR>
W4/KB1AAA/MM 1234 B W1/KC8ZZZ/MM 71 EMA<BR>
111=
111111122222222223333333333<BR>
123456789012345678901234567890123456789<BR>
<BR>
Some nerd operating portable, on a boat, away from his home state, talks<BR=
>
to another nerd doing the same thing off the coast of Massachusetts. I<BR>
actually have no idea if this is a legal call setup or if this exchange<BR>
would ever happen. But, it is plausible enough that you should probably <BR=
>
allow it.<BR>
<BR>
So, reluctantly, I guess the Str63 is probably a better choice. Then <BR>
again, if<BR>
I had to do this exchange, I'd turn the radio off, get a beer, and read <BR=
>
the<BR>
paper for a while. :-)<BR>
<BR>
I downloaded b16 before I left work tonight. Then, apparently, you <BR>
posted<BR>
b17. Man, you work FAST! :-) I'll check out the new one in the mornin=
g.<BR>
<BR>
=3D=3D> I should reiterate: what a fantastic job you do with this stuff!<BR>
=3D=3D> It is my pleasure to drop whatever ideas I can to help out. Please<B=
R>
=3D=3D> feel free to use some, most, all, or none of what I suggest.<BR>
=3D=3D> You're the developer; I'm just the nutty user. :-)<BR>
<BR>
-- Scott<BR>
<BR>
PS Regarding:<BR>
>> 6) document including revised "B. Scott Andersen's Contesting=
Tips" <BR>
>> for the manual.<BR>
I'd be honored to be included. Of course, now that you've got all these <BR=
>
changes<BR>
in place, I'll need to revise my suggestions!<BR>
<BR>
<BR>
On Saturday, May 31, 2003, at 04:49 PM, Don Agro wrote:<BR>
<BR>
> Hi Scott,<BR>
><BR>
> On Saturday, May 31, 2003, at 07:13 AM, Don Agro wrote:<BR>
><BR>
>> 1) review ADIF 2.1.1 and LOTW to finalize spec (above).<BR>
>> 2) Add new fields to database.<BR>
>> 3) add new fields to log table (display and edit).<BR>
>> 4) add new fields to ADIF import/export.<BR>
>> 5) add UI support, auto increment etc.<BR>
>> 6) document including revised "B. Scott Andersen's Contesting=
Tips" <BR>
>> for the manual.<BR>
><BR>
> I have done steps 1-5 with the following exception -<BR>
><BR>
> There is UI support for SRX autoincrement, and SRX_STRING<BR>
> The only way to enter STX or STX_STRING is by editing the actual log <=
BR>
> entry.<BR>
> I still need to think about how to do this. Your suggestions are <BR>
> welcome.<BR>
><BR>
> (I may have mixed up SRX and STX - I made SRX the self generated auto =
<BR>
> increment field).<BR>
><BR>
> (I made all the new fields Str31, but perhaps SRX and STX can be 15 <B=
R>
> chars and SRX_STRING and STX_STRING could be 63).<BR>
><BR>
> <ftp://dogparksoftware.com/MacLoggerDX2.9b17.sit><BR>
><BR>
> Give it a try and let me know what you think.<BR>
><BR>
><BR>
> Best Regards,<BR>
> Don Agro<BR>
><BR>
> D o g P a r k S o f t w a r e L t =
d .<BR>
><BR>
> email: dagro@dogparksoftware.com<BR>
> www: http://www.dogparksoftware.com<BR>
><BR>
> _______________________________________________<BR>
> DogParkList mailing list<BR>
> DogParkList@dogparksoftware.com<BR>
> http://two.pairlist.net/mailman/listinfo/dogparklist<BR>
><BR>
><BR>
B. Scott Andersen | "Magic is real, unless declared =
integer."<BR>
bsandersen@mac.com | -- The collected sayings of Wiz Zumwalt<BR=
>
Acton, Massachusetts | Amateur Radio =3D=3D> ne1rd<BR>
<BR>
_______________________________________________<BR>
DogParkList mailing list<BR>
DogParkList@dogparksoftware.com<BR>
http://two.pairlist.net/mailman/listinfo/dogparklist<BR>
<BR>
</TT></FONT></BLOCKQUOTE><FONT FACE=3D"Monaco"><TT><BR>
</TT></FONT><FONT FACE=3D"Verdana"><BR>
</FONT>
</BODY>
</HTML>
--B_3137263258_203592--