Hi,
In addition to the already discussed "worked before" bug, there is another inconsistency in the color scheme logic, which from my point of view is a more general issue: How is a new call highlighted, which is also a new CQ zone (and eventually also a new ITU zone, et cetera)? According to my Color scheme settings "New Call" should have not been highlighted at all, but it should have been highlighted as "CQ" unless the "New CQ Zone" was detected. All these settings did not work! In practice the call was first time highlighted as "New Call" and then as "New CQ Zone" (see screenshot). (Btw. I don't believe that it was a new CQ zone, because I've already worked all of them. Means that recognition of CQ zones doesn't work correctly either.) Unfortunately I could not work this station, so that I could not see whether it had changes anything. (RX3DHR was the only station this morning using the V2 protocol). My proposal: Instead of "New Call" name it "Worked Before" or "Already Worked", and make the algorithm behind it the other way round, so that it is highlighted when the station was worked before. This way round logic makes sense, because a station worked before cannot be a new call, nor a new DXCC, nor a new continent, nor a new CQ zone, nor new ITU zone, nor a new grid. I made this proposal already on October 18th, but didn't get any reply until today. And PLEASE FIX ALL COLOR SCHEME BUGS BEFORE THE GA VERSION IS ANNOUNCED!!! I don't want to be impolite, but we have been discussing the color scheme issues at least for one and a half months now and rc4 is still full of bugs regarding this (and still contains this general inconsistency)! As you want ALL FT8 USERS to change from v1.9.1 to v2.0.0 in December 2018 , this issue must NOW been solved. Otherwise it will lead to a great deal of chaos! 73 de Uwe, DG2YCB
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
