Bob,
The bottom line is TR would be a BETTER program if you could
edit any QSO in the log, last 5, last 100 I don't care. A logging
program should not prohibite you from editing the log. When
I realize HP1ZZZ is really SP1ZZZ, I would like to fix it. Right
away, later when the band goes dead, or whenever I want.
The last 5 QSO thing bothers a lot of people. It might not
bother you... great!! 73 Bill N9BR
----------
> From: Bob Wruble <ai7b@teleport.com>
> To: Larry Tyree <n6tr@teleport.com>; trlog@contesting.com
> Subject: Re: [TRLog] ASCII vs. BINary
> Date: Tuesday, July 08, 1997 4:51 AM
>
> I think all the talk abt editing is BS anyway.....use the SW
> and u will see with a lil practice that its not a problem to
> edit either via the last 5 qso scroll method or drop
> a note into cntrl N and deal with it later......the idea is to
> make qso's....F**** with the log later !!!!
>
> w7gg
>
> ----------
> > From: Larry Tyree <n6tr@teleport.com>
> > To: trlog@contesting.com
> > Subject: Re: [TRLog] ASCII vs. BINary
> > Date: Monday, July 07, 1997 1:14 PM
> >
> > > I have used TR for a couple of years, and CT for many more
(previously).
> > > This is not meant as a rude complaint, but the lack of user
friendliness
> > > when correcting entry mistakes is a real sore spot for TR...
> > >
> > > Don't take my word for it, though. Look at the choice of logging
> > > software for the competitors in WRTC last year. I really expected
most
> > > of them would use TR because of its high performance aspect, and the
> > > fact that it was already updated/debugged for the contest (CT was
> > > crashing just a week before the event) But that was not the case... I
> > > asked a couple of the competitors why they weren't using TR--the
reason
> > > given was "difficulty in error recovery".
> >
> > Okay - I am a little confused here... Over the years, there have
> > been improvements to the error correcting methods in TR. We have
> > done away with the question asking if you want to make the changes
> > take effect (if you want it that way). Pressing uparrow with no
> > call window entry moves you up into the editable window, and the cursor
> > keys can be used to move around, along with TAB and shift-TAB.
> >
> > I am used to people having perceptions of TR that are out of date...
> > but I am not sure this is a valid perception any more.
> >
> > So, please tell me what else needs to be done to make it easier?
> >
> > Or, are we talking about the 5 QSO limitation?
> >
> > > If interested, see the WRTC statistics & log summary at www.jzap.com.
> > > This site shows breakdowns, including logging s/w.
> >
> > I am not sure the ONLY reason is the editing issue. In most cases
> > people don't use TR because they aren't comfortable with it, and will
> > use the "least common denominator" when two or more people need to
> > make a decision.
> >
> > > As for me? Well, I will be using TR this weekend. However, I do wish
it
> > > was a bit easier to correct my (many) errors in real time.
> >
> > "real time?" I am perplexed by this... wouldn't this mean fixing
> > them during the QSO? Because of the way CT operates (by sometimes
> > logging a QSO before you might have the right zone for example), it
> > seems to make correcting the previous QSO a "normal" procedure.
> >
> > With TR, it always wants you to press that additional key (on SSB)
> > after you have entered the exchange information to log the QSO.
> >
> > At any rate - I am all ears on how to make the last 5 QSOs more
> > editable. For those who want more than 5 QSOs, please see the
> > comments on the wish list (http://www.jzap.com/n6tr/trwish.html).
> >
> > Tree N6TR
> > tree@contesting.com
> >
> > --
> > FAQ on WWW: http://www.contesting.com/trlogfaq.html
> > Submissions: trlog@contesting.com
> > Administrative requests: trlog-REQUEST@contesting.com
> > Problems: owner-trlog@contesting.com
>
> --
> FAQ on WWW: http://www.contesting.com/trlogfaq.html
> Submissions: trlog@contesting.com
> Administrative requests: trlog-REQUEST@contesting.com
> Problems: owner-trlog@contesting.com
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
|