Lazy Log: Entering FT8 data - no reports possible

[DK9JC]

v 2.5.0.0

When entering a report like R-15 for a FT8 QSO it seems as that the -15 can not be interpreted as a report.

Here is what I entered:

2020-05-01_14h01_32.png (17.87 KiB) Viewed 3142 times

In the overview it shows 59 / 59

2020-05-01_13h58_47.png (1.46 KiB) Viewed 3142 times

and in the details +30db each:

2020-05-01_13h58_34.png (805 Bytes) Viewed 3142 times

I guess the software is waiting for numbers like 59 and no - [minus].

[G4POP]

Yes I can see the problem but don't bite my head off for asking!

Why are you manually entering FT8 QSO'S manually when every FT8 program saves to an ADIF file?

It's because we did not think anyone would manually enter any JT mode manually that we did not include the minus and plus db values

[DK9JC]

Why are you manually entering FT8 QSO'S manually when every FT8 program saves to an ADIF file?

I knew you would ask. Sometimes 3-5 people are calling me the same times and the sequence get messed up or I don't receive my 73 after I have sent RR73. Then usually I do not log the contact. Often I see QRZ.com open requests after I upload my logs. I then check the all.txt unter log and if we had a QSO and exchanged reports both ways, then I log afterwards. It's not a big problem for me. 1-2 QSOs a month I guess, but after reading the whole manual I found this feature and thought I give it a shot.

[G4POP]

Why are you manually entering FT8 QSO'S manually when every FT8 program saves to an ADIF file?

I knew you would ask. Sometimes 3-5 people are calling me the same times and the sequence get messed up or I don't receive my 73 after I have sent RR73. Then usually I do not log the contact. Often I see QRZ.com open requests after I upload my logs. I then check the all.txt unter log and if we had a QSO and exchanged reports both ways, then I log afterwards. It's not a big problem for me. 1-2 QSOs a month I guess, but after reading the whole manual I found this feature and thought I give it a shot.

We will add the required signal report ability when we have time.

If it's only 2 or 3 QSO'S per month I think its far easier to just enter the qso's the same as you would a new QSO in the main UI using manual settings for time, date, band freq etc

[DK9JC]

We will add the required signal report ability when we have time.

I do not necessarily need the function and certainly not need it quickly. I just noticed it and thought I would let you know. Prio super super low (at least for me).

If it's only 2 or 3 QSO'S per month I think its far easier to just enter the qso's the same as you would a new QSO in the main UI using manual settings for time, date, band freq etc

Right, that's how I usually do it then.

EDIT: Another idea - if it will not be fixed, an additional clarification like "FT8 or modes with no reports like 59 or 599 are not supported" in the manual would be great.