Advanced: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
* ? - Tucnak knows locators of this station but typed locator is different | * ? - Tucnak knows locators of this station but typed locator is different | ||
* nothing - callsign is unknown or locator corresponds with callsign. | * nothing - callsign is unknown or locator corresponds with callsign. | ||
See also: [[Split VFO]] |
Latest revision as of 07:28, 23 August 2020
If you insert a callsign which is known in the C_W database, the program will automatically fill up to two locators. Locators are inverse displayed. If locator on higher row is valid you must confirm it by pressing <Alt+X> key. If second WWL is valid you must swap locators by pressing <Alt+V> key. If callsign isn't contained in the database, Tucnak fills in the large square with highest activity or that of the Capital City of worked DXCC and calculates approximate QTF.
Similar situation is if you insert known locator. There'll be displayed two inverted callsigns which you can swap -press <Alt+C> and confirm by pressing <Alt+D>. Alternatively Tucnak shows prefix(es) of possible DXCC only if the entry isn't any known callsign
Tucnak checks if pair of locator and callsign exists. If Tucnak thinks that it's invalid then it shows at locator some of these characters.
- ! - large square doesn't lie in DXCC. If callsign and locator are correct an invalid record is in tucnakdw.
- ? - Tucnak knows locators of this station but typed locator is different
- nothing - callsign is unknown or locator corresponds with callsign.
See also: Split VFO