This seems like it will work OK for CW, but it still doesn't provide a work-around for the Escape key problem when operating Phone (or RTTY), described below and in Task #289.<br><br>I don't understand why this can't be fixed for all modes (no custom scripts required). You don't need an SO2R box to recreate the problem, just watch the red RX/TX "LEDs" in the secondary radio window.<br>
<br><span style="font-family: arial,helvetica,sans-serif;">Scenario for <b>secondary radio</b></span>:<br>
<br><span style="font-family: courier new,monospace;"> F1: $R1R1 $F1 $R2R2</span><br><span style="font-family: courier new,monospace;"> INSERT: $R1R1 $INSERT $R2R2</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> PLUS: $R1R1 $PLUS $R2R2</span><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> F1: CQ F6FVY F6FVY<br></span><span style="font-family: courier new,monospace;">INSERT: $LOGGEDCALL $QSOB4 $GUESSEXCH $F2</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> PLUS: $CORRECT TU F6FVY </span><br style="font-family: courier new,monospace;">
<br>Set focus to secondary radio window via [CapsLock], then press Escape after pressing F1, INSERT or PLUS, and you are stuck listening to radio 1 instead of radio 2.<br><br>Get called by a dupe, and you are stuck listening to radio 1 instead of radio 2.<br>
<br>If a message is interrupted, either by $QSOB4 or pressing Escape, the rest of the CW/RTTY message should just be ignored, <i>except</i> for all of $R2R2 focus commands, which should still be respected.<br>
<br>In sum, Advanced SO2R is kind of broken right now in Win-Test:<br><br><a href="http://flyspray.win-test.com/index.php?do=details&id=205" target="_blank">http://flyspray.win-test.com/index.php?do=details&id=205</a> - QSOB4 leaves you listening to wrong radio<br>
<a href="http://flyspray.win-test.com/index.php?do=details&id=264" target="_blank">http://flyspray.win-test.com/index.php?do=details&id=264</a> - Can't use secondary radio to announce serial numbers on phone<br>
<div style="margin-left: 40px;">(side effect of fix for <a href="http://flyspray.win-test.com/index.php?id=137&do=details" target="_blank">task #137</a> reported by OH2UA for Alternating CQs, now closed)<br></div><a href="http://flyspray.win-test.com/index.php?do=details&id=289" target="_blank">http://flyspray.win-test.com/index.php?do=details&id=289</a> - Escape key always puts both ears on primary radio<br>
<div style="margin-left: 40px;">(also a side effect of the fix for task #137, perhaps).<br></div>
<br>73,<br>Bob, N6TV<br><br><div class="gmail_quote">On Wed, Sep 15, 2010 at 2:11 PM, Laurent HAAS - F6FVY <span dir="ltr"><<a href="mailto:f6fvy@free.fr" target="_blank">f6fvy@free.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Hi Bob et al.<br>
<br>
Bob Wilson, N6TV a écrit :<br>
<br>
</div><div>> Thanks, this sounds like an excellent enhancement that will definitely<br>
> simplify things. QRX for Version 3 of the PSE QSY scripts after some<br>
> testing.<br>
><br>
> Is there a wtKeyer:Play API that works the same way (synchronously)?<br>
> Ideally it wouldn't return until the message completed, or Escape halted<br>
> the CW. It could then return "true" if the CW message completed, or<br>
> "false" if it was interrupted.<br>
<br>
</div>If the wtKeyer:Play was working synchronously, it would block all other<br>
actions in the main thread of Win-Test, meaning that you couldn't even<br>
use the keyboard, click a window etc...<br>
<br>
But, if you want to "mimic" it, it's pretty easy.<br>
<br>
-- bPlaying.wts<br>
<br>
if (wtArg == 1) then<br>
bPlaying = 1;<br>
else<br>
bPlaying = nil;<br>
end;<br>
<br>
CW message :<br>
<br>
#@BPLAYING(1) BLAH BLAH BLAH #BPLAYING()<br>
<br>
-- esc.wts (assigned to the Esc key)<br>
<br>
if (wtApp:IsPostKeyProcess()) then<br>
if (bPlaying ~= nil) then<br>
wtApp:AlertBox("Message Interrupted");<br>
end;<br>
else<br>
return 1; -- Triggers a post key process call<br>
end;<br>
<br>
Of course, you can use any global variable name.<br>
<br>
Also, in a next release (maybe the next nightly build), you will be able<br>
to include scripts calls in the $QSOB4 variable.<br>
<div><br>
> Finally, I see in the wt_dev Release.txt that you have also added the<br>
> wtStatus API to make it possible to automate PSE QSY messages at a multi-op:<br>
><br>
> - wtStatus:GetFreq(strBand[, strMode]) returns the "best" pass freq for<br>
> a given band and mode.<br>
><br>
> How is "best" defined? Same search priority as $FREQnn (R, R+, M, and<br>
> M+)? If it always goes to the PASSFREQ, that is not what I would want<br>
> it to do. Most often one would pass stations to the Run frequency of<br>
> the Primary Run radio on that band. Also, I don't remember how to<br>
> delete a PASSFREQ once it gets set. Typing PASSFREQ and deleting the<br>
> frequency and press OK doesn't seem to have any effect in manual mode<br>
> (which is what you do when you don't have an RS-232 line available to<br>
> control a rig).<br>
<br>
</div>It is defined the same way as the $FREQnn variable, only relying on the<br>
RUN freq. But, with the new APIs provided, you can tailor the algorithm<br>
as you want.<br>
<br>
Regarding the pass frequencies, I thought it was possible with the<br>
dialog you mentioned. I will check it - It looks like no one ever wanted<br>
to clear it since almost 10 years ;-)<br>
<div><div></div><div><br>
73<br>
<br>
Larry - F6FVY<br>
</div></div></blockquote></div><br>