You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't a bug but a current feature which might need changing. Not high priority.
The CW speed control in the main console is not sync'd with the speed control in the CWX window. In principle there's nothing wrong with this because maybe you want them to be different. But I find that in actual operation, you want them to be the same.
For example if you're using CWX messages to call into a DX pileup, when the DX answers and the QSO begins you might want to send something different from what's in one of the CWX message memories, or add to it. In that case you grab your paddle and send it manually. Usually (maybe always) you'd want to be sending at the same speed as when you were calling with CWX. As it is now, you are forced to keep track of two CW speed controls and keep them in sync manually. Probably not ideal.
Keeping them in sync should at least be an option, IMHO.
The text was updated successfully, but these errors were encountered:
This isn't a bug but a current feature which might need changing. Not high priority.
The CW speed control in the main console is not sync'd with the speed control in the CWX window. In principle there's nothing wrong with this because maybe you want them to be different. But I find that in actual operation, you want them to be the same.
For example if you're using CWX messages to call into a DX pileup, when the DX answers and the QSO begins you might want to send something different from what's in one of the CWX message memories, or add to it. In that case you grab your paddle and send it manually. Usually (maybe always) you'd want to be sending at the same speed as when you were calling with CWX. As it is now, you are forced to keep track of two CW speed controls and keep them in sync manually. Probably not ideal.
Keeping them in sync should at least be an option, IMHO.
The text was updated successfully, but these errors were encountered: