¿ªÔÆÌåÓý

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

Re: SC Outgoing Spot Control

 

Jim Besancon wrote:
When I click on a spot it populates WW and also populates the call sign in
the outgoing spot box in SC.
Mine doesn't do that unless I "double click" on a spot but perhaps that's what you meant to say.
If I clear WW, after deciding that I can't work
the spot or don't want to work the spot, the call sign in the outgoing spot
in SC remains populated.

How can the spot call sign be cleared automatically? Now I just highlight
the call sign and hit the space bar, kind of old fashioned.
Why clear it? It's not hurting anything and will be replaced when you double click the next spot. Min sits there with some callsign in it almost all the time.

Also the spot frequency is not locked to the spot. If I move the dial the
spot frequency changes but the call sign remains. Is this normal?
Yes, if you had to tune your radio to bring the station in, then the original spot frequency wasn't quite correct. If you re-spot the station, you want to do so with what your believe to be the correct frequency.

73, Rich - W3ZJ
Thanks

73 - Jim - K8SIA


Re: Q & A's - W9OL

FireBrick
 




Thanks for the W9OL Q's
but somehow none in 2009.



73 - Jim - K8SIA
Wife is working me to death. LOL

Kidding aside, a few minor health problems, and 18 grandkids makes weekends a tough go for contesting.

But slowing down a bit now, grandkids don't want those old smelly grandparents around so much. LOL

The other issue is I've been converted to SDR, Flex Radio is a fantastic DX machine.
But not so much a contesting machine.

So have been working with software writers of the Flex to make contesting easier.


Re: Q & A's - W9OL

 

Bill



Thanks Bill for the kind words. I have been using DXL for 16 months but
seldom get a chance to play with it and start asking questions.



I keep a separate folder in my email for DXL advice that I might find useful
and check that often before typing away.



I do support you in the request for a change to SC , that if it isn't
confirmed on band/mode it is needed J



Thanks for the W9OL Q's but somehow none in 2009.



73 - Jim - K8SIA



From: FireBrick [mailto:w9ol@...]
Sent: Monday, September 07, 2009 4:46 PM
To: DXLabs List
Subject: [dxlab] Q & A's





I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .

Which is why I read almost all of the Q&A's here.
I may have forgotten how a feature works.
I may not have known how it worked in the first place.
I see other ways to do things that could improve my techniques.

DXL is way to much for me to remember....so this Group is a way for me to
get my brain refreshed.

Plus...this is one of the most congenial, friendly, groups.
Some of the groups....get a bit testy at times.
Never in DXL

----------------------------------------------------------
"The attention span of a computer is only as long as its power cord.
----------------------------------------------------------
TOWER/WEBCAMS and Weather Page
@


Re: BEGIN MACRO Request or Did I Miss This Also?

 

Answers/Comments

If you want your RST items initialized to but don't want the QSO's start
time set when you capture a callsign, disable "set QSO start when RST
Rcvd". -

This is my setup. I have "set QSO start when RST Rcvd" unchecked and
"initialize RST items to
default" checked.

Note that if you log a QSO without having clicked the Begin button,
WinWarbler will record the QSO's start and end times as the time at which
you clicked the Log button (or executed the Log macro command).

I just clicked 3A2MD at 2045 and walked away from computer. I came back hit
my log macro F key and then looked in the DXK log file. The Q start time was
2045 and the Q end time was 2050.

73 - Jim - K8SIA



-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Monday, September 07, 2009 4:31 PM
To: dxlab@...
Subject: RE: [dxlab] BEGIN MACRO Request or Did I Miss This Also?

AA6YQ comments below


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 4:16 PM
To: dxlab@...
Subject: [dxlab] BEGIN MACRO Request or Did I Miss This Also?


Situation: Click on spot or find station in pile up and start entry (enter
call sign) in WW. I then use TAB to see if I should proceed with chasing the
station. The QSO Started At Date/Time appears in red above call sign in WW.

Problem: I don't always get the station for several minutes and when I do,
it is a mad click to hit the BEGIN button and then the F Key to send my
report.

Is there or can there be a <begin> macro that can be placed in a F Key
function to reset the start time of the QSO? I can't find one in the list of
macros.

By default, a QSO's start time is set when you click the Main window's
"QSO Info" panel's Begin button.

On the Config window's Log tab, enabling the "set QSO start when RST
Rcvd" option means that a QSO's start time will be set when you specify its
"RST Rcvd" item, either by typing a report into the Main windows' "Log QSOs"
tab, or by double-clicking a received signal report.

On the Config window's Log tab, there is also an "initialize RST items to
default" option. If you enable this option and have also enabled "set QSO
start when RST Rcvd", then when you type a callsign into the "QSO Info"
window or double-click a decoded callsign

1. the "RST Rcvd" item is initialized to the default

2. the QSO's start time is set (because the "RST Rcvd" was recorded and you
have "set QSO start when RST Rcvd" enabled

If you want your RST items initialized to but don't want the QSO's start
time set when you capture a callsign, disable "set QSO start when RST
Rcvd".

Note that if you log a QSO without having clicked the Begin button,
WinWarbler will record the QSO's start and end times as the time at which
you clicked the Log button (or executed the Log macro command).


I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links


Re: Stopping Programs

 

Hi Dave,

Thanks for the reminder to try "Advanced SystemCare." Wow! It found
lots of stuff that the other programs that I was using to keep the
computer clean had just passed over. I ran it and found that my
computer was noticeably faster in loading programs! Thanks for the
tip! I've added it to all my computers. It's nice to have all of these
functions in one program.

73,

Ken - K4XL

Dave AA6YQ wrote:

I forgot about GameBooster, Ken. I don't use it, but I tried it once and it
seemed to work well. Thanks for pointing this out!

My experience with IObit tools has been uniformly positive. I have the free
version of "Advanced SystemCare" running on every one of my PCs:

<>

I have no relationship with IObit.

73,

Dave, AA6YQ


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kenneth D. Grimm, K4XL
Sent: Monday, September 07, 2009 1:18 PM
To: dxlab@...
Subject: Re: [dxlab] Stopping Programs


aburkefl wrote:

What are the names of some of the popular (and successful!) programs that
will disable anything running in the background that doesn't need to be
running when running amateur applications (like DXKeeper or other parts of
the DXLab suite)?

Thanks.

Art - N4PJ




I use Game Booster. While this little program was designed for serious
game players, it will do what you are asking. Freeware. Works for me,
but there may be other, better programs that I don't know about.

73,

--
Ken K4XL
k4xl@...

*** BoatAnchor Manual Archive ***
On the web at and
FTP site info: bama.sbc.edu login: anonymous p/w: youremailadr




--
Ken K4XL
k4xl@...

*** BoatAnchor Manual Archive ***
On the web at and
FTP site info: bama.sbc.edu login: anonymous p/w: youremailadr


Re: SC Outgoing Spot Control

 

AA6YQ comments below
--- In dxlab@..., "Jim Besancon" <k8sia@...> wrote:

Last question of the day.

When I click on a spot it populates WW and also populates the call sign in the outgoing spot box in SC. If I clear WW, after deciding that I can't work the spot or don't want to work the spot, the call sign in the outgoing spot in SC remains populated.

How can the spot call sign be cleared automatically? Now I just highlight the call sign and hit the space bar, kind of old fashioned.

I didn't provide automation for this because its not necessary. If you double-click another spot database entry or double-click a decoded callsign in WinWarbler, the outgoing spot callsign will be updated. If you want to manually type in a new outgoing spot callsign, click on the existing outgoing spot callsign, strike CTRL-A to select it, and then type the new outgoing spot callsign.
Also the spot frequency is not locked to the spot. If I move the dial the spot frequency changes but the call sign remains. Is this normal?

Yes. You might find that the station's actual frequency is different than what was originally spotted, or the station may QSY after being spotted. Either way, your outgoing spot should include an accurate frequency.
73,

Dave, AA6YQ


Q & A's

FireBrick
 

I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .



Which is why I read almost all of the Q&A's here.
I may have forgotten how a feature works.
I may not have known how it worked in the first place.
I see other ways to do things that could improve my techniques.

DXL is way to much for me to remember....so this Group is a way for me to get my brain refreshed.

Plus...this is one of the most congenial, friendly, groups.
Some of the groups....get a bit testy at times.
Never in DXL




----------------------------------------------------------
"The attention span of a computer is only as long as its power cord.
----------------------------------------------------------
TOWER/WEBCAMS and Weather Page
@


SC Outgoing Spot Control

 

Last question of the day.

When I click on a spot it populates WW and also populates the call sign in
the outgoing spot box in SC. If I clear WW, after deciding that I can't work
the spot or don't want to work the spot, the call sign in the outgoing spot
in SC remains populated.

How can the spot call sign be cleared automatically? Now I just highlight
the call sign and hit the space bar, kind of old fashioned.

Also the spot frequency is not locked to the spot. If I move the dial the
spot frequency changes but the call sign remains. Is this normal?

Thanks

73 - Jim - K8SIA


Re: BEGIN MACRO Request or Did I Miss This Also?

 

AA6YQ comments below


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 4:16 PM
To: dxlab@...
Subject: [dxlab] BEGIN MACRO Request or Did I Miss This Also?


Situation: Click on spot or find station in pile up and start entry (enter
call sign) in WW. I then use TAB to see if I should proceed with chasing the
station. The QSO Started At Date/Time appears in red above call sign in WW.

Problem: I don't always get the station for several minutes and when I do,
it is a mad click to hit the BEGIN button and then the F Key to send my
report.

Is there or can there be a <begin> macro that can be placed in a F Key
function to reset the start time of the QSO? I can't find one in the list of
macros.

By default, a QSO's start time is set when you click the Main window's
"QSO Info" panel's Begin button.

On the Config window's Log tab, enabling the "set QSO start when RST
Rcvd" option means that a QSO's start time will be set when you specify its
"RST Rcvd" item, either by typing a report into the Main windows' "Log QSOs"
tab, or by double-clicking a received signal report.

On the Config window's Log tab, there is also an "initialize RST items to
default" option. If you enable this option and have also enabled "set QSO
start when RST Rcvd", then when you type a callsign into the "QSO Info"
window or double-click a decoded callsign

1. the "RST Rcvd" item is initialized to the default

2. the QSO's start time is set (because the "RST Rcvd" was recorded and you
have "set QSO start when RST Rcvd" enabled

If you want your RST items initialized to but don't want the QSO's start
time set when you capture a callsign, disable "set QSO start when RST
Rcvd".

Note that if you log a QSO without having clicked the Begin button,
WinWarbler will record the QSO's start and end times as the time at which
you clicked the Log button (or executed the Log macro command).


I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .

73,

Dave, AA6YQ


BEGIN MACRO Request or Did I Miss This Also?

 

Situation: Click on spot or find station in pile up and start entry (enter
call sign) in WW. I then use TAB to see if I should proceed with chasing the
station. The QSO Started At Date/Time appears in red above call sign in WW.

Problem: I don't always get the station for several minutes and when I do,
it is a mad click to hit the BEGIN button and then the F Key to send my
report.

Is there or can there be a <begin> macro that can be placed in a F Key
function to reset the start time of the QSO? I can't find one in the list of
macros.

This scenario happens in state QSO parties when I am chasing mobiles, etc.

I will bet that the group will be glad when today is over :)

73 - Jim - K8SIA


Re: New Feature or I Don't Click Enough Spots

 

Dave

Thanks, that cleared up my problem.

73 - Jim - K8SIA

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Monday, September 07, 2009 3:51 PM
To: dxlab@...
Subject: RE: [dxlab] New Feature or I Don't Click Enough Spots

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 3:41 PM
To: dxlab@...
Subject: RE: [dxlab] New Feature or I Don't Click Enough Spots


Dave and All


Answering: By " it populates WW and creates an entry in DXK", I assume you
mean "It
populates WinWarbler's 'QSO Info' panel and DXKeeper's Capture window".

No, I don't use the Capture Window. I had it active until yesterday but
found I never used it so I closed it. It populates DXK "Log QSO/Entry"
Window. If I have had a previous Q with the station it shows the previous Q
and places a red entry line in the log window. If no previous Q, then only a
red entry line in the DXK "Log Entry Window".

On the General tab of DXKeeper's Config window, uncheck the Options
panel's "New QSO on DX Spot activation" box.

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links


Re: free off-site backup

 

For what it's worth . . . I've used the free 2GB Mozy service for several months. Seems to me that it works as advertised.

Like Dave, I have no affiliation with Mozy other than being (so far) a satisfied user.

Steve K8JQ

Dave AA6YQ wrote:

Awhile back, I mentioned that I'd begun using "SOS Online Backup", an
off-site backup application that charges $20 annually for 2 GB of offline
storage and $30 annualy for 5 GB of offline storage. I set this up to
perform daily backups on my DXLab Development, Digital Photography, and XYL
PCs. While all of these systems are backed up nightly to a server, my data
was still vulnerable to a single catastrophe.

Unfortunately, "SOS Online Backup" has problems. The "client" application
that runs on each PC has resource leaks, takes forever to start up (around 2
minutes on my DXLab PC), and doesn't accurately report the amount of storage
in use. When I reported these problems to the company, they eventually sent
me a new version of the client that while improved in some dimensions is far
less reliable; it's great if you're a collector of stack traces.

I have begun evaluating Mozy (www.mozy.com) and find it to be both reliable
and useable. Initially, I was put off by the fact that files within

c:&#92;program files

could not be selected for backup, but there's a configuration option that
overrides this. The free version of Mozy gives you 2 GB -- likely more than
enough for your email, personal documents (not images), and log files. In

<>

and look for the "MozyHome Free" box along the left margin.

For those needing more than 2 GB, unlimited storage will cost you $5/month
for one PC.

I have no affiliation with Mozy beyond being a satisfied (so far) user.

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links




--
Read The Patriot Post
hppt://PatriotPost.US/Subscribe/ Vetitas vos Liberabit


Re: New Feature or I Don't Click Enough Spots

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 3:41 PM
To: dxlab@...
Subject: RE: [dxlab] New Feature or I Don't Click Enough Spots


Dave and All


Answering: By " it populates WW and creates an entry in DXK", I assume you
mean "It
populates WinWarbler's 'QSO Info' panel and DXKeeper's Capture window".

No, I don't use the Capture Window. I had it active until yesterday but
found I never used it so I closed it. It populates DXK "Log QSO/Entry"
Window. If I have had a previous Q with the station it shows the previous Q
and places a red entry line in the log window. If no previous Q, then only a
red entry line in the DXK "Log Entry Window".

On the General tab of DXKeeper's Config window, uncheck the Options
panel's "New QSO on DX Spot activation" box.

73,

Dave, AA6YQ


free off-site backup

 

Awhile back, I mentioned that I'd begun using "SOS Online Backup", an
off-site backup application that charges $20 annually for 2 GB of offline
storage and $30 annualy for 5 GB of offline storage. I set this up to
perform daily backups on my DXLab Development, Digital Photography, and XYL
PCs. While all of these systems are backed up nightly to a server, my data
was still vulnerable to a single catastrophe.

Unfortunately, "SOS Online Backup" has problems. The "client" application
that runs on each PC has resource leaks, takes forever to start up (around 2
minutes on my DXLab PC), and doesn't accurately report the amount of storage
in use. When I reported these problems to the company, they eventually sent
me a new version of the client that while improved in some dimensions is far
less reliable; it's great if you're a collector of stack traces.

I have begun evaluating Mozy (www.mozy.com) and find it to be both reliable
and useable. Initially, I was put off by the fact that files within

c:&#92;program files

could not be selected for backup, but there's a configuration option that
overrides this. The free version of Mozy gives you 2 GB -- likely more than
enough for your email, personal documents (not images), and log files. In

<>

and look for the "MozyHome Free" box along the left margin.

For those needing more than 2 GB, unlimited storage will cost you $5/month
for one PC.

I have no affiliation with Mozy beyond being a satisfied (so far) user.

73,

Dave, AA6YQ


Re: New Feature or I Don't Click Enough Spots

 

Dave and All


Answering: By " it populates WW and creates an entry in DXK", I assume you
mean "It
populates WinWarbler's 'QSO Info' panel and DXKeeper's Capture window".

No, I don't use the Capture Window. I had it active until yesterday but
found I never used it so I closed it. It populates DXK "Log QSO/Entry"
Window. If I have had a previous Q with the station it shows the previous Q
and places a red entry line in the log window. If no previous Q, then only a
red entry line in the DXK "Log Entry Window".

73 - Jim - K8SIA

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Monday, September 07, 2009 2:31 PM
To: dxlab@...
Subject: RE: [dxlab] New Feature or I Don't Click Enough Spots

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 2:12 PM
To: dxlab@...
Subject: [dxlab] New Feature or I Don't Click Enough Spots


Being a slow and damp day, I have been more active playing with the DXLab's
features than normal. I discovered something I don't recall happening before
and that is when I click on a spot it populates WW and creates an entry in
DXK. The problem is no matter what I do, I can't clear the entry in DXK and
end up logging the Q. After logging the Q in DXK, I go and delete the entry.
Kind of a pain but now I know where the odd contacts are coming from.

By " it populates WW and creates an entry in DXK", I assume you mean "It
populates WinWarbler's 'QSO Info' panel and DXKeeper's Capture window". To
clear the Capture window without logging a QSO, click the Clear button in
its lower-right corner, or strike CTRL-W (for Wipe).

If I've misunderstood your question, please elaborate...
73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links


Re: WAC report

Phil Cooper
 

Hi again Dave,

Yes, I see your point, but I read that statement to mean that ANY DXCC
entities already CREDITED for the DXCC program can be utilised in the
application.

As far as I can make out (and this is where the ARRL statement could be
misconstrued!) the important part is:
"Applicants who have a current DXCC award in the DXCC computer system can
apply for WAC by completing the WAC application form ........"

By that I assume they mean that if I have (for example) AA6YQ verified as my
DXCC entity on each band in LoTW, then I can claim that call for use in the
WAC application, as it is verified as a DXCC entity, and also counts for NA
in WAC.
Now, as I do NOT have AA6YQ listed in my DXCC list for W, then I cannot use
it to claim WAC for NA, even if it were a good match in LoTW.

To get my SQL statement, I had to use QSL_Rec'd (LoTW and Paper) ='v' and
='s' (but not 'y')!!

I plan to submit my claim using all DXCC credits, including a few that are
verified via LoTW, but I may just send them an email first to query that
staement.
I'll let you know what happens.

73 all

Phil GU0SUP


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 090906-1, 06/09/2009
Tested on: 07/09/2009 20:25:16
avast! - copyright (c) 1988-2009 ALWIL Software.


Re: CW with WinWarbler, a 746Pro, and a Rigblaster Plug and Play interface

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
john.w6hw
Sent: Monday, September 07, 2009 1:04 PM
To: dxlab@...
Subject: [dxlab] Re: CW with WinWarbler, a 746Pro, and a Rigblaster Plug
and Play interface


Dave, I'd like to bring up the question from WC5M again (Message 65183)
While there isn't a CI-V command to send CW via the transceiver Remote Jack,
the RIGblaster Plug & Play USB interface has a separate CW output that is
controlled by the serial port DTR line. (The P&P CW output is connected to
the IC-746 KEY jack.) Since Commander is already able to control the DTR
line, shouldn't CW be possible from WinWarbler without needing another
serial port?

Yes. The challenge is that only one application can open a serial port,
so Commmander must be extended to appropriately wiggle the DTR line. My
original plan was to replicate WinWarbler's CW generator in Commander (I
can't simultaneously remove the CW generator from WinWarbler, as some ops
use WinWarbler without Commander). Then I had the bright idea of making
WinWarbler convey the dots and dashes to Commander via DDE (the interprogram
communication mechanism used by DXLab applications). Unfortunately, this
experiment was a failure: DDE couldn't handle the command rate. Using
Windows Messages instead of DDE to convey the dots and dashes from
WinWarbler to Commander would definitely work, but this approach would make
both WinWarbler and Commander far more difficult to maintain (no
breakpoints). I'm planning to migrate interprogram communication from DDE to
TCP/IP; DXKeeper now accepts some commands via TCP/IP, for example. When
this TCP/IP capability reaches WinWarbler and Commander, I'll try conveying
dots and dashes from WinWarbler to Commander via TCP/IP to see if that
works. If not, then replicating the CW generator as originally planned would
be the only option.

While all of this has been happening, products like MicroHam's have
introduced virtual serial ports that make eliminating the need for a second
port for CW less urgent a requirement.

73,

Dave, AA6YQ


Re: CW with WinWarbler, a 746Pro, and a Rigblaster Plug and Play interface

 

John,

The answer is "no." Commander (which handles the CAT/CI-V
interface) and WinWarbler (which does the CW) are separate
programs. The Windows system architecture (as well as DOS
before it and CP/M before that, etc.) allows only one
program to access a serial port and by extension a USB to
serial converter at a time.

When WinWarbler gets frequency and mode information from the
radio, it is asking Commander for that information using DDE
(Dynamic Data Exchange) between programs. Unfortunately the
DDE process is not fast enough for Winwarbler to "flip the
DTR bit" with enough precision to generate CW by DDE. In
order to have WinWarbler generate CW through Commander,
Dave would need to build a CW generator into Commander and
then talk to it as if it were an external keyer ... a lot
of work (and time critical routines) for relatively little
functionality.

73,

... Joe, W4TV

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On
Behalf Of john.w6hw
Sent: Monday, September 07, 2009 1:04 PM
To: dxlab@...
Subject: [dxlab] Re: CW with WinWarbler, a 746Pro, and a
Rigblaster Plug and Play interface


Dave, I'd like to bring up the question from WC5M again
(Message 65183) While there isn't a CI-V command to send CW
via the transceiver Remote Jack, the RIGblaster Plug & Play
USB interface has a separate CW output that is controlled by
the serial port DTR line. (The P&P CW output is connected to
the IC-746 KEY jack.) Since Commander is already able to
control the DTR line, shouldn't CW be possible from
WinWarbler without needing another serial port?

Thanks & 73, John W6HW

--- In dxlab@..., "Dave Bernstein" <aa6yq@...> wrote:

With an Icom transceiver, CW generation from WinWarbler requires a
separate serial port; you can't use the serial port used for
transceiver control for CW generation.

73,

Dave, AA6YQ




------------------------------------

Yahoo! Groups Links



Re: SC and WW Questions

 

+++More AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 2:16 PM
To: dxlab@...
Subject: RE: [dxlab] SC and WW Questions


Dave wrote:

No. I was concerned that carrying over a filter from the previous
operating session might cause a user to miss needed DX. - I guess that
would be my problem and not yours :).

+++The tradeoff is pretty clear: one mouse click at SpotCollector startup to
manually re-instate the desired filter vs. potentially missing an all-time
new one...

snip<
DXLab does not explicitly set the memories of any transceiver. - I guess
what I was asking is there a way to have WW open silently? That is just
open the RTTY window when RTTY is clicked and not direct CC to do anything ?

+++That would require the user to remember that WinWarbler hadn't directed
Commander to put the transceiver on the correct frequency in the correct
mode, and later manually direct WinWarbler to do this. I don't believe this
increase in user-perceived complexity is justified; as I pointed out in an
earlier post, Commander provides memories that you can use instead of your
transceiver's memories.

73,

Dave, AA6YQ


Re: New Feature or I Don't Click Enough Spots

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 2:12 PM
To: dxlab@...
Subject: [dxlab] New Feature or I Don't Click Enough Spots


Being a slow and damp day, I have been more active playing with the DXLab's
features than normal. I discovered something I don't recall happening before
and that is when I click on a spot it populates WW and creates an entry in
DXK. The problem is no matter what I do, I can't clear the entry in DXK and
end up logging the Q. After logging the Q in DXK, I go and delete the entry.
Kind of a pain but now I know where the odd contacts are coming from.

By " it populates WW and creates an entry in DXK", I assume you mean "It
populates WinWarbler's 'QSO Info' panel and DXKeeper's Capture window". To
clear the Capture window without logging a QSO, click the Clear button in
its lower-right corner, or strike CTRL-W (for Wipe).

If I've misunderstood your question, please elaborate...
73,

Dave, AA6YQ