sending e-qsl lotw automatic or manual

[ik3ocd]

Feature Description

Hi, sometimes due to forgetfulness or laziness I forget to send the e-QSL, it would be nice to have the possibility to choose whether to send the e-QSL and the LOTW automatically at the end of the QSO or manually as in the clublog, I think it would help against forgetfulness. thanks and 73 from ik3ocd flavio

[aa5sh]

I know @foldynl is working on making some changes to the upload/download section for these items. I'm not sure how feasible it would be to have it autoupload especially for LoTW without some significant changes. I know for me for instance I have multiple locations setup in tQSL so each time I upload I am prompted to select which one to use. Also it has a good bit more overhead with its signing process as compared to Clublog where it is a relatively simple webcall. eQSL is fairly lightweight with simple webcall as well as QRZ.

[ik3ocd]

Hi and thank you for your consideration on the matter, in that case I would settle for e-qsl if all this is not feasible, in case it is not possible I will try to remember. Thank you and see you soon. Il Mar 29 Apr 2025, 15:58 Michael Morgan ***@***.***> ha scritto:

…

*aa5sh* left a comment (foldynl/QLog#658) <#658 (comment)> I know @foldynl <https://github.com/foldynl> is working on making some changes to the upload/download section for these items. I'm not sure how feasible it would be to have it autoupload especially for LoTW without some significant changes. I know for me for instance I have multiple locations setup in tQSL so each time I upload I am prompted to select which one to use. Also it has a good bit more overhead with its signing process as compared to Clublog where it is a relatively simple webcall. eQSL is fairly lightweight with simple webcall as well as QRZ. — Reply to this email directly, view it on GitHub <#658 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEBFR5KFEOICZ426JDQI4AD236AQRAVCNFSM6AAAAAB4CZ2PRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZZGAZTKNRRGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[foldynl]

Allow me to add my comment. As @aa5sh wrote, I am currently reworking the entire upload/download functionality, but mentioned change is something different. I don’t think there’s something wrong to forget upload QSL to online services immediately. However, that’s just my opinion, and it’s not based on any concrete evidence.

What I can comment on is QLog’s behavior. If you upload QSL at the end, it can take a long time to close the program, and when an operator wants to exit the program, they usually don’t want to wait. Uploading at the beginning rises problems with the database, because QSLite DB doesn’t allow simultaneous writing of two things — this is a limitation on the SQLite side not QLog.

Summary: I probably wouldn’t accept a change that performs QSL upload at exit. A change that uploads QSL at startup would require me to see how it’s implemented — then it might be possible to consider including something like that in the future.

But let me return to the beginning. I’m currently making a major change to the architecture of QSL/Upload/Download services. At this time, I’m not accepting any changes in this area, because it would create too many conflicts.

[mahacz]

Hi,
First, Thank you for this great piece of software.
From my point of view it would be best to have one button (eg. in the same line as search and filters) or menu item, which would send records to all configured services and receive QSLs. It would be one click to synchronize instead of 20 or so.
73 de SQ8BWM