Versions Compared

Old Version 7

changes.mady.by.user Gleb Matskevich

Saved on

compared with

New Version 8

changes.mady.by.user Evgeniya Kononova

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • empty field—search across layers is not limited;
  • 0—related layers are not taken into account during search, that is, in case of alarm, only the layer on which the alarm occurred will blink;
  • >0—indicates the number of layers through which the search will be performed. For example, the Map has 6 interconnected layers and the alarm appeared on the 3rd layer. If the key value=1, the alarm will blink on layer 3, as well as on layers 2 and 4.
Info
titleNote

The Search depth parameter in the interface is similar to the AlarmLinkSearchDepthKey registry key (see Registry keys reference guide): if the key was created earlier than the interface parameter was set, then the field is filled in based on the key value.

If the key is created on the Remote Client, then the value from the key will be used on the Remote Client, regardless of the Search depth parameter value specified on the Server. If a key is not created on the Remote Client, then the Server Search depth is used everywhere.

Examples:

  1. The Search depth is set to 1 on the Server; the key is not created on the Remote Client. Result: on the Server and on the Remote Client, the search depth is 1.
  2. The Search depth is set to 1 on the Server, the AlarmLinkSearchDepthKey with the value 2 is created on the Remote Client. Result: the search depth on the Server is 1, on the Remote Client it is 2.

The recursive search of objects on the Map is a type of search when it is possible to switch to a layer with an alarm from a layer where the link is located by sequential transitions to adjacent layers, using sequential links. If the Search for the shortest path checkbox is set (5), the shortest possible path to the layer with an alarm will be automatically selected.

...