[MacLoggerContest] Re: MacLoggerDX tab order

[John E Bastin]

On Aug 3, 2005, at 7:36 AM, Don Agro wrote:


> Where we stand with 4.1.1b25 is that this somewhat optimized  
> sequence (without using AppleScript or Function Keys) is now  
> possible where it wasn't before...
>
> <http://www.dogparksoftware.com/MacLoggerDX/Manual/Pages/ 
> controlwindow.html>
>

At the risk of further muddying the waters of desired/needed  
functions in a contest program, here's what I'm used to working with  
in a contest program:


>
> Fast Keyboard Logging for Contesters:           Faster logging  
> sequence:
>
>    1. Enter call.                            1. Enter call  
> (progressive display of similar
>
                                                  calls in SuperCheck  
Partial window as call is
                                                  entered - dupes are  
displayed in red)


>    2. Hit return (this does a lookup).       2. Hit return (does a  
> dupe check, if a dupe, displays
>
                                                  time and sequence  
number of previous contact), moves
                                                  to SRX numeric (ONE  
keypress, not two)


>    3. One <tab> takes you to SRX numeric. STX auto-increments (set  
> in Prefs Panel)
>
                                                   (this all happens  
with the <return> keypress)

                                                  After entering the  
SRX info, hitting <return> again
                                                  (when the cursor is  
NOT in the callsign field)
                                                  logs the QSO,  
blanks the callsign and SRX fields,
                                                  moves the cursor to  
the callsign field ready for the
                                                  next callsign entry.


>    4. Hit <shift><command> L this logs the call and highlights call  
> text.
>
                                                   This takes two  
hands to accomplish, far too
                                                   cumbersome if  
you're working for rate.


>    5. <command> K clears all the fields and repositions the cursor  
> to the Call Sign field. - Ready for 1 again.
>
                                                    This is four  
keypresses to accomplish what I
                                                    normally do in  
two - adds at least a few seconds to
                                                    each contact.

>
>     * Power, RST Sent, and RST Received fields are remembered  
> across sessions and not cleared since they are hand entered and not  
> found in a look up.
>

What I've described is what normally happens when I'm sitting on a  
frequency calling CQ. If I'm S&P'ing I'm
then using different (single) function keys instead of the <return>  
key, but there is still only two keypresses per contact outside of  
entering exchange data.

In addition to the logging functions, if this is a CW or RTTY contest  
the computer is sending the exchange information at the same time.


>
> The reason that I am doggedly sticking to this thread is simply  
> that I would like to get this nailed down for release in v4.1.1  
> since UI changes to the main screen affect the whole manual.
>

I'm assuming that this discussion is aiming at ultimately producing a  
contest logging program for the Mac, and not just contest  
enhancements to MacLoggerDX. MacLoggerDX is a great DX logging and  
record-keeping program, and I think Don would agree that it is a very  
complex package, both from the user's and from the programmer's point  
of view.

Contest logging programs are equally complex programs in their own  
right, if they are to be able to do everything that contesters demand  
and still maintain a premium on doing everything in a minimum amount  
of time. Due to this complexity, I think that efforts to make  
MacLoggerDX into a contesting program would not contribute to its  
present function, and would produce a sub-optimal contest program at  
best. The contest logging program needs to be a stand-alone design,  
with features that enhance contesting at the forefront.

After the contest is over, ADIF the contest log to MacLoggerDX for  
the rest of the work, DX record keeping, QSLing and the like.

I would like nothing better than to be able to put a Mac back in the  
shack for contesting as well as normal logging. I don't consider  
myself a top contester by any stretch of the imagination, but I have  
pushed my present contesting program to QSO rates of 150-per-hour,  
and the software is really capable of a lot more than that if I was  
better at it.

Maybe it's farther than this discussion is aiming, but that's my  
target. Until a contesting program for the Mac gets to that point,  
I've got a PC in the shack. Use the best tools for the job you need  
done.

Best wishes to all and keep this effort alive,

John E Bastin, K8AJS
jbastin at sssnet.com
http://www.qsl.net/k8ajs/