Win-Test

for Project:

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

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 #296 — Check mult window not updated properly when using in ESM mode with S&P mode selected

Attached to Project— Win-Test
Opened by Robert A. Wilson (N6TV) - Monday, 25 Oct 2010, 4:47am
Bug Report
Check country wnd (F10)
Unconfirmed
No-one
All
High
Normal
Current WT-4.x
Undecided
0% complete

Seen in WT 4.5.1 and 4.6.0 Rev 326

  1. Open a new CQ WW log
  2. Select Tools | Data Entry | Exchange Guessing | Automatically and make sure it is checked
  3. Select Windows | Clock to make it visible
  4. Press [F10] to display the Check Multipliers window
  5. Type RUNSP [Enter] to enable RUN/S&P switching
  6. Type ESM [Enter] to enable ESM mode
  7. Press Ctrl-Tab to select RUN mode (RUN shows in Clock window)
  8. Type a partial prefix like EA9 in the callsign field, and nothing else (do NOT press spacebar)
  9. Check Mult window updates immediately (OK)
  10. Press F11 to erase the QSO
  11. Press Ctrl-Tab to select S&P mode (S&P shows in Clock window)
  12. Type EA9 in the logging window and nothing else
  13. BUG: The check country window is NOT updated
  14. Press F11 to erase the QSO
  15. Type NOESM [Enter] to disable ESM mode
  16. Type EA9 in the logging window and nothing else (you should still be in S&P mode)
  17. Check Country Window is udpated OK

The combination of ESM mode with S&P mode seems to prevent the Check Multiplier window from being updated instantly as you type a valid prefix. This forces you to press SPACEBAR every time, to update the multiplier status.

This task depends upon

This task blocks these from closing

Comments (1) | Attachments (0) | Related Tasks (0/0) | Notifications (3) | Reminders (0) | History |

Comment by Robert A. Wilson - Monday, 25 Oct 2010, 8:38pm

This issue seems to have been fixed in WT 4.6-dev Rev 437 -- thanks!