[Logic] How to best use QRZ lookup and Log

Sun, 7 Sep 2003 19:15:08 -0400

Yes you are right... But it's a bug... ANYTHING that can cause you to
lose data in the heat of battle is a bug... And I'm sure Dennis will fix
it because the design of the program does seem to focus on data
security. It probably also explains how I managed to do the same thing
with a fix to the Name field...
I've encountered the same "bug" in programs I've written in Access VB...
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Bill VanAlstyne
Sent: September 7, 2003 17:34
To: [email protected]
Subject: Re: [Logic] How to best use QRZ lookup and Log
Mel,
OK, I've investigated this further myself. Here's what is really
happening, as best I can determine:
If you type into ANY field and leave the field "open" by leaving the
cursor at the end of the entry, pressing F6 will cause the contents of
that field to revert to the last recorded state of the field. This could
be blank, or it could be something else.
As an example pf "something else," suppose I type "EAST PODUNK" into the
QTH field, then move the cursor to a different field, then come back to
the QTH field and correct the entry to "WEST PODUNK". While the cursor
is still at the end of this line, I press F6. The QTH field will revert
to "EAST PODUNK", rather than to blank.
Basically, pressing F6 appears to force the entry form to reflect
whatever has been recorded thus far in the "soft" record, and also
updates the date/time stamp. This is all presumably in a structured
array in RAM; I'm using here the term "soft" record to differentiate the
record as it exists in RAM while it's being built, from the record as it
will exist on the hard disk once it is saved.
To work around this behavior, you can simply make sure that you don't
leave the cursor at the end of an entry in a field that you have
manually changed, since you really haven't written anything to the
"soft" record until you move to the next entry field. Pressing the TAB
key works, as does mouse-clicking anywhere away from the field in
question.
Obviously I'm not privy to the source code, but I have a a bit of
professional experience debugging software under development, and this
entails figuring out what the programmer might have done that could
cause the behavior in question. (Sometimes you even get it right!) Often
what you're seeing is not a bug per se, but rather a conscious design
choice that perhaps has usability consequences the programmer didn't
think of.
Hope I got this right -- :-)
Bill / W5WVO
----- Original Message ----- 
From: "Mel" <[email protected]>
To: <[email protected]>
Sent: 07 September, 2003 12:49 PM
Subject: RE: [Logic] How to best use QRZ lookup and Log
> I stand partially corrected...
>> It's just the Comments field that gets clobbered...
>> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Bill VanAlstyne
> Sent: September 7, 2003 10:35
> To: [email protected]
> Subject: Re: [Logic] How to best use QRZ lookup and Log
>>> ----- Original Message -----
> From: "Mel" <[email protected]>
> To: <[email protected]>
> Sent: 07 September, 2003 7:47 AM
> Subject: RE: [Logic] How to best use QRZ lookup and Log
>>> > There is an issue with doing it this way which I plan to discuss 
> > with Dennis... If you hit F6, it undoes any changes you have made to

> > name/QTH/Comment... It shouldn't do this in my opinion...
>> Mel,
>> Don't know what build of LOGic 6 you are using, but my version 
> (6.0.162) doesn't behave that way. It updates only the date/time 
> stamp. I've tried altering all kinds of things from the 
> pre-filled-by-QRZ fields, and they all stay put except date/time when 
> I hit F6.
>> I wonder if this is a bug fix that you don't have, or if it is some 
> kind of setup option that we have set differently?
>> Bill / W5WVO
>> >
> > >That's the time I use for QSLing.
> >
> >
> > -----Original Message-----
> > From: [email protected] 
> > [mailto:[email protected]]
> > On Behalf Of Frank Ayers
> > Sent: September 6, 2003 19:49
> > To: [email protected]
> > Subject: Re: [Logic] How to best use QRZ lookup and Log
> >
> >
> > Hi
> > I use LOGic 5 and I'm not sure which one you're using, but I set the

> > log to have "automatically log time off". I can type in a call and 
> > get
>> > all the lookup stuff, but it logs the time off when I hit enter. 
> > That's the time I use for QSLing.
> >
> > Frank
> > W2FCA
> >
> > > In the case of 2), let's say there's a pile-up on him, and working

> > > him
> > takes
> > > some time. After about twenty minutes of trying, I get through and

> > > score
> > the
> > > QSO. But the time stamp in my log is twenty minutes ago. If I 
> > > remember
> >
> > > in
> > the
> > > heat of the action, I go into the log and correct the time field, 
> > > but
> > sometimes
> > > I forget. Bad news for QSLing!
> > >
> >
> > _______________________________________________
> > LOGic mailing list
> > [email protected] http://mailman.qth.net/mailman/listinfo/logic
> >
> > _______________________________________________
> > LOGic mailing list
> > [email protected] http://mailman.qth.net/mailman/listinfo/logic
> >
>> _______________________________________________
> LOGic mailing list
> [email protected] http://mailman.qth.net/mailman/listinfo/logic
>> _______________________________________________
> LOGic mailing list
> [email protected] http://mailman.qth.net/mailman/listinfo/logic
>
_______________________________________________
LOGic mailing list
[email protected] http://mailman.qth.net/mailman/listinfo/logic