Jasper,
Before the most recent version (with the TCP bug), when using AIS-catcher and accessing the web client, ending the web client would close the web page and the AIS-catcher icon would have an orange dot on it, indicating it was still running in the background.
In the current version, there is no orange dot on closing the web client.
AIS-catcher still runs in the background and processes data and when icon pressed screen comes back with correct display.
If stop feed, the program still runs in the background, the Running Time counter increments, even though there is no feed (tested using rtl_tcp).
I think that the previous version did end, but I might be wrong.
A force stop for the app ends the program and on startup the Running Time counter is reset.
I would expect the following to happen:
Assume AIS-catcher is running with the web client displaying a page:
End web client, should end it (it does) and leaves AIS-catcher still running (it does). It should indicate that the app is running in the background (orange dot), it does not do that.
Select AIS-catcher icon and it displays current data (it was running in background): expected result.
Stop processing by pressing Stop: AIS-catcher disconnects from feed (expected). Running Time increments (if it is 'app running time', that is correct).
Press the square symbol in middle bottom of screen, AIS-catcher appears to close. It still has the Running Timer running. I would expect the app to end and stop completely if not processing data. On restart app, it should be a new session with Running Time reset.
If 'force stop' app, it does end and reset Running Time counter on restart.
Is the current behaviour intended?
Roger