Hello, CQRlog developers and users,
I propose to make contest fields same as all other fields. What do you think?
In detail:
- Whether the contest fields are visible in the "New QSO" window or not is controlled by some new option in preferences.
- When those fields are visible, they behave exactly like the other fields we already have. They are usable for entering new QSO data and also for displaying or editing an existing QSO. Same as all the other fields there.
- When those fields are not visible in "New QSO", the effect is as if the user never typed in anything into them. (When editing existing QSOs, that means any contest data is left untouched.)
- Visibility of contest fields in "New QSO" and visibility of the contest window become independent. (Users of small screens will appreciate this.)
- Typing stuff into the contest fields of "New QSO" and typing stuff into the contest window is handled uniformly for all fields: Be it "call" or be it "contest serial" or whatever.
- Whether "serial number sent" is increased automatically also becomes a preference. That preference steers functionality in both the "New QSO" and the contest window.
I think this would maximize usability and, maybe more importantly, minimize confusion.
Vy 73, Andreas, DJ3EI
Hi Andreas!
That needs complete redesign of NewQSQ layout. I have once done version that did divide RST fields to hold contest nr and message but it was not good idea.
As cqrlog is not a contest program NewQSO is kept as is for normal usage. Contest window is made just making qso information typing faster to see just those fields you really need to fill and move there without mouse. Ether with TAB-key or SPACE-key,
Seeing contest fields in NeWQSO is possible only when contest window is open and NewQSO is made horizontally larger (otherwise they are "hidden" by DXCC data). That is just for temporary need of editing already entered contest qso. That should not be needed, but sometime it happens that you press enter and then notice that you had a typing error in received serial or message,
If you really need a contest logger you should use something else than cqrlog for that. As the help section text says contest window is just a notepad type helper for "Sunday contester working in Tourist class"
--
Saku
OH1KH
Hi, Saku,
I do not propose to change the layout. I propose to leave the layout as it is, but to change the logic when the contest fields are visible and when not.
That is not a good idea. I fully agree. It is also not at all what I am proposing.
In my thinking, if the existing material would be organized a bit more straightforwardly, CQRLog would be much more usable for contest logging than it presently is. And for other purposes as well: Logging of *OTA activations or similar pile-up situations. It would simply be a better logging program.
What is the advantage of tying together the appearance of the contest fields in the NewQSO window with the contest window? Why not make those two independent?
In particular, as you say the contest window is for new data and the NewQSO fields are for editing. Which means while one uses the fields in the NewQSO window, the contest window is guaranteed to be not used. Outright in the way, more likely than not. But the moment you close it, the fields in the NewQSO window disappear.
I fail to understand why these two are always displayed together. It is not straightforward to me. If you could please explain to me for which kind of usage the present logic of displaying either both or none is good, I'll learn something. And I always love to learn something.
Vy 73
Andreas, DJ3EI
HI Andreas!
About visibility of contest fields in new qso.
Most users do not want to see those fields as they do not need them. So they are hidden in 2 ways.
1) Contest window must be open. I also considered that NewQSO must be in View or Edit mode at same time, but as you have noticed: then you can not type in qsos from paper log. So it is better to show them in all 3 modes of NewQSO.
Of course they could be set visible by another drop down menu item made just for that purpose.
But why not use contest window for that purpose? Anyway it is a question of contest qsos and you can easily roll over contest window with new qso because the window is bigger and so always visible.
2) Contest fields are hidden by DXCC info. If you do not need them, that is question in over 90% of cases, you do not have to see them. Just keep the horizontal width of NewQSO narrow enough. Even if you have contest window open for entering qsos. Either for search and pounce or keeping own pileup.
Contest window was made as simple "notepad" and keeping serial numbers running automated. It uses NewQSO's routines by just placing written fields to corresponding fields of NewQSO and at the point of saving qso NewQSO's code to do the job.
In first versions serial and messages were placed together with reports to database. Later when we got proper database fields for contest information also the need of place to edit them showed up. Mainly because of correcting typing errors that are found ~5ms after enter has been pressed.
Recalling last qso back to contest window for fixing would have caused more exception codes to keep serial running right, etc.
And that had again lead to situation where no contest fields in NewQSO, no possibility to enter paper logs with exact information as you now do.
Contest window filled the need of easy running serial and contest messages that I had and I just wanted to share it with other users.
Excellent thing with open source is that anyone can redesign badly working sections of program. Or make completely new program based on original source.
Petr had a project to create a separate contest version of cqrlog but that has not finished. And I can very easily understand why.
One can think it is just a little job to convert working logging program to contest log version. But that is not!
It needs equal work, perhaps even more, and the time must be taken from somewhere: working time, sleeping time, family time or from other hobbies one may have.
Ideas for making cqrlog better are welcome. If they can be done by minimizing current code they are even better. The house of cards has reached rather high with cqrlog.
--
Saku
OH1KH
How feasible would it be to add a Dupe Call msg or screen for Contest Mode?
Regards,
Ken - KV5Y
HI Ken!
Could you specify what kind of Dupe Call msg you are looking for?
At the moment (2.4.0) same call in same band and mode turns bold red when you type it to contest window/call field.
To get this working in particular contest you need either create a need log for that contest or set contest starting day to "preferences/fldigi/wsjt interface/WB4 check starts from/call" and cjeck the "call" checkbox.
Just used that in last OK-OM contest and OH6-Cup and it worked very well in both.
Same methods can also be used in FT-contest when duplicates will show up in CQ monitor or wsjtx-map with red color.
I noticed this is not told in help section Contest. I will update it.
--
Saku
OH1KH
"a need log for" supposed to be "a new log for" in last msg. (How to edit a sent message???)
--
Saku
OH1KH