Windows build v 0.1.16 Latest packet decode does not match altitude in position window

[zanco]

After running for about 24 hours I notice when receiving an 4fsk payload that the latest packet altitude is not the actual one. Lat and Long appears to be OK, and the uploaded packet also has the good altitude .

[darksidelemm]

There are known issues with the GUI not updating correctly after a while.
I never really expected the GUI to be left running for 24 hours :-/ For continuously running applications I kind of expected that the command-line horusdemodlib demodulator would be used.

[darksidelemm]

Can you have a look at the latest version and see how it behaves?

[zanco]

Hi, I am running 0.3.6 now, but the "position" field shows a different time as the log shows.

This happened at PD7R too yesterday, after only about 2 hours of running the software.

I am running 2 instances of the same software at the same time to decode 2 different hardware versions , it appears to happen on V2 decoding, I did not notice this on V1 decoding.

[darksidelemm]

The code that updates the displays is the same for V1 and V2 (and for RTTY for that matter...) so I don't think it's a V1 vs V2 issue.

I still think it's a threading issue, probably caused by how i'm running the GUI... but given other parts are updating, i'm not sure why it's occurring, sorry :-/.