[WT-support] Manual band map entry

[Jim Fisher]

Bob,
The requirement for manual entry of the sub receiver is so that while the run op is using the main VFO another op can be scouring the rest of the band in between transmissions.
The sub RX op is then populating the band map for the run op to point and click for mults or new stations.
Using the swap rx-sub stops the run op and any small advantage is lost.
I would just right mouse click in the bandmap window as per Writelog and entry via a dialogue box.
Thanks for the reply I eventually got once sorting out my spam filter!
Sorry for the double post.

73

Jim
  ----- Original Message ----- 
  From: Bob Wilson, N6TV 
  To: support at win-test.com 
  Sent: Sunday, June 01, 2008 10:57 PM
  Subject: Re: [WT-support] Manual band map entry


  2008/6/1 Jim Fisher <gm0nai at btinternet.com>:

    I would like to be able to manually enter into the band map but can't find this function.
    I am only able to add with the main RX frequency automatically "ctrl-enter" 
    I would like to be able to add to the band map from the Sub receiver manual frequency input.
    Any ideas?


  As far as I know, this feature is not supported.  Even if it were added, what key combination would you suggest to do it?  Alt-Enter?  No, that's already used for Partner Mode.

  The only suggestion I have is to press the "Swap Main / Sub Rx" button on the radio, then press Ctrl-Enter, then press the swap button again.  You may need to uncheck "Wipe QSO" and "Populate the band map" in the Bandmap properties dialog to prevent an automatic and incorrect band map posting when you press the Swap button, or stay in "CQ mode" rather than "S&P mode"73,
  Bob, N6TV



------------------------------------------------------------------------------


  _______________________________________________
  Support mailing list
  Support at win-test.com
  http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.win-test.com/pipermail/support/attachments/20080604/457ae690/attachment.htm>