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
Please don't ask for feature requests here but on the mailing list.
Thanks for your help. Olivier F5MZN and Laurent F6FVY
Task #209 — If you double-click on a call in the radio 2 band map, [F5] $LOGGEDCALL sends nothingAttached to Project— Win-Test
This is probably caused by the same bug reported in task #208.
If you press [F11] and /type/ W6XYZ in the secondary radio window, then press [F5], it works OK.
Somehow double-clicking on a call in the secondary radio\'s band map doesn\'t work the same as typing in the call, or as double-clicking on a call in the primary radio\'s band map (which makes [F5] work properly).
Intended to make this bug Severity MEDIUM, rather than LOW.
AC6T is reporting he ran into this same problem using WT 4.14, and I can still replicate it. Why does loading a call into the secondary radio window by clicking on the band map fail to initalize or update the $LOGGEDCALL variable?
Mods done on 4.15.0 revision. Must be heavily tested before closing the task.