-
Notifications
You must be signed in to change notification settings - Fork 21
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
Minimal contest support #345
Comments
I often answer this question. At the moment I can answer you as I did on the Groups.io mailing list. However, this does not mean that my decision is final. I tried something new during CQ WPX, but I just test it. Currently nothing specific.
|
I would like also some light contesting option on the log. Maybe a solution would be to to apply some methods of the N1MM software, meaning the configuration files that applies what fields are needed etc. I'm not an avid contester so can't talk too much about n1mm or different rules or what not, but if I'm not mistaken n1mm you can create the contest configuration file and then import it to the software. That way you create the "platform" in a tab next to "My Notes", define the rules for the file, and leave it to the comunity to create a template/configuration file to import for any particular contest. |
WSJTX Widget does not show DUPEs - filter is active DXC Widget does not show DUPEs - filter is active Alerts Widget shows DUPEs - no filter for dupes Bandmap Widget shows DUPEs - no filter for dupes
I know, I know, QLog won't force on contest. But I think add minimal contest support is necessary. Last month's CQ WPX SSB contest I do log with pen and paper, then I want to add the QSOs into qlog, I found that there is no place to enter contest exchange info, but in the QSO detail dialog there already have a contest tab. If I can enter contest exchange info, I will use qlog to do contest (other contest logger programs are too complex :( ). So Ladislav can you add this contest tab in the main window?
73
The text was updated successfully, but these errors were encountered: