Improve NIL (Not In Log) handling #441
Description
Summary
Improve NIL (Not In Log) processing by reporting incomplete QSO that was started by the user but was not completed. In this case, the calling station timed-out and disappeared resulting in an incomplete QSO. Optionally, display any calling stations who timed-out because the user did not call them.
Motivation
MRCE will sometimes report a NIL (Not In Log) error in the QSO Log, however it is not clear to the user why this error occurred.
By improving NIL handling, the user will better understand why they had an incomplete QSO. For example, if the user is running in Pile-Up mode and notice the occasional NIL errors, they may need to increase their Rx Bandwidth to hear more off-frequency stations.
Detailed Description
There are two scenarios to consider:
- The user has entered partial information for a given QSO, but did not complete the QSO before the calling station timed out. We can consider this an incomplete QSO.
- A calling station disappeared (due to a timeout) because the user never responded. The best example of this is an off-frequency station that the user did not hear. Or perhaps it was a weak station and they chose not to respond. I see this more as an optional case and should be enabled with a switch.
In either of these cases, the MRCE log would display the NIL error. If space permits, add "(timeout)" or "(incomplete)". Another option might be to add a "TO" error to indicate a timeout situation.
For the second use case above, we can add a switch in the INI file to enable this case. Long-term when we have a Setting dialog, this can be a checkbox.