No.
The precedence would depend on the direction the scanner is scannIng.
The point is that scanning priority pecedence or preference depends on the scanning direction.
I'm sure you know that now.👍
Wrong.
Conventional priority (when multiple channels are flagged as priority capable) assigns precedence in the order in which the channels are arranged/programmed. Scan direction has no bearing on priority.
A very simple test for anyone who wants to prove this out: Program a few busy channels into a single department. Order them so that the most important channel is first in the list, followed by a few more channels. Set the first channel as priority, then set one of the other channels as priority as well. Enable Priority Scan, then start scanning in the up
↑ direction.
Observe as the scanner stops on a non-priority channel and will start to sample for priority (the dropouts in audio you hear). If you wait long enough, the channel further down the list will go active ("secondary" priority), causing the scanner to leave a non-priority channel. If you wait longer still, you'll probably catch the first channel in the list ("primary" priority) preempt the "secondary" priority channel.
Pay very close attention to the fact that when the scanner stops on the secondary priority channel, it continues to sample for activity on the primary priority channel, however when it lands on the primary priority channel, sampling stops. This is a key piece of info.
Now reverse the scan direction
↓ and observe that the behavior is exactly the same as it was in the other direction. The first channel in the list is still primary priority, and the other channel still secondary priority. The precedence of those channels did not change simply by reversing scan direction.
I scan FDNY this way with Bronx as the primary priority (first channel in the list) and Manhattan as the secondary priority (third channel in the list), and it works exactly as I described regardless of which direction the 536HP is scanning.