This is not easily accomplished. If you delete a log entry for a QSO
with P5, the program must rescan all P5 QSOs to properly compute the
P5 progress table entry. The "Recompute" button will accomplish this,
but a Prefix-specific version would run a little faster. A prefix-
specific Recompute could be made automatic after you delete a QSO,
but I fear it would make the delete operation annoyingly expensive.
Personally, I just run "Recompute" at the end of each operating
session to cleanup afer any deletions; this too could be made
automatic.
I could special case the most-recently-added log entry by remembering
the progress table entry for its DXCC entity prior to logging the
QSO, thereby allowing an "undo" without recomputation if this log
entry is deleted; deleting any other QSO would invalidate the
remembered progress entry for the last QSO. Would this be worth the
additional user-visible complexity?
Comments? If there's a better way to handle this, I'm all ears.
73,
Dave, AA6YQ
toggle quoted message
Show quoted text
--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Deleting a log entry in DXKeeper 1.2.5 does not automatically
remove the data from the progress table.
-----
73, Rich - W3ZJ
www.w3zj.com