More options for handling bad input.

4 posts / 0 new
Last post
KB8AP
More options for handling bad input.

Using CQRLOG 0.8.5 on Ubuntu 9.10.

If I edit an existing QSO and leave the Frequency field blank, when I hit the "Save QSO" button I get a dialog that says:

"" is an invalid float.

Press OK to ignore and risk data corruption.
Press Cancel to kill the program.

I'd like an option to let me go back and fix the problem. Accepting bad data or killing the whole program seems rather harsh.

73
--
Joe KB8AP

ok2cqr
ok2cqr's picture
Re: More options for handling bad input.

Hi Joe,

I'll fix it, thank you.

73 Petr, OK2CQR

la3rk
Call check before entry into freq column

I note that new call is checked when call field loses focus. Would like to see a check based on partial call input in call field and maybe the previous QSO history when call has been verified by leaving the call field.

Used CQRLOG as my logger during recent CQ WW CW contest and did notice this after I got some wrk bef.

73 de Olaf LA3RK

Olaf Devik LA3RK

ok2cqr
ok2cqr's picture
Re: Call check before entry into freq column

Hi Olaf,

if call field loses focus it is the same like leaving edit field. Is it a problem?

73 Petr, OK2CQR