I'm not sure if this is a result of the problems with the build that I've posted about previously in the Open Discussion, but the Start Time and End Time are not updating like they have in the past.
In the past the times would update as long as the user did not TAB out of the Call field. Even with a call in the Call field they would continue to update.
Now they are updating when a call is typed in and will not update again after that. This is not beneficial if chasing DX. In the past I would type in the DX Call and not tab out of the Call box until I had made the contact. This way the times would update with the clock until the contact has actually been made. This would ensure that the Start Time was correct.
I am using 1.5.6 (used the .deb file to install in Lucid) and it works very well.
Just to make sure, I entered a callsign in the appropriate field,hit TAB to "His RST" and waited a few minutes. The starttime kept on updating untill I TABBED again to "My RST". That is when the QSO started and the "duration" started to count.
Upon saving, the QSO ended and both start- and stoptime were properly logged.
73, Tjalling PA3GOS.
Hi Tjalling,
this is not a bug, it's a feature.
If I'm in S&P mode, I enter the callsign and hit arrow down, it moves cursor to RST_S and log shows me previous QSO and other information. Then I can decide if I will call the station or not. If yes, it may take some time to be successfull and that time can't be part of QSO. So after he calls me back, I'll add the report, move to next field and counter starts.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi Petr,
True. I realize that and use it a lot too. Just like I described.
However, at the original posters setup it seems not to work that way.
Therefore I checked mine and it works perfectly as expected.
Thanks for responding anyhow Petr. Maybe you know what is wrong with the setup of the OP.
73, Tjalling PA3GOS.
My point is that I am not seeing this feature. This is how I would expect it to work, but it's not. Again, this could be a result of 1.5.6 not installing correctly, but I wanted to ask here.
You've confirmed that the behaviour that I am experiencing is not correct. Hopefully, when y'all get the issue with the build errors corrected the log will all work as designed.
Thank you - Michael K5WRN
Seven-Three,
Michael - K5WRN
Texas, USA