Welcome to SpotSpy's Bug- and Feature Request page.
Due to increasing spam attacks, I had to disable the feature of anonymous bug reports and feature requests. You will have to register before you are able to report a new bug or add a new feature request.
Due to increasing spam attacks, I had to disable the feature of anonymous bug reports and feature requests. You will have to register before you are able to report a new bug or add a new feature request.
FS#34 - 425 DOWNLOAD, FILTERED BY DXKEEPER
Attached to Project:
SpotSpy
Opened by William Heinzinger (w9ol) - Monday, 19 October 2009, 14:10 GMT+2
Last edited by Volker Rose (DL9HO) - Saturday, 24 October 2009, 23:36 GMT+2
Opened by William Heinzinger (w9ol) - Monday, 19 October 2009, 14:10 GMT+2
Last edited by Volker Rose (DL9HO) - Saturday, 24 October 2009, 23:36 GMT+2
|
Detailsnot sure this is possible.
I've been downloading the Dxpediton Calendars. that's puts a lot of callsigns, dxcc, iota into the 'watch for list'. And these will Alarm Now I'm not sure if when downloaded, they go through the same process as a cluster spotted callsign and Spotcollector checks to see if worked, confirmed etc. My request, if possible is, after the download of a Calendar, can SpotSpy check my log and see if those IOTA's are already confirmed, and if so, automatically remove them from the 'Needed Screen'. I'm pretty sure that if it's in the SpotSpy 'Needed' window that it will alarm even if I already have that IOTA/RDA worked on that band/mode. But I'm not sure. I don't actively request qsl cards from IOTA operations as that would be too expensive for a retirement pension. Hope I've made this clear. If anyone wishes to comment to me, my email is w9ol@billnjudy.com |
This task depends upon
SpotSpy
- Compares published IOTA information with the DXKeeper log database if the specific IOTA is still needed (i.e. not verified or confirmed)
- Displays the call of that specific IOTA in coloured letters (blue as of today, different colours to separate unconfirmed and unverified are on the enhancement list)
- Automatically selects that specific IOTA for Import
- Compares published DXCC information with the DXKeeper log database if the specific DXCC is still needed (i.e. never worked on any band or mode)
- Displays the call of that specific DXCC in coloured letters (red as of today, different colours to separate unconfirmed and unverified are on the enhancement list)
Automatically selects that specific DXCC for Import
If they don't confirm via LoTW, they probably won't get confirmed unless it's also a needed Band/Mode for Quixoti Quest.
So it could alarm even though it's already worked.
The only way it would get verified or confirmed is if I intentionally logged it as confirmed, which would be incorrect.
DXKeeper doesn't have an option such as Unworked, Unconfirmed and No intention of requesting a qsl. LOL
So in this case, I guess I'll just have to manually check DXK/DXV to see if it's worth chasing.
thanks for considering.
But that doesn't effect the incoming qsl status so the point is mute.
No problem Volker, you have more important issues.
thanks for reading.
William Heinzinger