Bill, thanks for your reply. I understand UI design is a hard problem and I'm glad you're on it. It sure seems that WSJT-X has a solid technical core to build around, which is a good thing.
*As always, finding the balance of developing a tool that makes digital * *communication by amateur radio fun and requires traditional aspects of * *operating skill to do it well without making an automated QSO server * *that spoils the fun for everyone.* Yes. On that point, I was a little surprised to see that "Call 1st" was available as an option in RU contest mode. *I wonder if anyone has reverted to the old fashioned dupe sheet * *techniques using a pen and paper? * Back in the day, my memory was a lot better and I would work without a dupe sheet until a break, when I would go back over the log and update it. Now I'm totally spoiled with contest logging software... 73, Paul K6PO On Thu, Nov 29, 2018 at 5:52 AM Bill Somerville <g4...@classdesign.com> wrote: > On 29/11/2018 04:47, Paul Kube wrote: > > Is there any way to control colors of a non-CQ message? There doesn't > > seem to be, and I would like to do that. > > > > For example:, I'd like to have a visual cue when someone not in the > > log is finishing a QSO, so I know they're not a dupe and I can tailend > > without waiting for their next CQ: highlight their "W1XYZ K0ABC 73" > > message. (This came up a lot in this evening's mock contest.) > > > > Possible? > > > Hi Paul, > > not currently. Clearly applying decode colour highlighting to non-CQ > messages is very desirable and it is on the to-do list but is not > trivial to implement given the current code base. Also some sort of > mechanism to highlight new multipliers, in contests like the ARRL RTTY > RU where multipliers are not covered by the current decode highlighting > facility, would be equally desirable for serious contest operators. > > For some background, as the speed of QSOs has increased and the number > of decodes has increased with modes like FT8 on HF, it has become > necessary for WSJT-X to do more and more interpretation of message > content for it to be anything like satisfying and ergonomic to use. This > has evolved organically on top a framework that was originally developed > to just display the decoded messages and let he user make all the > decisions about what to transmit next and what to log at the end of a > QSO. Some fairly major internal reworking is desperately needed to make > further implementation like this practical without introducing many new > defects as a side-effect. > > As always, finding the balance of developing a tool that makes digital > communication by amateur radio fun and requires traditional aspects of > operating skill to do it well without making an automated QSO server > that spoils the fun for everyone. > > I wonder if anyone has reverted to the old fashioned dupe sheet > techniques using a pen and paper? I always used to use an A3 sheet > divided into 26 boxes for each letter of the alphabet and enter worked > calls indexed by the first letter of the end letters part of their > callsign, e.g. my call G4WJS would be written into the 'W' square when > worked. Another sheet was used for mults worked, ok until trying the WPX > contest! > > 73 > Bill > G4WJS. > > > > _______________________________________________ > 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
