Page 1 of 2

Possible Bug in Latest version

Posted: 23 Sep 2016, 21:23
by WA2SQQ
Terry
I just upgraded to the latest version. I've been working the Spanish special event stations. I'm noticing that, randomly, worked stations are not being highlighted as "worked" on the DX Cluster. See attached photo. AN400M was worked, and noted so in the Callsign field. On the cluster screen it is not marked, in green, as are other worked stations
log 4 om Error.jpg
log 4 om Error.jpg (100.75 KiB) Viewed 7710 times
.

Re: Possible Bug in Latest version

Posted: 24 Sep 2016, 06:53
by G4POP
WA2SQQ wrote:Terry
I just upgraded to the latest version. I've been working the Spanish special event stations. I'm noticing that, randomly, worked stations are not being highlighted as "worked" on the DX Cluster. See attached photo. AN400M was worked, and noted so in the Callsign field. On the cluster screen it is not marked, in green, as are other worked stations.
Strange it works fine for me, I suppose that you are waiting for the next cluster refresh for it to highlight the cluster entry as worked?

Re: Possible Bug in Latest version

Posted: 24 Sep 2016, 21:23
by WA2SQQ
It's not doing it with every contact which is why I mentioned randomly. Last night I made 12 contacts and it occurred 2 times.

Re: Possible Bug in Latest version

Posted: 25 Sep 2016, 12:16
by G4POP
Does any other user have this issue - Please respond if you do!

Re: Possible Bug in Latest version

Posted: 27 Sep 2016, 21:21
by KI5IO
Terry,

I noted that I was experiencing this same situation this afternoon when I was also getting Q's with the AN400-'x' stations.

I've refreshed and changed display taps several times and is not indicating "worked".

FWIW: Both of my Log4OM installations are new (v1.26.0.0) as I've been trying to trouble-shoot other issues related to SUB/Serial signals being sent to my K3. I've done very little modifications to the app (as of now anyway ... ;) )

Re: Possible Bug in Latest version

Posted: 28 Sep 2016, 06:46
by G4POP
I am beginning to think that this could be due to ether our user or the person spotting occasionally using an O instead of a zero when entering AN400xx as this is not reported on any other callsigns just this particular series of calls.

Re: Possible Bug in Latest version

Posted: 28 Sep 2016, 09:54
by CT1BXX
G4POP wrote:Does any other user have this issue - Please respond if you do!
Hi Terry,

I confirm, I have same error here.

Re: Possible Bug in Latest version

Posted: 28 Sep 2016, 11:22
by G4POP
CT1BXX wrote:
G4POP wrote:Does any other user have this issue - Please respond if you do!
Hi Terry,

I confirm, I have same error here.

The issue of 'Worked before' not working Manuel ???? and if so is this only for AN400xxxx calls?
or
IOTA highlights?

Re: Possible Bug in Latest version

Posted: 29 Sep 2016, 13:56
by CT1BXX
G4POP wrote:
CT1BXX wrote:
G4POP wrote:Does any other user have this issue - Please respond if you do!
Hi Terry,

I confirm, I have same error here.

The issue of 'Worked before' not working Manuel ???? and if so is this only for AN400xxxx calls?
or
IOTA highlights?
Sorry Terry I was not clear about the problem.
Only IOTA highlits

Re: Possible Bug in Latest version

Posted: 29 Sep 2016, 14:56
by DF5WW
Have tried to force this error here with the spanish special calls but no chance. All is working perfectly. I use some other colours for the "worked on same band" spots but here all is working as it should.