I apologize if this has been mentioned, but I do not think it has...
When going through the scanlists left to right, it may be easy to forget some less-often used scanlists. A good way I found to "name" the scanlists is to create some dummy talkgroups with the names.
You have to use objects 1-20, as the lowest numbered object is displayed when changing scanlists (using the left and right arrows.)
So, what I did is name object 1 to be the name of scanlist 1, using talkgroup 0, and locking the object out. It is a member of scanlist 1 only.
Object 2 is named my scanlist 2 name, N.Simulcast All. It is talkgroup 0, and it is locked out. It is a member of scanlist 2 only.
... And so on.
What this does is create a non-scanned object, named the same as your scanlist, and is the lowest object number in the scanlist, making this the first object shown when scrolling left and right through scanlists.
Helps me remember!
-- Kevin
When going through the scanlists left to right, it may be easy to forget some less-often used scanlists. A good way I found to "name" the scanlists is to create some dummy talkgroups with the names.
You have to use objects 1-20, as the lowest numbered object is displayed when changing scanlists (using the left and right arrows.)
So, what I did is name object 1 to be the name of scanlist 1, using talkgroup 0, and locking the object out. It is a member of scanlist 1 only.
Object 2 is named my scanlist 2 name, N.Simulcast All. It is talkgroup 0, and it is locked out. It is a member of scanlist 2 only.
... And so on.
What this does is create a non-scanned object, named the same as your scanlist, and is the lowest object number in the scanlist, making this the first object shown when scrolling left and right through scanlists.
Helps me remember!
-- Kevin