[MacLoggerContest] MLC compared to MLDX

[Ted Brattstrom]

Drat - I'm doing this each time - hitting reply like a normal list, and
forgetting  it doesn't go to the list...   cheers - ted - nh6yk

----- Original Message -----
From: Ted Brattstrom <ted at hawaii.edu>
Date: Saturday, February 12, 2005 9:42 am
Subject: Re: [MacLoggerContest] MLC compared to MLDX

> Aloha -
> 
> Just a few comments :-)
> 
> ----- Original Message -----
> From: Jonathan G0DVJ <g0dvj at amsat.org>
> Date: Friday, February 11, 2005 10:39 am
> Subject: [MacLoggerContest] MLC compared to MLDX
> 
> > 
> > Hi all,  (sorry for the burst of activity from me on the list at 
> > weekends but work is giving me little chance during the week at 
> > present!)
> 
> Work does get in the way of fun :-) :-) weekends are the time to catch
> up on all the other  stuff (of course, I'm a teacher, so it's also the
> time to catch up on work :-) )
> 
> 
> > MLDX good for MLC:
> > 
> > -  DX Clusters Pane and functions (with added links to scoring 
> > potential etc. as per separate thread - e.g. identifying new 
> mults 
> > that have been spotted)
> 
> Note - if implemented, this should be able to be turned off - or made
> one way... (I'd leave it out, personally :-) )
> 
> The reason, using any cluster changes you from Single Op to 
> Assisted -
> there are enough people who are "assisted" who are submitting as 
> Single Op.
> 
> > -  Map Pane (should concentrate of what has been worked as an 
> > indicator 
> > of propagation etc.  maybe coloured by band etc. but secondary 
> nice-
> > if 
> > rather than essential) - also only really of use when HF contest 
> > selected unless we can have loadable more localised maps
> 
> Cute, but how needed  is it --- if I hear a lot of African stations 
> on,I can guess that propagation supports that direction :-) and, 
> knowingthe bands from my QTH, and the like - it's not particularly 
> needed.Unless you put something like the SFI/A/K in to make band 
> predictions in
> real time. (that's a separate program)
> 
> > -  Beam rotor support
> > -  Rig control support for such a wide range of radios.  (Again 
> > maybe 
> > linked to specific quick QSY for different band/mode button 
> functions)> -  MicroBand decoder support
> > -  Keyer support (adapted specifically for contesting needs)
> > -  Cabrillo support (need export instead of import !)
> > -  ADIF support (only need export)
> 
> 
> I'd add - the ability to do a quick edit on a QSO - How many times 
> haveI entered the info quickly, hit return twice, then noticed that I
> mis-typed the call - Post contest editing is fine - (and 
> important), as
> long as you keep a pad of note paper next to you (which I do)
> 
> 
> > MLDX not good/not needed for MLC:
> > 
> > -  QSL pane and functions
> > -  Labels pane and functions
> > -  Awards pane and functions
> > -  Schedules pane and functions (Could imagine a different but 
> > analogous sked/band change/other (e.g. fill genny!) reminder system)
> > -  Memories pane and functions (Could imagine a different but 
> > analogous 
> 
> > Memory map of what you have heard/logged per band e.g. on S&P mode)
> 
> I don't know how this is implemented - but, the ability to enter a 
> calland band that you can come back to... because you didn't get 
> through
> I envision something like entering the call, trying to call for a 
> minuteor 20 - then hitting a function key to put it over on the 
> side with the
> freq and call... it can be gone back to later.
> 
> (I spent about 30 minutes + trying to get to FP/VE7SV on 10M since it
> was an all time new one - and that ends up being a higher priority 
> thanthe contest :-) )  
> 
> 
> 
> > -  UCB pane and functions
> > -  Previous (only implemented by the Super Check Partial support 
> as 
> > well as Dupe Checks in the same current contest).
> > -  Support for WARC bands - no contests happen here.
> 
> (yeah, I know I keep saying it :-) keep the WARC bands in there - no
> need to take them out :-) then it's still ok for DXpeditions - part of
> why a number of WIN contest programs are used on DXpeditions, same 
> fastentry speed - DXpeditioners are often Contestors and want the same
> interface  in both scenarios. (same networking for network 
> backups!!!))
> > -  Log pane - fields never needed such as address related, power, 
> > contact details, plus others only displayed according to contest 
> > configuration.
> > -  Different pane/layout completely needed - some common 
> > info/fields 
> > but emphasis completely different.
> > 
> > 
> > Comments from any others who are familiar with MLDX?
> 
> Sorry to be not familiar with MLDX - My experience has been with: 
> Paperlogs, Excel, LogEQF (win/dos), MacContest 3.5 (mac), CT (win -
> networked), and (drat, and I'm sorry I forgot your name...) the 
> contestspecific logger worked up by a list member....
> 
> Aloha - ted - nh6yk
> 
> > 73,
> > Jonathan G0DVJ
>