A. DXKeeper's "Sync LoTW QSOs" function directs LoTW to report all QSOs accepted by LoTW after the date and time specified beneath
the "Sync LoTW QSOs" button; when the operation completes, the date and time that the last QSO was accepted is placed beneath the
B. DXKeeper's "Sync LoTW QSLs" function directs LoTW to report all QSOs confirmed by LoTW after the date and time specified beneath
the "Sync LoTW QSOs" button; when the operation completes, the date and time that the last QSO was confirmed is placed beneath the
C. Depressing the CTRL key while clicking either "Sync LoTW QSOs" or "Sync LoTW QSLs" button will direct LoTW to report all QSOs
ever accepted or confirmed by LoTW, respectively. This is typically only done when moving to DXKeeper from another logging
application whose ADIF export does not include information about LotW acceptance and confirmation. It is also employed by users who
lose their QSOs and have no other form of backup from which to recover.
D. Double-clicking the date beneath the Sync LoTW QSOs" or "Sync LoTW QSLs" button will display a small window that enables you to
modify the date and time that will be used when you next invoke the function. Under normal circumstances, it should never be
necessary to do this, but it can occasionally be useful.
In a post on the ARRL-LoTW Discussion Group earlier today, IT Director Mike K1MK stated that acceptance and confirmation queries
with default "since" parameters (scenarios A and B above) are serviced with normal priority. Acceptance and confirmation queries
with non-default "since parameters" (scenarios C and D above) are processed with reduced priority.
Mike adds "As a practical matter, except during infrequent episodes of unusually high user demand, there is sufficient idle CPU time
available that running a download task at the lowest possible priority versus one running at nominal priority has no discernible
effect on the time required to complete the download."