search

foldynl / QLog

Amateur radio logbook software
GNU General Public License v3.0
111 stars 16 forks source link

0.37 doesn't populate field data from FT8 QSOs #405

Open muihlinn opened 1 week ago

muihlinn commented 1 week ago

when a QSO starts picks up all the data just fine. None of those are saved when the QSO is effectively logged, as it used to do (0.34 or 0.35). Only the wsjtx data.

Built from source viar AUR package, as previous version.

foldynl commented 1 week ago

Sorry, I do not understand you. Example would be a good starting point.

muihlinn commented 1 week ago

Once the QSO starts Qlog correctly pulls from somewhere callsign data displaying it in the QSO form for most callsigns (and not for some, for whatever reason and that's fine).

With previous version [0.34 or 0.35] that data was saved when the QSO was logged. It doesn't do it anymore for any QSO, and I couldn't find why. Capture show the last time it happened. Hope it makes it clearer.

2024-07-06-203926_2688x1080_scrot

foldynl commented 1 week ago

I think we are discussing this in #403.

muihlinn commented 1 week ago

I think we are discussing this in #403.

could be, I'm not referring to QTH only, mostly operator name and other related data. Also if you look at the screenshot you can see several with 6 characters grids which arent filled.

Anyway to me is a minor annoyance - if anything - it's just the fact that it once worked and now it doesn't.

It'll be nice to be able to automatically fill those fields once a QSL is received.

foldynl commented 1 week ago

I think I will disappoint you in this. Your expectations from the automatic filling of QTH and other fields cannot be met. LoTW or eQSL provide only limited set of ADIF fields. ADIF fields for QTH are not there. The only thing that can be "extracted" from electronic QSLs is the gridsquare. And yes, here you can say that you have an exact locator for the given Callsign and QLog can query the QRZ or HamQTH for details. But imagine importing a few hundred or a thousand electronic QSLs. The authors of LoTW or eQSL would not be very happy if QLog search the information about the QSO after receiving of each electronic QSL. This would also increase the import time.

muihlinn commented 1 week ago

I'm afraid that issues isn't the right place to discuss this, and I am fine whatever you decide about it.

My point was a "heads up" about something that worked once [even as a "feature bug" ] and then not. I loved the previous behaviour and will like to keep it, but won't make the discussion longer than necessary if it's not really an issue.

BTW To me looks clear what I'll do, I'll keep the data already imported (or looked up) at the start of the QSO (name, etc) except what will come from the ADIF once confirmed. If it cannot/should be, it won't be a deal breaker by any means.