> This weekend I was using CT for the first time since 1995 (at W3LPL).
> CT works fine for Multi Op situations, and I think some of these things
> could be improved in TR.
>
> As I have understood TR, you have two options how to send a QSO between
> computers. Either DIRECT after you hit enter, or after it scrolles off your
> screen. This is 5 qsos later... If the QSO is sent over to the other
> computer it will not be updated if it is edited later. At SK3GW M/S we have
> used Ctrl-N or just paper and pen to mark corrections and edited after the
> contest.
>
> I know that some M/Ms are using TR, have you experienced problems with this?
> With the rates we had this weekend 5 QSOs will scroll of your screen VERY
> fast.
When you are in this mode - only your QSOs are shown in the screen,
so you have some time to do the edits.
CT (and NA) organize their log in a binary file - which is compact
and easy for the program to edit. However, it isn't human readable
outside the program.
In order for TR to have the same editing power as CT, it really
would need to change how the log is stored - using a binary
file. This would be a major change, and I don't see the problem
to be significant enough to go through the pain of doing it.
Maybe, someday, I will put in the effort to write a really efficient
text editor to use. As processors get faster and faster, dealing
with a text file might be more practical.
Tree
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|