+ AA6YQ comments below

If I press "CLEAR" all entries are deleted, but if I press again on World or Plot a other station I see all entries again.

+ If you click the World button again, you will see plots of active stations that arrived after you clicked the Clear button.

+ The Clear button works correctly here, Christian. There hasn't been a new version of DXView since April, so any recent change cannot be attributable to DXView.

+ Please reboot Windows into "Safe Mode with Networking", and then start DXView and SpotCollector. Is there any change in the behavior you're reporting?

73,

Dave, AA6YQ

+ AA6YQ comments below

Please consider enhancing the "use bureau" area of the DXKeeper Capture screen.  This action would reflect a growing practice of "Electronic-only" confirmations by many stations.

 

Replace "use bureau" checkbox with pull-down selection or another mechanism to convey the following mutually exclusive selections:

- "use bureau": continue to populate QSL_SENT_VIA = 'B'

- "direct only": populate QSL_SENT_VIA = 'D'

- "Electronic only": populate QSL_SENT_VIA = 'E', populate QSL_SENT = 'N'

+ Let me see if I understand:

1. you're not proposing any change to the QSL_SENT_VIA field

2. you'd like a new selector in the "Capture window options' panel on the Configuration window's General tab, those selects among 3 mutually exclusive choices:

    a. display a "use buro" check box in the Capture window (current functionality, default setting for the new selector)

    b. display a "QSL direct" check box in the in the Capture window (if checked, QSO is logged with its QSL_SENT_Via item set to 'D')

    c. display a "QSL elect" check box in the Capture window (if checked, QSO is logged with its QSL_SENT_VIA item set to 'E' and its QSL_SENT item set to 'N')

Do I have it right?

      73,

           Dave, AA6YQ

 

 

On 2022-12-25 9:38 PM, Neil W3ZQI via groups.io wrote:

This action would reflect a growing practice of "Electronic-only" confirmations by many stations.

Electronic only (e-mail) QSLs have no use and should not be supported
by DXKeeper. Implementation of support for e-mail QSLs is a complete
and utter waste of developer cycles that could be better used for
*useful* features.

73,

... Joe, W4TV

On 2022-12-25 9:38 PM, Neil W3ZQI via groups.io wrote:

Hello Dave:
Please consider enhancing the "use bureau" area of the DXKeeper Capture screen.  This action would reflect a growing practice of "Electronic-only" confirmations by many stations.
Replace "use bureau" checkbox with pull-down selection or another mechanism to convey the following mutually exclusive selections:
- "use bureau": continue to populate QSL_SENT_VIA = 'B'
- "direct only": populate QSL_SENT_VIA = 'D'
- "Electronic only": populate QSL_SENT_VIA = 'E', populate QSL_SENT = 'N'
Thank you and 73,
Neil W3ZQI

Neil W3ZQI

+ AA6YQ comments below

After a few versions of DXView, the error has now reappeared.
When I click on the "Clear" button in DXView, the dot indicators are not immediately removed from the DXAtlas card, as is the case with the standard card.
What's the mistake? Thank you in advance for your reply and help.

+ You last reported that the "Clear button doesn't remove plotted spots from DX Atlas" in October 2019; the responsible defect was corrected in DXView version 4.5.7.

+ DXView was most recently updated to version 4.8.9 on April 5, 2022 - more than 8 months ago. I just checked, and the Main window's "Clear" button continues to removed plotted spots from DX Atlas when I test it here. If the behavior you're reporting began after you upgraded to DXView 4.8.9, it's the result of some other change on your system - not a change in DXView.

+ Is your anti-malware correctly configured to consider DXView and DX Atlas to be "safe"? Have you tried rebooting Windows?

73,

Dave, AA6YQ

+ AA6YQ comments below

For me using WSJT-X 2.5.4 a double click on a spot collector entry changes the WSJT-X band and frequency but not the mode. It's not something I've used much so maybe I'm doing some thing wrong

+ re "but not the mode", do you mean the mode in WSJT-X (e.g. FT4 or FT8), or the your transceiver's mode?

+ Are you using JT-Alert, or the direct connection between DXLab and WSJT-X?

       73,

             Dave, AA6YQ

For me using WSJT-X 2.5.4 a double click on a spot collector entry changes the WSJT-X band and frequency but not the mode. It's not something I've used much so maybe I'm doing some thing wrong.
73
Tony G4CJC

My 10 yo home brew computer has served me well.  It booted quickly (20 seconds, with a SSD) and it seemed fast. However, now that I run remote, it was beginning to max out CPU running the remote software (with pan adapter), WSJT-X, and the DXLab Suite. I was also annoyed with how long it took DXKeeper to open and close (over 60,000 Qs). Also I would eventually need to upgrade to Windows 11.

The computer was a decent spec AMD FX-8120, 8 core, @ 3.1GHz, 32 GB RAM, running Windows 10.

Comparing CPU performance benchmarks and looking at the cost of buying a new computer or upgrading the old one I chose to upgrade.  That meant a new motherboard (TPM needed for Win11), a new CPU, RAM, and a Windows 11 license (I didn't want to load 10 then upgrade to 11).   All in with a $79 AMD Ryzen 5 4500 CPU, I spent $420.

Can't believe the difference in performance with the new hardware.  Now it just takes a couple of seconds to open DXKeeper and runs my remote set up with ease.

So the moral of my story, your older may not be as fast as you think.

Thanks Dave - I'll give it a try when I get a chance - Merry Christmas!
--
John P.
WA2FZW

+ AA6YQ comments below

Command structure is the same for either "one off" messages in
Commander's Messages window or for user defined commends.

Hex commands/messages are a string of hex characters (two 0-F
characters per hex digit) or a string of ASCII characters
prefixed by a single apostrophe (').

+ Joe W4TV is correct. I have updated the documentation in

https://www.dxlabsuite.com/commander/Help/MonitoringMessages.htm

+ to make this explicit.

      73,

           Dave, AA6YQ

Command structure is the same for either "one off" messages in
Commander's Messages window or for user defined commends.

Hex commands/messages are a string of hex characters (two 0-F
characters per hex digit) or a string of ASCII characters
prefixed by a single apostrophe (').

73,

... Joe, W4TV

Thanks Joe but I'm not tying to use the user defined commands.
--
John P.
WA2FZW

See the Commander Help file (click the Help button or press F1)

Scroll down the first page to the User-Defined Controls section
Click on that topic and scroll down to the table heading
"Valid commands are enumerated in the following table:"

Hex commands are defined in the first row of that table ...

One does not use the decimal equivalent of the hex commands, one
uses the two digit hex command directly.

73,

... Joe, W4TV

Looking at the manual for how to send CAT commands to a radio using the 'Messages' window, I see no way to send a hexadecimal command; in particular to my Icom IC-9700. I see one can use '<n>' to send a number that would translate to an ASCII character (the manual example is '<13>' which translates to a carriage return. But the range of 'n' is limited to 0 to 127, which means one cannot send the decimal equivalent of the hexadecimal number 'FE' for example.

The 'Messages' window allows one to view the messages in hexadecimal. Can the program be modified to allow commands to be in hex or am I missing something?

--
John P.
WA2FZW

+ AA6YQ comments below

When I import an .adif file the select button is set to yes in the auxiliary tab.  That is great. 

+ That's appropriate if you're planning to modify each of the just-imported QSOs.

I've gotten in the habit of setting the select button to Y after a QSO is automatically logged (JTAlert in this case).

+ Why are you doing that?

DXKeeper uploads the QSO to Clublog and sets the Club button to Y.

When I change the Select button from N to Y, it changes the club button from Y to M.   I am not sure why that happens and perhaps I should not use Select in this case since it throws off my Club upload.

+ Changing the Select button from N to Y marks the QSO as "modified since last uploaded to Club Log" by setting the "Club Log" item to M. It means that the next time you initiate a Club Log upload, that QSO will be submitted again.

+ Unless there's a reason to set Select to Y after importing or logging a QSO, I suggest that you not do so.

        73,

            Dave, AA6YQ

When I import an .adif file the select button is set to yes in the auxiliary tab.  That is great. 
I've gotten in the habit of setting the select button to Y after a QSO is automatically logged (JTAlert in this case). DXKeeper uploads the QSO to Clublog and sets the Club button to Y.

When I change the Select button from N to Y, it changes the club button from Y to M.   I am not sure why that happens and perhaps I should not use Select in this case since it throws off my Club upload.
I am trying to unconfuse myself. 

Mike KC7V

+ AA6YQ comments below

I have looked in the help file but I can't find what I am looking for or even if it exists . Is there a setting to keep DX view focused on the capture window till the  QSO is entered? When I enter a call in Capture , Dx View will give me all the info on the call but when I turn my head to go back info, DX view has been populated with the info of the next spot that has come through Spot collector before I have completed the contact that is in Capture. 

+ In the second column of the General panel on the General tab of SpotCollector's Configuration window, uncheck the "Automatic DXView lookup" box.

        73,

               Dave, AA6YQ

Sounds like your rig and Commander are not communicating. What rig?
What interface?

73,

... Joe, W4TV