<html>
At 9/21/2002 02:07 PM +0100, Dirk Koopman wrote:<br>
<blockquote type=cite class=cite cite>These are not new ...<br><br>
I will discuss some of the issues...<br><br>
On Sat, 2002-09-21 at 02:17, Hank Kohl K8DD wrote:<br>
> If there is .....<br>
> <br>
> DX spots come down the screen - oldest at the top and newest at the
bottom.<br>
> SHow/DX is newest at the top and oldest at the bottom.<br>
> Can SHow/DX put the oldest at the top and newest at the
bottom.<br>
> I think it would help with
NA and CT packet windows.<br><br>
Not certain it will help NA and CT as they are designed (I presume)
for<br>
standard behaviour. However a flag could be created which determines
the<br>
order in which things like DIR, SH/DX etc display their output.<br><br>
Is one flag enough? Because you will notice the DIR outputs stuff in
the<br>
opposite way to SH/DX and friends.</blockquote><br>
<b>My primary thought was that SH/DX should be in the same chronological
order as DX spots coming down the page.<br><br>
I noticed the DIR outputs down chronologically - the way I'd think it
would.<br><br>
If it were a flag, I'd like to see it as a default_user or default_node
flag.<br><br>
<br>
</b><blockquote type=cite class=cite cite>> <br>
> Same for SHow/WWV & WCY<br>
> <br>
> DX spots beep but Talk's don't.<br>
> Can Talk's do a double beep?<br><br>
Not easily from the cluster nodes point of view. </blockquote><br>
<b>Add 2 CTRL-G's to the TALK single line message. But not the TALK
mode messages.<br><br>
</b><blockquote type=cite class=cite cite>This is really a client<br>
issue. If someone (not me) wants to write a better client, there is
a<br>
very simple protocol between client and node which I will be happy
to<br>
document and (if necessary) extend.<br><br>
> Announcements (EU Talk)
can remain silent!<br>
> <br><br>
acc/ann by_zone 4,5,6</blockquote><br>
<b>I meant silent as in no beep! It was a subtle comment about some
of the EU stations who use ANNounce FULL as talk messages to other
stations! And that's why my users do set the announce
filter!<br><br>
</b><blockquote type=cite class=cite cite> <br>
> When I'm connected to a node that sends all spots - from all over
the world -<br>
> I do a SEt/FILTer node_default by_dxcc
w,xe,ve,kp,kl<br>
> and SEt/FILTer
user_default by_dxcc w,xe,ve,kp,kl<br>
> it works fine .... users don't get spots outside of North America
.... but when<br><br>
acc/spots xxxx_default by_zone 4,5,6 <br><br>
would probably be more efficient.</blockquote><br>
<b>True .... probably easier to type, too!<br><br>
<br>
</b><blockquote type=cite class=cite cite>> I do
a SHow/DX I get spots from all
over the world.<br>
> Can DX Spider (with those filters set) dump non North American spots
in the bit<br>
> bucket?<br>
> <br><br>
Now this is a bit difficult. The answer is: yes it could - but -
what<br>
happens if you want to override this behaviour? what if, as an
average<br>
user, you have forgotten that you have such a filter on and are
puzzled<br>
about why you see all these EU announces about some juicy DX and
you<br>
can't see any reference to it in sh/dx?<br><br>
I have erred on the side of safety and given all information. <br><br>
You can sort of filter it by doing something like:-<br><br>
sh/dx on 20m by w dxcc<br><br>
I could add a keyword that makes sh/dx run the result thru your
spot<br>
filter.<br><br>
Could have a command or an alias that does it automatically
(sh/dxf?).</blockquote><br>
<b>A command or alias could work. sh/dxf would output sh/dx using
the users acc/spots filter. That way the users who do want to see
all 2000+ spots from all over the world can, and the ones who want zones
1,2,3,4,5,6,7,8 spots can have them too.<br><br>
I guess the question came from the old DOS Ak1a cluster. From what
I remember, you could set up a file with country numbers (from wpxloc)
that would be the countries of origin that you want to accept spots from
for users and DX.DAT. But it would pass all spots on to the next
node in line.<br><br>
<br>
</b><blockquote type=cite class=cite cite>> Would be nice if
SHow/NODES could give a list of nodes that you have put <br>
> in, and<br>
> what kind of a node (ar, ak1a, spider, etc) it is.<br>
> SHow/NODES AR all the ar nodes<br>
> SHow/NODES AK1A all the ak1a nodes
etc, etc, etc<br>
> <br><br>
This could be done, but is it really interesting? I can't remember
the<br>
last time I did a SH/NODES. Afterall, getting upwards of a 1000
nodes<br>
on-line the result is information overload.</blockquote><br>
<b>Like SHow/BADWords it is not something that you would use every
day. <br>
"sh/node all" does show all nodes, but (except for previously
definde nodes) it defines them all as AK1A. 5-4.99 is arcluster,
5-4.<55 is AK1A, 5449 or 5450 is Spider, etc. Could spider
define the node by version? <br><br>
73 Hank K8DD <br><br>
<br>
</b><blockquote type=cite class=cite cite>Dirk G1TLH<br><br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
Dxspider-support@dxcluster.org<br>
<a href="http://www.tobit.co.uk/mailman/listinfo/dxspider-support" eudora="autourl">http://www.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</blockquote></html>