Now the user has full control of all notepad features. You can create a notepad for a selected call as in the past by pressing ALT-N either from the call entry field with a call entered or from the F6 review mode.
A new command CTRL-N will remove the notepad attached to a selected call and delete the notepad flag accordingly. Before this operation is performed you will be prompted for really executing the delete command. This should make sure that you will not delete any notepad information accidently.
If a call was selected and a notepad file created for this call all other log entries for the same call will automatically be marked with the flag on the event of a rebuild of all index files. The opposite happens if an existing notepad file attached to a call is deleted. A rebuild operation in this case will remove all flags from all log entries for this call.
Composite calls e.g. GU/DJ9KG/P will be treated in such a way as a notepad in this case will be created for DJ9KG only. This means there will be a notepad file named DJ9KG.NOT in FILEDIR. The flag, however, will be assigned to the composite call as selected. Furthermore, any characters which would yield confusion in DOS-filenames such as "*" "." "\" "?" will be replaced by a "$" in the assigned name of the notepad file.
When the SCAN mode is entered from the callsign field and TL starts to control the transceiver to switch to the frequencies which were specified in the ADVANCED SETUP, submenu MISC, prior to this operation the information window on the logging screen now keeps track with the commanded frequencies. This feature is independent from the frequency capture scheme as selected im the CAT menu. Mode will be adapted automatically if AUTOMODE is activated.
Please note: The scanning starts at the next full minute with respect to your PC's internal clock. This allows for interesting operations such as tracking of NCDXF beacon system, meteor scatter, etc. The dwelltime on channel can be specified in the setup menu at your desire.
By the way: You can interrupt the scanning procedure at any time you want by simply entering NOSCAN from the callsign field.
For the time being this feature is available for all Kenwood rigs. We
have very limited info about support of remote S-Meter reading for other
rigs. All generic CAT-files, xxxx.GEN, however, are prepared for the operation.
In case of other brands: All which needs to be done is to define a suitable
command line for reading the strength and for a strength multiplier in the
appropriate generic or private CAT-file. Since these files are available
for the experienced users for modification....no big deal ...if your rig
supports this feature. See how it needs to be done for example in KENWOOD.GEN.
The right hand side of the expressions is where you rig's interface handbook
comes into play.
Now, with this version of TL the procedure is very much easier:Based on the experience that always very few cards, if any at all, return without being accepted we have designed a "bulk update facility". This one can be accessed from the OUTPUT operations submenu. The moment you have selected the QSOs for printing the DXCC application form you are enabled to mark them ALL as ACCEPTED at the same time. And this is the only moment when it can be done correctly!! Imagine, you have sent out your bunch of cards and while the weeks are passing by you receive new confirmations which you would like to apply DXCC approval for. If you would now mark the cards as received you would mess up the whole book keeping since the status will not be the same as at the time you filed your application. There are various other scenarios which could cause trouble in a bulk update regime, such as QSO-imports, deleted records, new country assignments due to errors, etc.
Since it would be a hell of a task to manually correct an accidental bulk update we have payed very high attention to its fool-proofness in the following ways:
First of all you can only access the BULK UPDATE menu item if youhad run at least one of the subitems, such as output
- to screen,
- to printer,
- to print file, or
- to data file before.
This assures that there will be at least a close inspection or a backupof the records which you bulk-updated.
Secondly, as mentioned above, DXCC application and bulk update must becarried out in a tight timely cnnection as to prevent the database fromchanging `under your fingers`. This means that you have to carry outboth operations in the same List & Report session.
Thirdly, you will be only allowed to bulk-update if you strictly followed the DXCC-APPLICATION path throughout the menus.
If you violated any of these conditions the access to the bulk update will be denied and an error message displayed accordingly.Even if you proceded as requested there will be a final reminder "DO YOU REALLY WANT....." as a last barrier. On pressing Y(es) the update will be started and effectively you will see the records which you updated being counted for you.
Of course, if there really should be a few cards not being accepted in the returned bunch of cards you need to go into review mode ( F6-->F6 ) for those particular records and remove the right hand "Y" from the QSL receiced entry. This should be considerably less work than updating everything manually....under normal circumstances.
!!!! WARNING !!! !!!! WARNING !!! !!!! WARNING !!!
Only run the bulk update operation after you are a 100% sure on what you intend to do and in connection with a DXCC application only. The bulk update facility is a very helpful and powerful tool. We do not want you to accidently update 10.000 records in a moment of weakness causing you weeks to manually correct this mishappening.
Thus we urge you to strictly follow the guidelines mentioned above!
In any case we recommend to backup your logbook file before you start the bulk update operations.....just in case....
!!!! WARNING !!! !!!! WARNING !!! !!!! WARNING !!!
Outlook for version 3.23:
back to version index Home