开云体育

Gyula - that's great news! Please continue testing - you need to have at least 100 QSO's logged in order for us to be sure the change is working!? ;-)

Dupe Checking - so when the LOG>> button is clicked, the current software checks to see if the same callsign was logged in the current minute. If it was, the new log request is rejected. This approach may not be the best:

Some contests will allow you to log a station again on a different band / mode / grid square.

Good contesters will log a duplicate contact anyway, because 1) the other station may not have logged your callsign correctly the first time, so if you don't log the other station again, the contest sponsor's log checking software will not give you credit for the contact, and 2) it just wastes time to tell the other station they are a dupe.

The current software does not clear the log fields when the a log operation is completed successfully. So it may be that Farhan's intention was to prevent multiple clicks of the LOG>> button from making multiple log entries unintentionally. A better approach might be to just clear out the log fields when the log entry is completed successfully. Confirmation of the logged contact is displayed in the text window so that's not an issue.

Thoughts anyone?

73; Steve, N3SB

Steve,
I'm trying to get 100 QSOs together. :-)
The LOG>> button now works after successful logging in the 2nd minute. I managed to double it at least once.
I don't think this log drive was made for competition.
I have looked at many logging programs, where the creators explain this, that there are competition logs made for special competitions with different parameters,
there are year ones made for the daily diary.
I think that this logging program is also incomplete for daily logging.
Until now, I used the yfklog program, whose creator made it suitable for entering negative rst.
But unfortunately, he is very busy at work and his program was created under Perl programming around 2005, with the requirements of that time.
Since then, many parameters should be modified, as I tested.
However, it fits well on the 800x480 screen and does many things.
--
Gyula HA3HZ

"The current software does not clear the log fields when the a log operation is completed successfully."

The logging data is deleted in case of successful logging. According to my experience so far.
--
Gyula HA3HZ

I should have been more specific - log field clearing after successful logging does not appear to occur in CW or SSB modes.

Will continue to test. It's a single function call to clear those fields.

73; Steve, N3SB

Farhan - thanks for the explanation. I'm more familiar with logging programs that clear out the fields when the LOG operation is selected, however I understand how logging the QSO when signal reports are exchanged, while keeping those fields filled in to be used by the other macros, could be useful.

73; Steve, N3SB

Ashar,
you say that
"2. The other station replies back with your rst. Now that the reports are exchanged, you enter this in your logger and press the LOG button. The qso is logged."

When the connection is not completed because the RRR or RR73 confirming the reception is not received - then the entry saved in the log file should be deleted. Where can this be done?
Or some data is not correct and after saving it is still possible to see what needs to be corrected - but it is not possible to correct or edit the input saved in the log file.

Is there any concrete solution to this?
If this is the final log, then it's not finished!
Am I waiting for a solution or will the forum solve this too?
--
Gyula HA3HZ

Don't throw the radio just because you have to hit the swipe button!
The calllsign field is also used to fill in the cw macros with your call sign.
There is ample need to send cw macros even after you have logged the contact if you want to continue to ragchew.
To clear the callsign field, you can hit the swipe button.