Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-25 Thread Bill Somerville
On 25/12/2015 02:36, Laurie, VK3AMA wrote: On 25/12/2015 7:52 AM, Bill Somerville wrote: Hi Laurie, as I said we do not check for redundant status updates. I will have a scan through the code and see if any can be easily eliminated but checking for every field against previous values may be q

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Laurie, VK3AMA
On 25/12/2015 8:41 AM, Bill Somerville wrote: Hi Laurie & Mike, turns out this was so trivial that I'm not going to look further at stopping redundant messages at source. I've committed a change (r6315) to the development branch. Laurie, is this causing JTAlert serious issues? The change is sma

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Laurie, VK3AMA
On 25/12/2015 7:52 AM, Bill Somerville wrote: Hi Laurie, as I said we do not check for redundant status updates. I will have a scan through the code and see if any can be easily eliminated but checking for every field against previous values may be quite tricky. WSJT-X is largely event driven

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Bill Somerville
On 24/12/2015 21:22, Bill Somerville wrote: > Otherwise I should be able to come up with a fairly simple generic > solution by comparing the whole byte array of the packed message rather > than doing this at the individual field level. Hi Laurie & Mike, turns out this was so trivial that I'm not g

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Bill Somerville
On 24/12/2015 21:13, Michael Black wrote: > Bill, how about the attached to eliminate duplicate status updates? > This isn't tested. > Seems like it should do the job. > > Do any of these need initialization (QStrings???) > Hi Mike, that's ok but I would rather not add yet another maintenance ha

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Michael Black
Bill, how about the attached to eliminate duplicate status updates? This isn't tested. Seems like it should do the job. Do any of these need initialization (QStrings???) 73 Mike W9MDB On Thu, Dec 24, 2015 at 2:52 PM, Bill Somerville wrote: > On 24/12/2015 20:46, Laurie, VK3AMA wrote: > > Thes

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Bill Somerville
On 24/12/2015 20:46, Laurie, VK3AMA wrote: These Status packets are being sent when there is NO change in status. * What is the purpose of these status packets sent at the 50 seconds (just prior to decode processing it appears)? * What is the purpose of sending a second duplicate status

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Laurie, VK3AMA
On 24/12/2015 10:23 PM, Bill Somerville wrote: On 24/12/2015 08:44, Laurie VK3AMA wrote: Using WSJT-X 1.6.0, I am receiving two (2) identical UDP status messages being sent at the 50 second mark. Is this a defect or by design? Hi Laurie, neither, there are several points in the WSJT-X source

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Bill Somerville
On 24/12/2015 08:44, Laurie VK3AMA wrote: > Using WSJT-X 1.6.0, I am receiving two (2) identical UDP status messages > being sent at the 50 second mark. > > Is this a defect or by design? Hi Laurie, neither, there are several points in the WSJT-X source code where events are being processed that

[wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

2015-12-24 Thread Laurie VK3AMA
Using WSJT-X 1.6.0, I am receiving two (2) identical UDP status messages being sent at the 50 second mark. Is this a defect or by design? All other UDP messages (heartbeat, logging, status change, etc) are received only once. de Laurie VK3AMA -