Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Console vs CWX CW speed control #545

Open
W2PA opened this issue Jan 5, 2025 · 0 comments
Open

[FEATURE] Console vs CWX CW speed control #545

W2PA opened this issue Jan 5, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@W2PA
Copy link

W2PA commented Jan 5, 2025

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.

@W2PA W2PA added the enhancement New feature or request label Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant