Re: [wsjt-devel] Inconsistency in color scheme logic - PSE name it "Worked before" instead of "New Call"

2018-11-14 Thread Bill Somerville
On 14/11/2018 13:57, DG2YCB, Uwe wrote: Status now (= only 4-6 weeks from deadline when ALL users in the world have to switch to v2.0.0) is that (A) most of the new highlighting ideas are not operational, and (B) the ones which worked very well until in v1.9.1 are now at least partly broken. I

Re: [wsjt-devel] Inconsistency in color scheme logic - PSE name it "Worked before" instead of "New Call"

2018-11-14 Thread Joe Taylor
Uwe -- On 11/14/2018 6:29 AM, DG2YCB, Uwe wrote: *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 ... There is

Re: [wsjt-devel] Inconsistency in color scheme logic - PSE name it "Worked before" instead of "New Call"

2018-11-14 Thread Bill Somerville
Uwe, as stated recently, the worked before highlighting is broken in WSJT-X v2.0.0 RC4. This is true for all worked before highlighting. A fix is in place. Please remember that RC releases are beta quality and not expected to be defect free. We have every intention to fix reported issues

[wsjt-devel] Inconsistency in color scheme logic - PSE name it "Worked before" instead of "New Call"

2018-11-14 Thread DG2YCB, Uwe
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