[Dx4win] Incomming spots changing QSO window

[Duane A Calvin]

John,
        I'm in front of my computer now - go to Preferences, to the QSO
tab, and UNCHECK the "Callsign Update" entry.  See if that fixes your
problem.  I think that's the one, but I'm not sure.  On my setup, it is
checked, but the only time that the callsign follows the incoming spots
is if I have pressed F9, and the callsign field is empty (i.e., it's
waiting for me to type a call in).  I never leave it in this condition. 
I hit F9 just before I'm going to enter a call to log it.  At any rate,
hopefully this answers your question.

        73,  Duane


On Fri, 20 Jan 2006 06:51:02 +1300 "John Shaw" <jnshaw at internet.co.nz>
writes:
> Well Duane if when you are in front of your computer you figure it 
> out I
> would appreciate the answer to this.
> 
> I can't see the logic behind this.  It basically gives control of my 
> log
> to the others sending packet spots.
> 
> Arhh!  I feel another rant coming on.
> 
> 73 John ZL1BYZ.
> 
> -----Original Message-----
> From: Duane A Calvin [mailto:ac5aa at juno.com] 
> Sent: Friday, 20 January 2006 5:55 a.m.
> To: jnshaw at internet.co.nz
> Subject: Re: [Dx4win] Incomming spots changing QSO window
> 
> John,
>         I'm not in front of my station computer at the moment, but 
> I
> believe there is a setting in the Preferences that will stop this
> behavior.  I seem to recall when it was added due to some folks 
> thinking
> it would be a good thing to have, but whatever my settings are, 
> they
> don't do this.
> 
>         73,  Duane
> 
> 
>         
> On Thu, 19 Jan 2006 16:21:36 +1300 "John Shaw" 
> <jnshaw at internet.co.nz>
> writes:
> > I have asked this before but no answers other than one other who 
> > agreed
> > he didn't like the way this works either.
> > 
> > Is there a way to stop incoming packet spots from changing the 
> band 
> > and
> > mode in the QSO window.
> > 
> > This is a real pain, I don't have rig control so I don't know it 
> > may
> > work better with that but reading Dennis's post maybe not.
> > 
> > DX4WIN didn't used to do this ver 5.07 but when I upgraded to 7.01 
> 
> > it
> > now does. I don't know exactly when the change happened.
> > 
> > The problem is that you can be working away say 40m CW and end up
> > logging the qso as 20m PSK31 or something unless you remain for 
> > ever
> > vigilant.  I want the log to follow what I am doing not someone on 
> 
> > the
> > other side of the world.
> > 
> > The only work around I have found so far other than turning the 
> > spots
> > off and clearing all spots from the spot window is to type 
> > something
> > quickly into the callsign box then hitting home so that when you 
> > start
> > typing a real call you can delete the bogus character ahead of 
> the
> > curser.  Sometimes the spot beats you, sometimes I forget to do 
> > this.
> > Its not a very good solution and although I don't think I have 
> been
> > caught out it is very likely to cause errors in the log.
> > 
> > I have been using DX4WIN for over 5 years now and think it is a 
> > fine
> > program and continue to support it.  I like the implementation of
> > support for LoTW and MTTY in the new version but in my opinion the 
> 
> > above
> > problem is a serious blunder in the operation of DX4WIN.
> > 
> > I have entered it as a bug in the bug reports but never got an
> > acknowledgement so I don't know if it has been taken on board or 
> > not.
> > 
> > 73 John ZL1BYZ.
> > 
> > 
> > _______________________________________________
> > Dx4win mailing list
> > Dx4win at mailman.qth.net
> > http://mailman.qth.net/mailman/listinfo/dx4win
> > 
> > 
> 
> 
> Duane Calvin, AC5AA
> Austin, Texas
> 
> 
> 
> _______________________________________________
> Dx4win mailing list
> Dx4win at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win
> 
> 


Duane Calvin, AC5AA
Austin, Texas