<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><font size="+1">Ah, more explanation
required.<br>
<br>
I was searching for a good word to use for illustrating what is
going on. I used 'slot'. This is not the 'slot' in the sense
that you mean it.<br>
<br>
For every thing you can create a filter for, there is a "socket"
for input and one for output (the help and user manual try to
explain this in more detail). So for example for spots there is
'spotfilter' (output) and 'input_spotfilter' for input. The
normal 'acc/spot on hf' that you use, as well as the
'user_default' are both output filters because they filter stuff
before the output it to you (the user) <u>from</u> the node. I
cannot see why a normal user would ever use an inpiut filter.
These are used exclusively to filter unwanted input data /
protocol from other nodes <u>into</u> the node. <br>
<br>
So, with that in mind, when you login as a user, one of the
setup things the login process does is to setup all the possible
filters (spots, announce, wcy, wwv, rbn etc etc). It checks in
the following order (using ladder logic - the first condition
that matches sets up the filter 'socket' and the stops looking
for more options).<br>
<br>
1, Has the user set a filter? If so, use that, then exit setup
for that filter.<br>
2, Is there a user_default then use that and exit.<br>
3. Use no filtering for that thing. <br>
<br>
So if you do an "acc/spot on hf", you will have created a spot
filter file (in /spider/local_data/filters/spots/W1NR.pl), you
can read it with an editor - but PLEASE don't modify it (use the
acc/* rej/* commands). When you login, that is the spot filter
that you will get, regardless of whether a user_default exists
or not. <br>
<br>
If this is NOT the case. then please send me both your personal
spot file and also any user_default there might be. <br>
<br>
73 Dirk G1TLH<br>
</font><br>
On 02/12/2020 18:43, Mike McCarthy, W1NR via Dxspider-support
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7dd9f61c-9b7d-1a38-b555-107830125dea@w1nr.net">
<pre class="moz-quote-pre" wrap="">I think I answered my question. It sets the user_default in the filter1
slot.
On 12/2/2020 1:38 PM, Mike McCarthy, W1NR via Dxspider-support wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Thanks Dirk. So which filter slot is "default"? Sounds like a
logout/login is needed to "override" the user_default if you have no
filters defined when you initially set them?
73 de Mike, W1NR
On 12/2/2020 12:16 PM, Dirk Koopman via Dxspider-support wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">The code says, in effect:
On user login:
1. Load user filter into filter slot if it exists.
2. Load user default if the filter slot is empty and a user_default
fillter exists.
before sending something, if the filter slot is is set, then filter it
first.
There is a long standing bug which I have not been able to squash where,
sometimes, if you create a filter and that slot is already in use by the
user_default, then the filter may not take for that session. Logging out
and then in again fixes that. Ditto if you delete a filter.
Dirk G1TLH
On 02/12/2020 16:54, Mike McCarthy, W1NR via Dxspider-support wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I was under the impression that setting a user_default filter could be
over-ridden with user settings. What I am finding is that if a user sets
their own filters with a user_default filter set, I get very broken
filtering results.
Do user_default filters over-ride all others?
73 de Mike, W1NR
_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<br>
</body>
</html>