Results 60 comments of Vic

Traceback (most recent call last): File "C:\Users\stone\py\learningPython.py", line 243, in main() File "C:\Users\stone\py\learningPython.py", line 195, in main scr = curses.initscr() File "C:\Python34\lib\curses\__init__.py", line 30, in initscr fd=_sys.__stdout__.fileno()) AttributeError: 'NoneType' object...

Is this happening? This would be a killer feature. It would need to take audio from the radio.

Same here added /P and no luck uploading to eQSL

I know that in Log4OM you need to provide "DG3NAB/P" as user not "DG3NAB". So, the User and Nickname have to match. It seems logging software is required to support...

It seems like `Date Created` corresponds in some unknown way with the LoTW cert `Valid` vs `QSO Dates` I created cert yesterday to upload stuff from July last year. Valid...

It should accept all QSO from 01/07/2021 QSO Dates: 2021-07-01 00:00:00 - 2025-05-01 23:59:59

Using TQSL I was able to upload all those QSOs ![image](https://user-images.githubusercontent.com/6089679/166575576-8f64749c-fc0a-4ebd-a587-d094295058d4.png)

What I am saying is cert is valid from 02/05/2022 but I can upload QSOs from 01/07/2021. I could not use that cert on the 01/05/2022 if I could travel...

> Oh just spotted, OK so when you create a lotw cert you give it a state you started which according to your cert is "2022-05-02 00:00:00" there for it...

After sync (or multiple synchs) the page is not updated. It's as if Cloudlog never acknowledged existence of those QSOs. ![image](https://user-images.githubusercontent.com/6089679/166581333-e9b0d186-2e3c-44c9-ba4e-686dbe068af7.png)