[WT-support] PTT on COM port and WINKEY

[Satoshi Nakamura]

Hi again Bob,

I think I need to learn much more about SO2R operating!

Now I have found the cause of the problem.

If both WINKEY and OTRSP Compatible Device are removed from Interfaces
Configurations, hitting ESC works as it should be.

My problem can be replicated if either WINKEY or OTRSP Compatible Device
is enabled in the Interfaces Configurations.

73,

Saty JE1JKL


> > When the Automatic repeating CQ is enabled:
> > Hitting any key, not only ESC, interrupts CQ transmission
> > and the red bar on RX stays on Radio 2.
> >
> 
> For me, it only does that if I type while listening to R2.  If I wait for
> the CQ to finish, then type a call, RX stays on R1/R2.  I think this may be
> OK.  Win-Test assumes that if you start typing, you are doing it because you
> are hearing something on Radio1 or Radio2.  So, Win-Test is trying to keep
> both ears on the proper radio.
> 
> If you are too slow and start typing a callsign after the repeating CQ has
> restarted, well, by then you are listening to Radio 2, so Win-Test assumes
> you are typing something that you heard on Radio 2, and that is why it keeps
> the receiver there (though the data entry area is incorrect).  Maybe it
> should do the same thing as the Escape; I'm really not sure.
> 
> You have to switch the data entry area manually by pressing CapsLock or
> Shift.  Typing on the secondary radio will not interrupt a repeating CQ on
> the primary, so you can do lots of S&P on the secondary radio while the CQ
> continues on the primary.
> 
> Using the "Plain Pileup" scenario, if I press Escape, RX always goes to
> R1/R2, at all times, whether Automatic repeating CQ is enabled or not.  This
> is correct behavior.  If Escape works differently for you, check to make
> sure you don't have the Escape key assigned to a LUA script or a keyboard
> redefinition.  Check this via SCRIPTS [Enter] and DEFINEKEYS [Enter].  Make
> sure the Escape key is not listed in either dialog.
> 
> Is this behavior strange?
> >
> 
> I suggest reviewing the SO2R
> section<http://docs.win-test.com/wiki/SO2R/Advanced_SO2R>of the
> Win-Test manual as well as CT1BOH's
> SO2R page <http://www.qsl.net/ct1boh/so2r.htm>, to understand the philosophy
> behind Win-Test's SO2R design.  But many people find it hard to use.
> 
> To swap the data entry window automatically so that it follows the receiver
> you are listening to, you could try installing two new LUA scripts I just
> published at http://bit.ly/wtscripts in SwapFocus.zip.  The two new scripts
> are named Focus1.wts and Focus2.wts.
> 
> Then change the plane pileup scenario as follows:
> 
>      Primary                               Secondary
> F1:  $R2R2 #FOCUS2 $F1 $R1R2 #FOCUS1       $R1R1 #FOCUS1 $F1 $R1R2 #FOCUS2
> 
> Now when you press F1, the data entry focus temporarily moves to the
> secondary radio window.  When the CQ is finished, it moves back.  However,
> if you start typing a callsign, both #FOCUS2 and #FOCUS1 do nothing.  The
> focus doesn't change unless the callsign field is blank, because you won't
> want the callsign you are typing to be split between two windows.  Try it.
> 
> One downside is that if you press Escape, the data entry focus doesn't move
> back, because it is not clear where the focus should be.  You have still to
> press CapsLock to do it yourself.
> 
> Many people who find this confusing may still prefer the TRlog style of SO2R
> data entry.  I created some completely separate Win-Test scripts to make
> SO2R operating with Win-Test work much more like TRlog.  See
> http://bit.ly/wtscripts and download AltDScripts3.zip .
> 
> 73,
> Bob, N6TV