No? Just not having that scanlist enabled doesn't make the TGs in that omitted scanlist to be skipped. The wildcards will still produce all TGs without excluding any of the TGs from another scanlist. That would be one crazy scanner.
/Ubbe
Allow me to be more specific - and you can try this test on your own --
- Import a system and all of it's talkgroups
- Assign all of those known talkgroups to Scanlist 1
- Create a WILDCARD talkgroup object attached to that same system and assign it (alone) to Scanlist 2
In this scenario, if you scan both Scanlist 1 and Scanlist 2, the radio will stop on
all talkgroups including (potentially) unknown/undocumented "wildcard" talkgroups (FWIW: for this test, you can force wildcard activity by deleting a busy known talkgroup).
If you disable Scanlist 1 (leaving Scanlist 2 enabled), the radio will only stop on wildcard (unknown, undocumented) talkgroups.
As you can see, in the above programming/scenario, if you disable Scanlist 1, you've effectively locked out all known talkgroups.
NOW - for something completely different, if you create the same system TWICE - one with all known talkgroups assigned to Scanlist 1 and the other with only a wildcard assigned to Scanlist 2, that would be a completely different scenario with a completely different result... disabling Scanlist 1 would have no affect on the wildcard in Scanlist 2. Scanlist 1 would only stop on known talkgroups and display their alpha tags. Scanlist 2 would stop on those same talkgroups and any previously unknown, undocumented talkgroups but none would have any labels/alpha tags.