[Dx4win] Incomming spots changing QSO window
Hi Duane, If my rig was capable of rig control I would certainly be using it, some day I will get a more modern one. It seems that there may be some concerns around this issue with rig control too, but I can't comment. See some of the other posts. I concur that in the past I had good experience to requests, although it was a long time ago and only once or twice. This time I went through the bug report route with no response and I have sent an email to support, no response. Maybe I need to be more direct to the people you have mentioned. Note also that they do have a known problem list on their site and it says there are no problems at this time. Perhaps if this was updated would save a lot of aggravation. 73 John ZL1BYZ -Original Message- From: Duane A Calvin [mailto:[EMAIL PROTECTED] Sent: Saturday, 21 January 2006 4:20 a.m. To: [EMAIL PROTECTED] Subject: Re: [Dx4win] Incomming spots changing QSO window Ah, I see - I do have rig control lashed up and once I made the change it no longer changed with incoming spots. You've probably tried this, but just in case - have you written to Steve or Paul on this one? Steve is good at tracking requests, and Paul, if you hit him when he's not busy (rare) is fairly responsive. 73 & GL, Duane On Fri, 20 Jan 2006 20:08:19 +1300 "John Shaw" <[EMAIL PROTECTED]> writes: > Hi Duane, > > Yes I had tried that before and almost thought it was it but no. It > is > not actually the callsign but the band and mode that is the > problem. > > Thank you for trying. Of course many are using rig control etc and > it > may well behave better with that. > > Yes it is after pressing F9 and the call field is empty. Gee you > have > to be quick I have had the spot band mode info jump in there > between > completing one QSO and starting another. That's when I put a bogus > letter in there so it is not empty but that is a bit clumsy too, > shouldn't really have to do that. > > 73 now de John ZL1BYZ. > > -Original Message- > From: Duane A Calvin [mailto:[EMAIL PROTECTED] > Sent: Friday, 20 January 2006 5:12 p.m. > To: [EMAIL PROTECTED] > Cc: dx4win@mailman.qth.net > Subject: Re: [Dx4win] Incomming spots changing QSO window > > 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" > <[EMAIL PROTECTED]> > 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:[EMAIL PROTECTED] > > Sent: Friday, 20 January 2006 5:55 a.m. > > To: [EMAIL PROTECTED] > > 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" > > <[EMAIL PROTECTED]> > > 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 Den
[Dx4win] Incomming spots changing QSO window
Hi Tony & I see Larry has said much the same.
Thank you for your replies and informing me that it is a known bug and
should be fixed in due course.
I am a patient person and can work around things as long as I know they
are being addressed. I see on the DX4WIN site there is a place for a
list of known problems, at present says there are no known problems at
this time. Duh!
Come on DX4WIN guys (if you are watching) you used to be really good
with supporting your software. That's why I bought your product and
keep updating it.
Larry, yes I can see your concern with loosing control of your
transmitter to the incoming spots. That does raise it to another level
of seriousness.
I see in the popup you get in the spot window there is the listen &
monitor options, it's not one of those causing you trouble is it Larry?
For me they are greyed out as I am not using rig control.
I also note that F8 doesn't function like it used to either.
So it looks like some tidying up to do in DX4WIN.
73 John ZL1BYZ.
-Original Message-
From: Tony Lord [mailto:[EMAIL PROTECTED]
Sent: Saturday, 21 January 2006 2:04 a.m.
To: 'Larry Gauthier (K8UT)'; 'John Shaw'; dx4win@mailman.qth.net
Subject: RE: [Dx4win] Incomming spots changing QSO window
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Larry Gauthier
(K8UT)
Sent: 20 January 2006 11:43
To: John Shaw; dx4win@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" <[EMAIL PROTECTED]>
To:
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@mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win
___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win
[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" <[EMAIL PROTECTED]>
To:
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@mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win
From [EMAIL PROTECTED] Fri Jan 20 08:04:04 2006
From: [EMAIL PROTECTED] (Tony Lord)
Date: Fri Jan 20 08:10:07 2006
Subject: [Dx4win] Incomming spots changing QSO window
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Larry Gauthier
(K8UT)
Sent: 20 January 2006 11:43
To: John Shaw; dx4win@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" <[EMAIL PROTECTED]>
To:
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 e
[Dx4win] Incomming spots changing QSO window
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" <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > Sent: Friday, 20 January 2006 5:55 a.m. > To: [EMAIL PROTECTED] > 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" > <[EMAIL PROTECTED]> > 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@mailman.qth.net > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > > Duane Calvin, AC5AA > Austin, Texas > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win > > Duane Calvin, AC5AA Austin, Texas From [EMAIL PROTECTED] Fri Jan 20 02:08:19 2006 From: [EMAIL PROTECTED] (John Shaw) Date: Fri Jan 20 02:13:45 2006 Subject: [Dx4win] Incomming spots changing QSO window In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Hi Duane, Yes I had tried that before and almost thought it was it but no. It is not actually the callsign but the band and mode that is the problem. Thank you for trying. Of course many are using rig control etc and it may well behave better with that. Yes it is after pressing F9 and the call field is empty.
[Dx4win] Incomming spots changing QSO window
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:[EMAIL PROTECTED] Sent: Friday, 20 January 2006 5:55 a.m. To: [EMAIL PROTECTED] 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" <[EMAIL PROTECTED]> 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@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win > > Duane Calvin, AC5AA Austin, Texas
[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.
