From dagro at dogparksoftware.com  Fri Jan  9 18:40:38 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Fri, 9 Jan 2009 18:40:38 -0500
Subject: [MacLoggerContest] Contesting list
Message-ID: <B13AA951-2D60-4552-9ACD-4F7C84D10B8A@dogparksoftware.com>

I have heard privately from numerous customers that the mass exodus  
(over 300 in less than 24 hours) from the dogpark list was in fact due  
to an inability to read through one more contest oriented thread. The  
majority of people on the list are lurkers and subscribed to hear the  
occasional bit of news about our products or get help in using them. I  
have heard from several contesters that this is a matter of no  
consequence - but this is simply wrong. I would therefore request that  
you post contest related material (including comments about this post)  
to the MacLoggerDX Contest list: <http://seven.pairlist.net/mailman/listinfo/macloggercontest 
 >. It has been there since 2005 but has not had a single post since  
2007.

Thanks,

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Fri Jan  9 18:58:02 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Fri, 9 Jan 2009 18:58:02 -0500
Subject: [MacLoggerContest] Whirlwind (long)
References: <372E9E8D-D1E9-4438-BEB2-E318FAE7B150@mac.com>
Message-ID: <9E667DBC-D12F-41E9-859E-F7A62244FB7A@dogparksoftware.com>

From: "B. Scott Andersen" <bsandersen at mac.com>
Date: January 8, 2009 6:25:48 PM GMT-05:00
To: Dogpark List <dogparklist at dogparksoftware.com>
Subject: [DogParkList] Whirlwind (long)

Wow. I stop paying attention to email for a day and look what happens!

At risk of making a fool of myself (I've not read everything as  
carefully
as I should and the fever from this head-cold has not yet subsided
making me a little thick) here are a couple of observations.

1. Cab-converter is a compliment/add-on to MacLoggerDX. I've been
doing these Cabrillo conversions since I began contesting immediately
after becoming licensed in 2002. After several rewrites the lineage of
software we all now call Cab-converter is nearly 4 years in the field.
I've tried not to have any "overlap" with Don's product--MacLoggerDX
captures the data and Cab-converter packages it into a form suitable
for contest sponsors. I don't look for this relationship to change.

2. Don is giving MacLoggerDX a complete rewrite. I have made it clear
that I believe Cab-converter should also get the same treatment. I would
also like to see at least the possibility of end-user participation in  
the
development of contest support. Don's exactly right: the contesting
group is _small_ within the MacLoggerDX community. A quick check
of the membership list for Cab-converter shows only 116 entries. Some
of these may not be active anymore (it is difficult to say who is  
"actively"
contesting, who is still using the Mac, etc.). That's not very many  
users
for a complex piece of software like MacLoggerDX or Cab-converter!

I don't know if many of you can imagine the many hundreds or thousands
of hours that goes into a significant software development project-- 
only to
have the results spread over such a tiny population. As a self- 
sufficient
group, we've done very well so far mustering development resources
towards getting usable software competitive, at least to some extent,
with that used by our Windows-using counterparts whom number in the
many thousands.

So, during this time of rewrites I would urge all of us to remember that
programming resources are scarce (both Don and I are working alone
on our perspective ends of it) and programming itself is time-consuming
and tedious. Please be patient.

3. The current Cab-converter input is ADIF. I'm not sure if that will  
be the
best choice after Don's rewrite. Instead, it might be better to simply  
access
the relational database Don is using as a backing store for the log. I  
suspect
the log will have columns similar to those identified as "fields" in  
the ADIF
specification--but Don can also break out individual items if that makes
sense. In short--some of the goofy things we've had to do to capture
contest exchange data in the SRX and STX text fields may be better
handled with the New-and-Improved MLDX and its database. If so, this
will make Cab-converter that much better and contest submissions that
much more robust. This is something that Don and I should work out
at some point.

As a side-effect of this, MacLoggerDX may also be able to achieve
data interchange via ADIF with other contesting programs because
our data layout will more closely mimic that used by those other
programs. For example, the SRX_STRING is the only way we can
currently capture TEXT fields. Yet, the ADIF specification has the
following:

CHECK - Contest check for ARRL sweepstakes
CLASS - for Field Day
CNTY - The contacted station's secondary administrative division
COUNTRY - obvious
GRIDSQUARE - for VHF contests and Stew Perry, for example
IOTA - Islands on the Air identifier for the contacted station
ITUZ - ITU Zone of contacted station for CQ WW, etc.
PRECEDENCE - for ARRL SWEEPS
TEN_TEN - 10 10 number

Right now we cram all this stuff into the SRX field as each contest  
demands.
The ARRL CHECK string is particularly urksome. It would be REALLY nice
to sort this stuff out so it went into individual columns and was  
captured at
QSO time with some sensible and streamlined UI. Don is asking for our  
help
on these things. Providing _meaningful_ help will be very hard work  
indeed!
And, given the scarcity of resources on both Don's end and mine there  
are
no guarantees that anything proposed will be implemented. Don takes a
chance every time he spends a few days or a few weeks working on a
particular thing or another that the effort will fall short, not gain  
acceptance,
be ignored, or not help his bottom line. He's brave. We'll need to be  
just
as brave working hard "on spec" (prior to any commitment) organizing our
thoughts if we wish for them to be considered and perhaps implemented.

4. I believe that there are two categories of feature requests  
contesters might
push for:

(*) Data entry and management during the contest
(*) Data import, export, and processing post-contest

The first group consists of database column definitions, data entry  
screen
designs, and contest-specific logic.

The second group consists of import/export to LoTW, eQSL, and other
services, possibly the export of logs or log segments to HTML so that  
they
may be published to the web, and robust interchange between MLDX and
Windows-based programs through ADIF and its continually evolving  
standard.
This second group of feature requests have a broad appeal outside of the
contesting community and would help all MLDX users, not just the  
contesters.

Because the contesting part of the MLDX community is also some of the  
more
heavy users, we should be expected to apply our extra expertise and  
insight
into helping with the non-contesting-specific features as well.

LONG MESSAGE. SORRY.

I typed too long. Sorry. These are my thoughts except for one: Don has  
done
an excellent job supporting the Macintosh community. There are other  
logging
programs out there--even for the Macintosh--yet we don't flood these  
other
vendors email boxes with ideas and demands. We continue to go back to  
Don
because he continues to deliver. Thank you, Don, for your efforts.  
They are
appreciated.

-- Scott (NE1RD and author of Cab-converter)




B. Scott Andersen           | "Magic is real, unless declared integer."
bsandersen -atsign- mac.com | -- The collected sayings of Wiz Zumwalt
Acton, MA (NE1RD)           | http://www.bsandersen.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090109/c0163580/attachment-0001.html>

From dagro at dogparksoftware.com  Fri Jan  9 18:58:06 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Fri, 9 Jan 2009 18:58:06 -0500
Subject: [MacLoggerContest] Whirlwind (long)
References: <D8D6CE3F-00EC-4AC4-A94F-40332C7409ED@dogparksoftware.com>
Message-ID: <0DBEFA46-2B55-4AA0-A807-BD643E1CD0B7@dogparksoftware.com>

Hi Scott,

On 8-Jan-09, at 6:25 PM, B. Scott Andersen wrote:

> 3. The current Cab-converter input is ADIF. I'm not sure if that  
> will be the best choice after Don's rewrite. Instead, it might be  
> better to simply access the relational database Don is using as a  
> backing store for the log. I suspect the log will have columns  
> similar to those identified as "fields" in the ADIF specification-- 
> but Don can also break out individual items if that makes  sense. In  
> short--some of the goofy things we've had to do to capture contest  
> exchange data in the SRX and STX text fields may be better handled  
> with the New-and-Improved MLDX and its database. If so, this will  
> make Cab-converter that much better and contest submissions that  
> much more robust. This is something that Don and I should work out  
> at some point.

Yup - it is plain vanilla SQLite and can be read directly. It is very  
powerful, scaleable and I am very pleased with the way it is working  
out. I will send you  sample .sql file when you are ready, but we may  
be adding more fields as I read ahead :)

> As a side-effect of this, MacLoggerDX may also be able to achieve  
> data interchange via ADIF with other contesting programs because our  
> data layout will more closely mimic that used by those other  
> programs. For example, the SRX_STRING is the only way we can  
> currently capture TEXT fields. Yet, the ADIF specification has the  
> following:
>
> CHECK - Contest check for ARRL sweepstakes
> CLASS - for Field Day
> CNTY - The contacted station's secondary administrative division

Already in MLDX ADIF Export.

> COUNTRY - obvious
> GRIDSQUARE - for VHF contests and Stew Perry, for example

> IOTA - Islands on the Air identifier for the contacted station

Already in MLDX ADIF Expor.

> ITUZ - ITU Zone of contacted station for CQ WW, etc.
> PRECEDENCE - for ARRL SWEEPS
> TEN_TEN - 10 10 number

In MacLoggerDX for Cocoa ADIF Export.

All good suggestions Scott, thanks.

> Right now we cram all this stuff into the SRX field as each contest  
> demands. The ARRL CHECK string is particularly urksome. It would be  
> REALLY nice to sort this stuff out so it went into individual  
> columns and was captured at QSO time with some sensible and  
> streamlined UI. Don is asking for our help on these things.  
> Providing _meaningful_ help will be very hard work indeed! And,  
> given the scarcity of resources on both Don's end and mine there are  
> no guarantees that anything proposed will be implemented. Don takes  
> a chance every time he spends a few days or a few weeks working on a  
> particular thing or another that the effort will fall short, not  
> gain acceptance, be ignored, or not help his bottom line. He's  
> brave. We'll need to be just as brave working hard "on spec" (prior  
> to any commitment) organizing our thoughts if we wish for them to be  
> considered and perhaps implemented.

Sounds like a sensible approach. Adding a carefully thought out list  
of data inputs, corresponding database fields and ADIF outputs is not  
a huge task - picking the right ones and presenting them usefully is :)

The Contest panel belongs to the contesters. Within reason, I will put  
there whatever makes sense to the majority of contesters.

> 4. I believe that there are two categories of feature requests  
> contesters might
> push for:
>
> (*) Data entry and management during the contest
> (*) Data import, export, and processing post-contest
>
> The first group consists of database column definitions, data entry  
> screen designs, and contest-specific logic.
>
> The second group consists of import/export to LoTW, eQSL, and other  
> services, possibly the export of logs or log segments to HTML so  
> that they may be published to the web, and robust interchange  
> between MLDX and Windows-based programs through ADIF and its  
> continually evolving standard. This second group of feature requests  
> have a broad appeal outside of the contesting community and would  
> help all MLDX users, not just the contesters.

I agree completely.

> Because the contesting part of the MLDX community is also some of  
> the more heavy users, we should be expected to apply our extra  
> expertise and insight into helping with the non-contesting-specific  
> features as well.
>
> LONG MESSAGE. SORRY.
>
> I typed too long. Sorry. These are my thoughts except for one: Don  
> has done an excellent job supporting the Macintosh community. There  
> are other logging programs out there--even for the Macintosh--yet we  
> don't flood these other vendors email boxes with ideas and demands.  
> We continue to go back to Don because he continues to deliver. Thank  
> you, Don, for your efforts. They are appreciated.

Thank you Scott.

73 Don Agro VE3VRW


_______________________________________________
DogParkList mailing list
DogParkList at dogparksoftware.com
http://two.pairlist.net/mailman/listinfo/dogparklist


73 Don Agro VE3VRW

D o g   P a r k   S o f t w a r e   L t d .

email: dagro at dogparksoftware.com
   www: http://www.dogparksoftware.com
     iChat AV:dogpark at mac.com


From dagro at dogparksoftware.com  Sat Jan 10 16:32:23 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 10 Jan 2009 16:32:23 -0500
Subject: [MacLoggerContest] Notes from the Skunworks:Icom
Message-ID: <63120D53-CCD7-49ED-900C-8CF4C3B2384C@dogparksoftware.com>

While Chen was helping me debug MacLoggerDX for Cocoa today with the  
mH Router (It's working! Thanks Chen) I discovered a bug that has been  
in MacLoggerDX since day 1!

So, if you are using an Icom with MacLoggerDX and have been suffering  
occasional (or frequent) disconnects, please give v4.3.6b16 a try and  
let me know if it helps.

Thanks,

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Sat Jan 10 23:12:41 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 10 Jan 2009 23:12:41 -0500
Subject: [MacLoggerContest] Notes from the Skunworks:Icom
In-Reply-To: <63120D53-CCD7-49ED-900C-8CF4C3B2384C@dogparksoftware.com>
References: <63120D53-CCD7-49ED-900C-8CF4C3B2384C@dogparksoftware.com>
Message-ID: <AE1CF03E-D059-4EDE-BEAF-E50915331FCC@dogparksoftware.com>

On 10-Jan-09, at 4:32 PM, Don Agro wrote:

> So, if you are using an Icom with MacLoggerDX and have been  
> suffering occasional (or frequent) disconnects, please give  
> v4.3.6b16 a try and let me know if it helps.

Oops! Better make that b18

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Sat Jan 24 11:29:01 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 24 Jan 2009 11:29:01 -0500
Subject: [MacLoggerContest] MacLoggerDX v5.0 Contesting comments
In-Reply-To: <22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
References: <48FB5B19-9356-49C5-B9E7-E5C3D7B3A827@dogparksoftware.com>
	<22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
Message-ID: <65F4D42B-C916-48FF-98D1-3C147F422362@dogparksoftware.com>

Hi David,

I have moved this to the contest list - I don't want a repeat of last  
week's fiasco.

On 24-Jan-09, at 11:03 AM, David Ferrington, M0XDF wrote:

> Really was hoping for a less busy contest entry, without lots of  
> address fields etc (most UK contest forbid using lookup, or at least  
> make it assisted section if you do).

The layout was designed by Scott Andersen (NE1RD) an avid contester  
and author of cab_converter - but then I have never met 2 contesters  
who can agree with one another :)

> Was hoping for a simpler keystroke to log call, like command-return  
> and on contest, tabbing past last field to be filled in would log  
> and place you back to call field - perhaps I'm looking for to much.

Perhaps you are looking for problems instead of solutions ?

<command>K clears and takes you back to call - as it always did.

On 11-Jan-09, at 3:36 PM, B. Scott Andersen wrote:

> So: here's how a QSO would go.
>
> CMD-K clears Call, Recv text, and Recv S/N. Focus left in Call
> The clock continues to tick while I call CQ
> Somebody answers my CQ. I type in the call.
> I hit CMD-L to lookup. All that great data gets filled in.
> Tab. I copy his exchange data into the Recv text area. OR!
> Tab Tab. I copy his exchange serial number into the Recv S/N area.
> Shift-CMD-L to log it.  This clears call, Recv text, and Recv S/N.  
> Focus is left in Call.
> I'm ready to go again.

73 Don Agro VE3VRW

D o g   P a r k   S o f t w a r e   L t d .

email: dagro at dogparksoftware.com
   www: http://www.dogparksoftware.com
     iChat AV:dogpark at mac.com


From M0XDF at Alphadene.co.uk  Sat Jan 24 11:53:20 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Sat, 24 Jan 2009 16:53:20 +0000
Subject: [MacLoggerContest] MacLoggerDX v5.0 Contesting comments
In-Reply-To: <65F4D42B-C916-48FF-98D1-3C147F422362@dogparksoftware.com>
References: <48FB5B19-9356-49C5-B9E7-E5C3D7B3A827@dogparksoftware.com>
	<22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
	<65F4D42B-C916-48FF-98D1-3C147F422362@dogparksoftware.com>
Message-ID: <3109BF8D-4DDA-4F06-9F5F-D97AEE7EA441@Alphadene.co.uk>

no problem Don, completely understand
and ok on Scott - I also understand about no 2 contesters agreeing.

Just that I don't tend to lookup calls - it was slower, but I notice  
MLDX5 is faster.
And then again, your not allowed too in some contests. So just enter  
call, std 59 both ways, pass a serial number (hence my previous  
request for the serial number to be BIG and location (sometimes just a  
serial number) and log. Then back to call again.
And in that order, so tab order would ideally be (for me), Rcvd sn,  
Rcvd (to put locator in).
  And the field positions would be changed accordingly, so the RSTS,  
Sent Sn, followed by Sent.

however as you say, I wonder how many others would agree.
-- 
Dear God, Did you mean for the giraffe to look like that or was it an
accident? -Norma [Children's Letters to God, 1991]

On 24 Jan 2009, at 16:29, Don Agro wrote:

> Hi David,
>
> I have moved this to the contest list - I don't want a repeat of  
> last week's fiasco.
>
> On 24-Jan-09, at 11:03 AM, David Ferrington, M0XDF wrote:
>
>> Really was hoping for a less busy contest entry, without lots of  
>> address fields etc (most UK contest forbid using lookup, or at  
>> least make it assisted section if you do).
>
> The layout was designed by Scott Andersen (NE1RD) an avid contester  
> and author of cab_converter - but then I have never met 2 contesters  
> who can agree with one another :)
>
>> Was hoping for a simpler keystroke to log call, like command-return  
>> and on contest, tabbing past last field to be filled in would log  
>> and place you back to call field - perhaps I'm looking for to much.
>
> Perhaps you are looking for problems instead of solutions ?
>
> <command>K clears and takes you back to call - as it always did.
>
> On 11-Jan-09, at 3:36 PM, B. Scott Andersen wrote:
>
>> So: here's how a QSO would go.
>>
>> CMD-K clears Call, Recv text, and Recv S/N. Focus left in Call
>> The clock continues to tick while I call CQ
>> Somebody answers my CQ. I type in the call.
>> I hit CMD-L to lookup. All that great data gets filled in.
>> Tab. I copy his exchange data into the Recv text area. OR!
>> Tab Tab. I copy his exchange serial number into the Recv S/N area.
>> Shift-CMD-L to log it.  This clears call, Recv text, and Recv S/N.  
>> Focus is left in Call.
>> I'm ready to go again.
>

From bsandersen at mac.com  Sat Jan 24 12:53:37 2009
From: bsandersen at mac.com (B. Scott Andersen)
Date: Sat, 24 Jan 2009 12:53:37 -0500
Subject: [MacLoggerContest] Contest entry screen specification
In-Reply-To: <22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
References: <48FB5B19-9356-49C5-B9E7-E5C3D7B3A827@dogparksoftware.com>
	<22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
Message-ID: <C557B5DE-0519-41AC-95D5-608629199127@mac.com>

Colleagues,

I would like to reiterate Don's request that these discussions appear  
on the
Contesting list ONLY so that we do not cross-post to uninterested  
groups.
That's the Netiquette way!

Below is the very specific suggestions that I gave Don for the contest  
data entry screen.
The data entry screen is a little more "busy" than some contest-only  
logging programs
might demand, but the extra information (name, QTH info, etc.) are  
helpful when logging
even in a contest (or so I find). Certainly the mapping of the call  
sign to country is very
helpful in DX contests and I contend mapping call sign to state is  
helpful for US contests.
The other information presented (name, street, city) is not  
distracting, IMHO, and
because this screen might be used for DXpeditions--and sometimes  
you'll be working
somebody who sounds familiar, but in the heat of the pile-up you  
didn't recognize the
call--the full information popping up is actually very helpful! I  
confess there were several
pile-ups while I was on Montserrat where a friend from the local club  
called, I typed in
the (very familiar) call sign, but did not recognize him until I did  
the lookup. So, while
it might not be key for contesting, I contend that this panel could be  
used for quick entry
for DXing, too, and it is very helpful to have the QTH information  
present.

The above handles the left-side of the box.

Now to the right side. The following is an exact copy of the message I  
sent to Don along
with the details of the specification, rationale, and some additional  
thoughts that I had,
but ultimately dropped. Don has asked the contesting community for a  
specification of
what might be helpful for contesters--and I responded with a  
lightweight software
specification with rationale. The fact that the new contesting data  
entry screen looks very
much like the one I designed and specified is a testament to Don's  
willingness to listen
and accept solid, specific, unambiguous, and detailed suggestions. For  
that, I gladly
give him my thanks!

The design I sent Don follows. Questions about why I asked Don for these
specific things are best sent to me, probably. After all, Don just did  
what we (I)
asked. {grin}

Here's the thing I sent Don:





Don,

Here's my idea. If we are confined to just one panel then this is a  
good start IMHO.

1. Tabs move between the following fields:
	Call --> Recv text --> Recv S/N --> Sent text --> Sent S/N --> RSTR -- 
 > RSTS

2. CMD-K (clear) clears call, Recv text, and Recv S/N. Focus is left  
in Call.

3. Lookup doesn't change anything in the data entry fields

4. Logging clears like CMD-K. Again, focus is left in the Call to  
begin again.

5. If enabled, serial number increment for Sent S/N happens when Logging
as with the current software.

6. The clock (lower right) should increment in real time, not just  
when the lookup
is preformed. Near the beginning and end of the contest it is  
important to know
the time and log it closely to prevent accusations of "rubber clocking".

7. Power could be set elsewhere (preferences panel?) or set here. In  
some ways,
having it set elsewhere might be preferable -- just reminding the  
operator of the
category they are playing in.

-=-=-

So: here's how a QSO would go.

CMD-K clears Call, Recv text, and Recv S/N. Focus left in Call
The clock continues to tick while I call CQ
Somebody answers my CQ. I type in the call.
I hit CMD-L to lookup. All that great data gets filled in.
Tab. I copy his exchange data into the Recv text area. OR!
Tab Tab. I copy his exchange serial number into the Recv S/N area.
Shift-CMD-L to log it.  This clears call, Recv text, and Recv S/N.  
Focus is left in Call.
I'm ready to go again.

I toyed with the idea of making the focus change from Call to Recv S/N
selectable with a checkbox option--and it still might be a good idea-- 
but
this gets us close.

Frequency/band/mode information is up top so you know where you're  
playing.
The clock, important but not critical until the end of the contest, is  
still in an obvious
place but well away from the main area of activity.

The ITC and CQ Zone information appears directly below the call so  
they can be
seen in a single glance after lookup and BEFORE exchange capture. This  
is handy
for any contest like CQ WW.

Users can repeatedly log QSOs without touching the mouse--just keyboard,
keyboard, keyboard. That's good. If your hand needs to leave the  
keyboard
during a contest is should be going for the radio, not the mouse.

The data handling (using the ADIF STX, SRX, STXn, and SRXn fields) is
unchanged from the current incarnation of MLDX. There is little  
incentive,
therefore, to alter the current Cab-converter approach of consuming an
exported ADIF file. So, my world will remain the same.

That is my thinking on the design. Your thoughts?

-- Scott (NE1RD)

B. Scott Andersen           | "Magic is real, unless declared integer."
bsandersen -atsign- mac.com | -- The collected sayings of Wiz Zumwalt
Acton, MA (NE1RD)           | http://www.bsandersen.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090124/9fea5abf/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: contest-layout-bsa.png
Type: image/png
Size: 64720 bytes
Desc: not available
Url : <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090124/9fea5abf/attachment-0001.png>

From dagro at dogparksoftware.com  Sat Jan 24 13:00:09 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 24 Jan 2009 13:00:09 -0500
Subject: [MacLoggerContest] MacLoggerContest post from
	bsandersen@mac.com requires approval
In-Reply-To: <mailman.1.1232819629.56726.macloggercontest@dogparksoftware.com>
References: <mailman.1.1232819629.56726.macloggercontest@dogparksoftware.com>
Message-ID: <8FCCA899-680B-49CE-AF84-6B3A81B16512@dogparksoftware.com>

Hi Scott,

On 24-Jan-09, at 12:53 PM, macloggercontest-owner at dogparksoftware.com  
wrote:

> Here's the thing I sent Don:

Sorry Scott, looks like the list software scrubbed the attachment.

I have put it here: <www.dogparksoftware.com/contest-layout-bsa.png>


73 Don Agro VE3VRW

D o g   P a r k   S o f t w a r e   L t d .

email: dagro at dogparksoftware.com
   www: http://www.dogparksoftware.com
     iChat AV:dogpark at mac.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090124/4e873d53/attachment.html>

From M0XDF at Alphadene.co.uk  Sat Jan 24 18:24:56 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Sat, 24 Jan 2009 23:24:56 +0000
Subject: [MacLoggerContest] Contest entry screen specification
In-Reply-To: <C557B5DE-0519-41AC-95D5-608629199127@mac.com>
References: <48FB5B19-9356-49C5-B9E7-E5C3D7B3A827@dogparksoftware.com>
	<22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
	<C557B5DE-0519-41AC-95D5-608629199127@mac.com>
Message-ID: <18439814-E4DD-4DDD-AA6A-D1849AFFE667@Alphadene.co.uk>

Ok, macloggercontest it is. As I said to Don, this is intended to be  
constructive criticism and not a moan, however, I will find myself  
jumping around quite a bit as it is - at least until AppleScript is  
enabled and I can use XKeys to move around.
Please see my embedded comments below:
-- 
It is almost impossible to carry the torch of truth through a crowd  
without
singeing somebody's beard. -George Christopher Lichtenberg, scientist  
and
philosopher (1742-1799)

On 24 Jan 2009, at 17:53, B. Scott Andersen wrote:
> Below is the very specific suggestions that I gave Don for the  
> contest data entry screen.
> The data entry screen is a little more "busy" than some contest-only  
> logging programs
> might demand, but the extra information (name, QTH info, etc.) are  
> helpful when logging

Yes it may be. And after playing a little, if I clear the fields and  
turn off lookup, the field labels don't really get in the way. In most  
of the contests I've done, and I admit its not many, you can't use  
aids like Internet lookup unless you are prepared to move into an  
assisted section.

> Now to the right side.

Picking out the serial number I have to send (assuming everything else  
is rubberstamp) is not so easy when the field is in the middle of two  
other fields and to the right of something with text, and I find  
contesting hard enough as it is :-(

> The design I sent Don follows. Questions about why I asked Don for  
> these
> specific things are best sent to me, probably. After all, Don just  
> did what we (I)
> asked. {grin}
More below....
>
> Here's the thing I sent Don:
> 1. Tabs move between the following fields:
> 	Call --> Recv text --> Recv S/N --> Sent text --> Sent S/N --> RSTR  
> --> RSTS
>
OK, we must work very different contests, because although I'm  
searching & pouncing, not running, in every contest I've ever been in  
(and I admit not that many), the sequence is
Recv Call -> Recv RST (normally 59, but in VHF, not always) -> Recv S/ 
N -> Recv text (or something, sometimes 2 or 3 bits of into)
Then I reply with
Sent RST -> Sent S/N -> Sent text  --> Log it

So 'I' would prefer the fields to be in that order and the tab to  
follow it/

Since the contesters are on here, would other people chime in and  
describe their typical exchange please. I've straw polled the UK  
Contest reflector and replies indicate that the exchange is more  
likely to be as stated by me above. However, they also acknowledge  
that we do tend to fill in fields as we hear them, so being able to  
jump straight to a field with a hot key (function key as described  
below) is good too.

> 2. CMD-K (clear) clears call, Recv text, and Recv S/N. Focus is left  
> in Call.
OK, but if we could use Return as well as tab and Return on the last  
field completed, would log and go to Call, it's even easier and  
faster. CMD-K is not a simple keystroke (especially if your left  
handed) and you still have to use cmd-shift-L to log first, that's  
even harder and now two keystrokes. If on the last field that needed  
completion, the return logged and cleared fields and took you to call  
entry, you've done it all in one big (literally) key-press. And Tab  
remains to go back around the fields again. Return will always log as  
soon as all required fields as complete (brings us back to being able  
to configure which fields we need). This was also a comment from UK- 
Contest.

>
> 7. Power could be set elsewhere (preferences panel?) or set here. In  
> some ways,
> having it set elsewhere might be preferable -- just reminding the  
> operator of the
> category they are playing in.
Or as with K3, reads what I've actually set it too - nice if I could  
set it in MLDX and have K3 change, but that's not important right now.
>
> -=-=-
>
> So: here's how a QSO would go.
>
> CMD-K clears Call, Recv text, and Recv S/N. Focus left in Call
> The clock continues to tick while I call CQ
> Somebody answers my CQ. I type in the call.
> I hit CMD-L to lookup. All that great data gets filled in.
> Tab. I copy his exchange data into the Recv text area. OR!
> Tab Tab. I copy his exchange serial number into the Recv S/N area.
> Shift-CMD-L to log it.  This clears call, Recv text, and Recv S/N.  
> Focus is left in Call.
> I'm ready to go again.
>

Ok, for me, who S&P, it's -
use PowerMate to move up and down band
hear a CQ, maybe get part or all of callsign, or some other part of  
the exchange (locator for instance)
use cmd-k to get into detail panel (easiest way) and tab to right  
field for that data or mouse to it (too many keyclicks away from  
field, no function keys to get there and no Apple Script yet)
move to call sign field since that's likely to be what I hear next
complete rest of details, fill in and send outgoing exchange
log it with (well in Classic, a script to Log, Clear fields and move  
to VFO) - sorry, but cmd-shift-l is not a key combo I like - why not  
something much simpler, like cmd-return or even just enter (enter  
being on a keypad), why not a number of possible keystrokes?
go back to VFO to move up or down band again - no point clearing  
fields, the next call may be close or in same locator

> I toyed with the idea of making the focus change from Call to Recv S/N
> selectable with a checkbox option--and it still might be a good  
> idea--but
> this gets us close.
please don't bother, you never can tell what one hears first, I'd  
rather have function keys to get to each field I have to enter - yes  
XKeys helps, but because it has to launch an apple script, it takes  
time - I'd rather have assignable function keys for each field I need  
to go to.
>


> Users can repeatedly log QSOs without touching the mouse--just  
> keyboard,
> keyboard, keyboard. That's good. If your hand needs to leave the  
> keyboard
> during a contest is should be going for the radio, not the mouse.
Sure, but I defy someone not to touch the mouse sometime! :)
>
> The data handling (using the ADIF STX, SRX, STXn, and SRXn fields) is
> unchanged from the current incarnation of MLDX. There is little  
> incentive,
> therefore, to alter the current Cab-converter approach of consuming an
> exported ADIF file. So, my world will remain the same.
That's fine, but without at least one more field, not all contests can  
be achieved (I've been considering getting in touch to add a lot more  
RSGB contests to CC and to find out what I need to do, to do it, it  
will require a different output format too).
>
> That is my thinking on the design. Your thoughts?
As above. However if you want to pursue this, don't go on the above,  
I'll write an RFC.
73 de M0XDF

>
> -- Scott (NE1RD)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090124/6051c5e8/attachment.htm>

From bsandersen at mac.com  Sat Jan 24 19:27:40 2009
From: bsandersen at mac.com (B. Scott Andersen)
Date: Sat, 24 Jan 2009 19:27:40 -0500
Subject: [MacLoggerContest] Contest entry screen specification
In-Reply-To: <18439814-E4DD-4DDD-AA6A-D1849AFFE667@Alphadene.co.uk>
References: <48FB5B19-9356-49C5-B9E7-E5C3D7B3A827@dogparksoftware.com>
	<22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
	<C557B5DE-0519-41AC-95D5-608629199127@mac.com>
	<18439814-E4DD-4DDD-AA6A-D1849AFFE667@Alphadene.co.uk>
Message-ID: <2F267904-8E8A-45BF-B4FF-3F92EDF103D7@mac.com>

Good evening. I'm sure I've not addressed everything,
but I've tried to expand upon my previous explanations
and clarify my thinking on those points you've raised.

Lots of stuff in-line below.

-- Scott (NE1RD)


On Jan 24, 2009, at 6:24 PM, David Ferrington, M0XDF wrote:

> Ok, macloggercontest it is. As I said to Don, this is intended to be  
> constructive criticism and not a moan, however, I will find myself  
> jumping around quite a bit as it is - at least until AppleScript is  
> enabled and I can use XKeys to move around.
> Please see my embedded comments below:
> -- 
> It is almost impossible to carry the torch of truth through a crowd  
> without
> singeing somebody's beard. -George Christopher Lichtenberg,  
> scientist and
> philosopher (1742-1799)
>
> On 24 Jan 2009, at 17:53, B. Scott Andersen wrote:
>> Below is the very specific suggestions that I gave Don for the  
>> contest data entry screen.
>> The data entry screen is a little more "busy" than some contest- 
>> only logging programs
>> might demand, but the extra information (name, QTH info, etc.) are  
>> helpful when logging
>
> Yes it may be. And after playing a little, if I clear the fields and  
> turn off lookup, the field labels don't really get in the way. In  
> most of the contests I've done, and I admit its not many, you can't  
> use aids like Internet lookup unless you are prepared to move into  
> an assisted section.

Use of a local copy of the Super Check Partial database or the QRZ CD  
ROM is not cheating.
Further, logging programs often present information associated with a  
call sign gathered from
previous encounters (such as the exchange given in last year's  
contest).  None of these will
put you in the "assisted" category since they do not assist you in  
finding people on the air;
they simply help collaborate information you have received on the air.
>
>> Now to the right side.
>
> Picking out the serial number I have to send (assuming everything  
> else is rubberstamp) is not so easy when the field is in the middle  
> of two other fields and to the right of something with text, and I  
> find contesting hard enough as it is :-(

My suggested design put it so the eye could glance to the right edge  
and see the serial Number.
As for it being to the right of something with text, all the labels  
are positioned to the left of the
field they label. I am not sure what alternative you would suggest.

>
>> The design I sent Don follows. Questions about why I asked Don for  
>> these
>> specific things are best sent to me, probably. After all, Don just  
>> did what we (I)
>> asked. {grin}
> More below....
>>
>> Here's the thing I sent Don:
>> 1. Tabs move between the following fields:
>> 	Call --> Recv text --> Recv S/N --> Sent text --> Sent S/N -->  
>> RSTR --> RSTS
>>
> OK, we must work very different contests, because although I'm  
> searching & pouncing, not running, in every contest I've ever been  
> in (and I admit not that many), the sequence is
> Recv Call -> Recv RST (normally 59, but in VHF, not always) -> Recv  
> S/N -> Recv text (or something, sometimes 2 or 3 bits of into)
> Then I reply with
> Sent RST -> Sent S/N -> Sent text  --> Log it
>
> So 'I' would prefer the fields to be in that order and the tab to  
> follow it/
>
> Since the contesters are on here, would other people chime in and  
> describe their typical exchange please. I've straw polled the UK  
> Contest reflector and replies indicate that the exchange is more  
> likely to be as stated by me above. However, they also acknowledge  
> that we do tend to fill in fields as we hear them, so being able to  
> jump straight to a field with a hot key (function key as described  
> below) is good too.

Perhaps we do work different contests. When I am able (which has not  
been often recently)
I work CQ WW, ARRL SS, CQ WPX, CQ VHF, NAQP, NEQP, ARRL 10m, and some  
other
QSO parties. For these and others the RST sent and received is 59 or  
599.
That is: the RST is set at 59 or 599 before the contest and is never  
touched.  Everybody is 59.
So, there is no reason to tab around and even touch these entries  
during most/nearly-all contests.

Whether S/N or Text Exchange should be first after the call sign is  
something that could be debated.
I spent some considerable time thinking about this and made good  
arguments for both. In the end,
I decided that more contests exchange text and only text than exchange  
only serial numbers. For
those contests that expect both, Shift-Tab can move you back. Ugly, I  
know, but if we are only
given one screen and tab configuration we will have to make  
compromises and some contests
will have smoother entry sequences than others.

>
>> 2. CMD-K (clear) clears call, Recv text, and Recv S/N. Focus is  
>> left in Call.
> OK, but if we could use Return as well as tab and Return on the last  
> field completed, would log and go to Call, it's even easier and  
> faster. CMD-K is not a simple keystroke (especially if your left  
> handed) and you still have to use cmd-shift-L to log first, that's  
> even harder and now two keystrokes. If on the last field that needed  
> completion, the return logged and cleared fields and took you to  
> call entry, you've done it all in one big (literally) key-press. And  
> Tab remains to go back around the fields again. Return will always  
> log as soon as all required fields as complete (brings us back to  
> being able to configure which fields we need). This was also a  
> comment from UK-Contest.

My suggestion was consistent with the current keystroke mappings of  
the Pre-Cocoa MLDX.
I have worked both contests and DXpeditions with the CMD-K type SHIFT- 
CMD-L and found
Don's original keyboard shortcut definitions to be satisfactory. Well,  
that's one man's opinion
I guess. It isn't clear to me why one who is left-handed would find  
any particular keystroke
combination more-or-less difficult than someone right-handed. Why  
would that be? I always
thought touch typing with fingers on both hands fully engaged was an  
equal art for both
righty's and lefty's!

I do believe that logging and clearing should be two different  
operations. When running
one might log AB1HB and then the calling station comes back and says,  
"Negative, negative,
the calls is AB1HD!" At that point you do NOT want to re-enter all the  
captured information,
you really want to just update the call and log again. Automatic  
clearing would preclude this
use case. It happens often enough that a deliberate clear is  
warranted, IMHO.

>
>>
>> 7. Power could be set elsewhere (preferences panel?) or set here.  
>> In some ways,
>> having it set elsewhere might be preferable -- just reminding the  
>> operator of the
>> category they are playing in.
> Or as with K3, reads what I've actually set it too - nice if I could  
> set it in MLDX and have K3 change, but that's not important right now.

I don't really care who sets the number. I just thought it would be  
helpful to see what
power was nominally used.

>
>>
>> -=-=-
>>
>> So: here's how a QSO would go.
>>
>> CMD-K clears Call, Recv text, and Recv S/N. Focus left in Call
>> The clock continues to tick while I call CQ
>> Somebody answers my CQ. I type in the call.
>> I hit CMD-L to lookup. All that great data gets filled in.
>> Tab. I copy his exchange data into the Recv text area. OR!
>> Tab Tab. I copy his exchange serial number into the Recv S/N area.
>> Shift-CMD-L to log it.  This clears call, Recv text, and Recv S/N.  
>> Focus is left in Call.
>> I'm ready to go again.
>>
>
> Ok, for me, who S&P, it's -
> use PowerMate to move up and down band
> hear a CQ, maybe get part or all of callsign, or some other part of  
> the exchange (locator for instance)
> use cmd-k to get into detail panel (easiest way) and tab to right  
> field for that data or mouse to it (too many keyclicks away from  
> field, no function keys to get there and no Apple Script yet)
> move to call sign field since that's likely to be what I hear next
> complete rest of details, fill in and send outgoing exchange
> log it with (well in Classic, a script to Log, Clear fields and move  
> to VFO) - sorry, but cmd-shift-l is not a key combo I like - why not  
> something much simpler, like cmd-return or even just enter (enter  
> being on a keypad), why not a number of possible keystrokes?
> go back to VFO to move up or down band again - no point clearing  
> fields, the next call may be close or in same locator
>
>> I toyed with the idea of making the focus change from Call to Recv  
>> S/N
>> selectable with a checkbox option--and it still might be a good  
>> idea--but
>> this gets us close.
> please don't bother, you never can tell what one hears first, I'd  
> rather have function keys to get to each field I have to enter - yes  
> XKeys helps, but because it has to launch an apple script, it takes  
> time - I'd rather have assignable function keys for each field I  
> need to go to.
>>
>
>
>> Users can repeatedly log QSOs without touching the mouse--just  
>> keyboard,
>> keyboard, keyboard. That's good. If your hand needs to leave the  
>> keyboard
>> during a contest is should be going for the radio, not the mouse.
> Sure, but I defy someone not to touch the mouse sometime! :)

Obviously this is a goal.

>
>>
>> The data handling (using the ADIF STX, SRX, STXn, and SRXn fields) is
>> unchanged from the current incarnation of MLDX. There is little  
>> incentive,
>> therefore, to alter the current Cab-converter approach of consuming  
>> an
>> exported ADIF file. So, my world will remain the same.
> That's fine, but without at least one more field, not all contests  
> can be achieved (I've been considering getting in touch to add a lot  
> more RSGB contests to CC and to find out what I need to do, to do  
> it, it will require a different output format too).

One of the worst for tedium is the ARRL SS exchange:
* serial number
* precedence
* callsign
* check (last two digits of first year licensed)
* ARRL/RAC section

and all this goes into the STX / SRX fields (in an order specified by  
the Cab-converter manual).
I would be delighted if these were broken into separate fields, but as  
it stands today we have
MLDX and Cab-converter handling this contest, even with all this stuff  
in one field. If there is
another contest even worse than this one (besides those contests where  
they read back
previous QSOs) I'd like to know about it. Then again, don't bother,  
Cab-converter isn't going
to support it anyway. {grin}


>>
>> That is my thinking on the design. Your thoughts?
> As above. However if you want to pursue this, don't go on the above,  
> I'll write an RFC.
> 73 de M0XDF
>
>>
>> -- Scott (NE1RD)

B. Scott Andersen           | "Magic is real, unless declared integer."
bsandersen -atsign- mac.com | -- The collected sayings of Wiz Zumwalt
Acton, MA (NE1RD)           | http://www.bsandersen.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090124/d85ae990/attachment.html>

From M0XDF at Alphadene.co.uk  Sat Jan 24 20:05:13 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Sun, 25 Jan 2009 01:05:13 +0000
Subject: [MacLoggerContest] Contest entry screen specification
In-Reply-To: <2F267904-8E8A-45BF-B4FF-3F92EDF103D7@mac.com>
References: <48FB5B19-9356-49C5-B9E7-E5C3D7B3A827@dogparksoftware.com>
	<22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
	<C557B5DE-0519-41AC-95D5-608629199127@mac.com>
	<18439814-E4DD-4DDD-AA6A-D1849AFFE667@Alphadene.co.uk>
	<2F267904-8E8A-45BF-B4FF-3F92EDF103D7@mac.com>
Message-ID: <6535477D-3D40-47E5-BF6F-3B4CBBFC6E95@Alphadene.co.uk>

and mine to yours - we could spend all year going on like this!
--  
They are ill discoverers that think there is no land, when they can  
see nothing but sea.
-Francis Bacon, essayist, philosopher, and statesman (1561-1626)

On 25 Jan 2009, at 00:27, B. Scott Andersen wrote:
> Use of a local copy of the Super Check Partial database or the QRZ  
> CD ROM is not cheating.
> Further, logging programs often present information associated with  
> a call sign gathered from
> previous encounters (such as the exchange given in last year's  
> contest).  None of these will
> put you in the "assisted" category since they do not assist you in  
> finding people on the air;
> they simply help collaborate information you have received on the air.

I stand corrected than and will have to double check my understanding,  
I was thinking of  General RSGB rules, which state:
b) A single-operator station is operated by one person, who receives  
no assistance whatsoever from any other person in operating, log- 
keeping, checking and so on, and who does not receive notification of  
callsign information by packet, telnet, telephone or any other method  
including skimmer and skimmer-like technologies.

I'll check up on that and see if it covers SCP/DXCluster used by  
yourself etc.

> My suggested design put it so the eye could glance to the right edge  
> and see the serial Number.
you've got better eyes that me - or better trained anyway :-)

> As for it being to the right of something with text, all the labels  
> are positioned to the left of the
> field they label.
I ment that its to the right of the Recv S/N number, easiy to look at  
the wrong one and since they will both be in standard text, easiy to  
get confused. I've done it a few times with MLDX classic and have to  
be very careful.

> I am not sure what alternative you would suggest.

a layout of

Recv RST [__]         Recv sn [_____]
Recv Txt  [____________________]

Sent RST [__]     Sent sn [00012] -- this last in bigger font and bold
Sent Txt  [____________________]

however, this is where things get difficult, because of people's way  
of working etc - I expect if you were 'running' you'd want it as

Sent RST [__]     Sent sn [00012] -- this last in bigger font and bold
Sent Txt  [____________________]

Recv RST [__]         Recv sn [_____]
Recv Txt  [____________________]

I accept you can't please all of theops, all of the time :-(

>

> Perhaps we do work different contests. When I am able (which has not  
> been often recently)
> I work CQ WW, ARRL SS, CQ WPX, CQ VHF, NAQP, NEQP, ARRL 10m, and  
> some other
> QSO parties. For these and others the RST sent and received is 59 or  
> 599.
> That is: the RST is set at 59 or 599 before the contest and is never  
> touched.  Everybody is 59.
> So, there is no reason to tab around and even touch these entries  
> during most/nearly-all contests.

But not in most VHF contests - at least in Europe, where the RST (ok  
just RS) is important, in some cases checked and gives an indication  
of how likley you are to get around at the edge. I fully accept that  
most HF contests don't do this, even some VHF ones don't. Anything UHF 
+ does tend to, I understand.
>
> Whether S/N or Text Exchange should be first after the call sign is  
> something that could be debated.
> I spent some considerable time thinking about this and made good  
> arguments for both. In the end,
> I decided that more contests exchange text and only text than  
> exchange only serial numbers. For
> those contests that expect both, Shift-Tab can move you back. Ugly,  
> I know, but if we are only
> given one screen and tab configuration we will have to make  
> compromises and some contests
> will have smoother entry sequences than others.

Hmmm - every rule I've looked at has at least serial number, but I  
admit, I've not done many variants of contest.
>
>>
> My suggestion was consistent with the current keystroke mappings of  
> the Pre-Cocoa MLDX.
> I have worked both contests and DXpeditions with the CMD-K type  
> SHIFT-CMD-L and found
> Don's original keyboard shortcut definitions to be satisfactory.  
> Well, that's one man's opinion
> I guess. It isn't clear to me why one who is left-handed would find  
> any particular keystroke
> combination more-or-less difficult than someone right-handed. Why  
> would that be? I always
> thought touch typing with fingers on both hands fully engaged was an  
> equal art for both
> righty's and lefty's!

Ah - well I can't touch type and my right hand just doesn't 'lay'  
right to get the 'L'. Cmd-L would have been easier.
Again, you wont be able to please everybody

And find I need two hand to achieve cmd-shift-l, but could for  
example, use just one hand to get cmd-shift-s (or, a/z), on the right,  
it would be cmd-shift-/ and that's about it.
But my point is more about having to press 3 keys for what is a very  
common function, and would have thought just one or at most 2, far  
simpler - we must agree to disagree.
>
> I do believe that logging and clearing should be two different  
> operations. When running
> one might log AB1HB and then the calling station comes back and  
> says, "Negative, negative,
> the calls is AB1HD!" At that point you do NOT want to re-enter all  
> the captured information,
> you really want to just update the call and log again. Automatic  
> clearing would preclude this
> use case. It happens often enough that a deliberate clear is  
> warranted, IMHO.

Well, I'm saying that in fact, I tend to clear as I start a new QSO  
and not after login the last one. however, you said you log and then  
clear, I don't quite spot how that isn't doing it in one keystroke.
>
>
> I don't really care who sets the number. I just thought it would be  
> helpful to see what
> power was nominally used.
Yes agreed on that, we are just talking at cross purposes.
>

>
> One of the worst for tedium is the ARRL SS exchange:
> * serial number
> * precedence
> * callsign
> * check (last two digits of first year licensed)
> * ARRL/RAC section
>
> and all this goes into the STX / SRX fields (in an order specified  
> by the Cab-converter manual).
> I would be delighted if these were broken into separate fields, but  
> as it stands today we have
> MLDX and Cab-converter handling this contest, even with all this  
> stuff in one field. If there is
> another contest even worse than this one (besides those contests  
> where they read back
> previous QSOs) I'd like to know about it. Then again, don't bother,  
> Cab-converter isn't going
> to support it anyway. {grin}
I'm not aware of one in the UK, RoPoCo gives it a run for its money in  
difficulty, but not in number of fields. So CC expects a number of  
fields, combined into just the one STX/RTX field and separated in some  
way. That obivously works because people are using it. Also, at that  
point you've got the other other end nailed, so you just have to fill  
it in.

73 de M0XDF


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090125/ec6cb04a/attachment.htm>

From bsandersen at mac.com  Sat Jan 24 20:32:58 2009
From: bsandersen at mac.com (B. Scott Andersen)
Date: Sat, 24 Jan 2009 20:32:58 -0500
Subject: [MacLoggerContest] Contest entry screen specification
In-Reply-To: <6535477D-3D40-47E5-BF6F-3B4CBBFC6E95@Alphadene.co.uk>
References: <48FB5B19-9356-49C5-B9E7-E5C3D7B3A827@dogparksoftware.com>
	<22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
	<C557B5DE-0519-41AC-95D5-608629199127@mac.com>
	<18439814-E4DD-4DDD-AA6A-D1849AFFE667@Alphadene.co.uk>
	<2F267904-8E8A-45BF-B4FF-3F92EDF103D7@mac.com>
	<6535477D-3D40-47E5-BF6F-3B4CBBFC6E95@Alphadene.co.uk>
Message-ID: <EA48F388-B70A-418F-A7D7-C249A67CF6F8@mac.com>

David,

I'll start this without all the indents.

1. Super check partial
This is just a text file containing call signs of known contesters.
It does not involve contact with the outside world at all. That's
why it is OK. The SCP is already implemented in the current
MLDX. This is part of the contest helper panel.

2. The RST thing is obviously contest-dependent.
I can only speak to the typical HF contests. The RST is a blind
59 or 5NN for most everything below 30 MHz. I can't speak
to whether this is a good thing or a bad thing; I can tell you
only that it seems well entrenched.

3. Every contest has at least a serial number?
Here are some that do not:
* CQ WW (both Phone and CW) ==> RS(T) + CQ Zone 5905 or 5NN05
* ARRL 10m ==> RS(T) and state/province (DX sends S/N)
* North American QSO party ==> Name + S/P/C (note RS(T) not required!)
* New England QSO party ==> RS(T) + S/P, DX sends "DX"
... just to name a few.
This isn't to say that support of serial numbers isn't important.
Of course it is! But, there are a fair number of contests, including
CQ WW DX -- the biggest contest of them all -- that do not.

Again, with only a fixed contest frame in MLDX everything will be
a compromise. That said, I'm sure that sufficient thought could
better the attempt that I have made. If we are to try, then I would
recommend that we have the discussion here on this MLDX contest
list, engage its members, and come up with something that the
group can get behind. Once we have consensus we can approach
Don and ask if he would consider the proposal.

What we should avoid, of course, is to have multiple, contradictory,
competing proposals all land on Don's desk. I dare say that would
get us nowhere. Or so it seems to me...

-- Scott (NE1RD)

>

B. Scott Andersen           | "Magic is real, unless declared integer."
bsandersen -atsign- mac.com | -- The collected sayings of Wiz Zumwalt
Acton, MA (NE1RD)           | http://www.bsandersen.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090124/dcbcdb53/attachment.html>

From M0XDF at Alphadene.co.uk  Sun Jan 25 06:54:10 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Sun, 25 Jan 2009 11:54:10 +0000
Subject: [MacLoggerContest] Contest entry screen specification
In-Reply-To: <EA48F388-B70A-418F-A7D7-C249A67CF6F8@mac.com>
References: <48FB5B19-9356-49C5-B9E7-E5C3D7B3A827@dogparksoftware.com>
	<22EC39FD-F506-4899-97FD-2042CF94DF56@Alphadene.co.uk>
	<C557B5DE-0519-41AC-95D5-608629199127@mac.com>
	<18439814-E4DD-4DDD-AA6A-D1849AFFE667@Alphadene.co.uk>
	<2F267904-8E8A-45BF-B4FF-3F92EDF103D7@mac.com>
	<6535477D-3D40-47E5-BF6F-3B4CBBFC6E95@Alphadene.co.uk>
	<EA48F388-B70A-418F-A7D7-C249A67CF6F8@mac.com>
Message-ID: <71F6553B-4ADA-40A8-8A9C-A27DDBA75C3F@Alphadene.co.uk>

Scott, not sure where you remember the 2E0XDF at Alphadene.co.uk from,  
but it only got here because I have a catch all address at present.  
Could you please use the address this mail comes from, so I don't miss  
any. No problem, just I changed my address when I got my full license.  
Oh and I'd better figure where I didn't do that.

1. I know and use
2. Yes I know that too
3. That I didn't know, you'll note I said that I knew about, but  
having only been a ham since 2003 and not doing taken part in those  
yet, I didn't know that.

I agree with the last and have only mailed the list this time, so you  
(and I) don't keep getting too mails. This is exactly what I've been  
trying to do for the last few weeks.
Unfortunately, it started on the other list (this one hadn't seen any  
mail for a year I believe) and tick'd Don off no end that people were  
leaving because of all the contest related mails. For that I apologise.

Lets do have a discussion here. I suggest everyone who wants to join  
in, at least download and try the beta version - it's free (with 10  
min time-out) and you can at least see what Scott and Don have come  
up. Sorry to those that aren?t running 10.5, it's not going to work on  
anything lower.

People can comment and discuss it. It's unlikely that Don will  
introduce new fields, although there was a suggestion in a previous  
post he might introduce 1 or 2 (see note at bottom).

What we're asking people to do is comment on the layout and tab order  
of the Contest panel.

Note on the Recv/Sent fields:
My understanding from Scott is that this field can contain multiple  
values when used with a contest requiring more than just RST/Serial/ 
Locator/plusone and CabConverter will pick out the required bits. I'd  
ask people to consider if that is easy to use and fulfils the bill for  
those (I guess few) contests that require 5+ exchanges. I goes against  
my relational nature to multi-value a column, but if that's the  
easiest way...
73 de M0XDF
-- 
Everything secret degenerates, even the administration of justice;  
nothing
is safe that does not show how it can bear discussion and publicity.
-Lord Acton, historian (1834-1902)

On 25 Jan 2009, at 01:32, B. Scott Andersen wrote:

> David,
>
> I'll start this without all the indents.
>
> 1. Super check partial
> This is just a text file containing call signs of known contesters.
> It does not involve contact with the outside world at all. That's
> why it is OK. The SCP is already implemented in the current
> MLDX. This is part of the contest helper panel.
>
> 2. The RST thing is obviously contest-dependent.
> I can only speak to the typical HF contests. The RST is a blind
> 59 or 5NN for most everything below 30 MHz. I can't speak
> to whether this is a good thing or a bad thing; I can tell you
> only that it seems well entrenched.
>
> 3. Every contest has at least a serial number?
> Here are some that do not:
> * CQ WW (both Phone and CW) ==> RS(T) + CQ Zone 5905 or 5NN05
> * ARRL 10m ==> RS(T) and state/province (DX sends S/N)
> * North American QSO party ==> Name + S/P/C (note RS(T) not required!)
> * New England QSO party ==> RS(T) + S/P, DX sends "DX"
> ... just to name a few.
> This isn't to say that support of serial numbers isn't important.
> Of course it is! But, there are a fair number of contests, including
> CQ WW DX -- the biggest contest of them all -- that do not.
>
> Again, with only a fixed contest frame in MLDX everything will be
> a compromise. That said, I'm sure that sufficient thought could
> better the attempt that I have made. If we are to try, then I would
> recommend that we have the discussion here on this MLDX contest
> list, engage its members, and come up with something that the
> group can get behind. Once we have consensus we can approach
> Don and ask if he would consider the proposal.
>
> What we should avoid, of course, is to have multiple, contradictory,
> competing proposals all land on Don's desk. I dare say that would
> get us nowhere. Or so it seems to me...
>
> -- Scott (NE1RD)
>
>>
>
> B. Scott Andersen           | "Magic is real, unless declared  
> integer."
> bsandersen -atsign- mac.com | -- The collected sayings of Wiz Zumwalt
> Acton, MA (NE1RD)           | http://www.bsandersen.com
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090125/a22c71df/attachment.html>

From wb0m at flashdog.us  Sun Jan 25 13:41:49 2009
From: wb0m at flashdog.us (wb0m at flashdog.us)
Date: Sun, 25 Jan 2009 12:41:49 -0600
Subject: [MacLoggerContest] MLDX Contest
Message-ID: <037E01A8-CC11-432E-9857-520E34DB77A5@flashdog.us>

Has anyone else tried the contest log of the MLDX v.5?
I played with it just a bit in the CQ 160 cw contest this weekend.
One glitch: When I exported the .adi file, it came out with the mode  
marked as SSB instead of the CW (which the log showed).
I don't know if Don's doing much yet with the contest side. Just a  
FYI. Other than the "sent' field clearing and not reading from my  
QRZ.com CD, it was really nice to use.
I especially liked be able to create new log from the file menu.
I'm sure those will be fixed later, also.
Cheers & 73,
Jeff/wb0m

From wb0m at flashdog.us  Sun Jan 25 14:11:55 2009
From: wb0m at flashdog.us (wb0m at flashdog.us)
Date: Sun, 25 Jan 2009 13:11:55 -0600
Subject: [MacLoggerContest] MLDX Contest
Message-ID: <05EC445D-FE13-4DE8-8D52-E25E49D8F9A3@flashdog.us>

Just an addendum to my first post: I ran the 20 QSOs through Scott's  
Cab-converter? program and that's when I noticed the mode problems. I  
changed a bunch of the QSO's mode to "CW" in Text Edit and ran Cab- 
converter again and it worked. Also, when I imported the .adi file  
into MLDX v4.3.6 the QSOs with the CW mode were imported as well as a  
second identical QSO with the SSB mode. 73, Jeff/wb0m

From dhkaplan at mac.com  Tue Feb 10 07:28:35 2009
From: dhkaplan at mac.com (David Kaplan)
Date: Tue, 10 Feb 2009 07:28:35 -0500
Subject: [MacLoggerContest] Contest Panel Question
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
Message-ID: <CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>

Don,

Using beta85, I just tried to display a contact from my playing in the  
QSO parties this weekend, and the sent and received strings which were  
in the DB (such as 59 CT) did not display when I tried to look at the  
info. Just checked and the serial numbers don't show up either,  
although they are in the db.

Thanks as usual for all your efforts.

David, WA1OUI


From dagro at dogparksoftware.com  Tue Feb 10 08:01:36 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Tue, 10 Feb 2009 08:01:36 -0500
Subject: [MacLoggerContest] Contest Panel Question MacLoggerDX for Cocoa
In-Reply-To: <CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
Message-ID: <C380C9AE-F63D-490A-A6E4-06826B98A7FB@dogparksoftware.com>

Hi David,

On 10-02-2009, at 7:28 AM, David Kaplan wrote:

> Using beta85, I just tried to display a contact from my playing in  
> the QSO parties this weekend, and the sent and received strings  
> which were in the DB (such as 59 CT) did not display when I tried to  
> look at the info. Just checked and the serial numbers don't show up  
> either, although they are in the db.


RST-S and RST-R are displaying OK here in both the DX and Contest  
Panel but the serial numbers are not displaying in the Contest Panel.  
I will have a look. I guess the important thing is that they are  
correct in the log.

73 Don Agro VE3VRW


From dhkaplan at mac.com  Tue Feb 10 08:37:36 2009
From: dhkaplan at mac.com (David Kaplan)
Date: Tue, 10 Feb 2009 08:37:36 -0500
Subject: [MacLoggerContest] Contest Panel Question MacLoggerDX for Cocoa
In-Reply-To: <C380C9AE-F63D-490A-A6E4-06826B98A7FB@dogparksoftware.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
	<C380C9AE-F63D-490A-A6E4-06826B98A7FB@dogparksoftware.com>
Message-ID: <C2F466E3-2B18-4295-A204-99947023EABC@mac.com>

Hi Don,

Yes RST S/R are ok, it was the Serial Numbers and STRINGS TX/RX that  
weren't displaying... and I agree that at least the log has them!

David, WA1OUI


On Feb 10, 2009, at 08:01 AM, Don Agro wrote:

Hi David,

On 10-02-2009, at 7:28 AM, David Kaplan wrote:

> Using beta85, I just tried to display a contact from my playing in  
> the QSO parties this weekend, and the sent and received strings  
> which were in the DB (such as 59 CT) did not display when I tried to  
> look at the info. Just checked and the serial numbers don't show up  
> either, although they are in the db.


RST-S and RST-R are displaying OK here in both the DX and Contest  
Panel but the serial numbers are not displaying in the Contest Panel.  
I will have a look. I guess the important thing is that they are  
correct in the log.

73 Don Agro VE3VRW



From dagro at dogparksoftware.com  Tue Feb 10 14:44:27 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Tue, 10 Feb 2009 14:44:27 -0500
Subject: [MacLoggerContest] Contest Panel Question
In-Reply-To: <CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
Message-ID: <B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>

Hi David,

On 10-02-2009, at 7:28 AM, David Kaplan wrote:

> Using beta85, I just tried to display a contact from my playing in  
> the QSO parties this weekend, and the sent and received strings  
> which were in the DB (such as 59 CT) did not display when I tried to  
> look at the info. Just checked and the serial numbers don't show up  
> either, although they are in the db.

The SRX, STX string and numeric log display are fixed in beta 86, but  
these are persistent fields, so if they are blank or 0 in the log they  
will not overwrite the existing display.

73 Don Agro VE3VRW


From dhkaplan at mac.com  Tue Feb 10 21:37:24 2009
From: dhkaplan at mac.com (David Kaplan)
Date: Tue, 10 Feb 2009 21:37:24 -0500
Subject: [MacLoggerContest] Contest Panel Question
In-Reply-To: <B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
	<B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>
Message-ID: <C59B1FF9-242C-4E71-B8A4-B7E319368B9D@mac.com>

Hi Don, Just tried b86, and let's see if I can quantify what I saw on  
the contest panel:

1) Rcvd, Rcvd sn, Sent sn, Sent fields are not persistent between  
program sessions, while RSTS/RSTR/Power are persistent.

Also, Cmd-K clears those fields but does NOT clear RSTS/RSTR/Power  
fields. Shouldn't all the fields remain when Cmd-K is used, as well as  
between sessions? It seems that way in version 4.

Thanks,

David, WA1OUI


On Feb 10, 2009, at 02:44 PM, Don Agro wrote:

Hi David,

On 10-02-2009, at 7:28 AM, David Kaplan wrote:

> Using beta85, I just tried to display a contact from my playing in  
> the QSO parties this weekend, and the sent and received strings  
> which were in the DB (such as 59 CT) did not display when I tried to  
> look at the info. Just checked and the serial numbers don't show up  
> either, although they are in the db.

The SRX, STX string and numeric log display are fixed in beta 86, but  
these are persistent fields, so if they are blank or 0 in the log they  
will not overwrite the existing display.

73 Don Agro VE3VRW



From dagro at dogparksoftware.com  Wed Feb 11 05:52:11 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Wed, 11 Feb 2009 05:52:11 -0500
Subject: [MacLoggerContest] Contest Panel Question
In-Reply-To: <C59B1FF9-242C-4E71-B8A4-B7E319368B9D@mac.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
	<B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>
	<C59B1FF9-242C-4E71-B8A4-B7E319368B9D@mac.com>
Message-ID: <2178C7B5-2694-40C1-881E-D6A3014459EF@dogparksoftware.com>

Hi David,

On 10-02-2009, at 9:37 PM, David Kaplan wrote:

> Hi Don, Just tried b86, and let's see if I can quantify what I saw  
> on the contest panel:
>
> 1) Rcvd, Rcvd sn, Sent sn, Sent fields are not persistent between  
> program sessions, while RSTS/RSTR/Power are persistent.

Correct this is also how V4 works.

> Also, Cmd-K clears those fields but does NOT clear RSTS/RSTR/Power  
> fields.

Correct.

> Shouldn't all the fields remain when Cmd-K is used,

What about SN received (string and numeric)  ?

Why not clear them - they change with every exchange.
SN sent numeric is often auto incremented so you don't clear that.
That only leaves sn sent string.

> as well as between sessions?  It seems that way in version 4.


No V4 does not remember srx or stxstring or numeric  between sessions,  
just rst s, rst r and power.

73 Don Agro VE3VRW

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090211/2daf5583/attachment.html>

From dagro at dogparksoftware.com  Wed Feb 11 07:09:15 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Wed, 11 Feb 2009 07:09:15 -0500
Subject: [MacLoggerContest] Contest Panel Question
In-Reply-To: <2178C7B5-2694-40C1-881E-D6A3014459EF@dogparksoftware.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
	<B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>
	<C59B1FF9-242C-4E71-B8A4-B7E319368B9D@mac.com>
	<2178C7B5-2694-40C1-881E-D6A3014459EF@dogparksoftware.com>
Message-ID: <382CE4BD-5F48-4053-9870-5720B338CA96@dogparksoftware.com>

For the next beta I have changed the clear function to not clear Sent  
Serial or Sent String.
Also, Sent Serial and Sent String are saved across sessions.

So Clear leaves: RST S, RTS R, Power, Sent Serial (which can be auto- 
incremented) , and Sent String untouched.
Sent Serial and Sent String are changed with each exchange but in case  
the change is minor we leave the old one there.
(Received Serial and Received String should change with every exchange  
so they are cleared)

Preserved across sessions are : RST S, RTS R, Power, Sent Serial and  
Sent String.
(I'm not sure what the value is in preserving Sent Serial and Sent  
String across sessions is but it shouldn't do any harm)
(Received Serial and Received String should change with every exchange  
so they are not saved)

If I'm missing something let me know.

73 Don Agro VE3VRW


From dhkaplan at mac.com  Wed Feb 11 07:41:47 2009
From: dhkaplan at mac.com (David Kaplan)
Date: Wed, 11 Feb 2009 07:41:47 -0500
Subject: [MacLoggerContest] Contest Panel Question
In-Reply-To: <2178C7B5-2694-40C1-881E-D6A3014459EF@dogparksoftware.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
	<B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>
	<C59B1FF9-242C-4E71-B8A4-B7E319368B9D@mac.com>
	<2178C7B5-2694-40C1-881E-D6A3014459EF@dogparksoftware.com>
Message-ID: <D06DE027-5A18-4571-A631-C9F6D7EC666C@mac.com>

Hi again,

You are right (of course), and I was a bit confuzzled when I mentioned  
persistent between program sessions...
I should have been referring to between Call lookups (even though I DO  
know the difference!)

Between CALL lookups the fields I mentioned persist in V4, and  
disappear in V5.
Also the Cmd-K does NOT clear them in V4 and does in V5.

That said, upon thinking about it, I agree with 99% of your changes...  
lose them all between program sessions is fine since serials change  
and so should Rcvd field, but should the Sent field remain between  
Call Lookups and Cmd-K usage? I will usually send 59 CT (or whatever).  
Let's not discuss the 59 sent in contests in this forum! However,  
shouldn't the Sent field remain for the contest?

Thanks,

David, WA1OUI


On Feb 11, 2009, at 05:52 AM, Don Agro wrote:

Hi David,

On 10-02-2009, at 9:37 PM, David Kaplan wrote:

> Hi Don, Just tried b86, and let's see if I can quantify what I saw  
> on the contest panel:
>
> 1) Rcvd, Rcvd sn, Sent sn, Sent fields are not persistent between  
> program sessions, while RSTS/RSTR/Power are persistent.

Correct this is also how V4 works.

> Also, Cmd-K clears those fields but does NOT clear RSTS/RSTR/Power  
> fields.

Correct.

> Shouldn't all the fields remain when Cmd-K is used,

What about SN received (string and numeric)  ?

Why not clear them - they change with every exchange.
SN sent numeric is often auto incremented so you don't clear that.
That only leaves sn sent string.

> as well as between sessions?  It seems that way in version 4.


No V4 does not remember srx or stxstring or numeric  between sessions,  
just rst s, rst r and power.

73 Don Agro VE3VRW


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090211/826bcbe9/attachment.html>

From dhkaplan at mac.com  Wed Feb 11 07:44:56 2009
From: dhkaplan at mac.com (David Kaplan)
Date: Wed, 11 Feb 2009 07:44:56 -0500
Subject: [MacLoggerContest] Contest Panel Question
In-Reply-To: <382CE4BD-5F48-4053-9870-5720B338CA96@dogparksoftware.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
	<B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>
	<C59B1FF9-242C-4E71-B8A4-B7E319368B9D@mac.com>
	<2178C7B5-2694-40C1-881E-D6A3014459EF@dogparksoftware.com>
	<382CE4BD-5F48-4053-9870-5720B338CA96@dogparksoftware.com>
Message-ID: <763A160E-CD29-4B01-8359-5A68C929B925@mac.com>

Oops, sent my recent reply without having seen yours (Sorry!). To  
summarize my previous email I think sent string is the only worth  
saving between contacts, and not sessions...

Not discussing RST...

DHK

On Feb 11, 2009, at 07:09 AM, Don Agro wrote:

For the next beta I have changed the clear function to not clear Sent  
Serial or Sent String.
Also, Sent Serial and Sent String are saved across sessions.

So Clear leaves: RST S, RTS R, Power, Sent Serial (which can be auto- 
incremented) , and Sent String untouched.
Sent Serial and Sent String are changed with each exchange but in case  
the change is minor we leave the old one there.
(Received Serial and Received String should change with every exchange  
so they are cleared)

Preserved across sessions are : RST S, RTS R, Power, Sent Serial and  
Sent String.
(I'm not sure what the value is in preserving Sent Serial and Sent  
String across sessions is but it shouldn't do any harm)
(Received Serial and Received String should change with every exchange  
so they are not saved)

If I'm missing something let me know.

73 Don Agro VE3VRW



From dagro at dogparksoftware.com  Wed Feb 11 08:48:48 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Wed, 11 Feb 2009 08:48:48 -0500
Subject: [MacLoggerContest] Contest Panel Question
In-Reply-To: <763A160E-CD29-4B01-8359-5A68C929B925@mac.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
	<B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>
	<C59B1FF9-242C-4E71-B8A4-B7E319368B9D@mac.com>
	<2178C7B5-2694-40C1-881E-D6A3014459EF@dogparksoftware.com>
	<382CE4BD-5F48-4053-9870-5720B338CA96@dogparksoftware.com>
	<763A160E-CD29-4B01-8359-5A68C929B925@mac.com>
Message-ID: <32ECB929-6A98-475C-9B77-B21AFE0C9AC9@dogparksoftware.com>

Hi David,

On 11-02-2009, at 7:44 AM, David Kaplan wrote:

> Oops, sent my recent reply without having seen yours (Sorry!). To  
> summarize my previous email I think sent string is the only worth  
> saving between contacts, and not sessions...


No problem, have a look at Beta 87 and see if what it is doing makes  
sense.

73 Don Agro VE3VRW

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090211/e1ff0687/attachment.html>

From M0XDF at Alphadene.co.uk  Wed Feb 11 09:15:49 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Wed, 11 Feb 2009 14:15:49 +0000
Subject: [MacLoggerContest] MLXD v5b87 - Serial numbers in wrong field
Message-ID: <F3867666-A754-4B09-858B-C9EE96236EEB@Alphadene.co.uk>

Don, I have a log entry with the column SRX# = 28 and STX#=24, these  
are the correct serials I received and sent.
When I 'Display' the record, those go into the Rcvd and Sent fields in  
the Contest Panel, shouldn't they be going into Rcvd sn and Sent sn  
fields?
73 de M0XDF
-- 
The soul is the same in all living creatures, although the body is
different. -Hippocrates, physician (460-c.377 BCE)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090211/ec64e449/attachment.html>

From dagro at dogparksoftware.com  Wed Feb 11 09:48:20 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Wed, 11 Feb 2009 09:48:20 -0500
Subject: [MacLoggerContest] MLXD v5b87 - Serial numbers in wrong field
In-Reply-To: <F3867666-A754-4B09-858B-C9EE96236EEB@Alphadene.co.uk>
References: <F3867666-A754-4B09-858B-C9EE96236EEB@Alphadene.co.uk>
Message-ID: <4BA21DF7-7D1D-4A36-8F46-39EE9C9AED0D@dogparksoftware.com>


On 11-02-2009, at 9:15 AM, David Ferrington, M0XDF wrote:

> Don, I have a log entry with the column SRX# = 28 and STX#=24, these  
> are the correct serials I received and sent.
> When I 'Display' the record, those go into the Rcvd and Sent fields  
> in the Contest Panel, shouldn't they be going into Rcvd sn and Sent  
> sn fields?


Yes, they were reversed. Fixed in Beta 88. Thanks for catching it.

73 Don Agro VE3VRW


From M0XDF at Alphadene.co.uk  Wed Feb 11 10:20:49 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Wed, 11 Feb 2009 15:20:49 +0000
Subject: [MacLoggerContest] MLXD v5b87 - Serial numbers in wrong field -
	fixed
In-Reply-To: <4BA21DF7-7D1D-4A36-8F46-39EE9C9AED0D@dogparksoftware.com>
References: <F3867666-A754-4B09-858B-C9EE96236EEB@Alphadene.co.uk>
	<4BA21DF7-7D1D-4A36-8F46-39EE9C9AED0D@dogparksoftware.com>
Message-ID: <DCC663CE-C275-4CFE-9D5E-236146517A4E@Alphadene.co.uk>

Yes, fixed, thanks Don
73 de M0XDF, MLDXv5b88
--  
Math Anxiety: an intense lifelong fear of two trains approaching each  
other at speeds of 60 and 80 MPH. -Rick Bayan

On 11 Feb 2009, at 14:48, Don Agro wrote:

>
> On 11-02-2009, at 9:15 AM, David Ferrington, M0XDF wrote:
>
>> Don, I have a log entry with the column SRX# = 28 and STX#=24,  
>> these are the correct serials I received and sent.
>> When I 'Display' the record, those go into the Rcvd and Sent fields  
>> in the Contest Panel, shouldn't they be going into Rcvd sn and Sent  
>> sn fields?
>
>
> Yes, they were reversed. Fixed in Beta 88. Thanks for catching it.


From dhkaplan at mac.com  Wed Feb 11 14:00:31 2009
From: dhkaplan at mac.com (David Kaplan)
Date: Wed, 11 Feb 2009 14:00:31 -0500
Subject: [MacLoggerContest] Contest Panel Question
In-Reply-To: <32ECB929-6A98-475C-9B77-B21AFE0C9AC9@dogparksoftware.com>
References: <582E1BEC-B39B-4DE8-AA9A-E899D9543C41@mac.com>
	<CADD2EDA-7EBA-4959-B68B-B7EDA2FCE139@mac.com>
	<B0E3F338-E838-467E-8E8B-7734782980DB@dogparksoftware.com>
	<C59B1FF9-242C-4E71-B8A4-B7E319368B9D@mac.com>
	<2178C7B5-2694-40C1-881E-D6A3014459EF@dogparksoftware.com>
	<382CE4BD-5F48-4053-9870-5720B338CA96@dogparksoftware.com>
	<763A160E-CD29-4B01-8359-5A68C929B925@mac.com>
	<32ECB929-6A98-475C-9B77-B21AFE0C9AC9@dogparksoftware.com>
Message-ID: <2EA1ABA0-E497-4DED-816B-FEBF5F0FB972@mac.com>

Checked out b88 and seems great. Many thanks.

David, WA1OUI



On Feb 11, 2009, at 08:48 AM, Don Agro wrote:

Hi David,

On 11-02-2009, at 7:44 AM, David Kaplan wrote:

> Oops, sent my recent reply without having seen yours (Sorry!). To  
> summarize my previous email I think sent string is the only worth  
> saving between contacts, and not sessions...


No problem, have a look at Beta 87 and see if what it is doing makes  
sense.

73 Don Agro VE3VRW


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090211/dc056d40/attachment.html>

From dhkaplan at mac.com  Fri Feb 13 14:38:47 2009
From: dhkaplan at mac.com (David Kaplan)
Date: Fri, 13 Feb 2009 14:38:47 -0500
Subject: [MacLoggerContest] Color codes work
Message-ID: <6435406E-BA3C-4711-807F-9B1807DA299A@mac.com>

Color codes work after I deleted my sql db and re-imported it from my  
log.dat.

As I said earlier: I dunno...

David, WA1OUI

From g0dvj at amsat.org  Thu Feb 19 10:54:15 2009
From: g0dvj at amsat.org (Jonathan G0DVJ)
Date: Thu, 19 Feb 2009 15:54:15 +0000
Subject: [MacLoggerContest] Fwd: [DogParkList] MacLoggerDX V5 for Cocoa
	5.01b3
References: <3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
Message-ID: <1AB99ECF-66D8-4F22-8F85-6D4AA6368543@amsat.org>


Have moved this thread for fear of driving folk away again !

My 2c/2p worth

Best not to confuse the purpose of each SCP and Dupe checks in  
contests ...

Dupe Check needs to flag as soon as you type a call whether it has  
been worked in this event (i.e. since/limited time/date) and  
optionally (maybe a checkbox) on the same band.

SCP needs to match calls from K5ZD's database as you type a call so  
that when so many call you or condx are difficult, you can make a  
better judged guess at what the full call is... just as it did in  
v4.   SCP doesnt need options for limiting by band/date/time although  
it would be nice to highlight/color matches that have already been  
worked on another band according to the Dupe Check (above) If and only  
If the checkbox has not been marked to say that it wouldnt be a  
dupe.   i.e. there is more chance you will match a call with someone  
you already worked on another band than with the entire database!

HTH

J.

Begin forwarded message:

> From: "David Ferrington, M0XDF" <M0XDF at Alphadene.co.uk>
> Date: February 19, 2009 3:08:45 pm GMT
> To: Don Agro <dagro at dogparksoftware.com>
> Subject: Re: [DogParkList] MacLoggerDX V5 for Cocoa 5.01b3
>
> Well, when looking for dups in a contest, not having a lot of chaff  
> from previous contest or different bands helps a lot in spotting a  
> call.
> The setup in v4 was pretty good
> 73 de M0XDF, MLDXv5.01b3
> -- 
> Ok, so what's the speed of Dark?
>
> On 19 Feb 2009, at 15:00, Don Agro wrote:
>
>>
>> On 19-02-2009, at 9:52 AM, David Ferrington, M0XDF wrote:
>>
>>> Cool. Are you planning on allow us to specify specific bands to  
>>> look in and also allow us to limit dup search to a specific date &  
>>> time?
>>
>> Possibly, which is more useful or more used ? I'm trying to keep  
>> the interface as simple as possible.
>>
>> Don't forget you can now sort the partial call list in the Contest  
>> Helper Window by date or by band or by call.
>>
>> Any other fields that would be useful in the partial call list ?
>>
>> 73 Don Agro VE3VRW
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090219/f7002fa5/attachment.htm>

From g0dvj at amsat.org  Thu Feb 19 11:04:30 2009
From: g0dvj at amsat.org (Jonathan G0DVJ)
Date: Thu, 19 Feb 2009 16:04:30 +0000
Subject: [MacLoggerContest] [DogParkList] MacLoggerDX V5 for Cocoa 5.01b3
In-Reply-To: <1AB99ECF-66D8-4F22-8F85-6D4AA6368543@amsat.org>
References: <3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<1AB99ECF-66D8-4F22-8F85-6D4AA6368543@amsat.org>
Message-ID: <DED9761F-4F09-463E-AB11-262CE846C1EC@amsat.org>


In terms of what else would be useful in the contest helper window ...  
a simple traffic light or status line indicator of whether the call  
typed is a new DXCC, new IOTA, new Zone (ITU/CQ) since the same  
criteria already used for the dupe check (i.e. date and time plus  
optional same band) so can see at a glance if the station you hear is  
of higher value (can just ignore it in contests where there are no  
mults).

My previous post was typed very quick so apologies if it wasnt very  
clear about the link between SCP and Dupe check.   Happy to try to  
explain better if needed!

J.
--

On Feb 19, 2009, at 3:54 pm, Jonathan G0DVJ wrote:

>
> Have moved this thread for fear of driving folk away again !
>
> My 2c/2p worth
>
> Best not to confuse the purpose of each SCP and Dupe checks in  
> contests ...
>
> Dupe Check needs to flag as soon as you type a call whether it has  
> been worked in this event (i.e. since/limited time/date) and  
> optionally (maybe a checkbox) on the same band.
>
> SCP needs to match calls from K5ZD's database as you type a call so  
> that when so many call you or condx are difficult, you can make a  
> better judged guess at what the full call is... just as it did in  
> v4.   SCP doesnt need options for limiting by band/date/time  
> although it would be nice to highlight/color matches that have  
> already been worked on another band according to the Dupe Check  
> (above) If and only If the checkbox has not been marked to say that  
> it wouldnt be a dupe.   i.e. there is more chance you will match a  
> call with someone you already worked on another band than with the  
> entire database!
>
> HTH
>
> J.
>
> Begin forwarded message:
>
>> From: "David Ferrington, M0XDF" <M0XDF at Alphadene.co.uk>
>> Date: February 19, 2009 3:08:45 pm GMT
>> To: Don Agro <dagro at dogparksoftware.com>
>> Subject: Re: [DogParkList] MacLoggerDX V5 for Cocoa 5.01b3
>>
>> Well, when looking for dups in a contest, not having a lot of chaff  
>> from previous contest or different bands helps a lot in spotting a  
>> call.
>> The setup in v4 was pretty good
>> 73 de M0XDF, MLDXv5.01b3
>> -- 
>> Ok, so what's the speed of Dark?
>>
>> On 19 Feb 2009, at 15:00, Don Agro wrote:
>>
>>>
>>> On 19-02-2009, at 9:52 AM, David Ferrington, M0XDF wrote:
>>>
>>>> Cool. Are you planning on allow us to specify specific bands to  
>>>> look in and also allow us to limit dup search to a specific date  
>>>> & time?
>>>
>>> Possibly, which is more useful or more used ? I'm trying to keep  
>>> the interface as simple as possible.
>>>
>>> Don't forget you can now sort the partial call list in the Contest  
>>> Helper Window by date or by band or by call.
>>>
>>> Any other fields that would be useful in the partial call list ?
>>>
>>> 73 Don Agro VE3VRW
>>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090219/119454f1/attachment.htm>

From M0XDF at Alphadene.co.uk  Thu Feb 19 11:05:35 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Thu, 19 Feb 2009 16:05:35 +0000
Subject: [MacLoggerContest] Fwd: [DogParkList] MacLoggerDX V5 for Cocoa
	5.01b3
In-Reply-To: <1AB99ECF-66D8-4F22-8F85-6D4AA6368543@amsat.org>
References: <3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<1AB99ECF-66D8-4F22-8F85-6D4AA6368543@amsat.org>
Message-ID: <5FC76BB1-76E3-4965-90C6-7DE583D2EC41@Alphadene.co.uk>

good idea about the move, sorry I didn't think of it
and total agree with the requirement Jonathan.

One point, the option checkboxes will ideally be on the contest panel,  
don't want to have to go find them in prefs while running the contest
73 de M0XDF, MLDXv5.01b3
-- 
"There is no limit to what you can accomplish if you don't care who
gets the credit." --Ronald Reagan

On 19 Feb 2009, at 15:54, Jonathan G0DVJ wrote:

>
> Have moved this thread for fear of driving folk away again !
>
> My 2c/2p worth
>
> Best not to confuse the purpose of each SCP and Dupe checks in  
> contests ...
>
> Dupe Check needs to flag as soon as you type a call whether it has  
> been worked in this event (i.e. since/limited time/date) and  
> optionally (maybe a checkbox) on the same band.
>
> SCP needs to match calls from K5ZD's database as you type a call so  
> that when so many call you or condx are difficult, you can make a  
> better judged guess at what the full call is... just as it did in  
> v4.   SCP doesnt need options for limiting by band/date/time  
> although it would be nice to highlight/color matches that have  
> already been worked on another band according to the Dupe Check  
> (above) If and only If the checkbox has not been marked to say that  
> it wouldnt be a dupe.   i.e. there is more chance you will match a  
> call with someone you already worked on another band than with the  
> entire database!
>
> HTH
>
> J.
>
> Begin forwarded message:
>
>> From: "David Ferrington, M0XDF" <M0XDF at Alphadene.co.uk>
>> Date: February 19, 2009 3:08:45 pm GMT
>> To: Don Agro <dagro at dogparksoftware.com>
>> Subject: Re: [DogParkList] MacLoggerDX V5 for Cocoa 5.01b3
>>
>> Well, when looking for dups in a contest, not having a lot of chaff  
>> from previous contest or different bands helps a lot in spotting a  
>> call.
>> The setup in v4 was pretty good
>> 73 de M0XDF, MLDXv5.01b3
>> -- 
>> Ok, so what's the speed of Dark?
>>
>> On 19 Feb 2009, at 15:00, Don Agro wrote:
>>
>>>
>>> On 19-02-2009, at 9:52 AM, David Ferrington, M0XDF wrote:
>>>
>>>> Cool. Are you planning on allow us to specify specific bands to  
>>>> look in and also allow us to limit dup search to a specific date  
>>>> & time?
>>>
>>> Possibly, which is more useful or more used ? I'm trying to keep  
>>> the interface as simple as possible.
>>>
>>> Don't forget you can now sort the partial call list in the Contest  
>>> Helper Window by date or by band or by call.
>>>
>>> Any other fields that would be useful in the partial call list ?
>>>
>>> 73 Don Agro VE3VRW
>>>
>
> _______________________________________________
> MacLoggerContest mailing list
> MacLoggerContest at dogparksoftware.com
> http://seven.pairlist.net/mailman/listinfo/macloggercontest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090219/c31a28b1/attachment.html>

From dagro at dogparksoftware.com  Thu Feb 19 11:24:35 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 11:24:35 -0500
Subject: [MacLoggerContest] [macloggerdx] Re: [DogParkList] MacLoggerDX
	V5 for Cocoa 5.01b3
In-Reply-To: <3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
Message-ID: <771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>


On 19-02-2009, at 10:08 AM, David Ferrington, M0XDF wrote:

> Well, when looking for dups in a contest, not having a lot of chaff
> from previous contest or different bands helps a lot in spotting a  
> call.
> The setup in v4 was pretty good


5.01 Beta 4

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Thu Feb 19 11:33:14 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 11:33:14 -0500
Subject: [MacLoggerContest] [macloggerdx] Re: [DogParkList] MacLoggerDX
	V5 for Cocoa 5.01b3
In-Reply-To: <771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
Message-ID: <0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>


On 19-02-2009, at 11:24 AM, Don Agro wrote:

> 5.01 Beta 4


With Beta 4 a double-click on either list will put the call in the  
contest and dx call sign text fields and optionally do a lookup, but  
perhaps a double click on the dupes list should just display the log  
entry ?

What do you think ?

73 Don Agro VE3VRW

D o g   P a r k   S o f t w a r e   L t d .

email: dagro at dogparksoftware.com
   www: http://www.dogparksoftware.com
     iChat AV:dogpark at mac.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090219/2a32931f/attachment.html>

From wb0m at flashdog.us  Thu Feb 19 13:57:11 2009
From: wb0m at flashdog.us (wb0m at flashdog.us)
Date: Thu, 19 Feb 2009 12:57:11 -0600
Subject: [MacLoggerContest] dupe notifaction
Message-ID: <828C03D7-24D9-42F2-BA8E-A8D1102E4E2A@flashdog.us>

I believe this has been mentioned before, but I don't remember seeing  
the answer. Are there any plans to change the "dupe" notification on  
v5 so it's similar to v4, i.e. the red dot, so it's a little easier to  
see if there a dupe?
I'm anxious to give MLDX v5 a good workout this weekend during the DX  
cw contest.
Tnx, Don, & 73, Jeff/wb0m

From dagro at dogparksoftware.com  Thu Feb 19 14:26:09 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 14:26:09 -0500
Subject: [MacLoggerContest] dupe notifaction
In-Reply-To: <828C03D7-24D9-42F2-BA8E-A8D1102E4E2A@flashdog.us>
References: <828C03D7-24D9-42F2-BA8E-A8D1102E4E2A@flashdog.us>
Message-ID: <0E8CC266-53AA-4046-B9F7-065295B71FE5@dogparksoftware.com>

Hi Jeff,

On 19-02-2009, at 1:57 PM, wb0m at Flashdog.us wrote:

> I believe this has been mentioned before, but I don't remember  
> seeing the answer. Are there any plans to change the "dupe"  
> notification on v5 so it's similar to v4, i.e. the red dot, so it's  
> a little easier to see if there a dupe?

None at the moment.

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Thu Feb 19 14:38:24 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 14:38:24 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
Message-ID: <A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>

Hi Jonathan,

On 19-02-2009, at 2:04 PM, Jonathan G0DVJ wrote:

> Thanks for the heads up on the new beta ... I am about to go out for  
> an appointment but will try to find time later to look at this more.
>
> A few quick observations from the contester viewpoint ...
>
> Dupes:
>
> 1) The band drop down could usefully have an option which is  
> "current band" since you are most likely to want to flag up a dupe  
> station on the band you are currently on - so that you don't work it  
> again on that band.  "All bands" is also useful in some events where  
> you are not able to work the same station regardless of band.   I  
> would only use the individual band options if it were a single band  
> contest but if there was a "current band" option that would cater in  
> place of all the individual band options.   So to make it a simpler  
> drop down, two options "All Bands" and "Current Band" would do.

What makes you think that is "easy" ? The Contest Helper does not know  
what the current band is. It could be done but it would be several  
weeks worth of work, so please consider how much you need this  
carefully.

> 2) When a dupe is found it is useful to display a table of band,  
> date (Today or Yesterday is sufficient), time and serial number  
> received (where applicable).  The call is not needed in a column  
> since it will be the call which is being logged at the time, if that  
> helps simplify the interface.

So you want:

Date/time (Today or Yesterday may be sufficient for you but it is not  
that simple - can we assume the contester knows what day it is ? There  
is a date criteria so that can be set to whatever you want)
Time-on
Serial Number Received (what about the received string ?)


> 3) I always use CAT control and so frequency is auto logged ...  
> however Band is not filled in I think ... so Band in the Dupe table  
> is often blank for me.

V5 Fills in Band

> 4) I don't think I would ever use the 2 check boxes provided Lookup  
> & Display QSO.   Others might I suppose (David?) but I would skip  
> them.

Does that mean you want them always active or always inactive ?


> SCP:
>
> 1) The lookup currently only works from the start of a callsign ...  
> would be good to scrap this limitation ... an example might help ...
> If I type K3Z then the Lookup offers me K3ZO which works now.
> If I only hear and type 3ZO it would be good if it offered me K3ZO  
> as well !

OK, so we never need to restrict it to the start of the call for SCP,  
but we do for the dupes ? or we don't ?



73 Don Agro VE3VRW

D o g   P a r k   S o f t w a r e   L t d .

email: dagro at dogparksoftware.com
   www: http://www.dogparksoftware.com
     iChat AV:dogpark at mac.com


From M0XDF at Alphadene.co.uk  Thu Feb 19 15:00:14 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Thu, 19 Feb 2009 20:00:14 +0000
Subject: [MacLoggerContest] [macloggerdx] Re: [DogParkList] MacLoggerDX
	V5 for Cocoa 5.01b3
In-Reply-To: <0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
Message-ID: <55AEDF98-59EF-4CB6-BE55-32A8D9D44C9C@Alphadene.co.uk>

By lookup, do you mean in QRZ etc or in the SCP?
Some contests prohibit the use of  QRZ type lookups I believe. I  
generally don't do a online lookup during contests, I disable it,  
because it slows logging down.
-- 
i don't do caps, i'm a unix man!
david ferrington, 1953 -

On 19 Feb 2009, at 16:33, Don Agro wrote:

>
> On 19-02-2009, at 11:24 AM, Don Agro wrote:
>
>> 5.01 Beta 4
>
>
> With Beta 4 a double-click on either list will put the call in the  
> contest and dx call sign text fields and optionally do a lookup, but  
> perhaps a double click on the dupes list should just display the log  
> entry ?
>
> What do you think ?
>
> 73 Don Agro VE3VRW
>
> D o g   P a r k   S o f t w a r e   L t d .
>
> email: dagro at dogparksoftware.com
>   www: http://www.dogparksoftware.com
>     iChat AV:dogpark at mac.com
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090219/ca06f5e1/attachment.htm>

From dagro at dogparksoftware.com  Thu Feb 19 15:07:24 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 15:07:24 -0500
Subject: [MacLoggerContest] [macloggerdx] Re: [DogParkList] MacLoggerDX
	V5 for Cocoa 5.01b3
In-Reply-To: <55AEDF98-59EF-4CB6-BE55-32A8D9D44C9C@Alphadene.co.uk>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<55AEDF98-59EF-4CB6-BE55-32A8D9D44C9C@Alphadene.co.uk>
Message-ID: <5D41454D-E208-4936-9C26-BFBC3AC48FE9@dogparksoftware.com>

Hi David,

On 19-02-2009, at 3:00 PM, David Ferrington, M0XDF wrote:

> By lookup, do you mean in QRZ etc or in the SCP?

Both, Beta 8 optionally (check box) does a lookup for SCP, and a "Show  
QSO" for a dupe when you double-click on an entry in each list.

> Some contests prohibit the use of  QRZ type lookups I believe. I  
> generally don't do a online lookup during contests, I disable it,  
> because it slows logging down.

There is a checkbox to disable it in both cases and you don't have to  
double-click in either case. The question is - what do you want to  
happen when you double click in each list ?

73 Don Agro VE3VRW

D o g   P a r k   S o f t w a r e   L t d .

email: dagro at dogparksoftware.com
   www: http://www.dogparksoftware.com
     iChat AV:dogpark at mac.com


From dagro at dogparksoftware.com  Thu Feb 19 15:03:59 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 15:03:59 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
Message-ID: <0FB38592-364F-4A65-A8C4-C2EA990D83BC@dogparksoftware.com>

Hi Jonathan,

On 19-02-2009, at 2:04 PM, Jonathan G0DVJ wrote:

> Thanks for the heads up on the new beta ... I am about to go out for  
> an appointment but will try to find time later to look at this more.

I put some of those changes in Beta 8. Please have a look when you get  
a chance.

Thanks,


73 Don Agro VE3VRW


From wb0m at Flashdog.us  Thu Feb 19 15:34:31 2009
From: wb0m at Flashdog.us (wb0m@flashdog.us)
Date: Thu, 19 Feb 2009 14:34:31 -0600
Subject: [MacLoggerContest] dupe notifaction
Message-ID: <D23D4113-9FAC-4AB2-998D-F29BAD9164AA@Flashdog.us>

Is this something that may get added in the future? When contesting  
with v4 (and just in general), it's been really nice to see that red  
dot... (he asks hopefully). 73, Jeff/wb0m




On 19-02-2009, at 1:57 PM, wb0m at Flashdog.us wrote:

> I believe this has been mentioned before, but I don't remember  
> seeing the answer. Are there any plans to change the "dupe"  
> notification on v5 so it's similar to v4, i.e. the red dot, so it's  
> a little easier to see if there a dupe?

None at the moment.

73 Don Agro VE3VRW
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090219/cbf5ebb0/attachment.html>

From M0XDF at Alphadene.co.uk  Thu Feb 19 15:48:30 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Thu, 19 Feb 2009 20:48:30 +0000
Subject: [MacLoggerContest] dupe notifaction
In-Reply-To: <D23D4113-9FAC-4AB2-998D-F29BAD9164AA@Flashdog.us>
References: <D23D4113-9FAC-4AB2-998D-F29BAD9164AA@Flashdog.us>
Message-ID: <A4DAA007-660B-4E6D-BA6C-3EC81274A6F4@Alphadene.co.uk>

It was I who asked it we could have the red dot back. And yes, I look  
around the CallSign field for an indication - do the text on the far  
left.
73 de M0XDF, MLDXv5.01b8
-- 
Not all those that wander are lost. -J.R.R. Tolkien, novelist and
philologist (1892-1973)

On 19 Feb 2009, at 20:34, wb0m at flashdog.us wrote:

> Is this something that may get added in the future? When contesting  
> with v4 (and just in general), it's been really nice to see that red  
> dot... (he asks hopefully). 73, Jeff/wb0m
>
>
>
>
> On 19-02-2009, at 1:57 PM, wb0m at Flashdog.us wrote:
>
>> I believe this has been mentioned before, but I don't remember  
>> seeing the answer. Are there any plans to change the "dupe"  
>> notification on v5 so it's similar to v4, i.e. the red dot, so it's  
>> a little easier to see if there a dupe?
>
> None at the moment.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090219/efcca8d5/attachment.html>

From dagro at dogparksoftware.com  Thu Feb 19 15:51:54 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 15:51:54 -0500
Subject: [MacLoggerContest] dupe notifaction
In-Reply-To: <A4DAA007-660B-4E6D-BA6C-3EC81274A6F4@Alphadene.co.uk>
References: <D23D4113-9FAC-4AB2-998D-F29BAD9164AA@Flashdog.us>
	<A4DAA007-660B-4E6D-BA6C-3EC81274A6F4@Alphadene.co.uk>
Message-ID: <03440D4F-91FB-43FE-B72F-406369BB667A@dogparksoftware.com>


On 19-02-2009, at 3:48 PM, David Ferrington, M0XDF wrote:

> It was I who asked it we could have the red dot back. And yes, I  
> look around the CallSign field for an indication - do the text on  
> the far left.

I guess you guys don't remember the 100 or so emails from the  
contester who objected to the Iconic ramifications of using a flashing  
red anything in the GUI. That ate up a lot of time.

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Thu Feb 19 15:52:47 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 15:52:47 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <DA206D56-D2B2-409A-98F1-3059DC2E30B2@Alphadene.co.uk>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<DA206D56-D2B2-409A-98F1-3059DC2E30B2@Alphadene.co.uk>
Message-ID: <EECD4A98-CAA4-441E-A583-882E820F7988@dogparksoftware.com>


On 19-02-2009, at 3:26 PM, David Ferrington, M0XDF wrote:

> Current Band - really killer feature; need to have, low on scale
> Being able to choose the band in the contest helper pop-up is  
> probably the significant issue. Some contests allow dup QSO's on a  
> different mode/band - ie in multi-band contests. So being able to  
> choose if a dupe is per date or per date AND band is important -  
> doing so automatically based on current band would be a very good  
> feature, but picking it by hand is ok in my book.
>
> Having said that, I also would have though it was a reasonable  
> simple thing yo do - get current band from main window - apply to  
> band displayed in Contest helper.
> Obviously it's not as simple as one would have thought - why?

The Contest Data Source is not connected to the radio, it would have  
to query the Radio Controller object through the application delegate.  
This would also add to the CPU load for each item in the log as they  
are tested in real time for the search criteria each time a key is  
pressed in the Contest call sign text field.

> As I understand it (I haven't yet done a contest that spans > 24hrs  
> or goes over midnight) what we are  looking for is an indication of  
> when the contact was previously made. THis would normally be up to  
> 48 hrs ago on a lomg weekend contest.
>
> Don't assume that 36 hrs into a contest with perhaps no sleep, the  
> op is capable of a lot of stimulant thought - I would think at that  
> point the sub-neural has cut in and everything is working by  
> remembered reflex :-)
>
> Don't assume the operator remembers their own name, that's alone  
> what day it is!
>
> Time-on and Serial number is what is required, typical response is  
> "we worked yesterday at 23:58, I gave you 1234". received string  
> probably not required.

But Jonathan specifically asked for received serial number :

On 19-02-2009, at 2:04 PM, Jonathan G0DVJ wrote:

> 2) When a dupe is found it is useful to display a table of band,  
> date (Today or Yesterday is sufficient), time and serial number  
> received (where applicable)

Do you want both received serial number and sent serial number ?

Rewriting the duplicate list data source to display dates as  
"Yesterday" instead of the date is not trivial.
You can set the date controller at the start of the contest to show  
nothing before the start of the contest and that is remembered in the  
Prefs so you are only dealing with one or two dates.

>>> 4) I don't think I would ever use the 2 check boxes provided  
>>> Lookup & Display QSO.   Others might I suppose (David?) but I  
>>> would skip them.
>>
>> Does that mean you want them always active or always inactive ?
> I don't use them currently, it takes too much time (yes it's only a  
> second or so, but that is too long). I leave look-up off (QRZ  
> subscribed).
> However, clearly some ops do use look-up and I guess that look-up  
> via a CDRom or disk list is fast and therefore not a problem.
>
> So just what does the 'Look Up' check box on the Contest Helper  
> enable?

In the K5ZD list it does a full lookup on the call.
In the Duplicates List it displays the QSO from your log.


>> OK, so we never need to restrict it to the start of the call for  
>> SCP, but we do for the dupes ? or we don't ?
> Dupes must be exact match in my book - you can only test for a dupe  
> when you've got the exact call. Even a single letter difference  
> means its not a dupe.

What about a different prefix or suffix - do they never change during  
a contest ?

At any rate if you type in enough letters you will by definition be  
getting an exact match - try it.

73 Don Agro VE3VRW



From wb0m at Flashdog.us  Thu Feb 19 16:19:27 2009
From: wb0m at Flashdog.us (wb0m@flashdog.us)
Date: Thu, 19 Feb 2009 15:19:27 -0600
Subject: [MacLoggerContest] dupe notification
Message-ID: <88C36933-BD40-4DD9-89D3-B7778A8FEFB2@Flashdog.us>

Oops. Sorry. Selective memory on my part. - jeff/wb0m


On 19-02-2009, at 3:48 PM, David Ferrington, M0XDF wrote:

> It was I who asked it we could have the red dot back. And yes, I  
> look around the CallSign field for an indication - do the text on  
> the far left.

I guess you guys don't remember the 100 or so emails from the  
contester who objected to the Iconic ramifications of using a flashing  
red anything in the GUI. That ate up a lot of time.

73 Don Agro VE3VRW

From dagro at dogparksoftware.com  Thu Feb 19 16:44:38 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 16:44:38 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <DA206D56-D2B2-409A-98F1-3059DC2E30B2@Alphadene.co.uk>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<DA206D56-D2B2-409A-98F1-3059DC2E30B2@Alphadene.co.uk>
Message-ID: <673C8266-8A37-4943-A189-C8FFABDC93E6@dogparksoftware.com>


On 19-02-2009, at 3:26 PM, David Ferrington, M0XDF wrote:

> Current Band - really killer feature; need to have,

It's in Beta 10 (Just wanted to make sure you really needed it ;)

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Thu Feb 19 17:01:05 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 17:01:05 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <9771004E-2B3A-4830-A61D-6D0C54773A4E@mac.com>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<DA206D56-D2B2-409A-98F1-3059DC2E30B2@Alphadene.co.uk>
	<673C8266-8A37-4943-A189-C8FFABDC93E6@dogparksoftware.com>
	<9771004E-2B3A-4830-A61D-6D0C54773A4E@mac.com>
Message-ID: <2D8D8CA6-CB7A-43E7-AE4E-CA99FDA181B3@dogparksoftware.com>

Hi Rick,

On 19-02-2009, at 4:52 PM, Rick Prather wrote:

> Contest Helper looks great to me now.  Can't figure our why I would  
> want the "RX and TX" columns but I guess they don't hurt and if it's  
> good for someone then so be it.Should be able to give it a workout  
> this weekend.

Great !

Don't forget you can move the columns you aren't interested in, off to  
the right.

Every contester seems to have slightly different requirements so I  
guess the trick is to put as many of the important requirements in  
there as possible, but allow them to be disregarded, or turned off so  
they don't get in the way of those that don't need or want them. The  
other possibility is to configure the GUI for each contest - but  
please, let's not go there :)
I have always considered an abundance of user configuration to be an  
admission of poor design.

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Thu Feb 19 17:23:02 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Thu, 19 Feb 2009 17:23:02 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <6C15328F-A7CE-4847-A4D9-B044AB3BC786@amsat.org>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<DA206D56-D2B2-409A-98F1-3059DC2E30B2@Alphadene.co.uk>
	<EECD4A98-CAA4-441E-A583-882E820F7988@dogparksoftware.com>
	<6C15328F-A7CE-4847-A4D9-B044AB3BC786@amsat.org>
Message-ID: <076B2550-2835-420C-AC5C-CB0684CE5B4D@dogparksoftware.com>

Hi Jonathan,

On 19-02-2009, at 5:03 PM, Jonathan G0DVJ wrote:

> I'm sure that a quick audio discussion on iChat would resolve some  
> of these queries quicker than the 20 or so emails flowing back and  
> forth but not sure that fits the logistics of you both ... happy to  
> bend to fit tho

It's probably best to keep it on the contest list to get as much  
feedback as possible.

> On Feb 19, 2009, at 8:52 pm, Don Agro wrote:
>>
>> On 19-02-2009, at 3:26 PM, David Ferrington, M0XDF wrote:
>>
>>> Current Band - really killer feature; need to have, low on scale
>>> Being able to choose the band in the contest helper pop-up is  
>>> probably the significant issue. Some contests allow dup QSO's on a  
>>> different mode/band - ie in multi-band contests. So being able to  
>>> choose if a dupe is per date or per date AND band is important -  
>>> doing so automatically based on current band would be a very good  
>>> feature, but picking it by hand is ok in my book.
>
> OK but I'm thinking about all those comments that people made  
> telling me that some folk contesting solid for >24 hours cant  
> remember their own name necessarily so we shouldn't assume things  
> etc.   I am afraid I would forget to change the drop down in the  
> contest helper every time I change band and hence the dupe  
> indication would be worthless.  That's the only reason I suggested  
> automatically offering "current band" ... I had no idea that it  
> wasn't simple to do ... sorry - to clarify when I said make the drop  
> down simpler I merely meant aesthetically having 2 entries instead  
> of each band plus all!  I didn't mean to second guess how easy or  
> difficult it is to program - Don's the expert there ... what he says  
> goes!

It's in Beta 10.

>>> David and I are almost agreeing here I think!  That typical  
>>> response is almost right - what I want to be able to give...  
>>> except that it is received serial not sent which is most useful in  
>>> convincing the other guy that we have indeed already worked ...  
>>> Telling him what serial you gave him yesterday at 23:58 doesn't  
>>> help him find (and possibly correct) your call in his log.   
>>> Instead saying "we worked yesterday at 23:58 - you gave me 106"  
>>> immediately lets him look in his log at QSO 106 and check the call  
>>> recorded then against your call now.  Hence my asking for received  
>>> and not sent number.

OK, well they are both in beta 10

> Agree with David ...  It is NOT necessary to display received string  
> - just number.

OK, no strings in beta 10, just tx and rx sn.

>>> Do you want both received serial number and sent serial number ?
>
> No - as above.  If he copied my number wrong and my call wrong then  
> its not a QSO !!!  I would just work the dupe again.

They are both there in Beta 10 - move the one you are not interested  
in off to the right.

>> Rewriting the duplicate list data source to display dates as  
>> "Yesterday" instead of the date is not trivial.
>> You can set the date controller at the start of the contest to show  
>> nothing before the start of the contest and that is remembered in  
>> the Prefs so you are only dealing with one or two dates.
>
> Ok - again didn't know what the complexity is - just noticed that  
> Apple often code things to substitute Yesterday and Today rather  
> than actual dates in finder windows in details view for example.    
> In the case of dupes ... contests only last max 48 hours so it can  
> only be one of two days max.  And rather than remembering the date  
> in the heat of it all, I just thought reading it and saying as David  
> suggested "We worked yesterday/today at ..." would be simpler for  
> the operator than mentally thinking and saying the relevant word.   
> However this is not a big deal at all ... I can manage the mental  
> work!

There will only be one or two dates displayed if you set the date  
picker at the start of the contest.

> If the others have that use it have time to click and populate it  
> fine .. I don't (when working 6Qs a minute) - its no big deal if the  
> facility stays but I David and I need not use it.  I wouldn't use  
> the lookup feature in the contest helper window so to answer your  
> question I guess always inactive.

The Prefs will keep them set to whatever you like.

> Let me try another example on the Dupe thing to see if it is easier  
> to explain how it would help the operator most  (but yes I agree  
> that exact match is required for dupe)...
>
> I type G0A (Dupe window shows nothing unless I have worked short  
> call G0A) .. I continue typing B (Dupe window still shows nothing  
> unless I have worked G0AB - unlikely as 2 letter suffixes with G0  
> prefix were never issued!) ... I continue to type C and the Dupe  
> window stays empty unless I have worked G0ABC, subject to the date  
> and band criteria already set.  If I have worked him on other bands  
> within the time/date criteria ideally it would show in normal  
> colour.  If I have worked him on the band I am on (assuming I have  
> set the band drop down correctly or current is implemented) it  
> should show highlighted in the list (dare I mention red?)  to  
> immediately tell me NOT to work him again.
> I dont care if he calls me as G0ABC/P or /A or anything ... if it is  
> the same station on the same band (or different band depending on  
> contest) I don't want him again.  This is similarly true in the  
> unlikely case that he crosses the border into Wales and calls me as  
> GW0ABC ... he's still a dupe!

Beta 10 will find the typed string in any position for both call  
completion and dupes. I don't think it will be a problem.

73 Don Agro VE3VRW



From M0XDF at Alphadene.co.uk  Fri Feb 20 01:30:03 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Fri, 20 Feb 2009 06:30:03 +0000
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <076B2550-2835-420C-AC5C-CB0684CE5B4D@dogparksoftware.com>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<DA206D56-D2B2-409A-98F1-3059DC2E30B2@Alphadene.co.uk>
	<EECD4A98-CAA4-441E-A583-882E820F7988@dogparksoftware.com>
	<6C15328F-A7CE-4847-A4D9-B044AB3BC786@amsat.org>
	<076B2550-2835-420C-AC5C-CB0684CE5B4D@dogparksoftware.com>
Message-ID: <0A17E9D2-B360-491A-B558-AEDB5011972F@Alphadene.co.uk>

Good heavens, I go away for a few hours and all this... :-)
--  
It is forbidden to kill; therefore all murderers are punished unless  
they
kill in large numbers and to the sound of trumpets.
-Voltaire, philosopher (1694-1778)

On 19 Feb 2009, at 22:23, Don Agro wrote:
> It's in Beta 10.
now that is good

>>>> David and I are almost agreeing here I think!  That typical  
>>>> response is almost right - what I want to be able to give...  
>>>> except that it is received serial not sent which is most useful  
>>>> in convincing the other guy that we have indeed already  
>>>> worked ... Telling him what serial you gave him yesterday at  
>>>> 23:58 doesn't help him find (and possibly correct) your call in  
>>>> his log.  Instead saying "we worked yesterday at 23:58 - you gave  
>>>> me 106" immediately lets him look in his log at QSO 106 and check  
>>>> the call recorded then against your call now.  Hence my asking  
>>>> for received and not sent number.
>
> OK, well they are both in beta 10
Yes, Jonathan is correct there, it is better to give him time and the  
serial # he gave me (I wasn't thinking straight when I said the serial  
I gave him) and your solution to that is just ideal.
That is just fantastic and very fast too.

> Beta 10 will find the typed string in any position for both call  
> completion and dupes. I don't think it will be a problem.

Very good Don, I think you've got it. Jonathan?

I think I've figured out the check boxes...
Lookup - if checked then double-click on left column (SCP) will fill  
in Call on main panel and look the call up. If not checked, then  
double-click just fills in call.

Display QSO - if checked then double-click on right column (dupes)  
will display the entire QSL in the mail panel.  If not checked, then  
double-click does nothing.

Have I got that right?

I'm very impressed with this Don, I think this is a great step forward  
for contesters.

73 de M0XDF, MLDXv5.01b11

From M0XDF at Alphadene.co.uk  Fri Feb 20 01:42:52 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Fri, 20 Feb 2009 06:42:52 +0000
Subject: [MacLoggerContest] While on subject of Contests
Message-ID: <73005FE9-8074-4404-A344-2A3B94590706@Alphadene.co.uk>

Don, While your in 'contest' mode, could you make the Grid field in  
the Contest panel enterable?
If we are working a contest where we can not use an Internet lookup  
(for whatever reason; banned or portable with no network etc), then we  
will often need to enter the Grid. VHF+ contests use this a lot (at  
least in the UK).

Typical exchange if I'm responding to a CQ, goes something like
"G0ABC contest"
	M0XDF
"M0XDF 57 number 034 IO91JO"
	Thank you for the 34, you are 59 002 in IO91PK, QSL?
"QSL"
"G0ABC contest"

So, we need to record the Grid.

You can also see from this why I was requesting a different sequence  
to the field order, or a configurable tab order. For the present, I  
understand you have other priorities.

73 de M0XDF, MLDXv5.01b11
-- 
When work is a pleasure, life is a joy! When work is a duty, life is
slavery. -Maxim Gorky, author (1868-1936)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090220/259dd2e5/attachment.html>

From M0XDF at Alphadene.co.uk  Fri Feb 20 04:12:04 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Fri, 20 Feb 2009 09:12:04 +0000
Subject: [MacLoggerContest] dupe notification
In-Reply-To: <88C36933-BD40-4DD9-89D3-B7778A8FEFB2@Flashdog.us>
References: <88C36933-BD40-4DD9-89D3-B7778A8FEFB2@Flashdog.us>
Message-ID: <0669AA61-2E32-49E3-9160-F8464ECBA3A8@Alphadene.co.uk>

No I don't remember, but ok, we have the contest help and I do look  
there.
So no problem with that.

I have to learn to look over to the left in DX window!
-- 
A child, like your stomach, doesn't need all you can afford to give it.
-Frank A. Clark, writer (1911- )

On 19 Feb 2009, at 21:19, wb0m at flashdog.us wrote:

> Oops. Sorry. Selective memory on my part. - jeff/wb0m
>
>
> On 19-02-2009, at 3:48 PM, David Ferrington, M0XDF wrote:
>
>> It was I who asked it we could have the red dot back. And yes, I  
>> look around the CallSign field for an indication - do the text on  
>> the far left.
>
> I guess you guys don't remember the 100 or so emails from the  
> contester who objected to the Iconic ramifications of using a  
> flashing red anything in the GUI. That ate up a lot of time.
>
> 73 Don Agro VE3VRW
> _______________________________________________
> MacLoggerContest mailing list
> MacLoggerContest at dogparksoftware.com
> http://seven.pairlist.net/mailman/listinfo/macloggercontest


From dagro at dogparksoftware.com  Fri Feb 20 05:52:12 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Fri, 20 Feb 2009 05:52:12 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <0A17E9D2-B360-491A-B558-AEDB5011972F@Alphadene.co.uk>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<DA206D56-D2B2-409A-98F1-3059DC2E30B2@Alphadene.co.uk>
	<EECD4A98-CAA4-441E-A583-882E820F7988@dogparksoftware.com>
	<6C15328F-A7CE-4847-A4D9-B044AB3BC786@amsat.org>
	<076B2550-2835-420C-AC5C-CB0684CE5B4D@dogparksoftware.com>
	<0A17E9D2-B360-491A-B558-AEDB5011972F@Alphadene.co.uk>
Message-ID: <18B830A6-45DD-44BE-85A7-30D53883056C@dogparksoftware.com>


On 20-02-2009, at 1:30 AM, David Ferrington, M0XDF wrote:

> I think I've figured out the check boxes...
> Lookup - if checked then double-click on left column (SCP) will fill  
> in Call on main panel and look the call up. If not checked, then  
> double-click just fills in call.
>
> Display QSO - if checked then double-click on right column (dupes)  
> will display the entire QSL in the mail panel.  If not checked, then  
> double-click does nothing.
>
> Have I got that right?

Almost. If unchecked - double clicking a line in either list will put  
the text in the call sign fields of both the contest and the dx panel.

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Fri Feb 20 06:02:41 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Fri, 20 Feb 2009 06:02:41 -0500
Subject: [MacLoggerContest] Tab order and editable fields
In-Reply-To: <73005FE9-8074-4404-A344-2A3B94590706@Alphadene.co.uk>
References: <73005FE9-8074-4404-A344-2A3B94590706@Alphadene.co.uk>
Message-ID: <0AD20412-4688-47E4-80D8-F60ED0C77502@dogparksoftware.com>

Hi David,

On 20-02-2009, at 1:42 AM, David Ferrington, M0XDF wrote:

> Don, While your in 'contest' mode, could you make the Grid field in  
> the Contest panel enterable?

I can, but every field that is editable increases the number of fields  
to tab through.

Please have a look at Scott's original email.

<http://seven.pairlist.net/pipermail/macloggercontest/ 
2009q1/000183.html>

You guys will have to sort this out amongst yourselves and let me know  
what conclusion you all come to.


> If we are working a contest where we can not use an Internet lookup  
> (for whatever reason; banned or portable with no network etc), then  
> we will often need to enter the Grid. VHF+ contests use this a lot  
> (at least in the UK).
>
> Typical exchange if I'm responding to a CQ, goes something like
> "G0ABC contest"
> 	M0XDF
> "M0XDF 57 number 034 IO91JO"
> 	Thank you for the 34, you are 59 002 in IO91PK, QSL?
> "QSL"
> "G0ABC contest"
>
> So, we need to record the Grid.
>
> You can also see from this why I was requesting a different sequence  
> to the field order, or a configurable tab order. For the present, I  
> understand you have other priorities.


It's not just that - but each contester has a different preferences.  
Please consult with Scott and the others and let me know what you all  
agree on.

It only takes a few minutes to do this but without consensus I will be  
redoing it constantly.


73 Don Agro VE3VRW


From M0XDF at Alphadene.co.uk  Fri Feb 20 06:25:50 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Fri, 20 Feb 2009 11:25:50 +0000
Subject: [MacLoggerContest] Tab order and editable fields
In-Reply-To: <0AD20412-4688-47E4-80D8-F60ED0C77502@dogparksoftware.com>
References: <73005FE9-8074-4404-A344-2A3B94590706@Alphadene.co.uk>
	<0AD20412-4688-47E4-80D8-F60ED0C77502@dogparksoftware.com>
Message-ID: <B04A13F3-EC7D-4D35-9E8D-59F2E0AC44A0@Alphadene.co.uk>

>
> Please have a look at Scott's original email.
>
> <http://seven.pairlist.net/pipermail/macloggercontest/2009q1/000183.html 
> >
>
> You guys will have to sort this out amongst yourselves and let me  
> know what conclusion you all come to.

OK, will do that

> It's not just that - but each contester has a different preferences.  
> Please consult with Scott and the others and let me know what you  
> all agree on.
>
> It only takes a few minutes to do this but without consensus I will  
> be redoing it constantly.

Yes completely agree on that too - I don't want to cause more work for  
you or Scott and I don't wish to thrust my views on how it should be  
upon others.

I will discuss the possibilities with Scott, before I then ask on here  
what people would like, based on what is possible.

I hope that is an acceptable route?

73 de M0XDF, MLDXv5.01b11

From dagro at dogparksoftware.com  Fri Feb 20 08:34:27 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Fri, 20 Feb 2009 08:34:27 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <4753A4BB-E55F-452E-B0EE-2BB74FA64DF4@amsat.org>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<4753A4BB-E55F-452E-B0EE-2BB74FA64DF4@amsat.org>
Message-ID: <780F8661-CE9A-4A0B-8EDF-3C0ED1854877@dogparksoftware.com>

Hi Jonathan,

On 19-02-2009, at 7:16 PM, Jonathan G0DVJ wrote:

> How easy are timers to add?   Just another thought to support  
> contesters in the helper window at the bottom line ...
>
>   - A counting timer that shows "mm:ss since last QSO"
>
>   - A counting timer that shows "mm since band change"
>
> These reference points help good contesters consider when to S&P  
> instead of running (i.e. QSO rate slows) and when to change band  
> during a long multi-band event.

Beta 12 has the timers as well as corrected tool tips for each GUI  
component of the Contest Helper Window and Grid Square is now editable  
in the Contest Panel.

73 Don Agro VE3VRW


From M0XDF at Alphadene.co.uk  Fri Feb 20 08:36:14 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Fri, 20 Feb 2009 13:36:14 +0000
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <780F8661-CE9A-4A0B-8EDF-3C0ED1854877@dogparksoftware.com>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<4753A4BB-E55F-452E-B0EE-2BB74FA64DF4@amsat.org>
	<780F8661-CE9A-4A0B-8EDF-3C0ED1854877@dogparksoftware.com>
Message-ID: <3B720CBA-FC97-4A35-AB9B-0F10B2C961DC@Alphadene.co.uk>

Thank you very much Don.
--  
Two things are infinite, the universe and human stupidity.
But I'm not so sure about the universe. -- Albert Einstein.



On 20 Feb 2009, at 13:34, Don Agro wrote:

> Hi Jonathan,
>
> On 19-02-2009, at 7:16 PM, Jonathan G0DVJ wrote:
>
>> How easy are timers to add?   Just another thought to support  
>> contesters in the helper window at the bottom line ...
>>
>>  - A counting timer that shows "mm:ss since last QSO"
>>
>>  - A counting timer that shows "mm since band change"
>>
>> These reference points help good contesters consider when to S&P  
>> instead of running (i.e. QSO rate slows) and when to change band  
>> during a long multi-band event.
>
> Beta 12 has the timers as well as corrected tool tips for each GUI  
> component of the Contest Helper Window and Grid Square is now  
> editable in the Contest Panel.
>
> 73 Don Agro VE3VRW
>
> _______________________________________________
> MacLoggerContest mailing list
> MacLoggerContest at dogparksoftware.com
> http://seven.pairlist.net/mailman/listinfo/macloggercontest


From wb0m at flashdog.us  Fri Feb 20 08:53:18 2009
From: wb0m at flashdog.us (wb0m at flashdog.us)
Date: Fri, 20 Feb 2009 07:53:18 -0600
Subject: [MacLoggerContest] ARRL DX contest
Message-ID: <8FE6A5B0-CFAE-40B9-8E38-F24EFC395456@flashdog.us>

This should be fun this weekend with the ARRL DX cw contest and MLDX  
v5. I'm leaving soon for South Dakota to set up a field-day like QTH  
at a small cabin. While every one else heads for a warm island, I head  
north. No phone, no internet and no indoor plumbing (not too bright,  
eh?- hi). It's my radio weekend and it gives me a chance to put up  
some big wire antennas and long receiving antennas play radio  
uninterrupted in a really RF quiet place. I hope to work some of the  
MLDX users and give v5 a good workout. CU on the bands. GL & 73, Jeff/ 
wb0m

From g0dvj at amsat.org  Fri Feb 20 09:12:31 2009
From: g0dvj at amsat.org (Jonathan G0DVJ)
Date: Fri, 20 Feb 2009 14:12:31 +0000
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <780F8661-CE9A-4A0B-8EDF-3C0ED1854877@dogparksoftware.com>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<4753A4BB-E55F-452E-B0EE-2BB74FA64DF4@amsat.org>
	<780F8661-CE9A-4A0B-8EDF-3C0ED1854877@dogparksoftware.com>
Message-ID: <4BF380FC-EC07-4D51-9141-5335252B502E@amsat.org>


On Feb 20, 2009, at 1:34 pm, Don Agro wrote:

> Beta 12 has the timers as well as corrected tool tips for each GUI  
> component of the Contest Helper Window and Grid Square is now  
> editable in the Contest Panel.

Thanks Don.  Great stuff.
Was so dozy last night I kept forgetting to mention I had spotted the  
tool tips typos!   You caught them anyway!


While we are on the contest helper window ...

In the same way that you used colors with cluster spots to show DXers  
if the spot would be a new DXCC or WAZ or confirmed/unconfirmed  
etc ... would it be difficult to colour the call entered & shown in  
the helper window (or the SCP list) to show contesters if that call  
would be a new DXCC or zone or neither or both but subject to the date/ 
time & band settings already set in the helper window (i.e. only for  
the context of the contest being done) ...
(e.g. black if neither, blue if new DXCC, green if new zone, turquoise  
if both, ... oh and red - only text, no blob -  if dupe!)

This would give contesters some indication whether a particular call  
would be of extra value in contests that have country or zone mults.

Thanks again Don,
73
Jonathan G0DVJ
--


From dagro at dogparksoftware.com  Fri Feb 20 09:40:21 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Fri, 20 Feb 2009 09:40:21 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Contest Helper
In-Reply-To: <4BF380FC-EC07-4D51-9141-5335252B502E@amsat.org>
References: <A84D05DC-2B28-43AB-B3CC-1FDCA894C367@dogparksoftware.com>
	<335A65AB-38E7-45F0-81A1-6A87CC0D3949@Alphadene.co.uk>
	<16E0356E-740B-4EC0-B3DF-8500D10B1E0B@dogparksoftware.com>
	<3850579C-E1A9-4800-9126-9C8558DCCC78@Alphadene.co.uk>
	<771D9A5F-B8CC-4FD6-8F45-28EDA45A7584@dogparksoftware.com>
	<0B7E0048-C92B-4CDD-B8EC-6B9BDF4109C8@dogparksoftware.com>
	<7D6837F4-8990-433C-8AF1-E04DBA4F2C3C@dogparksoftware.com>
	<2A2628CC-DF86-4D87-98D5-060EAA97C253@amsat.org>
	<A1D1B944-3BCB-4CA8-BCC0-2FD17403D518@dogparksoftware.com>
	<4753A4BB-E55F-452E-B0EE-2BB74FA64DF4@amsat.org>
	<780F8661-CE9A-4A0B-8EDF-3C0ED1854877@dogparksoftware.com>
	<4BF380FC-EC07-4D51-9141-5335252B502E@amsat.org>
Message-ID: <7A88CCE6-98BA-4E38-839F-F0133CB355B1@dogparksoftware.com>

Hi Jonathan,

On 20-02-2009, at 9:12 AM, Jonathan G0DVJ wrote:

> In the same way that you used colors with cluster spots to show  
> DXers if the spot would be a new DXCC or WAZ or confirmed/ 
> unconfirmed etc ... would it be difficult to colour the call entered  
> & shown in the helper window (or the SCP list) to show contesters if  
> that call would be a new DXCC or zone or neither or both but subject  
> to the date/time & band settings already set in the helper window  
> (i.e. only for the context of the contest being done) ...
> (e.g. black if neither, blue if new DXCC, green if new zone,  
> turquoise if both, ... oh and red - only text, no blob -  if dupe!)

It would be simple to do for the whole log but CPU intensive to  
calculate all of that based on the date/time & band settings set in  
the Contest Helper window.

> This would give contesters some indication whether a particular call  
> would be of extra value in contests that have country or zone mults.

Let me think about it.


73 de VE3VRW Don Agro



From dagro at dogparksoftware.com  Sat Feb 21 07:37:54 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 21 Feb 2009 07:37:54 -0500
Subject: [MacLoggerContest] possible buglet MacLoggerDX for Cocoa
In-Reply-To: <C7444778-7414-4CC7-9940-16A4FB4F174C@amsat.org>
References: <C7444778-7414-4CC7-9940-16A4FB4F174C@amsat.org>
Message-ID: <F57F2207-186F-4962-AD1E-49E345750645@dogparksoftware.com>

Hi Jonathan,

On 21-Feb-09, at 6:50 AM, Jonathan G0DVJ wrote:

> Trying MLDX 5.01 b13 here during ARRL contest just for testing  
> purposes ... so may come up with some reports for you during my  
> day ... Will number them between emails if I find stuff...
>
> 1. Start MLDX ... type a call in Contest entry window (e.g. N3RS),  
> then open contest helper window, go back to main contest entry  
> window and edit the call entered (e.g. backspace to delete the s of  
> n3rs) ... short pause then MLDX unexpectedly quits.

Rick is also seeing a similar crash but I have been unable to  
reproduce it here.

Using your step-by-step sequence above I was able to reproduce it here  
and it is fixed in V5.01 b18 - Thanks !

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Sat Feb 21 14:42:24 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 21 Feb 2009 14:42:24 -0500
Subject: [MacLoggerContest] Contest Helper Mod
In-Reply-To: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
References: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
Message-ID: <6A2C3172-E7E4-4F4B-AF73-2AED3B20DD0D@dogparksoftware.com>

Hi Rick,

On 21-02-09, at 2:25 , Rick Prather wrote:

> Happily running crash free in the DX contest.

Fantastic !

> I do have a suggestion for the Contest Helper though.
> If you are using the cluster during the contest and you triple/click  
> a spot into the log field it is not seen by Contest Helper.
> The only way I can tell if it is a dupe is to go back and manually  
> enter the call.

Contest Helper only responds to keys manually typed into the call sign  
field. Always has.

I think we had better think through the implications if we are to  
change this.

73 Don Agro VE3VRW


From publitek at mac.com  Sat Feb 21 14:58:00 2009
From: publitek at mac.com (Bob Jones)
Date: Sat, 21 Feb 2009 19:58:00 +0000
Subject: [MacLoggerContest] Please unsubscribe me
Message-ID: <DD2DB621-BACA-439C-BF5B-7FA973151717@mac.com>

I keep trying to do this, but it doesn't work!

73 Bob G3YIQ

From dagro at dogparksoftware.com  Sat Feb 21 15:14:00 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 21 Feb 2009 15:14:00 -0500
Subject: [MacLoggerContest] Contest Helper Mod
In-Reply-To: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
References: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
Message-ID: <A957A86E-07F0-4460-937C-45BB5F87DB49@dogparksoftware.com>


On 21-02-09, at 2:25 , Rick Prather wrote:

> If you are using the cluster during the contest and you triple/click  
> a spot into the log field it is not seen by Contest Helper.

What does everyone think ?

I can put a "Cluster" check box on the Contest Helper Window.
What sort of spots ? All, or just the triple-clicked ones ?

73 Don Agro VE3VRW



From M0XDF at Alphadene.co.uk  Sat Feb 21 15:32:56 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Sat, 21 Feb 2009 20:32:56 +0000
Subject: [MacLoggerContest] Contest Helper Mod
In-Reply-To: <A957A86E-07F0-4460-937C-45BB5F87DB49@dogparksoftware.com>
References: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
	<A957A86E-07F0-4460-937C-45BB5F87DB49@dogparksoftware.com>
Message-ID: <7609C997-6910-4861-A83F-98C8CDA1C7B1@Alphadene.co.uk>

Hmmmm - I'd say just the triple-clicked ones - effectively looking it  
up in the SCP as well as on the Internet (if Internet lookup is enabled)
73 de M0XDF, MLDXv5.01b12
-- 
Write the bad things that are done to you in the sand, but write the
good things that happen to you on a piece of marble. -Arabian wisdom

On 21 Feb 2009, at 20:14, Don Agro wrote:

>
> On 21-02-09, at 2:25 , Rick Prather wrote:
>
>> If you are using the cluster during the contest and you triple/ 
>> click a spot into the log field it is not seen by Contest Helper.
>
> What does everyone think ?
>
> I can put a "Cluster" check box on the Contest Helper Window.
> What sort of spots ? All, or just the triple-clicked ones ?
>
> 73 Don Agro VE3VRW
>
>
> _______________________________________________
> MacLoggerContest mailing list
> MacLoggerContest at dogparksoftware.com
> http://seven.pairlist.net/mailman/listinfo/macloggercontest


From dagro at dogparksoftware.com  Sat Feb 21 15:38:19 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 21 Feb 2009 15:38:19 -0500
Subject: [MacLoggerContest] Contest Helper Mod
In-Reply-To: <B7BADC8E-621B-4EDD-9163-3D5CB269A270@mac.com>
References: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
	<A957A86E-07F0-4460-937C-45BB5F87DB49@dogparksoftware.com>
	<B7BADC8E-621B-4EDD-9163-3D5CB269A270@mac.com>
Message-ID: <442D7A2B-6007-4440-B585-D56775395BD6@dogparksoftware.com>


On 21-02-09, at 3:25 , Rick Prather wrote:

> I would be happy with just the triple-clicked ones.  Those are the  
> ones I am interested in working but don't know if they are dupes.
>
> If it were possible to have them checked just like I had hand input  
> them without an additional field in Contest Helper it would be great.

Beta 20, no additional field - just a check box to enable/disable it.

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Sat Feb 21 15:43:34 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 21 Feb 2009 15:43:34 -0500
Subject: [MacLoggerContest] Contest Helper Mod
In-Reply-To: <7609C997-6910-4861-A83F-98C8CDA1C7B1@Alphadene.co.uk>
References: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
	<A957A86E-07F0-4460-937C-45BB5F87DB49@dogparksoftware.com>
	<7609C997-6910-4861-A83F-98C8CDA1C7B1@Alphadene.co.uk>
Message-ID: <138DFA28-33EA-41F9-B3BA-6D6BF5B04E61@dogparksoftware.com>

Hi David,

On 21-02-09, at 3:32 , David Ferrington, M0XDF wrote:

> Hmmmm - I'd say just the triple-clicked ones -

Beta 20

> effectively looking it up in the SCP

What would the SCP tell you ? It's already a DX Spot ?

> as well as on the Internet (if Internet lookup is enabled)

DXCluster "Auto Lookup" already does that. What I have added is just  
the duplicates check.

73 Don Agro VE3VRW


From g0dvj at amsat.org  Sat Feb 21 16:09:18 2009
From: g0dvj at amsat.org (Jonathan G0DVJ)
Date: Sat, 21 Feb 2009 21:09:18 +0000
Subject: [MacLoggerContest] Contest Helper Mod
In-Reply-To: <442D7A2B-6007-4440-B585-D56775395BD6@dogparksoftware.com>
References: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
	<A957A86E-07F0-4460-937C-45BB5F87DB49@dogparksoftware.com>
	<B7BADC8E-621B-4EDD-9163-3D5CB269A270@mac.com>
	<442D7A2B-6007-4440-B585-D56775395BD6@dogparksoftware.com>
Message-ID: <8A1B1A3B-D438-4C82-9B6F-0E279B82768A@amsat.org>


FWIW - yes I think this is the right choice.

The key thing as Rick and David alluded to is that if you see a spot  
on the cluster for the contest, you want a near instant way to check  
if its a dupe in the contest - and the helper does that.  So triple  
click is fine.

Jonathan G0DVJ
--

On 21 Feb 2009, at 20:38, Don Agro wrote:

>
> On 21-02-09, at 3:25 , Rick Prather wrote:
>
>> I would be happy with just the triple-clicked ones.  Those are the  
>> ones I am interested in working but don't know if they are dupes.
>>
>> If it were possible to have them checked just like I had hand input  
>> them without an additional field in Contest Helper it would be great.
>
> Beta 20, no additional field - just a check box to enable/disable it.
>

From M0XDF at Alphadene.co.uk  Sat Feb 21 16:33:21 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Sat, 21 Feb 2009 21:33:21 +0000
Subject: [MacLoggerContest] Contest Helper Mod
In-Reply-To: <8A1B1A3B-D438-4C82-9B6F-0E279B82768A@amsat.org>
References: <30A0DE1B-421C-4274-8DBC-63B719EF9774@mac.com>
	<A957A86E-07F0-4460-937C-45BB5F87DB49@dogparksoftware.com>
	<B7BADC8E-621B-4EDD-9163-3D5CB269A270@mac.com>
	<442D7A2B-6007-4440-B585-D56775395BD6@dogparksoftware.com>
	<8A1B1A3B-D438-4C82-9B6F-0E279B82768A@amsat.org>
Message-ID: <3AA09040-5B12-400F-B4D2-411C657A1E8A@Alphadene.co.uk>

And Don is correct, it's dupe checking, not SCP. although it's  
possible someone missposted it on the cluster.
-- 
"There is no limit to what you can accomplish if you don't care who
gets the credit." --Ronald Reagan

On 21 Feb 2009, at 21:09, Jonathan G0DVJ wrote:

>
> FWIW - yes I think this is the right choice.
>
> The key thing as Rick and David alluded to is that if you see a spot  
> on the cluster for the contest, you want a near instant way to check  
> if its a dupe in the contest - and the helper does that.  So triple  
> click is fine.
>
> Jonathan G0DVJ
> --
>
> On 21 Feb 2009, at 20:38, Don Agro wrote:
>
>>
>> On 21-02-09, at 3:25 , Rick Prather wrote:
>>
>>> I would be happy with just the triple-clicked ones.  Those are the  
>>> ones I am interested in working but don't know if they are dupes.
>>>
>>> If it were possible to have them checked just like I had hand  
>>> input them without an additional field in Contest Helper it would  
>>> be great.
>>
>> Beta 20, no additional field - just a check box to enable/disable it.

From dagro at dogparksoftware.com  Sun Feb 22 08:44:22 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sun, 22 Feb 2009 08:44:22 -0500
Subject: [MacLoggerContest] MacLoggerDX V5.01 for Cocoa Time & Date Formats
Message-ID: <A48DFFD7-8858-4CC1-B67D-8E62C4FA625E@dogparksoftware.com>

In version 5.01 (Beta 22) the Log "Time On" and "Time Off" fields have  
been changed to a fixed format : 2009-02-22 08:14:01
This was done to fix a crash when edited QSO's were exported to ADIF.
Your System Preferences Time and Date Formats can now be set to  
anything you like without affecting MacLoggerDX.

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Sun Feb 22 12:28:29 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sun, 22 Feb 2009 12:28:29 -0500
Subject: [MacLoggerContest] [DogParkList] MacLoggerDX V5.01 for Cocoa
	Time & Date Formats
In-Reply-To: <5BDFE3AD-B2C6-4D59-A97F-0DCE86456F12@mac.com>
References: <A48DFFD7-8858-4CC1-B67D-8E62C4FA625E@dogparksoftware.com>
	<5BDFE3AD-B2C6-4D59-A97F-0DCE86456F12@mac.com>
Message-ID: <35E19BFA-887B-4AFC-922E-D80ACB28E85F@dogparksoftware.com>


On 22-Feb-09, at 12:20 PM, Rick Prather wrote:

> BTW, as far as I'm concerned you could drop the seconds.

I like the seconds :) But I have dropped the year and seconds from the  
Contest Helper time display. "02-22 14:44"

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Sun Feb 22 12:37:34 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sun, 22 Feb 2009 12:37:34 -0500
Subject: [MacLoggerContest] MacLoggerDX V5 for Cocoa Update Notifications
Message-ID: <DF41AA70-F52C-4E60-9E14-424566599455@dogparksoftware.com>

Starting with Version 5.01 Beta 24, MacLoggerDX will properly notify  
beta users when the next release version is available. Before that  
only those running 5.0 release would get the notification.

73 Don Agro VE3VRW

From dagro at dogparksoftware.com  Sun Feb 22 13:19:14 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sun, 22 Feb 2009 13:19:14 -0500
Subject: [MacLoggerContest] [DogParkList] MacLoggerDX V5.01 for Cocoa
	Time & Date Formats
In-Reply-To: <5BDFE3AD-B2C6-4D59-A97F-0DCE86456F12@mac.com>
References: <A48DFFD7-8858-4CC1-B67D-8E62C4FA625E@dogparksoftware.com>
	<5BDFE3AD-B2C6-4D59-A97F-0DCE86456F12@mac.com>
Message-ID: <1F6F9574-AE48-4046-A367-F355BCC13EF8@dogparksoftware.com>

On 22-Feb-09, at 12:37 , Don Agro wrote:

> Starting with Version 5.01 Beta 24, MacLoggerDX will properly notify  
> beta users when the next release version is available. Before that  
> only those running 5.0 release would get the notification.

On 22-Feb-09, at 12:20 , Rick Prather wrote:

> Thanks, that's something I have wanted since v4..

In version 5.01 Beta 25 the Log Time On and Time Off fields have been  
changed to a fixed format : "2009-02-22 08:14:01 PM" I have been  
unable to get the NSTableView NSDateFormatter to use a 24 hour clock  
so the Log will display UTC Time but in 12 hour format. It's a bug  
that probably won't be fixed until OS X 10.6 but the exported ADIF  
date is in the correct 24 hour format: "<QSO_DATE:8>20090222<TIME_ON: 
6>201401<TIME_OFF:6>201408"

73 Don Agro VE3VRW


From g0dvj at amsat.org  Sun Feb 22 13:24:01 2009
From: g0dvj at amsat.org (Jonathan G0DVJ)
Date: Sun, 22 Feb 2009 18:24:01 +0000
Subject: [MacLoggerContest] [DogParkList] MacLoggerDX V5.01 for Cocoa
	Time & Date Formats
In-Reply-To: <35E19BFA-887B-4AFC-922E-D80ACB28E85F@dogparksoftware.com>
References: <A48DFFD7-8858-4CC1-B67D-8E62C4FA625E@dogparksoftware.com>
	<5BDFE3AD-B2C6-4D59-A97F-0DCE86456F12@mac.com>
	<35E19BFA-887B-4AFC-922E-D80ACB28E85F@dogparksoftware.com>
Message-ID: <CE699852-9682-4A97-9349-28EEF9F957DB@amsat.org>


FWIW I like the seconds too...  In a contest I can be running at 6+ Qs  
a minute ... nice to see how the rate varied within the minutes :)

73
Jonathan G0DVJ
--

On 22 Feb 2009, at 17:28, Don Agro wrote:

>
> On 22-Feb-09, at 12:20 PM, Rick Prather wrote:
>
>> BTW, as far as I'm concerned you could drop the seconds.
>
> I like the seconds :) But I have dropped the year and seconds from  
> the Contest Helper time display. "02-22 14:44"
>
> 73 Don Agro VE3VRW
>

From dagro at dogparksoftware.com  Sun Feb 22 13:32:31 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sun, 22 Feb 2009 13:32:31 -0500
Subject: [MacLoggerContest] [DogParkList] MacLoggerDX V5.01 for Cocoa
	Time & Date Formats
In-Reply-To: <1F6F9574-AE48-4046-A367-F355BCC13EF8@dogparksoftware.com>
References: <A48DFFD7-8858-4CC1-B67D-8E62C4FA625E@dogparksoftware.com>
	<5BDFE3AD-B2C6-4D59-A97F-0DCE86456F12@mac.com>
	<1F6F9574-AE48-4046-A367-F355BCC13EF8@dogparksoftware.com>
Message-ID: <49CAD9F1-3165-4753-92A0-E82E59A5AD48@dogparksoftware.com>


On 22-Feb-09, at 13:19 , Don Agro wrote:

> It's a bug that probably won't be fixed until OS X 10.6

OK, so maybe it's fixed in Beta 26 :)

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Sun Feb 22 19:38:25 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sun, 22 Feb 2009 19:38:25 -0500
Subject: [MacLoggerContest] V5 in ARRLDX Contest
In-Reply-To: <72F9FE12-4F02-45E9-9C88-50575D4E21CE@mac.com>
References: <72F9FE12-4F02-45E9-9C88-50575D4E21CE@mac.com>
Message-ID: <CA328AC2-213F-4DCB-9198-F7573E277010@dogparksoftware.com>

Hi Rick,

On 22-Feb-09, at 19:18 , Rick Prather wrote:

> Just finished the contest and cleaned up my log for conversion.
> I have to say that except for the crashing I experienced on Friday  
> evening, that you fixed later that night, MLDX V5 was perfectly  
> stable for the whole contest.

Fantastic !

> The running changes you made during the weekend were all helpful and  
> made it in to a very nice contest logger. Thanks for all your help  
> during the contest.

You are welcome.

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Mon Feb 23 18:13:32 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Mon, 23 Feb 2009 18:13:32 -0500
Subject: [MacLoggerContest] STX MacLoggerDX
In-Reply-To: <68A204DA-6383-44FE-9352-2D6809E66853@mac.com>
References: <68A204DA-6383-44FE-9352-2D6809E66853@mac.com>
Message-ID: <4660CB4C-2763-4F3B-80A6-6B3C3300FAAC@dogparksoftware.com>

Hi Rick,

On 23-Feb-09, at 5:43 PM, Rick Prather wrote:

> I noticed this early on in the V5 development but forgot about it.
>
> Now that I am trying to use CabConverter for the ARRL DX contest I  
> run in to it again.
>
> When I export an ADIF file the STX field is not written.   Looking  
> at the output the SRX field is there buy not STX.
>
> Rick - K6LE

Oops! 5.02 Beta 2

Thanks for catching it.

This ADIF file was created by MacLoggerDX
<PROGRAMID:11>MacLoggerDX<PROGRAMVERSION:4>5.02<adif_ver:5>2.1.4
<EOH>
<CALL:6>EA1CWB<NAME:26>LUIS MIGUEL PICADO FEBRERO
<QTH:43>47162 ALDEAMAYOR DE SAN MARTIN (VALLADOLID)
<ADDRESS:65>C/ CALVARIO, 2
47162 ALDEAMAYOR DE SAN MARTIN (VALLADOLID)
SPAIN
<QSO_DATE:8>20090223<TIME_ON:6>195051<TIME_OFF:6>195056
<FREQ_RX:9>21.330000<FREQ:9>21.330000<BAND:3>15M<BAND_RX:3>15M<MODE: 
5>PSK31<TX_PWR:3>100
<RST_SENT:2>57<RST_RCVD:2>57<QSL_VIA:6>BUREAU
<DXCC:3>281<COUNTRY:5>Spain
<SRX:1>1<STX:1>2<SRX_STRING:10>SRX String<STX_STRING:10>STX String
<GRIDSQUARE:6>IN71qm<LAT:5>41.52<LON:5>-4.62
<CQZ:2>14<IOTA:6>EU-077<ITUZ:2>37
<MY_GRIDSQUARE:6>FN03jq<OPERATOR:6>VE3VRW<MY_RIG:11>Icom IC-756
<EOR>


73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Tue Feb 24 10:24:54 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Tue, 24 Feb 2009 10:24:54 -0500
Subject: [MacLoggerContest] MacLoggerDX V 5 for Cocoa AppleScriptiing
Message-ID: <C8595ED2-FE10-44DA-A79E-0B3F19AFA0A3@dogparksoftware.com>

In version 5.02 Beta 6 the AppleScript "log" and "lookup" commands  
have been separated to allow lookups via Applescript from CocoaModem  
and then logging with comments subsequently.

This will also allow default settings of start and end times to be  
more accurate but may require existing scripts to be modified.

-- MacLoggerDX Scripting commands

tell application "MacLoggerDX"
	
	-- General
	
	get version
	count every qso
	exists qso "W1AW"
	get call of qso 1
	get first_name of qso 1
	get last_name of qso 1
	call of every qso whose call starts with "W7"
	
	-- PTT : uses method chosen in Radio Prefs Keyer Popup
	
	setPTT "ON"
	delay 1
	setPTT "OFF"
	
	-- Lookup
	
	lookup "W1AW"
	
	-- Logging
	
	setModeMapping "USB PSK31"
	setVFOandMode "14.070 USB"
	setVFOLoggingOffset "0.00001"
	log
	
end tell

73 Don Agro VE3VRW


From M0XDF at Alphadene.co.uk  Sat Feb 28 07:06:31 2009
From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF)
Date: Sat, 28 Feb 2009 12:06:31 +0000
Subject: [MacLoggerContest] New file uploaded to macloggerdx (((( ALERT ))))
	- TRASHES System
In-Reply-To: <gob8m1+10d81@eGroups.com>
References: <gob8m1+10d81@eGroups.com>
Message-ID: <61D1D217-1264-4559-81A2-48CB590A975C@Alphadene.co.uk>

OK, my suggestion is for all those that have not seen this - there  
appears to be a file in the Yahoo group file list, but I don't at this  
point know which one.

This appears to have a bug that will cause it to attempt to delete a  
lot of files from your system, including the system. If you run with  
admin privs, which a lot of us do, it could badly damage your  
installation.

Just avoid it until we know more.

Jeff, if you ever get a moment, perhaps you could give me the URL to  
the file.
73 de M0XDF, MLDXv5.02b22
-- 
Mathematics is the language with which God has written the universe.
-Galileo Galilei, physicist and astronomer (1564-1642)

On 28 Feb 2009, at 11:54, Swiger, Jeffrey M. wrote:

> OK, Pardon my French here!...
> YOUR DAMN RIGHT it DID!.. WTF is the moderator to get that file off
> here!.. I have just lost my FRIKIN system because this ran!,.. I'm on
> my Macbook now and Trying Time Machine to restore my Drive, The
> NAQP-RTTY is at 1:00pm Local and I have NO Computer.. WHAT did this
> script Have in it, and WHO posted it?..
>
> Jeff-N8NOE
>
> --- In macloggerdx at yahoogroups.com, "David Ferrington, M0XDF"
> <M0XDF at ...> wrote:
> >
> > That looks very dangerous - it's attempting to delete every file (in
> > Unix, a directory is really a special file) it can.
> > I don't wish to be alarmist, but it's quiet possible some files have
> > been deleted (and they won't be in the trash).
> >
> > What was this s/w you were running? and why is it creating a tmp dir
> > below the MLDX home?
> > 73 de M0XDF, MLDXv5.02b
> > --
> > One glance at a book and you hear the voice of another person,  
> perhaps
> > someone dead for 1,000 years. To read is to voyage through time.
> > -Carl Sagan, astronomer and writer (1934-1996)
> >
> > On 28 Feb 2009, at 07:37, Swiger, Jeffrey M. wrote:
> >
> > > ERROR I Received.
> > >
> > > sh: line 0: cd: /Users/n8noe/Documents/MLDX_Logs/tmp/: No such  
> file or
> > > directory
> > > rm: Applications: is a directory
> > > rm: Desktop DB: Permission denied
> > > rm: Desktop DF: Permission denied
> > > rm: Developer: is a directory
> > > rm: Garvin Files: is a directory
> > > rm: Ham Toyz: is a directory
> > > rm: Library: is a directory
> > > rm: Network: is a directory
> > > rm: System: is a directory
> > > rm: Users: is a directory
> > > rm: Volumes: is a directory
> > > rm: bin: is a directory
> > > rm: cores: is a directory
> > > rm: dev: is a directory
> > > rm: home: is a directory
> > > rm: mach: Permission denied
> > > rm: mach_kernel: Permission denied
> > > rm: mach_kernel.ctfsys: Permission denied
> > > rm: net: is a directory
> > > rm: private: is a directory
> > > rm: sbin: is a directory
> > > rm: tmp: Permission denied
> > > rm: usr: is a directory
> > > rm: var: Permission denied
> > >
> >
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090228/b1357ff3/attachment.html>

From dagro at dogparksoftware.com  Sat Mar  7 21:35:55 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Sat, 7 Mar 2009 21:35:55 -0500
Subject: [MacLoggerContest] Daylight Savings Bug?
In-Reply-To: <F453D1A7-FD12-4A2F-9381-30D201FB7BF6@mac.com>
References: <F453D1A7-FD12-4A2F-9381-30D201FB7BF6@mac.com>
Message-ID: <7588482E-5EC4-42C7-B374-BAA97004B1E4@dogparksoftware.com>


On 7-Mar-09, at 9:24 PM, Rick Prather wrote:

> I am logging contacts during the ARRL DX SSB contest and just  
> noticed that since 0200 UTC my contacts are being logged as 01xx!
> For example, right now it is 0222 and if I put in a contact do a  
> look up and then log it it goes in the log as 0122!
> Even if I try to edit the time in the log to the correct 0222 it  
> changes back to 0122!

I'm not seeing that here. It is 2009-03-08 01:32:28 and I just logged:  
2009-03-08 01:32:28

73 Don Agro VE3VRW


From bsandersen at mac.com  Tue Mar 10 09:47:41 2009
From: bsandersen at mac.com (B. Scott Andersen)
Date: Tue, 10 Mar 2009 09:47:41 -0400
Subject: [MacLoggerContest] Cab-converter poll now open
Message-ID: <B2BD8AE9-649A-42DC-A8A1-C12F4A700404@mac.com>

Enter your vote today! A new poll has been created for the
cab-converter group:

MacLoggerDX 5 is released! It is a full rewrite with
a new backing store (SQLite3). In order to do some
planning here on the Cab-converter side, please
indicate which version of MacLoggerDX you're running or
plan to run.

o I've moved to MacLoggerDX 5
o I plan to upgrade to MacLoggerDX 5
o I am not planning on upgrading to MacLoggerDX 5
o I am no longer using MacLoggerDX for contesting
o Cowboy Neal told me to buy a PC

To vote, please visit the following web page:
http://groups.yahoo.com/group/cab-converter/surveys?id=2836187

Note: Please do not reply to this message. Poll votes are
not collected via email. To vote, you must go to the Yahoo! Groups
web site listed above.

B. Scott Andersen           | "Magic is real, unless declared integer."
bsandersen -atsign- mac.com | -- The collected sayings of Wiz Zumwalt
Acton, MA (NE1RD)           | http://www.bsandersen.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090310/fc497c95/attachment.htm>

From kilo2mit at gmail.com  Sat Mar 21 20:23:12 2009
From: kilo2mit at gmail.com (Jeffrey A. Steinberg)
Date: Sat, 21 Mar 2009 20:23:12 -0400
Subject: [MacLoggerContest] MacloggerDX 5.X and Icom 7800
Message-ID: <24B590EC-E197-4029-B4FD-417F3172D814@gmail.com>

My MacLogger 4.4 worked fine with my keyspan USB/Serial 4-port device  
and my rotator (Green Heron--DCU-1 emulation at 4800 baud) and my  
IC-7800).  If anyone has this combination (radio and Maclogger) would  
you be willing to share configurations over the phone.   If so, can you
PM me or reply to this e-mail letting me know.  Put your call in.

Currently my 7800 is set to CI-V baud rate auto, address: 6Ah, CI-V  
transceiver ON, RS-232C Function Decode, Decode baud rate:  98600.

Preferences on the radio is serial port, keyspan serial port id, 9600  
baud, 2 stop bits, icom-7800, DTR yes, RTS yes, command delay 0ms., icom
address 6A.

--Jeffrey Steinberg
K2MIT

Thanks in advance.  This is frustrating because it worked in 4.4

I tested the keyspan on my automated telescope and all is well with  
all 4 ports..

From maurizio at scansani.it  Mon Mar 23 07:16:49 2009
From: maurizio at scansani.it (Maurizio Scansani)
Date: Mon, 23 Mar 2009 12:16:49 +0100
Subject: [MacLoggerContest] Help on connecting MLDX 5
Message-ID: <80B04F08-3534-4E02-A227-1CA19CA70ABB@scansani.it>

Hi everyone and apologize for my English...

I am not able to connect to telnet dxcluster...

In the cluster panel, i read:

Telnet Startup:

But nothing happens, even thought I push the CONNECT button and change  
the node.

Thanks!

Max, IK2YSE

From dagro at dogparksoftware.com  Mon Mar 23 07:20:58 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Mon, 23 Mar 2009 07:20:58 -0400
Subject: [MacLoggerContest] Help on connecting MLDX 5 to dxcluster
In-Reply-To: <80B04F08-3534-4E02-A227-1CA19CA70ABB@scansani.it>
References: <80B04F08-3534-4E02-A227-1CA19CA70ABB@scansani.it>
Message-ID: <2DC621E1-4570-43F1-842B-D5F90D6D9500@dogparksoftware.com>

Hi Maurizio,

On 23-Mar-09, at 7:16 AM, Maurizio Scansani wrote:

> Hi everyone and apologize for my English...
>
> I am not able to connect to telnet dxcluster...
>
> In the cluster panel, i read:
>
> Telnet Startup:
>
> But nothing happens, even thought I push the CONNECT button and  
> change the node.
>
> Thanks!
>
> Max, IK2YSE

I have cross-posted this to the other two lists.

73 Don Agro VE3VRW


From dagro at dogparksoftware.com  Mon Mar 23 11:34:00 2009
From: dagro at dogparksoftware.com (Don Agro)
Date: Mon, 23 Mar 2009 11:34:00 -0400
Subject: [MacLoggerContest] [macloggerdx] Help on connecting MLDX 5 to
	dxcluster
In-Reply-To: <80B04F08-3534-4E02-A227-1CA19CA70ABB@scansani.it>
References: <80B04F08-3534-4E02-A227-1CA19CA70ABB@scansani.it>
Message-ID: <776C900F-9413-4E71-AC17-069A38162B38@dogparksoftware.com>

Hi Maurizio,

On 23-Mar-09, at 7:16 AM, Maurizio Scansani wrote:

> I am not able to connect to telnet dxcluster...

What happens when you try this in a Terminal.app window ?

$ telnet dxc.kn4f.net
Trying 76.107.211.254...
Connected to dxc.kn4f.net.
Escape character is '^]'.
*** Connected to: KN4F
Welcome to the KN4F AR-Cluster node Telnet port!
Please enter your call: ve3vrw


Hello Don Agro (VE3VRW)
Welcome to the KN4F AR-Cluster port located in Memphis, Tn.
WWV: SFI=69  A=4  K=1 No Storms -> No Storms 23-Mar-09 15:00Z
Since Mar 2007 the KN4F node has processed 3,642,555 DX spots

To set filters to just see spots from the US and Canada, do a
SET/FILTER K,VE/PASS  (or see HE FILTERS for more filter options)
Please enter your email address as SET/EMAIL terry at ab5k.net
Please enter your phone number. Example SET/PHONE 333-4567
40 nodes, 29 local / 285 total users  Uptime 12 11:14
VE3VRW de KN4F    23-Mar 1533Z  arc >




73 Don Agro VE3VRW