LS,

My monitor (1920x1080), displays under Windows 10, WSJTX on the left side and the WSJTX-waterfall at the underside of the screen.
DXkeeper is then positioned in the remaining space on the right upper side.

With version "DXKeeper 1640" the program takes the total vertical dimension of the screen height at the right site, even I did correct the height within the remaining space before using it the last time.

Using the earlier version  "DXKeeper 1638" again,  the program height of DXKeeper  is always correct within the selected space!

So, my question is: Is there  a bug involved in version 1640??? or is this a Window 10 problem???

Who can and will tel me??

73 de Wim, pa0wjg





--
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
https://www.avast.com/antivirus

+ AA6YQ comments below

This time i must have lost orientation!

The SC version i use at this moment is 8.9.4.

I have seen no updates. No version to assess.

+ I sent you an email message, Eddy.

       73,

             Dave, AA6YQ

Hello Dave,

This time i must have lost orientation!

The SC version i use at this moment is 8.9.4.

I have seen no updates. No version to assess.

What did i miss?

Thanks

Eddy ON5JK

Op 11/01/2022 om 0:20 schreef Dave AA6YQ:

# more AA6YQ comments below

I already have the user-defined item 0 set to Pota and its style to Alphanumeric, so all good there. So each time I import a pota adif I will need to chance the rum log userfield 1 to the Dxkeeper user-defined item- 0

+ Correct. DXKeeper could be extended to enable the user to specify an ADIF tag for each user-defined item so that importing that tag would route the information accordingly; this would eliminate the need for manually editing the ADIF file before importing. I've added this to DXKeeper's enhancement list.

# DXKeeper already provides this capability:

"Enabling a user-defined item's ADIF option enables that item to be both imported or exported using its Caption as the field name - in both ADIF and tab-delimited files."

https://www.dxlabsuite.com/dxkeeper/Help/Import.htm#User-defined%20Items

# Thus no further enhancement is necessary.

73,

Dave, AA6YQ

+ AA6YQ comments below

I operate my home station under a different callsign assigned by the FCC during some contests.  Should I create another log for my alternate callsign so I can separate those QSO's from my usual callsign?

+ Your QSOs made with either callsign count for the same awards. You can distinguish QSOs made with one callsign from those made with the other callsign by recording the correct Station Callsign item with each QSO; DXKeeper provides a "Default Station Callsign" setting that you can change when you switch callsigns.

If so, how do I do that? is there a better way to do this?

+ Yes: maintain all of your QSOs in the same log.

 

Or should I lump all QSO's together and use a note or something like a tag to identify my other QSO's? 

+ There is a QSO item specifically for that purpose: "Station Callsign"

 

Normally, I will create a file from N1MM and then import the file for the contest QSO's.

+ When you import an ADIF file, you can specify the "Station Callsign" to be recorded with each imported QSO on the Main window's "Import QSOs" tab.

+ See

https://www.dxlabsuite.com/dxlabwiki/MultipleLogFiles

+ You will also have to specify the correct "Callsign Certificate" when submitting logged QSOs to LoTW; see

https://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations

    73,

         Dave, AA6YQ

 

 

 

I operate my home station under a different callsign assigned by the FCC during some contests.  Should I create another log for my alternate callsign so I can separate those QSO's from my usual callsign? If so, how do I do that? is there a better way to do this? Or should I lump all QSO's together and use a note or something like a tag to identify my other QSO's?  Normally, I will create a file from N1MM and then import the file for the contest QSO's.

Greg
N9GB

Thank you Dave.....enjoy the snow!  Spent Christmas in Wellesley with my daughter and g-kids....was pretty nice...Happy New Year.
Mark  WC3W

+ AA6YQ comments below

Dave, you are absolutely correct!

Sorry to waste your time on this; I did look at JTAlert, but missed it - and the DXKeeper upgrade was purely coincidental.

+ It's never a waste of time to understand what's going on.

       73,

             Dave, AA6YQ

+ AA6YQ comments below

Recently SC started "Compacting Spot Database" when we prune manualy the Spot Database.

I have the "Prune hourly" box not checqued.

I have set "prune entries older than" to 0,05 (aprox 1 hour) . So i can prune whenever i want to, not automaticaly.

Now when pruning, often "Compacting Spot Database" starts. Thus loosing a lot of time before i can see Spots again.

Can't you please provide a "switch", so we can select "compacting or not" when pruning manualy?

The compacting Spot Database is very anoying during a contest or any other special Event. (Like the ON75... now)


+ I've sent you the next version of SpotCollector to assess. Please let me know how it goes...

73,

Dave, AA6YQ

I am not logging via DXKeeper's Capture window, I am logging via WSJT-X --> JTAlert.

 On the Defaults tab of DXKeeper's Configuration window, the "Antenna Path" selector is set to blank.

73 Parker W5ADD

Turn off the "Log bearing (heading) to ANT_AZ field" setting under the "Logging" section of the JTAlert Settings window.

Note: That setting has been part of JTAlert for many years and the default is for it to be off. So recent logging of the AZ data has to be a result of your enabling the setting.

de Laurie VK3AMA

Dave, you are absolutely correct!

Sorry to waste your time on this; I did look at JTAlert, but missed it - and the DXKeeper upgrade was purely coincidental.

73 Parker W5ADD

Note: According to the information on the DM4X QRZ.com page
the software has been changed to DX Spider.

Doing a little experimentation with this cluster this afternoon, it
is a "fire hose" - if you use it you *will* want to learn to filter
on the server:
<http://www.dxcluster.org/main/usermanual_en.html>
For example, a user might filter for only 6m/2m spots or other
"low activity" bands (from PSK Reporter) to supplement traditional
HF spots from his/her other cluster sources.

73,

... Joe, W4TV

+ AA6YQ comments below

I am not logging via DXKeeper's Capture window, I am logging via WSJT-X --> JTAlert.

+ That means JTAlert is the source of the Azimuth being recorded with each QSO it directs DXKeeper to log.

73,

Dave, AA6YQ

I am not logging via DXKeeper's Capture window, I am logging via WSJT-X --> JTAlert.

On the Defaults tab of DXKeeper's Configuration window, the "Antenna Path" selector is set to blank.

73 Parker W5ADD

This isn’t the forum for this.

That is exactly what I was looking for - thank you as always Dave

+ AA6YQ comments below

No, it is not enabled on the "Rotator Control" tab of DXView's Configuration window.

In fact, I worked more QSOs, after quitting each of the following in turn:

DXView
PropView
SpotCollector

which left only Commander, DXKeeper, and Launcher running, and the behavior persists.

+ Thanks. Are you logging QSOs via DXKeeper's Capture window, the "Log QSOs" tab of DXKeeper's Main window, WinWarbler, or another application?

+ On the Defaults tab of DXKeeper's Configuration window, to what is the "Antenna Path" selector set?

      73,

           Dave, AA6YQ

 

On 2022-01-10 2:41 PM, d_ziolkowski wrote:

I don't think eqsl printed cards are accepted either.

They are not.

In simple terms, in order to be valid (for ARRL awards), a computer
generated QSL requires an original signature or separately applied
"QSL Manager's stamp". Without the signature or stamp a computer
generated card is assumed to be e-mail/fax as there is no way to
authenticate it.

73,

... Joe, W4TV


On 2022-01-10 2:41 PM, d_ziolkowski wrote:

Scott-
anyone could create a fake card, if you were desperate enough. Certainly not ham spirit.
I have also received several of these emailed qsls. But nothing I needed a QSL for.
I don't think eqsl printed cards are accepted either.
Dan kc2sta

No, it is not enabled on the "Rotator Control" tab of DXView's Configuration window.

In fact, I worked more QSOs, after quitting each of the following in turn:

DXView
PropView
SpotCollector

which left only Commander, DXKeeper, and Launcher running, and the behavior persists.

73 Parker W5ADD