[WT-support] Proposed new interface for SO2R operators

Clive Whelan clive.whelan at btinternet.com
Fri Oct 9 02:05:32 CEST 2009


Bob

N1MM has imo by far the most natural interface for SO2R, viz two 
identical log entry windows  and then a separate log window where the 
QSO(s) go when complete, and as you say the ability to automatically 
shift data entry focus automatically is ( again imo)  absolutely 
essential  for maximum SO2R efficiency. The WT system by comparison is 
confused and confusing .

That said, WT does have some potential operational advantages , not 
least the ability to customise operation via the Lua scripting system. 
However, as I have also said, I keep having to shift back to N1MM 
because of unresolved bugs in v4 of WT, particularly the auto-dupe 
problem in ESM/S&P in Task #254 
<http://flyspray.win-test.com/index.php?do=details&id=254> which you 
have mentioned.

Frankly I am not sanguine about the possibility of  changes in style as 
in some ways the raison d'etre of WT for many users is its CT 
antecedents. The WT authors clearly have to consider their market which 
will, I believe, steadfastly prefer the present system.

I think the best we can hope for is a way to simulate Caps Lock in a Lua 
script so that we can automate binding to the second radio.


73


Clive
GW3NJW

Bob Wilson, N6TV wrote:
> Resending ... original version rejected due to attachment size limits.
>
> ---------- Forwarded message ----------
> From: *Bob Wilson, N6TV* <n6tv at arrl.net <mailto:n6tv at arrl.net>>
> Date: Tue, Oct 6, 2009 at 11:19 AM
> Subject: Proposed new interface for SO2R operators
> To: support at win-test.com <mailto:support at win-test.com>
>
>
> On Tue, Oct 6, 2009 at 10:14 AM, Clive Whelan 
> <clive.whelan at btinternet.com <mailto:clive.whelan at btinternet.com>> wrote:
>
>     Sadly the major bug in auto-duping when using ESM in S&P mode
>     means that these have yet to be realised for me.
>
>
> For reference, Clive is talking about Task #254 
> <http://flyspray.win-test.com/index.php?do=details&id=254>.
>
> I had to use N1MM for the first time in the California QSO Party this 
> last weekend, because Win-Test still does not support it.
>
> Though N1MM has its own unique issues that will keep me on Win-Test 
> for quite a while, I'm convinced the SO2R style that N1MM implemented 
> is more natural than what I've tried to use in CT, TRlog, or 
> Win-Test.  Moving the data entry focus automatically allowed me to do 
> Alternating CQs and log interleaved QSOs on two bands at once with a 
> minimum of key presses, at peak rates over 250 QSOs/hour on CW 
> (stressful but doable for brief periods).  Without a way to simulate 
> Caps Lock or Shift, I don't see how to achieve this with Win-Test.
>
> Also, as I've mentioned before, I think the "Secondary Radio" window 
> is just too confusing to the brain because sometimes it represents the 
> rig on the "right", and sometimes it represents the rig on the 
> "left".  The left/right screen position should always match the layout 
> of your radios and what you hear in your left and right ears, but that 
> is not the style of Win-Test today.
>
> Instead of the secondary radio window, I propose an option to expand 
> the main logging window so that it has two identical columns instead 
> of just one, with Radio 1 always on the left, and Radio 2 always on 
> the right, and it just stays that way.  They key bindings could work 
> the same as they do today.
>
> The proposed new main logging window (when Advanced SO2R is selected) 
> is shown here 
> <http://www.kkn.net/%7En6tv/ProposedNewSO2RMainLoggingWindow.PNG>, 
> with the 20m rig on the left and the 15m rig on the right.  The full 
> log is duplicated in both columns for ease of editing any prior QSO.
>
> Advantages: 
> Left/Right rig always matches Left/Right columns
> Keystrokes are the same as today
> Editing prior QSOs in either column is very convenient, no need to 
> jump between screens (better that N1MM).
> Dupe/Mult messages would appear below left column or right column, as 
> appropriate
>
> Disadvantages:
> Uses more screen width (but it is a background window that you can 
> cover up, and modern screens are very wide these days)
> Duplicate info adds a bit more screen clutter (but it is useful clutter)
>
> I'd like to know what other SO2R operators think of this proposal.  
> Doesn't it seem more natural than what we have today with the 
> secondary radio window?  I'm not proposing we eliminate the Secondary 
> Radio Window 
> <http://docs.win-test.com/wiki/Menu:Windows#Secondary_Radio> 
> completely, because it displays useful info.  Just remove the white 
> data entry area at the bottom and replace it with what I've 
> illustrated above.
>
> 73,
> Bob, N6TV
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>   



More information about the support mailing list