Add my vote for this: 1) In the contest log set the record entry field for the newest/latest entry to be that entry’s actual count since the first log, vs 1. Having the latest log at the top of the window is good, but having it numbered one not so much - especially if you are trying to keep track of your total log count as I was.
David, AK2L -----Original Message----- From: Al Pawlowski <k6...@almont.com> Sent: Monday, June 28, 2021 08:00 To: WSJT software development <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] 2021 Field Day Logging Issues WSJT-x worked well for me this FD. However, I would suggest a couple of changes/improvements be considered. 1) In the contest log set the record entry field for the newest/latest entry to be that entry’s actual count since the first log, vs 1. Having the latest log at the top of the window is good, but having it numbered one not so much - especially if you are trying to keep track of your total log count as I was. 2) Add some type of real obvious duplicate log entry indicator to the contest log so that such log entries can be found easily and corrected, perhaps even in for real time. Took me some time last night to find a few dupe’s I had. 3) At least for FD configurations, add a highlight color for Dupe and/or New/Unworked call on band or mode. JTalert “B4” helped on this, but was far from perfect. Al Pawlowski, K6AVP Los Osos, CA USA _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
