[Dx4win] DX spot colors revisited

2003-09-04 Thread Paul van der Eijk
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 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?  Sure!  Is it likely to happen?
Probably not. The most requested switch seems to be to choose whether band
spots have priority over mode spots, or vice versa (default right now is mode
over band).

So I hope Paul can fix the priority 3/4 problem (unworked band entity should
have priority over worked mode entity), as well as add this new switch.  This
should satisfy 95% of the users.  If you don't care about band or mode awards,
go into your DXCC prefernces and turn these awards off.

73 - Jim AD1C

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 not confirmed, the unworked entity has priority
 over the worked entity.

The priorities I suggested earlier seem to embody these requirements:

   1 = never worked
   2 = never worked mode
   3 = never worked band
   4 = unconfirmed mode
   5 = unconfirmed band


=
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC
___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win 


Paul van der Eijk (KK4HD)
[EMAIL PROTECTED]
http://www.dx4win.com



[Dx4win] DX spot colors revisited

2003-09-03 Thread Jose ct1aoz
Hi Jim and all others

Yes it makes sence

Can the user define Band or Mode ? It should be implemented also

best 73 de Jose CT1AOZ
[EMAIL PROTECTED]



- Original Message - 
From: Jim Reisert AD1C [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Sent: Tuesday, September 02, 2003 9: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 are
  worked but not confirmed, mode has priority over band.
 
 3.  When one entity is unworked and the other is worked
  but not confirmed, the unworked entity has priority
  over the worked entity.
 
 The priorities I suggested earlier seem to embody these requirements:
 
1 = never worked
2 = never worked mode
3 = never worked band
4 = unconfirmed mode
5 = unconfirmed band
 
 Does this make sense to everyone?
 
 73 - Jim AD1C
 
 --
 Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
 USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
 PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC
 
 ___
 Dx4win mailing list
 Dx4win@mailman.qth.net
 http://mailman.qth.net/mailman/listinfo/dx4win
 


[Dx4win] DX spot colors revisited

2003-09-03 Thread [EMAIL PROTECTED] (J. F. Samuels)
As others have said, I might want to swap 2 and 3, 4 and 5.  So, it must be
a preference setting.

Also, I might not want to see even black spots, much less gray, so would
want to hide them as I do the gray ones.

John, K2CIB


- Original Message - 
From: Jim Reisert AD1C [EMAIL PROTECTED]
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 are
  worked but not confirmed, mode has priority over band.

 3.  When one entity is unworked and the other is worked
  but not confirmed, the unworked entity has priority
  over the worked entity.

 The priorities I suggested earlier seem to embody these requirements:

1 = never worked
2 = never worked mode
3 = never worked band
4 = unconfirmed mode
5 = unconfirmed band

 Does this make sense to everyone?

 73 - Jim AD1C

 --
 Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
 USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
 PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC

 ___
 Dx4win mailing list
 Dx4win@mailman.qth.net
 http://mailman.qth.net/mailman/listinfo/dx4win





[Dx4win] DX spot colors revisited

2003-09-03 Thread Wendell Wyly - W5FL
I doubt that Paul will ever make these colors user programmable for the
priorities.  I think the order you laid out for 1) never worked 2) never
worked mode 3) never worked band will satisfy 90% of the DX community.  The
unconfirmed mode and band are neat touches, also.  Paul spent a period of
several months getting the never worked band as a reality, and that has
helped me more than any other improvement in DX4WIN as getting bands worked
for anyone chasing MIXED, PHONE, and CW (or RTTY) takes a lot of work
without this improvement working properly.  After a while there are not many
never worked left.  The logic used by DX4WIN is pretty straightforward and
as best I can sort it out, depends on the priority order for the searches to
be very quick (and it is).

Yes, I agree with your order.  I confirm DX to the ARRL requirements and do
not care for having to work every band in all modes as that requires working
Dxepeditions too many times, but there are those that want to work every
band on both CW and Phone and RTTY.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
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.  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 not confirmed, the unworked entity has priority
 over the worked entity.

The priorities I suggested earlier seem to embody these requirements:

   1 = never worked
   2 = never worked mode
   3 = never worked band
   4 = unconfirmed mode
   5 = unconfirmed band

Does this make sense to everyone?

73 - Jim AD1C

--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC

___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win



[Dx4win] DX spot colors revisited

2003-09-03 Thread Jim Reisert AD1C
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?  Sure!  Is it likely to happen?
Probably not. The most requested switch seems to be to choose whether band
spots have priority over mode spots, or vice versa (default right now is mode
over band).

So I hope Paul can fix the priority 3/4 problem (unworked band entity should
have priority over worked mode entity), as well as add this new switch.  This
should satisfy 95% of the users.  If you don't care about band or mode awards,
go into your DXCC prefernces and turn these awards off.

73 - Jim AD1C

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 not confirmed, the unworked entity has priority
 over the worked entity.

The priorities I suggested earlier seem to embody these requirements:

   1 = never worked
   2 = never worked mode
   3 = never worked band
   4 = unconfirmed mode
   5 = unconfirmed band


=
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC


[Dx4win] DX spot colors revisited

2003-09-03 Thread Stan Staten
The message seems to be that one size doesn't fit all.  I know
that I have seen similar things to those reported here.  Possibly
it is because I didn't understand the details of how it actually
works, but I found stations I wanted to work way low down in the
priorities (i.e. my priorities did 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 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?  Sure!  Is it likely
to happen?
Probably not. The most requested switch seems to be to choose
whether band
spots have priority over mode spots, or vice versa (default right
now is mode
over band).

So I hope Paul can fix the priority 3/4 problem (unworked band
entity should
have priority over worked mode entity), as well as add this new
switch.  This
should satisfy 95% of the users.  If you don't care about band or
mode awards,
go into your DXCC prefernces and turn these awards off.

73 - Jim AD1C

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 not confirmed, the unworked entity has priority
 over the worked entity.

The priorities I suggested earlier seem to embody these
requirements:

   1 =3D never worked
   2 =3D never worked mode
   3 =3D never worked band
   4 =3D unconfirmed mode
   5 =3D unconfirmed band


=3D=3D=3D=3D=3D
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1
70DC
___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win




[Dx4win] DX spot colors revisited

2003-09-02 Thread Jim Reisert AD1C
--- 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. Perhaps, it is a matter of personal choice and Paul made a 
 decision that an unconfirmed mode should take precedence over a new band. 

I think that an all-time new band *should* have priority over an unconfirmed
mode.  That makes good sense -- you would rather know it's something that you
have NEVER worked before.

However, I also think that when both mode-country and band-country are worked
but neither is confirmed, that once again MODE should have priority over BAND,
since there are fewer mode countries to work. I think this case is rare,
however.

So the first few priority levels work out as follows:

  1 = never worked
  2 = never worked mode
  3 = never worked band
  4 = unconfirmed mode
  5 = unconfirmed band

Does this make sense? The priorities above also interleave in a natural way.

73 - Jim AD1C


=
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC


[Dx4win] DX spot colors revisited

2003-09-02 Thread Anthony R Gargano N2SS
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. 
Tony N2SS

At 03:27 PM 9/2/2003, Jim Reisert AD1C wrote:
--- 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. Perhaps, it is a matter of personal choice and Paul made a
  decision that an unconfirmed mode should take precedence over a new band.

I think that an all-time new band *should* have priority over an unconfirmed
mode.  That makes good sense -- you would rather know it's something that you
have NEVER worked before.

However, I also think that when both mode-country and band-country are worked
but neither is confirmed, that once again MODE should have priority over BAND,
since there are fewer mode countries to work. I think this case is rare,
however.

So the first few priority levels work out as follows:

   1 = never worked
   2 = never worked mode
   3 = never worked band
   4 = unconfirmed mode
   5 = unconfirmed band

Does this make sense? The priorities above also interleave in a natural way.

73 - Jim AD1C


=
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC




[Dx4win] DX spot colors revisited

2003-09-02 Thread Jim Reisert AD1C
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 not confirmed, the unworked entity has priority
 over the worked entity.

The priorities I suggested earlier seem to embody these requirements:

   1 = never worked
   2 = never worked mode
   3 = never worked band
   4 = unconfirmed mode
   5 = unconfirmed band

Does this make sense to everyone?

73 - Jim AD1C

--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC



[Dx4win] DX spot colors revisited

2003-09-02 Thread Dave Jaksa
Jim,

I understand your logic but it doesn't fit everybody.  While I'm pretty
serious about Mixed, Phone, and CW DXCC, I have never fully gotten into
chasing band countries for the single band DXCC awards.  I have =
absolutely
nothing against chasing band countries, it was just a personal choice I =
made
not to do it.

I got my 5BDXCC back in 1984 before the ARRL kept band country records.
When the single band awards came out I decided it was too much trouble =
to
round up all the cards and send them in again.  Guess you could make the
observation that I was just too lazy! =20

So, for me the following works best:

1 =3D Never Worked
2 =3D Never Worked Mode
3 =3D Unconfirmed Mode
4 =3D Never Worked Band
5 =3D Unconfirmed Band

I think making it user configurable would be the best solution.  That =
way
everybody is happy.=20

73,
Dave, W0VX

-Original Message-
From: [EMAIL 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.  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 not confirmed, the unworked entity has priority
 over the worked entity.

The priorities I suggested earlier seem to embody these requirements:

   1 =3D never worked
   2 =3D never worked mode
   3 =3D never worked band
   4 =3D unconfirmed mode
   5 =3D unconfirmed band

Does this make sense to everyone?

73 - Jim AD1C

--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC

___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win




[Dx4win] DX spot colors revisited

2003-09-02 Thread Jim Reisert AD1C
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, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC



[Dx4win] DX spot colors revisited

2003-09-02 Thread Mel Martin
Only if Alert Unconfirmed is unchecked...

If it's checked it's...
1 = new DXCC never confirmed OR NewDXCC never worked
2 = never worked mode
3 = never worked band
4 = unconfirmed mode
5 = unconfirmed band

Which doesn't seem entirely logical to me...

OTOH, if you don't check Alert Unconfirmed you don't draw attention to
all-time new unconfirmed, which you may well want to work again, especially
if it's a different station.

1 = never worked
2 = never worked mode
3 = never worked band
4 = unconfirmed mode
5 = unconfirmed band

- Original Message - 
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 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 not confirmed, the unworked entity has priority
  over the worked entity.

 The priorities I suggested earlier seem to embody these requirements:

1 = never worked
2 = never worked mode
3 = never worked band
4 = unconfirmed mode
5 = unconfirmed band

 Does this make sense to everyone?

 73 - Jim AD1C

 --
 Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
 USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
 PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC

 ___
 Dx4win mailing list
 Dx4win@mailman.qth.net
 http://mailman.qth.net/mailman/listinfo/dx4win