开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Re: DXKeeper pbm when logging.

 

+ AA6YQ comments below

I just had it again by clicking on 3B9DJ's spot on 7.165. The pbm is also by clicking on spot.

No log window flashing.

+ Thanks, Phil. So that I can see what's going on, please do the following:

1. In DXKeeper, close the Awards panel on the Main window's "Log QSOs" tab

2. On DXKeeper's Configuration window's General tab, check the "Log debugging info" box

3. Terminate DXKeeper

4. Start DXKeeper, and wait for it to fully initialize

5. On SpotCollector's Main window, click (or double-click)? on 3B9DJ's Spot Database Entry on 7.165.
?
6. On DXKeeper's Configuration window's General tab, uncheck the "Log debugging info" box
?
7, Attach the Errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

? ? ? 73,

? ? ? ? ? ?Dave, AA6YQ
?


Re: DXKeeper pbm when logging.

 

开云体育

Dave


Tnx for quick answer as usual.


I just had it again by clicking on 3B9DJ's spot on 7.165. The pbm is also by clicking on spot.

No log window flashing.

Just the?window "Award" who appears.

It's difficult to explain, so I made a short video.

Sorry for the background noise, my Wife is watching tv. ;-)


https://youtu.be/1MOVOFnmnlA


73

Phil

envoyé : 4 avril 2025 à 18:31
de : Dave AA6YQ <aa6yq@...>
à : [email protected]
objet : Re: [DXLab] DXKeeper pbm when logging.


+ AA6YQ comments below

On DXKeeper, I just noticed since 2 days the following pbm with some QSO. Not all QSO.

When I log a new QSO, the "award" checkbox is automatically checked.

?

I'm used to work with DXKeeper without active checkbox.

When the "award" checkbox is automatically checked when logging the QSO, the size of the DXKeeper is modified and I have after to resize it.

+ When the Award panel becomes visible on the Main window's "Log QSOs" tab, are any of its labels flashing in blue or red font?

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ


Re: DXKeeper pbm when logging.

 

+ AA6YQ comments below

On DXKeeper, I just noticed since 2 days the following pbm with some QSO. Not all QSO.

When I log a new QSO, the "award" checkbox is automatically checked.

?

I'm used to work with DXKeeper without active checkbox.

When the "award" checkbox is automatically checked when logging the QSO, the size of the DXKeeper is modified and I have after to resize it.

+ When the Award panel becomes visible on the Main window's "Log QSOs" tab, are any of its labels flashing in blue or red font?

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ


Re: Special Callsign versus Leaderboard Entry Font Color

 

+ AA6YQ comments below
Many Clubs provide for awards for working members on various bands throughout a single year.? ?FOC, for example, has an award for working each member once per year on each band.? ??
?
The Leaderboard function provides a perfect mechanism for tracking progress on working club members on each band by identifying a spot with a specific color when it is unworked on a particular band for the defined time period (set for the current year).? ?
?
However, if you have worked that member during the year on that particular band, the Font Color reverts to the Unneeded DX font color.? ? Technically, that's correct.? But that results in the spot for the Club member disappears into the same font color as the rest of the spots, making it more difficult to identify club members (which was the goal of putting their callsign into Special Call signs in the first place).? ?
?
It would be nice if any call listed in Special Callsigns retained a different color or if Leaderboard Worked had a different color than DX Unneeded.
+ DXLab's automation for identifying active club members is described here:



+ For the reason you describe above, use of the Leaderboard tag for this purpose is not recommended unless the competition is more important to you than identifying active club members after you've already worked them. Implementing more complex automation to support one specific club is not justifiable.

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ



DXKeeper pbm when logging.

 

开云体育

Hello,

On DXKeeper, I just noticed since 2 days the following pbm with some QSO. Not all QSO.

When I log a new QSO, the "award" checkbox is automatically checked.


I'm used to work with DXKeeper without active checkbox.

When the "award" checkbox is automatically checked when logging the QSO, the size of the DXKeeper is modified and I have after to resize it.

Any idea please ?

Many thanks.

Best 73 de F5PHW Phil


Special Callsign versus Leaderboard Entry Font Color

 

Many Clubs provide for awards for working members on various bands throughout a single year.? ?FOC, for example, has an award for working each member once per year on each band.? ??
?
The Leaderboard function provides a perfect mechanism for tracking progress on working club members on each band by identifying a spot with a specific color when it is unworked on a particular band for the defined time period (set for the current year).? ?
?
However, if you have worked that member during the year on that particular band, the Font Color reverts to the Unneeded DX font color.? ? Technically, that's correct.? But that results in the spot for the Club member disappears into the same font color as the rest of the spots, making it more difficult to identify club members (which was the goal of putting their callsign into Special Call signs in the first place).? ?
?
It would be nice if any call listed in Special Callsigns retained a different color or if Leaderboard Worked had a different color than DX Unneeded.
?
Don
WB6BEE
?
?
?
?
?


Re: Primary database

 

+ AA6YQ comments below
Please resend instructions for replacing Primary database because of corruption. I would like to try again, Dave.

+ See

/g/DXLab/message/228533

? ? ?73,

? ? ? ? ? ?Dave, AA6YQ


Primary database

 

Please resend instructions for replacing Primary database because of corruption. I would like to try again, Dave.
?
Thank you,
?
Gerald, WA9GON
?


Re: Changing QSO-Sent to N

 

# more AA6YQ comments below

+ Presumably you followed step 1 in



+ and thus can quickly recover.

Of course not

# Mistake 1: always direct DXKeeper to backup your log before initiating an action in the "Modify QSOs" panel.

, BUT I had narrowed the log so that only the QSOs within a time period were shown and then told it to modify QSL_Sent to N. Then it asked if I wanted to Recompute, why?

# Because changing a QSO's "QSL Sent" field can alter its award progress.

No clue, but I said yes.

# Mistake 2: never initiate a function that you don't understand.

Then I got a multipage document of things it changed. When I sent the statement below I thought the Recompute had changed a bunch of Y to N, but that wasn’t the case. It made a BUNCH of changes to I suspect hundreds of QSOs and probably because what it changed corrected stuff that was somehow wrong.

# Yes, as described here:



The biggest thing I think this tells me is maybe I need to do recomputes more often, although I thought I was doing it whenever you made changes to DXKeeper and asked us to recompute.

# That's not correct. When you make changes that might alter your award status for the DXCC, IOTA, Marathon, VUCC, WAS, WAZ, or WPX awards, DXKeeper automatically updates Realtime Award Tracking for those awards without any action on your part (unless you have the "automatically recompute realtime award tracking" option disabled). DXKeeper does this by scanning only the QSOs associated with the change. For example, if you change the mode of a QSO with Iceland, DXKeeper will scan all QSOs with Iceland to update your DXCC award progress with that country, and (if you're pursuing WAZ) scan all QSOs with stations in Zone 40 to update your WAZ award progress with that zone. This "selective recomputation" automatically maintains accurate realtime award tracking for the above awards. "Selective recomputation" does not perform all of the checking, correcting, and reporting provided by the manually invoked Recompute function:



# As with many power tools, careless use of DXKeeper's "Modify QSOs" function can cause significant damage. I've warned you about this several times over the years that you've been using DXLab.

73,

Dave, AA6YQ


Re: AT&T ending email to text on June18

 

+ AA6YQ comments below

I use the method of sending email to my phone.number@.... (txt.att.net) The delay time to receive these is highly variable and up to 24hrs late.

Not sure if that answers your question.

Email to my Gmail address arrives via ATT if I'm not on WIFI and seems to be delivered promptly. And delivery by WIFI is prompt as well.

+ Sounds like you're a good candidate to try Pushover's 30-day free trial. See step 3 in



73,

Dave, AA6YQ


Re: Changing QSO-Sent to N

 

开云体育

Of course not, BUT I had narrowed the log so that only the QSOs within a time period were shown and then told it to modify QSL_Sent to N.? Then it asked if I wanted to Recompute, why? No clue, but I said yes.? Then I got a multipage document of things it changed.? When I sent the statement below I thought the Recompute had changed a bunch of Y to N, but that wasn’t the case.? It made a BUNCH of changes to I suspect hundreds of QSOs and probably because what it changed corrected stuff that was somehow wrong.? The biggest thing I think this tells me is maybe I need to do recomputes more often, although I thought I was doing it whenever you made changes to DXKeeper and asked us to recompute.

?

73, Bob KB4CL

?

From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ
Sent: Wednesday, April 2, 2025 4:43 PM
To: [email protected]
Subject: Re: [DXLab] Changing QSO-Sent to N

?

+ AA6YQ comments below

Oh Well I just totally screwed that log up.

+ Presumably you followed step 1 in



+ and thus can quickly recover.

? ? ? ?73,

? ? ? ? ? ? ? Dave, AA6YQ


Re: Changing QSO-Sent to N

 

+ AA6YQ comments below
Oh Well I just totally screwed that log up.
+ Presumably you followed step 1 in



+ and thus can quickly recover.

? ? ? ?73,

? ? ? ? ? ? ? Dave, AA6YQ


Re: Changing QSO-Sent to N

 

开云体育

Oh Well I just totally screwed that log up.

?

From: [email protected] <[email protected]> On Behalf Of Bob Main via groups.io
Sent: Wednesday, April 2, 2025 4:21 PM
To: DXLabs <[email protected]>
Subject: [DXLab] Changing QSO-Sent to N

?

Joe, I figured it out.? I was trying the create a filter, but Dave had already included it on the Advanced page.? I’m slow, but finally see it, most of the time.

?

73, Bob KB4CL


Changing QSO-Sent to N

 

开云体育

Joe, I figured it out.? I was trying the create a filter, but Dave had already included it on the Advanced page.? I’m slow, but finally see it, most of the time.

?

73, Bob KB4CL


Re: AT&T ending email to text on June18

 

+ AA6YQ comments below
I had similar unreliable email to sms service from Tmobile, and then Gmail. I found an Android app called Pushover. It costed like, $2.99 for lifetime use. I got an address to send my emails, and it sends me an SMS. It is nearly instantaneous and works very well.
+ Excellent! I've added Pushover as an option in step 3 of



? ? ? ? 73,

? ? ? ? ? ? ? Dave, AA6YQ


Re: Change QSL Sent to "N"

 

Well the fact that I had 2024 in the QSO_End doesn't help. Sorry about that.

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Bob Main via groups.io
Sent: Wednesday, April 2, 2025 2:43 PM
To: [email protected]
Subject: Re: [DXLab] Change QSL Sent to "N"

I tried the statement you have below and it didn't like it, so I changed it to: QSO_Begin #2025-04-02 1300# AND QSO_End #2024-04-02 1400# It didn't like that either. I'll do some digging later and see if I can figure out what's wrong. I'm sure it is something simple.

73, Bob KB4CL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV
Sent: Wednesday, April 2, 2025 11:46 AM
To: [email protected]
Subject: Re: [DXLab] Change QSL Sent to "N"



On 2025-04-02 10:49 AM, Bob Main via groups.io wrote:
Thanks Joe, no not using contest mode. It is the CWT contests that
last an hour four times on Wednesdays. For example, this morning from
1300Z to 1400Z.
QSO_Begin between #2025-04-02 13:00# and #2025-04-02 14:00# should do the job for the first hour this morning.

That becomes
QSO_Begin between #2025-04-02 19:00# and #2025-04-02 20:00# for this afternoon's run, etc.

Given the amount of changing (four times a week) and short duration, it would probably be just as easy to use the UTC filter in DXK Advanced Sorts, Filters & Modifiers. Select the After radio button, enter the same data as in the two examples above, and click "Filter"
at the right end of the panel.

You will be in the Advanced Sorts, Filters and Modifiers window to change QSL_Sent to 'N' anyway.

73,

... Joe, W4TV


On 2025-04-02 10:49 AM, Bob Main via groups.io wrote:
Thanks Joe, no not using contest mode. It is the CWT contests that last an hour four times on Wednesdays. For example, this morning from 1300Z to 1400Z. There aren't that many, but if I can filter them out then I can change it. Then in the future I just modify the filter to fit the date and time frame.

73, Bob KB4CL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV
Sent: Wednesday, April 2, 2025 10:44 AM
To: [email protected]
Subject: Re: [DXLab] Change QSL Sent to "N"


If you were using Contest mode, you could filter on CONTEST_ID.

If you were not using contest mode, you would probably need to use a
date filter QSO_Begin between #2025-01-01 16:00# and
#2025-01-02 24:00# (use the appropriate date and times).

For a date filter you can also use the UTC Filter in Advanced Sorts,
Filters & Modifiers

73,

... Joe, W4TV

On 2025-04-02 10:33 AM, Bob Main via groups.io wrote:
If I work a number of stations during a contest, but I don't plan to
mail out QSL cards to everybody I worked and I want to change QSL
Sent to "N" in one move how do I do it? I know that I go into the
DXKeeper Advanced Sorts, Filters & Modifiers. Then create a Filter
to isolate them. Finally, under "Modify QSOs in Log Play Display I
set QSL_Sent to "N". The question is what would the filter look like?



73, Bob KB4CL


Re: Change QSL Sent to "N"

 

I tried the statement you have below and it didn't like it, so I changed it to: QSO_Begin #2025-04-02 1300# AND QSO_End #2024-04-02 1400# It didn't like that either. I'll do some digging later and see if I can figure out what's wrong. I'm sure it is something simple.

73, Bob KB4CL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV
Sent: Wednesday, April 2, 2025 11:46 AM
To: [email protected]
Subject: Re: [DXLab] Change QSL Sent to "N"



On 2025-04-02 10:49 AM, Bob Main via groups.io wrote:
Thanks Joe, no not using contest mode. It is the CWT contests that
last an hour four times on Wednesdays. For example, this morning from
1300Z to 1400Z.
QSO_Begin between #2025-04-02 13:00# and #2025-04-02 14:00# should do the job for the first hour this morning.

That becomes
QSO_Begin between #2025-04-02 19:00# and #2025-04-02 20:00# for this afternoon's run, etc.

Given the amount of changing (four times a week) and short duration, it would probably be just as easy to use the UTC filter in DXK Advanced Sorts, Filters & Modifiers. Select the After radio button, enter the same data as in the two examples above, and click "Filter"
at the right end of the panel.

You will be in the Advanced Sorts, Filters and Modifiers window to change QSL_Sent to 'N' anyway.

73,

... Joe, W4TV


On 2025-04-02 10:49 AM, Bob Main via groups.io wrote:
Thanks Joe, no not using contest mode. It is the CWT contests that last an hour four times on Wednesdays. For example, this morning from 1300Z to 1400Z. There aren't that many, but if I can filter them out then I can change it. Then in the future I just modify the filter to fit the date and time frame.

73, Bob KB4CL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV
Sent: Wednesday, April 2, 2025 10:44 AM
To: [email protected]
Subject: Re: [DXLab] Change QSL Sent to "N"


If you were using Contest mode, you could filter on CONTEST_ID.

If you were not using contest mode, you would probably need to use a
date filter QSO_Begin between #2025-01-01 16:00# and
#2025-01-02 24:00# (use the appropriate date and times).

For a date filter you can also use the UTC Filter in Advanced Sorts,
Filters & Modifiers

73,

... Joe, W4TV

On 2025-04-02 10:33 AM, Bob Main via groups.io wrote:
If I work a number of stations during a contest, but I don't plan to
mail out QSL cards to everybody I worked and I want to change QSL
Sent to "N" in one move how do I do it? I know that I go into the
DXKeeper Advanced Sorts, Filters & Modifiers. Then create a Filter
to isolate them. Finally, under "Modify QSOs in Log Play Display I
set QSL_Sent to "N". The question is what would the filter look like?



73, Bob KB4CL


Re: DX Marathon Year

 

+ AA6YQ comments below
If I depress Alt, what does that do?
"To verify the entry for each CQ country by performing a??and to verify the entry for each CQ zone by performing a??(and if that fails, a??lookup), depress the?ALT?key while clicking the?Progress?button.?Depressing the?SHIFT?key while clicking the?Progress?button will verify only entries not confirmed via QSL card,??,??member of?,?, or??for each CQ country and each CQ zone"



? ? ?73,

? ? ? ? ? ?Dave, AA6YQ


Re: DX Marathon Year

 

If I depress Alt, what does that do?

Thanks
73
Kent
N6WT


On Tue, Apr 1, 2025 at 6:57?AM Dave AA6YQ via <aa6yq=[email protected]> wrote:
+ AA6YQ comments below
Disregard. I see it is Ctrl. However, the help popup says at the end "Depress Alt to" and that is it.
+ Windows imposes a limit on the length of explanatory popups. I'll see if I can compress the explanation...

? ? ? ? ?73,

? ? ? ? ? ? ? ?Dave, AA6YQ


Re: Change QSL Sent to "N"

 

Thanks Joe, I'll give it a try.

73, Bob KB4CL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV
Sent: Wednesday, April 2, 2025 11:46 AM
To: [email protected]
Subject: Re: [DXLab] Change QSL Sent to "N"



On 2025-04-02 10:49 AM, Bob Main via groups.io wrote:
Thanks Joe, no not using contest mode. It is the CWT contests that
last an hour four times on Wednesdays. For example, this morning from
1300Z to 1400Z.
QSO_Begin between #2025-04-02 13:00# and #2025-04-02 14:00# should do the job for the first hour this morning.

That becomes
QSO_Begin between #2025-04-02 19:00# and #2025-04-02 20:00# for this afternoon's run, etc.

Given the amount of changing (four times a week) and short duration, it would probably be just as easy to use the UTC filter in DXK Advanced Sorts, Filters & Modifiers. Select the After radio button, enter the same data as in the two examples above, and click "Filter"
at the right end of the panel.

You will be in the Advanced Sorts, Filters and Modifiers window to change QSL_Sent to 'N' anyway.

73,

... Joe, W4TV


On 2025-04-02 10:49 AM, Bob Main via groups.io wrote:
Thanks Joe, no not using contest mode. It is the CWT contests that last an hour four times on Wednesdays. For example, this morning from 1300Z to 1400Z. There aren't that many, but if I can filter them out then I can change it. Then in the future I just modify the filter to fit the date and time frame.

73, Bob KB4CL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV
Sent: Wednesday, April 2, 2025 10:44 AM
To: [email protected]
Subject: Re: [DXLab] Change QSL Sent to "N"


If you were using Contest mode, you could filter on CONTEST_ID.

If you were not using contest mode, you would probably need to use a
date filter QSO_Begin between #2025-01-01 16:00# and
#2025-01-02 24:00# (use the appropriate date and times).

For a date filter you can also use the UTC Filter in Advanced Sorts,
Filters & Modifiers

73,

... Joe, W4TV

On 2025-04-02 10:33 AM, Bob Main via groups.io wrote:
If I work a number of stations during a contest, but I don't plan to
mail out QSL cards to everybody I worked and I want to change QSL
Sent to "N" in one move how do I do it? I know that I go into the
DXKeeper Advanced Sorts, Filters & Modifiers. Then create a Filter
to isolate them. Finally, under "Modify QSOs in Log Play Display I
set QSL_Sent to "N". The question is what would the filter look like?



73, Bob KB4CL