[Dx4win] Incomming spots changing QSO window

[Tony Lord]

Hi,

As John says this is a known bug and should be fixed. I too am concerned
about antenna change when transmitting, however as long as QSO window is
filled out with, say current callsign info, then there is no problem. If
I call CQ with a blank QSO window then it will change in accordance with
spot info. So whilst a pain, as long as QSO window is filed out with
callsign I have no problems.

Hopefully bug will be sorted on next release.

73's de Tony G8DQZ


-----Original Message-----
From: dx4win-bounces at mailman.qth.net
[mailto:dx4win-bounces at mailman.qth.net] On Behalf Of Larry Gauthier
(K8UT)
Sent: 20 January 2006 11:43
To: John Shaw; dx4win at mailman.qth.net
Subject: Re: [Dx4win] Incomming spots changing QSO window

John,

This is a known bug ("feature") about which Paul is aware and has
committed 
to correcting in the next release.

For me, the biggest problem is not that my log might have the wrong 
band/mode. My panic occurs when transmitting and watching my remote
antenna 
switch automagically switched from a 20 meter quad loop with perfect SWR
to 
an 80 meter vertical with infinite SWR! ;-( my amplifier does not like 
that! )

Hopefully this will be corrected when we see the next rev...

-larry
K8UT
----- Original Message ----- 
From: "John Shaw" <jnshaw at internet.co.nz>
To: <dx4win at mailman.qth.net>
Sent: Wednesday, January 18, 2006 22:21
Subject: [Dx4win] Incomming spots changing QSO window


>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 
_______________________________________________
Dx4win mailing list
Dx4win at mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win