Flyspray:: Win-Test:

Welcome to the Bug Tracking System for the Win-Test contest logger. Things to note :

Always perform a search on both open and closed tasks before opening a new one. Your bug might already have been reported.
Only one bug per task

Feel free to report any bugs, however minor. To improve efficiency, please try to be as accurate as possible.

Please don't ask for feature requests here but on the mailing list.

Thanks for your help. Olivier F5MZN and Laurent F6FVY

Task #370 — Secondary radio QSOs may be logged on wrong band after entering text commands there

Attached to Project— Win-Test

Opened by Robert A. Wilson (N6TV) - Monday, 22 Feb 2016, 4:29am

Task Type	Bug Report
Category	Secondary radio wnd
Status	Unconfirmed
Assigned To	No-one
Operating System	All

Severity	High
Priority	Normal
Reported Version	Current WT-4.x
Due in Version	Undecided
Percent Complete

Details

wt v4.20

Set up for SO2R mode, Radio 1 and Radio 2 computer controlled, such as two Elecraft K3s
Windows | Secondary Radio
Radio 1 on 20m, Radio 2 on 15m
Options | CapsLock Binds to the Secondary Radio
Note correct band displayed in both primary and secondary radios
Press CapsLock
Type any text command or script shortcut in the secondary radio window, e.g., WORKDUPE, MOVEINMYLOGONLY, RUNSP, SPAN (calls my P3 script), etc.
BUG: Band changes in Secondary radio window, on the logging line, to match the Primary radio band (?)
Now, log a QSO on the secondary radio. It will be logged on the correct frequency, but wrong band.

Note: After typing the text command in the secondary radio window, if you move the Radio 2 VFO even a little, the band display will quickly correct itself. The bug only happens if you type a text command AND then log a QSO WITHOUT moving the VFO.

This task depends upon

This task blocks these from closing

Comment by Robert A. Wilson - Thursday, 18 Aug 2016, 12:58am

Username	Password	Remember me
Register as a new user \| Lost password?