[LOGic] Spot Log sends wrong info to Log?

[Jeff Griffin]

 Try changing the interval you have set to for a spot update to a larger 
number of minutes. This is set in the DXSCAPE window for example.

73 Jeff kb2m

----- Original Message ----- 
From: "Rich Kelly" <richpdc at centurytel.net>
To: "'LOGic is open to all radio amateurs for discussion of LOGic 
loggingprogram'" <logic at mailman.qth.net>
Sent: Sunday, February 19, 2006 8:55 PM
Subject: RE: [LOGic] Spot Log sends wrong info to Log?


>I have seen this sort of situation happen to me when the spots are coming 
>in
> at about the same time as I transfer the info from the spot log to the 
> log.
> Maybe this is a possibility for you too?? It seems that the info from the
> telnet or terminal window is in the "buffer" and not yet transferred to 
> the
> spotlog when I click on the spotlog to transfer that info.
>
> I'm not sure if anything can be done about it or if this is actually what 
> is
> happening to you, but it is something to consider.
>
> Rich Kelly
> KB9RNO
>
> -----Original Message-----
> From: logic-bounces at mailman.qth.net [mailto:logic-bounces at mailman.qth.net]
> On Behalf Of KS4S Nyles
> Sent: Sunday, February 19, 2006 7:07 PM
> To: logic at mailman.qth.net
> Subject: [LOGic] Spot Log sends wrong info to Log?
>
> Does anyone know what the reason is for Logic sending the wrong info to 
> the
> log when double clicking on the spot log?
>
> About 30% of the time, I can click on a Call in the spot log, and the 
> wrong
> call entirely ( and the associated info shown in the spot log) shows up in
> the log form.  It does not matter if it general logging or a contest form.
>
> The problem is intermittent, and after a couple of tries, hitting esc to 
> not
> enter the data into the log, then clicking again on the spot log it will
> finally go. Sometimes it works fine.
>
> There is no radio associated with the program to automatically set the 
> VFO,
> and the box for that option in the spot log form is not checked to do 
> that.
>
> It makes it frustrating to use, having to double check it as you go.  It 
> is
> impossible to use for even slow "search and pounce" entries on a casual
> contest when it behaves like this.
>
> Thanks for any suggestions,
>
> Nyles
> KS4S