Date   

Entities worked SSB but not CW

N1BUG
 

Here's a simple one but I don't seem to know or be able to find the answer.

According to DXKeeper I have worked three more for mixed DXCC than I have for CW. I know what two of them are from memory but the third must be ancient history and escapes me. Is there a simple way to get DXKeeper to show me which three DXCC entities I have worked on SSB but not on CW?

73,
Paul


--
Paul, N1BUG ME - Piscataquis - FN55mf
160-6m QRO CW - DX - Contesting
147.105 Repeater serving the Maine Highlands
444.950 Repeater, echolink node 444950


Re: OQRS question

DAVID BERNHEISEL
 

If you strike the EDIT button before striking the OQRS button, the change should work.  It is not necessary to 'SAVE' but is necessary to enable edit for each QSO.


On 2/8/2016 05:45, Dan Ziolkowski dan.ziolkowski@... [dxlab] wrote:
 
The one on the LOG QSL page

QSL subsection

Far left

Under sent, recd, RR

--
Dan Ziolkowski KC2STA
SKCC #4290T
30MDG #1250
Ubuntu LINUX


Re: OQRS question

d_ziolkowski
 

The one on the LOG QSL page

QSL subsection

Far left

Under sent, recd, RR

--
Dan Ziolkowski KC2STA
SKCC #4290T
30MDG #1250
Ubuntu LINUX


Re: OQRS question

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Monday, February 08, 2016 6:33 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] OQRS question

I just sent 3 OQRS. Clicked "OQRS" button for each on Log page.

To what "OQRS" button are you referring?
73,

Dave, AA6YQ


OQRS question

d_ziolkowski
 

Dave- 


I just sent 3 OQRS. Clicked "OQRS" button for each on Log page.


Cleared QSL queue.


Selected cards on QSL page


Selected add needed.


All 3 QSOs still in queue.


Look at QSOs-


all say QSL sent Y, rcvd is blank


all sent via E


What do I do to get them out of queue, and why don't the auto-drop?


Thanks DAN KC2STA




Re: Making Workspaces Easier

w3qt_mike
 

Dave,

I have only one small problem with the wording you suggest.� Logically, why would I create an "Empty" workspace?� Assuming I created it to save a set of settings, I wouldn't be creating an "empty" workspace but rather a new workspace.� This might be confusing to someone just beginning with DXLab.� If the purpose of the action is to signify the creation of a new set of settings, wouldn't the word "New" be a clearer designation than "Empty?"�

73,
Mike, W3QT



On 2/8/2016 12:37 AM, ' Dave AA6YQ' aa6yq@... [dxlab] wrote:
�

Many thanks for all of the comments and suggestions so far!

The Launcher's "mission" is to enable users to manage the DXLab Suite's separate applications without much more fuss than would be
required to manage a monolithic application. Since each application has its own settings that are stored in the Windows Registry
between operating sessions, there were two needs:

1. the ability to save settings to a file that could then be backed up for safekeeping, and the ability to restore settings from a
file after an event that requires re-installing Windows, or after an application's settings were inadvertently modified

2. the ability to switch between different "sets of settings", e.g. when changing operating style (DXing vs. rag chewing vs. net
operations) or when changing operators sharing the same computer

The concept of a Workspace -- which is simply a folder containing one file of registry settings for each DXLab application --
satisfies both needs. Given that these needs are unique to DXLab, we should continue to refer to this concept with its (relatively)
unique name: "Workspace".

The Launcher's Workspaces window is not going to reside on any user's monitor for long. Thus expanding it a bit to accommodate the
use of larger captions for the four Workspace buttons is entirely reasonable.

The first word of each caption should be a verb.

After reviewing your posts, I now propose that the buttons be named

"Create Empty Workspace"

"Save Settings to Workspace"

"Restore Settings from Workspace"

"Delete Workspace"

Comments, suggestions, and better ideas are still welcome.

A new version of the Launcher is imminent; I've been holding off until the VP8SGI operation is completed. I expect to include the
new Workspace button names in this new version.

73,

Dave, AA6YQ



Re: Making Workspaces Easier

N1BUG
 

Dave AA6YQ wrote:

"Create Empty Workspace"

"Save Settings to Workspace"

"Restore Settings from Workspace"

"Delete Workspace"

Comments, suggestions, and better ideas are still welcome.

I like it. That word Empty would save me from having to re-read the documentation every few months. :)

73,
Paul N1BUG


Re: Making Workspaces Easier

G4MUL
 


On 07 Feb 2016 21:41, 'Jerry (K3BZ)' k3bz@... [dxlab] wrote:
I'd rather keep what we have now.

I'm happy with the current wording
-- 
73,
Dave


Re: Making Workspaces Easier

DAVID BERNHEISEL
 

Howdy everyone,

I have been following the discussions here, and I have an observation.

Restore settings seems to indicate fixing something that is not working properly.  If workspaces are to be used to simply change from one set of operating conditions to another, then I "assume" one would restore all of the settings from a workspace definition without affecting the settings in the current workspace.  I guess the flyover help for Restore could include "Switch to"?

.005 cents.

Dave, N2DPF

On 2/8/2016 03:15, Randy Moore wrmoore47@... [dxlab] wrote:
 
Looks good.

On Feb 7, 2016, at 11:37 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

Many thanks for all of the comments and suggestions so far!

The Launcher's "mission" is to enable users to manage the DXLab Suite's separate applications without much more fuss than would be
required to manage a monolithic application. Since each application has its own settings that are stored in the Windows Registry
between operating sessions, there were two needs:

1. the ability to save settings to a file that could then be backed up for safekeeping, and the ability to restore settings from a
file after an event that requires re-installing Windows, or after an application's settings were inadvertently modified

2. the ability to switch between different "sets of settings", e.g. when changing operating style (DXing vs. rag chewing vs. net
operations) or when changing operators sharing the same computer

The concept of a Workspace -- which is simply a folder containing one file of registry settings for each DXLab application --
satisfies both needs. Given that these needs are unique to DXLab, we should continue to refer to this concept with its (relatively)
unique name: "Workspace".

The Launcher's Workspaces window is not going to reside on any user's monitor for long. Thus expanding it a bit to accommodate the
use of larger captions for the four Workspace buttons is entirely reasonable.

The first word of each caption should be a verb.

After reviewing your posts, I now propose that the buttons be named

"Create Empty Workspace"

"Save Settings to Workspace"

"Restore Settings from Workspace"

"Delete Workspace"

Comments, suggestions, and better ideas are still welcome.

A new version of the Launcher is imminent; I've been holding off until the VP8SGI operation is completed. I expect to include the
new Workspace button names in this new version.

73,

Dave, AA6YQ




Re: Making Workspaces Easier

Randy
 

Looks good.

On Feb 7, 2016, at 11:37 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

Many thanks for all of the comments and suggestions so far!

The Launcher's "mission" is to enable users to manage the DXLab Suite's separate applications without much more fuss than would be
required to manage a monolithic application. Since each application has its own settings that are stored in the Windows Registry
between operating sessions, there were two needs:

1. the ability to save settings to a file that could then be backed up for safekeeping, and the ability to restore settings from a
file after an event that requires re-installing Windows, or after an application's settings were inadvertently modified

2. the ability to switch between different "sets of settings", e.g. when changing operating style (DXing vs. rag chewing vs. net
operations) or when changing operators sharing the same computer

The concept of a Workspace -- which is simply a folder containing one file of registry settings for each DXLab application --
satisfies both needs. Given that these needs are unique to DXLab, we should continue to refer to this concept with its (relatively)
unique name: "Workspace".

The Launcher's Workspaces window is not going to reside on any user's monitor for long. Thus expanding it a bit to accommodate the
use of larger captions for the four Workspace buttons is entirely reasonable.

The first word of each caption should be a verb.

After reviewing your posts, I now propose that the buttons be named

"Create Empty Workspace"

"Save Settings to Workspace"

"Restore Settings from Workspace"

"Delete Workspace"

Comments, suggestions, and better ideas are still welcome.

A new version of the Launcher is imminent; I've been holding off until the VP8SGI operation is completed. I expect to include the
new Workspace button names in this new version.

73,

Dave, AA6YQ



Re: Making Workspaces Easier

Nuno Lopes - CT2IRY
 

Morning Dave & all,

You've my vote for your suggested names.
 
73 Nuno
  CT2IRY



On Monday, February 8, 2016 5:38 AM, "' Dave AA6YQ' aa6yq@... [dxlab]" wrote:


 
Many thanks for all of the comments and suggestions so far!

The Launcher's "mission" is to enable users to manage the DXLab Suite's separate applications without much more fuss than would be
required to manage a monolithic application. Since each application has its own settings that are stored in the Windows Registry
between operating sessions, there were two needs:

1. the ability to save settings to a file that could then be backed up for safekeeping, and the ability to restore settings from a
file after an event that requires re-installing Windows, or after an application's settings were inadvertently modified

2. the ability to switch between different "sets of settings", e.g. when changing operating style (DXing vs. rag chewing vs. net
operations) or when changing operators sharing the same computer

The concept of a Workspace -- which is simply a folder containing one file of registry settings for each DXLab application --
satisfies both needs. Given that these needs are unique to DXLab, we should continue to refer to this concept with its (relatively)
unique name: "Workspace".

The Launcher's Workspaces window is not going to reside on any user's monitor for long. Thus expanding it a bit to accommodate the
use of larger captions for the four Workspace buttons is entirely reasonable.

The first word of each caption should be a verb.

After reviewing your posts, I now propose that the buttons be named

"Create Empty Workspace"

"Save Settings to Workspace"

"Restore Settings from Workspace"

"Delete Workspace"

Comments, suggestions, and better ideas are still welcome.

A new version of the Launcher is imminent; I've been holding off until the VP8SGI operation is completed. I expect to include the
new Workspace button names in this new version.

73,

Dave, AA6YQ




Re: Logging NPOTA

Rory Sena
 

Thanks Dave I got it now. 

Sent from my shoe phone. 

On Feb 7, 2016, at 10:20 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 08, 2016 1:06 AM
To: dxlab@...
Subject: Re: [dxlab] Logging NPOTA

Sorry Dave, I'm not getting it. At the bottom of the Adv Sorts, Filters & Modifiers screen I see the box on the lower left that has "Modify QSO's in Log Page Display" and in the dropdown I can choose the user defined field that I have NPOTA set as, but where I'm lost is in the next box field "Item new value" am I to enter anything in it? I missing something really basic here I guess. Another question do I need to change the Item name at the top of the page dropdown?

>>>See

<http://www.dxlabsuite.com/dxkeeper/Help/ModifyLog.htm>

>>>The "Item New value" should be set to



>>>meaning "the contents of this QSO's COMMENT item".

>>>The "Item name" selector at the top of the "Advanced Sorts, Filters & Modifiers" windows is there to provide convenient access to all item names. It plays no functional role in the operation of the "Modify QSOs" panel.

>>>Be sure to backup your log before you click the "Modify QSOs" panel's Mod button!

73,

Dave, AA6YQ


Re: Logging NPOTA

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Monday, February 08, 2016 1:06 AM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] Logging NPOTA



Sorry Dave, I'm not getting it. At the bottom of the Adv Sorts, Filters & Modifiers screen I see the box on the lower left that has "Modify QSO's in Log Page Display" and in the dropdown I can choose the user defined field that I have NPOTA set as, but where I'm lost is in the next box field "Item new value" am I to enter anything in it? I missing something really basic here I guess. Another question do I need to change the Item name at the top of the page dropdown?

See
<http://www.dxlabsuite.com/dxkeeper/Help/ModifyLog.htm>

The "Item New value" should be set to
<COMMENT>

meaning "the contents of this QSO's COMMENT item".
The "Item name" selector at the top of the "Advanced Sorts, Filters & Modifiers" windows is there to provide convenient access to all item names. It plays no functional role in the operation of the "Modify QSOs" panel.
Be sure to backup your log before you click the "Modify QSOs" panel's Mod button!
73,

Dave, AA6YQ


Re: Logging NPOTA

Rory Sena
 

Sorry Dave, I'm not getting it. At the bottom of the Adv Sorts, Filters & Modifiers screen I see the box on the lower left that has "Modify QSO's in Log Page Display" and in the dropdown I can choose the user defined field that I have NPOTA set as, but where I'm lost is in the next box field "Item new value" am I to enter anything in it? I missing something really basic here I guess. Another question do I need to change the Item name at the top of the page dropdown?



Rory

On Sun, Feb 7, 2016 at 9:08 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 07, 2016 11:52 PM
To: dxlab@...
Subject: Re: [dxlab] Logging NPOTA

I'm trying to setup my DXKeeper per Dave's link and I have a question, I have already logged a few NPOTA stations before adding the query and didn't know where to put the unit's number so I dropped them in the comments field. Now how do I go back and edit my QSO's and move the unit numbers to the user defined field?

>>>I suggest that you simply type the park code into each logged QSO's NPOTA user-defined item. Then direct DXKeeper to generate an NPOTA progress report to confirm the accuracy of your updates.

>>>DXKeeper's "Modify QSOs" panel has the ability to copy information from one item (like COMMENT) to another (like the NPOTA user-defined field) en masse for all QSOs in the Log Page Display. But to use this, the COMMENT items in question must contain an NPOTA park code and nothing else, and there must be a way to filter the Log Page Display to contain only your logged QSOs with NPOTA stations. Unless you've only been logging QSOs with NPOTA stations and thus can select them all with a date filter, a one-time manual correction is recommended. If you do employ the "Modify QSOs" panel (at the bottom of the "Advanced Sorts, Filters, and Modifiers" window, backup your log before going near it! (Configuration window, Log tab, Backup button).

73,

Dave, AA6YQ




--

Tesla was one of the greatest geniuses to come out of the earth. He did things they said couldn't be done... He was the real father of radio, not Marconi. A U.S. Supreme Court patent decision, the year after Tesla's death, awarded him that honor.

Ken Strickfaden


Re: Making Workspaces Easier

Dave AA6YQ
 

Many thanks for all of the comments and suggestions so far!

The Launcher's "mission" is to enable users to manage the DXLab Suite's separate applications without much more fuss than would be
required to manage a monolithic application. Since each application has its own settings that are stored in the Windows Registry
between operating sessions, there were two needs:

1. the ability to save settings to a file that could then be backed up for safekeeping, and the ability to restore settings from a
file after an event that requires re-installing Windows, or after an application's settings were inadvertently modified

2. the ability to switch between different "sets of settings", e.g. when changing operating style (DXing vs. rag chewing vs. net
operations) or when changing operators sharing the same computer

The concept of a Workspace -- which is simply a folder containing one file of registry settings for each DXLab application --
satisfies both needs. Given that these needs are unique to DXLab, we should continue to refer to this concept with its (relatively)
unique name: "Workspace".

The Launcher's Workspaces window is not going to reside on any user's monitor for long. Thus expanding it a bit to accommodate the
use of larger captions for the four Workspace buttons is entirely reasonable.

The first word of each caption should be a verb.

After reviewing your posts, I now propose that the buttons be named

"Create Empty Workspace"

"Save Settings to Workspace"

"Restore Settings from Workspace"

"Delete Workspace"

Comments, suggestions, and better ideas are still welcome.

A new version of the Launcher is imminent; I've been holding off until the VP8SGI operation is completed. I expect to include the
new Workspace button names in this new version.

73,

Dave, AA6YQ


Re: Logging NPOTA

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Sunday, February 07, 2016 11:52 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] Logging NPOTA

I'm trying to setup my DXKeeper per Dave's link and I have a question, I have already logged a few NPOTA stations before adding the query and didn't know where to put the unit's number so I dropped them in the comments field. Now how do I go back and edit my QSO's and move the unit numbers to the user defined field?

I suggest that you simply type the park code into each logged QSO's NPOTA user-defined item. Then direct DXKeeper to generate an NPOTA progress report to confirm the accuracy of your updates.
DXKeeper's "Modify QSOs" panel has the ability to copy information from one item (like COMMENT) to another (like the NPOTA user-defined field) en masse for all QSOs in the Log Page Display. But to use this, the COMMENT items in question must contain an NPOTA park code and nothing else, and there must be a way to filter the Log Page Display to contain only your logged QSOs with NPOTA stations. Unless you've only been logging QSOs with NPOTA stations and thus can select them all with a date filter, a one-time manual correction is recommended. If you do employ the "Modify QSOs" panel (at the bottom of the "Advanced Sorts, Filters, and Modifiers" window, backup your log before going near it! (Configuration window, Log tab, Backup button).
73,

Dave, AA6YQ


Re: Logging NPOTA

Rory Sena
 

Hello all,

I'm trying to setup my DXKeeper per Dave's link and I have a question, I have already logged a few NPOTA stations before adding the query and didn't know where to put the unit's number so I dropped them in the comments field. Now how do I go back and edit my QSO's and move the unit numbers to the user defined field?


Thanks

On Sun, Feb 7, 2016 at 8:17 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 07, 2016 5:53 PM
To: dxlab@...
Subject: Re: [dxlab] Logging NPOTA

Thanks for the link Dave but I was there hours ago. I guess I have to make separate log entries for each park since that’s the only way I could get the progress report to show that all were worked.

>>>DXKeeper's NPOTA progress report should properly interpret an NPOTA user-defined field containing comma-delimited park codes. If you have evidence to the contrary, please send it to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ




--

Tesla was one of the greatest geniuses to come out of the earth. He did things they said couldn't be done... He was the real father of radio, not Marconi. A U.S. Supreme Court patent decision, the year after Tesla's death, awarded him that honor.

Ken Strickfaden


Re: SpotCollector and NOPTA

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Sunday, February 07, 2016 8:28 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] SpotCollector and NOPTA

Does anyone have a quick setup guide to make a SQL query for NOPTA? I saw one on FB but the OP said it was not an easy one!

The easiest query is
cumulative like '*NPOTA*'

If you have the "Record individual spot information" option enabled in the Controls panel on the "Spot Database" tab of SpotCollector's Configuration window, then the above query will show all Spot Database Entries for which the word NPOTA has appeared in spot notes.
DXKeeper has the ability to generate an NPOTA filter for SpotCollector that hides active NPOTA stations whose park codes you've already worked. See
<http://www.dxlabsuite.com/dxlabwiki/NPOTAAwardTracking>

Do note the "Limitations" section at the bottom of this article.
73,

Dave, AA6YQ


Re: Logging NPOTA

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Sunday, February 07, 2016 5:53 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] Logging NPOTA

Thanks for the link Dave but I was there hours ago. I guess I have to make separate log entries for each park since that’s the only way I could get the progress report to show that all were worked.

DXKeeper's NPOTA progress report should properly interpret an NPOTA user-defined field containing comma-delimited park codes. If you have evidence to the contrary, please send it to me via
aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: Making Workspaces Easier

iain macdonnell - N6ML
 

Personally, I think that the current terms more accurately reflect the
functions performed. Backup is one purpose of a workspace, but it is
not the only purpose. For example, a station used by multiple
operators may utilise one workspace for each. When an operators wishes
to commit configurations changes to his/her workspace, that's not
really a "backup" action. To me, backing up a workspace would mean to
take the saved ".reg" files and copy them to another location, in case
I lose them.

Perhaps something like "Save configuration to Workspace" and "Restore
configuration from Workspace" would be more clear, whilst maintaining
accuracy.... but the buttons would be very wide!

73,

~iain / N6ML


On Sun, Feb 7, 2016 at 1:31 PM, ' Dave AA6YQ' aa6yq@ambersoft.com
[dxlab] <dxlab@yahoogroups.com> wrote:



I think the proposal below is excellent, but would appreciate feedback from the user community before I re-title the buttons on the
Launcher's Workspaces window and update the documentation to match.

Comments, concerns, and better ideas are welcome.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Sunday, February 07, 2016 4:27 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Making Workspaces Easier

Workspaces might be easier if the terms were more familiar to users:

Create Workspace ---- > New Workspace
Update Workspace ---- > Backup Workspace
Activate Workspace ---- > Restore Workspace
Delete Workspace ---- > Delete Workspace

New, Backup, Restore and Delete are all terms that most users are familiar with.

The mouseovers would provide additional details.

Just a thought. I've had trouble explaining Workspaces to other users, and it's indispensable.

Good DX and thanks!

---
73 Parker W5ADD

47781 - 47800 of 202694