¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: DX Labs commander accessibility issues

 

On 16/04/2020 10:50, Dave AA6YQ wrote:
+ AA6YQ comments below

I have used NVDA for checking accessibility of the WSJT-X UI and find it easy to use. One thing I have noticed is that control labels rendered from rich-text strings are read as html strings including the metadata.
That may not be relevant in your case but perhaps using bold text or similar as an impact on screen readers. I note with NVDA the tab names in the DX Lab Suite applications do not get read, perhaps that is what is causing problems for Frank?

+ Microsoft's tab control renders the selected tab's label in bold font, and the non-selected tabs' labels in regular font.

73,

Dave, AA6YQ
Hi Dave,

perhaps adding a tool-tip or alternate text would cause something to be read by screen readers for navigating the various tabs. Having said that perhaps Frank's offer of a recording of what is causing him issues may be the best first step. IMHO visually impaired users are so used to navigating applications that do little to help them, that they often do not raise issues with software writers and just work around the problems. I know I am guilty of not doing enough for them.



--
73

Bill

G4WJS.


Re: DX Labs commander accessibility issues

 

+ AA6YQ comments below

I have used NVDA for checking accessibility of the WSJT-X UI and find it easy to use. One thing I have noticed is that control labels rendered from rich-text strings are read as html strings including the metadata.
That may not be relevant in your case but perhaps using bold text or similar as an impact on screen readers. I note with NVDA the tab names in the DX Lab Suite applications do not get read, perhaps that is what is causing problems for Frank?

+ Microsoft's tab control renders the selected tab's label in bold font, and the non-selected tabs' labels in regular font.

73,

Dave, AA6YQ


Re: DX Labs commander accessibility issues

 

On 16/04/2020 02:47, Dave AA6YQ wrote:
+ AA6YQ comments below

Hi Dave, thank you very much for the response. You can obtain a free license of JAWS, good until June 30 at:

Even the demo version of JAWS runs for 40 minutes at a time.

Also there is a free screen reader known as NVDA which can be downloaded at:

Look for the check box called "NV Access".

If you are interested in improving the accessibility I would definitely be willing to provide you with a full JAWS license.

+ You are the third ham to ask for JAWS support in the past 20 years. I will review the tab order in Commander's Configuration window, but DXLab applications are built with Microsoft tools that do not provide me with the ability to influence the JAWS-relevant behavior of controls.

73,

Dave, AA6YQ
Hi Dave,

I have used NVDA for checking accessibility of the WSJT-X UI and find it easy to use. One thing I have noticed is that control labels rendered from rich-text strings are read as html strings including the metadata. That may not be relevant in your case but perhaps using bold text or similar as an impact on screen readers. I note with NVDA the tab names in the DX Lab Suite applications do not get read, perhaps that is what is causing problems for Frank?



--
73

Bill

G4WJS.


Re: Pathfinder Map not loading

 

+ AA6YQ comments below

loaded qrz with Internet Explorer 11
and the map loaded.

closed pathfinder, reopened and map would not load.

+ Please reboot Windows, and then start Pathfinder. In the "Internet Explorer" panel on Pathfinder's Configuration window, what Version and Emulation are shown?

73,

Dave, AA6YQ


Re: Pathfinder Map not loading

 

loaded qrz with Internet Explorer 11
and the map loaded.

closed pathfinder, reopened and map would not load.
map load when using Crome.?


Re: "Sync LoTW QSLs" and DXCC Credits Granted

 

+ AA6YQ comments below

On Wed, Apr 15, 2020 at 09:14 PM, Stan Gammons wrote:

Bummer that the "Sync LoTW QSLs" can no longer be relied on :(

+ It can be relied on for its original purpose: to update your logged QSOs to reflect their confirmation via LoTW.

+ Note that invoking "Update LoTW Status" on a logged QSO to which DXCC credit has been granted will update that logged QSO to reflect the grant of DXCC credit.

? ? ? ?73,

? ? ? ? ? ? Dave, AA6YQ

?


Re: "Sync LoTW QSLs" and DXCC Credits Granted

 

¿ªÔÆÌåÓý

Oh.? Ok.? My bad.

Bummer that the "Sync LoTW QSLs" can no longer be relied on :(

Stay safe Dave.


73

Stan
KM4HQE






On 4/15/20 11:07 PM, Dave AA6YQ wrote:

+ AA6YQ comments below

On Wed, Apr 15, 2020 at 09:00 PM, Stan Gammons wrote:

So, are you saying we will need to link the credits manually after submitting them using DXKeeper's DXCC submission generator and the QSO's have been granted DXCC credit?

+ That's the opposite of what I posted, Stan.

+ If you use DXKeeper's DXCC Submission Generator and are informed that credit has been granted to each confirmed credit, than one mouse click will "promote" the status of your logged QSOs to "DXCC Credit Granted.

+ What you can't rely on is the "Sync LoTW QSLs" function to perform this update.?

? ? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ

?



Re: "Sync LoTW QSLs" and DXCC Credits Granted

 

+ AA6YQ comments below

On Wed, Apr 15, 2020 at 09:00 PM, Stan Gammons wrote:

So, are you saying we will need to link the credits manually after submitting them using DXKeeper's DXCC submission generator and the QSO's have been granted DXCC credit?

+ That's the opposite of what I posted, Stan.

+ If you use DXKeeper's DXCC Submission Generator and are informed that credit has been granted to each confirmed credit, than one mouse click will "promote" the status of your logged QSOs to "DXCC Credit Granted.

+ What you can't rely on is the "Sync LoTW QSLs" function to perform this update.?

? ? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ

?


Re: "Sync LoTW QSLs" and DXCC Credits Granted

 

So, are you saying we will need to link the credits manually after submitting them using DXKeeper's DXCC submission generator and the QSO's have been granted DXCC credit?


73

Stan
KM4HQE

On 4/15/20 10:34 PM, Dave AA6YQ wrote:
It was my understanding that the LoTW API invoked when you click DXKeeper's "Sync LoTW QSLs" button with the date YYYY-MM-DD shown
beneath this button would report

1. any new confirmations received date YYYY-MM-DD

2. any new grants of DXCC award credit made after date YYYY-MM-DD


In working through the issue that Pete N4ZR raised here

I was informed by LoTW staff that #2 is not correct. When you are informed that the LoTW-confirmed QSOs you submitted for award
credit have been granted that credit, you cannot simply invoke DXKeeper's "Sync LoTW QSLs" function to update your logged QSOs to
reflect the granting of that DXCC credit.

If you use DXKeeper's DXCC Submission Generator to select the QSOs you submitted for DXCC Award Credit, then your submitted QSOs can
be update to reflect their DXCC award credit by clicking the "DXCC Submission' window's "Verify Submission" button. This is steps 7
and 8 in the " Generating an LotW Submission" section of

<>


Note that you also have the option of having DXKeeper download all of your DXCC credits from the ARRL and use this information to
update the DXCC Credit status of all of your logged QSOs. This works smoothly for QSOs confirmed via LotW, but QSOs confirmed via
QSL cards may have slightly inaccurate DXCC credits as a result of data entry errors or shortcuts -- like specifying the correct
DXCC entity, band, and mode, but specifying an incorrect callsign or an incorrect date. Expect 25% of the DXCC credits generated
from QSL cards to require manual "linking" to your logged QSOs. Step-by-step instructions are here:

<.


While it's tempting to make a DXCC submission of QSOs confirmed via LoTW by letting LoTW pick the QSOs to submit, doing so is the
wrong choice for two reasons:

1. LoTW's selection of QSOs to submit is suboptimal; you may submit more confirmed QSOs than are necessary. For example, in need of
DXCC credit for P5 in both RTTY and on 160m (but not on 40m or Phone), LoTW might have you submit a 40m RTTY QSO and a 160m Phone
QSO when you have a confirmed 160m RTTY QSO.

2. You can't use DXKeeper's "Verify Submission" button to update your logged QSOs to reflect DXCC Credit granted with one gesture.

Thus you cannot rely on invoking the "Sync LoTW QSLs" function after being informed that the QSOs confirmed via LoTW that you
submitted for DXCC award credit have received that DXCC award credit to update your logged QSOs to reflect the granting of that DXCC
award credit.


73,

Dave, AA6YQ



"Sync LoTW QSLs" and DXCC Credits Granted

 

It was my understanding that the LoTW API invoked when you click DXKeeper's "Sync LoTW QSLs" button with the date YYYY-MM-DD shown
beneath this button would report

1. any new confirmations received date YYYY-MM-DD

2. any new grants of DXCC award credit made after date YYYY-MM-DD


In working through the issue that Pete N4ZR raised here

I was informed by LoTW staff that #2 is not correct. When you are informed that the LoTW-confirmed QSOs you submitted for award
credit have been granted that credit, you cannot simply invoke DXKeeper's "Sync LoTW QSLs" function to update your logged QSOs to
reflect the granting of that DXCC credit.

If you use DXKeeper's DXCC Submission Generator to select the QSOs you submitted for DXCC Award Credit, then your submitted QSOs can
be update to reflect their DXCC award credit by clicking the "DXCC Submission' window's "Verify Submission" button. This is steps 7
and 8 in the " Generating an LotW Submission" section of

<>


Note that you also have the option of having DXKeeper download all of your DXCC credits from the ARRL and use this information to
update the DXCC Credit status of all of your logged QSOs. This works smoothly for QSOs confirmed via LotW, but QSOs confirmed via
QSL cards may have slightly inaccurate DXCC credits as a result of data entry errors or shortcuts -- like specifying the correct
DXCC entity, band, and mode, but specifying an incorrect callsign or an incorrect date. Expect 25% of the DXCC credits generated
from QSL cards to require manual "linking" to your logged QSOs. Step-by-step instructions are here:

<.


While it's tempting to make a DXCC submission of QSOs confirmed via LoTW by letting LoTW pick the QSOs to submit, doing so is the
wrong choice for two reasons:

1. LoTW's selection of QSOs to submit is suboptimal; you may submit more confirmed QSOs than are necessary. For example, in need of
DXCC credit for P5 in both RTTY and on 160m (but not on 40m or Phone), LoTW might have you submit a 40m RTTY QSO and a 160m Phone
QSO when you have a confirmed 160m RTTY QSO.

2. You can't use DXKeeper's "Verify Submission" button to update your logged QSOs to reflect DXCC Credit granted with one gesture.


Thus you cannot rely on invoking the "Sync LoTW QSLs" function after being informed that the QSOs confirmed via LoTW that you
submitted for DXCC award credit have received that DXCC award credit to update your logged QSOs to reflect the granting of that DXCC
award credit.


73,

Dave, AA6YQ


Re: cant close app's launcher

 

+ AA6YQ comments below

i have a question about a problem i have not ran into before. i replaced one of the shack computers now have 3 hp all in ones
running win 7 home. dx lab loaded and works great till i go to launcher and click the term button . it will not close any of the
progams. i open them from launcher by clicking each one .
was using one of the other computers to check all the settings and found that i have another computer that will not close WW from
launcher BUT closes everything else. so i checked everything against the 3rd computer all have the same settings in each app. and
the last one works as it should. i do not recall ever running dxlab from ADMIN so i dont think that is it.
not a big deal just has me stumped as of now.

+ Reboot Windows into "Safe mode with networking. Start the Launcher, and have the Launcher start your application. Now direct the
Launcher to terminate your applications. What happens?

73,

Dave, AA6YQ


cant close app's launcher

 

i have a question about a problem i have not ran into before. i replaced one of the shack computers now have 3 hp all in ones running win 7 home. dx lab loaded and works great till i go to launcher and click the term button . it will not close any of the progams. i open them from launcher by clicking each one .
was using one of the other computers to check all the settings and found that i have another computer that will not close WW from launcher BUT closes everything else. so i checked everything against the 3rd computer all have the same settings in each app. and the last one works as it should. i do not recall ever running dxlab from ADMIN so i dont think that is it.
not a big deal just has me stumped as of now.
73 Tony WA4JQS


Re: DX Labs commander accessibility issues

 

Dave, thank you so much. It is odd that some controls have readable labels and some not so much. Thanks for looking at the TAB order and labels. Please let me know what I can do to help.
Frank, n1fmv

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ via groups.io
Sent: Wednesday, April 15, 2020 9:48 PM
To: [email protected]
Subject: Re: [DXLab] DX Labs commander accessibility issues

+ AA6YQ comments below

Hi Dave, thank you very much for the response. You can obtain a free license of JAWS, good until June 30 at:

Even the demo version of JAWS runs for 40 minutes at a time.

Also there is a free screen reader known as NVDA which can be downloaded at:

Look for the check box called "NV Access".

If you are interested in improving the accessibility I would definitely be willing to provide you with a full JAWS license.

+ You are the third ham to ask for JAWS support in the past 20 years. I will review the tab order in Commander's Configuration window, but DXLab applications are built with Microsoft tools that do not provide me with the ability to influence the JAWS-relevant behavior of controls.

73,

Dave, AA6YQ


Re: DX Labs commander accessibility issues

 

+ AA6YQ comments below

Hi Dave, thank you very much for the response. You can obtain a free license of JAWS, good until June 30 at:

Even the demo version of JAWS runs for 40 minutes at a time.

Also there is a free screen reader known as NVDA which can be downloaded at:

Look for the check box called "NV Access".

If you are interested in improving the accessibility I would definitely be willing to provide you with a full JAWS license.

+ You are the third ham to ask for JAWS support in the past 20 years. I will review the tab order in Commander's Configuration window, but DXLab applications are built with Microsoft tools that do not provide me with the ability to influence the JAWS-relevant behavior of controls.

73,

Dave, AA6YQ


Re: DX Labs commander accessibility issues

 

Hi Dave, thank you very much for the response. You can obtain a free license of JAWS, good until June 30 at:

Even the demo version of JAWS runs for 40 minutes at a time. Also there is a free screen reader known as NVDA which can be downloaded at:

Look for the check box called "NV Access". If you are interested in improving the accessibility I would definitely be willing to provide you with a full JAWS license. I can also get a few blind hams to test as well. You can contact me on this list or direct at:
Frank.ventura@...
617.267.1067


Thanks again
Frank

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ via groups.io
Sent: Wednesday, April 15, 2020 8:45 PM
To: [email protected]
Subject: Re: [DXLab] DX Labs commander accessibility issues

+ AA6YQ comments below

Hi all, I am trying to use DX Commander with two different Icom rigs; one being an ic7300 and the other an ic7100. Being blind I use a screen reader and am running into difficulties in the configuration dialog. I cannot press TAB to move to the next control and the controls are not read in the configuration screens. Is there any means of making this a little more accessible?

+ I have control over tab order, but if JAWS cannot identify the configuration controls, there is nothing I can do about that.

+ I asked Freedom Scientific for a copy of JAWS so I could improve its usefulness with DXLab applications, but they declined.

73,

Dave, AA6YQ


Re: Getting "Sat mode" to stick in DXKeeper log Capture window

 

+ AA6YQ comments below

New DXLabs user

+ Welcome to DXLab, Steve!

, starting out running DXKeeper stand alone. I read in the help files where to set defaults for satellite modes, but when I open the Capture log window, nothing is preset. So I have to enter satellite, mode and the TX and RX bands manually for each contact.

1) What am I missing here?

+ Type a callsign into the Capture window's call box, and strike the Enter or Tab key; the default Propagation Mode, Satellite Name, and Satellite Mode specified on the Configuration window's Defaults tab will be used to populate the appropriate Capture window items.

2) Is there was way to easily change the default satellite and mode in the Capture window without editing defaults (multiple satellite passes back-to back)?

+ "Editing defaults" sounds like you are making modifications to a file, which is unnecessary, Simply change the selectors on the Configuration window's Defaults tab.

73,

Dave, AA6YQ


Re: Pathfinder Map not loading

 

+ AA6YQ comments below

yes, it has Edge..
loaded Edge and logged into qrz and yes map works tnx Pat

+ Edge is not Internet Explorer. Try Internet Explorer.

73,

Dave, AA6YQ


Re: Two Rotors

 

+ AA6YQ comments below

Is there a plan to add a multi rotor feature to support more than one rotor from the program itself, thus be able to configure what rotor to turn for a specific band, etc.

+ You can do that now by using DXView's ability to interoperate with N1MM Rotor:

<>

+ Given this interoperation, providing the capability directly in DXView has low priority compared to other items on the enhancement lists.

73,

Dave, AA6YQ


Re: DX Labs commander accessibility issues

 

+ AA6YQ comments below

Hi all, I am trying to use DX Commander with two different Icom rigs; one being an ic7300 and the other an ic7100. Being blind I use a screen reader and am running into difficulties in the configuration dialog. I cannot press TAB to move to the next control and the controls are not read in the configuration screens. Is there any means of making this a little more accessible?

+ I have control over tab order, but if JAWS cannot identify the configuration controls, there is nothing I can do about that.

+ I asked Freedom Scientific for a copy of JAWS so I could improve its usefulness with DXLab applications, but they declined.

73,

Dave, AA6YQ


Re: Script for WAS after 2000-01-01

 

Havent tried it yet - as have been working today. The WAS report is
probably easier

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ
Sent: Wednesday, April 15, 2020 8:40 PM
To: [email protected]
Subject: Re: [DXLab] Script for WAS after 2000-01-01

+ AA6YQ comments below

If I wanted to write a script to determine the states I have worked,
confirmed and verified on 40M after 01 January 2000, would the script be:


filter Band='40m' and qso_begin > #2000-01-01#

report us_states <ReportsFolder>us_states_40.txt

If not, what should the script be?

+ Looks reasonable. Did you try it?

+ If you're pursuing the WAS award, you might use the WAS progress report
instead of the US_States report.

73,

Dave, AA6YQ