CT9.13 Bug report

[Tony Brock-Fisher]

Ken-

Here is an official bug report for 9.13 after CQWW:

1. Dupe checking has a bug related to 2-radios. After switching from 
one radio to another, the dupe checking uses the band information for the
previously selected radio. Example:

   Select Radio1. Set to 20 meters. Work DL0WW.
   Select Radio2. Set to 15 meters. Work F6BEE.
   Select Radio1. Enter F6BEE in the call field and dupe check him (F8).
   The dupe check says he's a dupe. Now dupe check DL0WW. The dupe
   check says he's a needed call. But log him, and he's a dupe, of course.

2. Band map doesn't scroll for Radio1. Works FB for Radio2.


3. F1, call CQ with external DVK, forces the rig control bit, LPT2 pin2, to
   the Radio1 state. It does not change the indicated Radio1/2 state, however.

4. This may be more of a comment than a bug, and it is certainly not unique
to V9:

   Hit Alt-A and Ctrl-right arrow to get into the announce window. Now
   get distracted as you here 5W1MM start to CQ on the frequency you just
   left on 15. You quickly work him, type in his call, and hit enter.
   Instead of logging him, CT does a grab spot from whatever was selected
   in the announce window. This means the 5W1MM got wiped from the
   call field, and the rig gets QSY'ed so you lose the frequency info.
   You then qualify for an OO award as you scream SHIT into the VOX.
   I would argue that if there is a valid call entered into the call
   field, hitting enter should log it. period. No matter if the announce
   window is selected. Use another key to select the spots from the
   announce window, or require the call field to be blank for enter to
   select a spot. Best yet, use the mouse to select any spot from anywhere
   on the screen, such as the announce window or the band maps.


All things considered, 2 radios with V9 is a winner. It's terrific to be
able to switch EVERYTHING with Alt-period. And the band map - well it's
all been said before... Keep up the good work...

-Tony, K1KP, fisher@hp-and.an.hp.com