Jim,
The next release has an extra priority added, so I can deal with the
band / mode combinations too. The rest is as you suggested,
with priority given to the 'mode'. This stuff gets complicated!
Paul
At 01:43 PM 9/3/03 -0700, Jim Reisert AD1C wrote:
Thanks for the feedback. My prior
Subject: Re: [Dx4win] DX spot colors revisited
I think I boiled the priorities down to three simple rules:
1. All-time never worked has the highest priority.
2. When both entities are unworked or both entities are
worked but not confirmed, mode has priority over band.
3. When one
]
To: dx4win@mailman.qth.net
Sent: Tuesday, September 02, 2003 4:23 PM
Subject: Re: [Dx4win] DX spot colors revisited
I think I boiled the priorities down to three simple rules:
1. All-time never worked has the highest priority.
2. When both entities are unworked or both entities
@mailman.qth.net
Subject: Re: [Dx4win] DX spot colors revisited
I think I boiled the priorities down to three simple rules:
1. All-time never worked has the highest priority.
2. When both entities are unworked or both entities are
worked but not confirmed, mode has priority over band.
3. When one
Thanks for the feedback. My prior analysis is included at the end for those
who can't remember. I think it was Mel VE2DC who pointed out that there is an
option to highlight unconfirmed new entities as if they are unworked, so #1
changes a little.
Would it be nice to be fully configurable?
not match those which 6.02 has
build in).
73 Stan, N3HS
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Reisert
AD1C
Sent: Wednesday, September 03, 2003 4:43 PM
To: dx4win@mailman.qth.net
Subject: RE: [Dx4win] DX spot colors revisited
Thanks
--- Anthony R Gargano N2SS [EMAIL PROTECTED] wrote:
Pete, I would agree that a new mode should take precedence over a new band.
However, this is not the situation that I have described. In what I have
described an unconfirmed mode (not a new mode) is taking precedence over a
new band.
Agreed. If it were user definable, that 's how I would set it up for my own
personal operating priorities. The interesting thing is that in the current
release the color codes and numerical assignments imply those priorities
but for whatever reason the program logic gives 4 precedence over 3.
I think I boiled the priorities down to three simple rules:
1. All-time never worked has the highest priority.
2. When both entities are unworked or both entities are
worked but not confirmed, mode has priority over band.
3. When one entity is unworked and the other is worked
but
PROTECTED] [mailto:[EMAIL PROTECTED] =
On
Behalf Of Jim Reisert AD1C
Sent: Tuesday, September 02, 2003 3:23 PM
To: dx4win@mailman.qth.net
Subject: Re: [Dx4win] DX spot colors revisited
I think I boiled the priorities down to three simple rules:
1. All-time never worked has the highest priority.
2
At 06:29 PM 9/2/2003, Jose ct1aoz wrote:
Can the user define Band or Mode ? It should be implemented also
Yes, Jose, I think that is a good idea as well and seems to be what people
want.
73 - Jim AD1C
--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933,
-
From: Jim Reisert AD1C [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Sent: Tuesday, September 02, 2003 16:23
Subject: Re: [Dx4win] DX spot colors revisited
I think I boiled the priorities down to three simple rules:
1. All-time never worked has the highest priority.
2. When both
12 matches
Mail list logo
