+ AA6YQ comments below

I reactivated DX atlas and DXView again, after a long time

used because I noticed this error.

Yes, but I have no changes.

+ I can't help you if you won't answer my questions and perform the tests I request.

      73,

               Dave, AA6YQ

When known during the contact that the other station uses only LOTW/eQSL and will NOT entertain cards, it seemed expedient to set QSL_SENT_VIA=E and QSL_SENT=N. No subsequent editing required after the contact is logged.

((((((((((
Hi Joe:
  LOTW and eQSL are promptly uploaded.   My emphasis is on eliminating later log viewing.  When known during the contact that the given station does NOT do QSL cards, the ability to then set QSL_SENT=N via the Capture panel would keep them out of the QSL Queue.
73 Neil W3ZQI


If all QSOs are routinely uploaded to LotW (even in real time) and a
QSO is not marked QSL_Sent='R', this situation is handled automatically.

LotW and cards are currently independent but if you wanted, perhaps
Dave could add another option to QSL Config -> General to preset
QSL_Sent='N' unless one checks "QSL Requested"

The only issue would be possibly sending a card to a "needed" entity
if the station did not respond to LotW in a timely manner. Even in
that case, routine address checking should flag those stations that
do not accept cards (either direct or via bureau).

73,

... Joe, W4TV

Aha. OK, as long as I know. And of course so does everyone else now.

73
Tony G4CJC

When known during the contact that the other station uses only LOTW/eQSL and will NOT entertain cards, it seemed expedient to set QSL_SENT_VIA=E and QSL_SENT=N. No subsequent editing required after the contact is logged.

If all QSOs are routinely uploaded to LotW (even in real time) and a
QSO is not marked QSL_Sent='R', this situation is handled automatically.

LotW and cards are currently independent but if you wanted, perhaps
Dave could add another option to QSL Config -> General to preset
QSL_Sent='N' unless one checks "QSL Requested"

The only issue would be possibly sending a card to a "needed" entity
if the station did not respond to LotW in a timely manner. Even in
that case, routine address checking should flag those stations that
do not accept cards (either direct or via bureau).

73,

... Joe, W4TV

On 2022-12-26 11:01 AM, Neil W3ZQI via groups.io wrote:

Joe: No promotion of any given confirmation method was intended. Rather,
simply to identify the other station's confirmation rules,
at time of contact (e.g. "bureau cards possible", "cards by Direct only"
or "LOTW/eQSL only (no cards whatsoever)".

If you're not talking about e-mail QSLs, your goal can be accomplished simply by putting LotW in the "QSL via" box. Bureau cards can be
handled by checking the existing bureau check box and direct cards can be handled by leaving the bureau check box unchecked.
Yes, it takes one more step in filling the QSL Queue ... filter the log page display for QSL_via = 'LotW' (or QSL_via <> 'LotW') before
doing add requested/add needed.
If all QSOs are routinely uploaded to LotW, the issue goes away entirely. Add requested/add needed will populate an outgoing
QSL queue for direct/bureau cards even if the QSO has already been uploaded to LotW.
73,  ... Joe, W4TV
:::::::::::::::::::::::::::::::::::
Hi Joe:
When known during the contact that the other station uses only LOTW/eQSL and will NOT entertain cards, it seemed expedient to set QSL_SENT_VIA=E and QSL_SENT=N.  No subsequent editing required after the contact is logged.  This is seen frequently by me.
73 Neil W3ZQI

Joe: No promotion of any given confirmation method was intended. Rather, simply to identify the other station's confirmation rules,
at time of contact (e.g. "bureau cards possible", "cards by Direct only" or "LOTW/eQSL only (no cards whatsoever)".

If you're not talking about e-mail QSLs, your goal can be accomplished simply by putting LotW in the "QSL via" box. Bureau cards can be
handled by checking the existing bureau check box and direct cards can be handled by leaving the bureau check box unchecked.

Yes, it takes one more step in filling the QSL Queue ... filter the log page display for QSL_via = 'LotW' (or QSL_via <> 'LotW') before
doing add requested/add needed.

If all QSOs are routinely uploaded to LotW, the issue goes away entirely. Add requested/add needed will populate an outgoing
QSL queue for direct/bureau cards even if the QSO has already been uploaded to LotW.

73,  ... Joe, W4TV

:::::::::::::::::::::::::::::::::::
Hi Joe:
  When known during the contact that the other station uses only LOTW/eQSL and will NOT entertain cards, it seemed expedient to set QSL_SENT_VIA=E and QSL_SENT=N.  No subsequent editing required after the contact is logged.  This is seen frequently by me.
73 Neil W3ZQI

I am using JT-Alert.

As designed ... SC has no connection with WSJTX when using JT Alert.
Double clicking in SC will set frequency via Commander but has no
way to change "mode" in WSJTX.

73,

... Joe, W4TV

On 2022-12-26 7:15 AM, Tony Dixon G4CJC wrote:

Thanks for the reply Dave.
As an example, if I'm on 28.180 MHz shown on the IC7600 and on WSJT-X also showing FT4 and then I double click on a spot collector station showing 20m FT8 then the IC7600 switches to 14.074 MHz as does WSJT-X but the mode in WSJT-X still stays at FT4.
I am using JT-Alert.
Cheers and all the best for the New Year.
Tony G4CJC

Joe: No promotion of any given confirmation method was intended. Rather, simply to identify the other station's confirmation rules,
at time of contact (e.g. "bureau cards possible", "cards by Direct
only" or "LOTW/eQSL only (no cards whatsoever)".

If you're not talking about e-mail QSLs, your goal can be accomplished
simply by putting LotW in the "QSL via" box. Bureau cards can be
handled by checking the existing bureau check box and direct cards
can be handled by leaving the bureau check box unchecked.

Yes, it takes one more step in filling the QSL Queue ... filter the
log page display for QSL_via = 'LotW' (or QSL_via <> 'LotW') before
doing add requested/add needed.

If all QSOs are routinely uploaded to LotW, the issue goes away
entirely. Add requested/add needed will populate an outgoing
QSL queue for direct/bureau cards even if the QSO has already been
uploaded to LotW.

73,

... Joe, W4TV


On 2022-12-26 9:26 AM, Neil W3ZQI via groups.io wrote:

Hi Dave and Joe:
Joe:  No promotion of any given confirmation method was intended.  Rather, simply to identify the other station's confirmation rules, at time of contact (e.g. "bureau cards possible", "cards by Direct only" or "LOTW/eQSL only (no cards whatsoever)".  This speeds up later QSL Queue operations.
Dave:  Your terminology is as requested, however, request is to display all three options on the Capture screen itself and then allow selection of only one of the three options.  If not possible then best to leave screen as is.
Many thanks and 73,
Neil W3ZQI
+ 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

Hi Dave and Joe:
  Joe:  No promotion of any given confirmation method was intended.  Rather, simply to identify the other station's confirmation rules, at time of contact (e.g. "bureau cards possible", "cards by Direct only" or "LOTW/eQSL only (no cards whatsoever)".  This speeds up later QSL Queue operations.

  Dave:  Your terminology is as requested, however, request is to display all three options on the Capture screen itself and then allow selection of only one of the three options.  If not possible then best to leave screen as is.

Many thanks and 73,
Neil W3ZQI

+ 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

Thanks for the reply Dave.
As an example, if I'm on 28.180 MHz shown on the IC7600 and on WSJT-X also showing FT4 and then I double click on a spot collector station showing 20m FT8 then the IC7600 switches to 14.074 MHz as does WSJT-X but the mode in WSJT-X still stays at FT4.
I am using JT-Alert.
Cheers and all the best for the New Year.
Tony G4CJC

Hello Dave! 

+ AA6YQ comments below

I don't use the spot collector because I don't need it.

I've always used DXkeeper and DXView only and it worked 

without any problems, not as described above.

 

+ When did you first notice this change in behavior?

+ Did you reboot Windows into "Safe Mode with Networking" and check the behavior, as I requested in my last response?

       73,

             Dave, AA6YQ
  
        
    

 

 

+ 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