9
A Few Things To Remember about Object Oriented
Scanning
Object oriented scanning is completely different from any prior scanning
receiver technology. Accordingly, some users may find it difficult to visualize
and understand how Object Oriented Scanning works. This may be espe-
cially true for users who have become very familiar with more recent scan-
ning receiver technologies.
We suggest that you keep the following “OOUI Tenets” in mind as you pro-
ceed with your study of this manual. If you find yourself confused or stuck
about the basics of Object Oriented Scanning, it may be helpful to review
this section again.
1. The OOUI memory organization is nothing more than a large list of "Scan-
nable Objects".
2. A "Scannable Object" is simply "something that can be scanned", includ-
ing conventional channels, trunking talkgroups, limit searches, service
searches and Spectrum Sweeper setups.
3. In OOUI scanning, there are no "systems", "banks", "groups", "sub-groups"
or "ID lists". There is simply a very large collection of objects, each with
their own attributes. Scannable Objects all exist at the same level or hi-
erarchy within the scanner - no single type of Scannable Object is more
important than another, and Scannable Objects do not have dependen-
cies on or links to other Scannable Objects in order for them to function
properly.
4. The primary method of grouping the collection of objects is by mapping
them to Scan Lists. Mapping a Scannable Object to one or more Scan
Lists does not change the physical location of the object in the memory
system. Even when an object is mapped to one or more Scan Lists, the
object itself has not moved nor changed from what it is - a simple, stand-
alone object that is part of a larger collection.
To Next Page
Loading...
