[WT-support] Click on spots Bug?

[Bob Wilson, N6TV]

On Tue, Dec 2, 2014 at 6:54 AM, Filipe Lopes <ct1ilt at gmail.com> wrote:

> 1st scenario:  Running on R1 and Mults on radio 2:
>
> While running on R1 and when I clicked on a DX Spot from the bandmap to
> work the mult on the 2nd radio, after the RUN QSO on R1 win-test sends the
> call that I clicked on the band for R2 and the TU message...
>

This bug was reported about 6 years ago as "High severity." See Task #208
<http://flyspray.win-test.com/index.php?do=details&id=208>.  It has to do
with the $CORRECT logic getting confused by callsigns loaded into the
secondary radio window in the middle of a run radio QSO.  You can type
NOCORRECT [Enter] in the logging window to disable this feature, or remove
$CORRECT.

Which version of Win-Test were you using?  Please add it as a comment to
this bug report.

2nd scenario: Skimmer with bandmaps:
>
> Is there a way to freeze the bandmap so it doesnt go up and down
> continuaslly as spots are added into the bandmap, it is kinda frustrationg
> when clicking on a dx spot it doesnt move you to the correct one because
> the scroll at the band map moves, the same thing happens for the DX Cluster
> ANNOUNCEMENTS.
>

I think you are saying that the callsign moves before you can click on it,
so you click on the wrong call?  Try using Ctrl-Up Arrow and Ctrl-Down
Arrow to navigate the band maps, instead of the mouse.  There are no hot
keys for navigating the Announcements window.

What value did you use for Spots bandwidth in bandmap properties?  Using 0
Hz instead of the default 300 Hz will prevent callsigns from disappearing
so quickly.

73,
Bob, N6TV
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20141202/f4bfa8a3/attachment-0001.html>