A hierarchical navigation linkage highlighting interaction method, device, and storage medium for a monitoring system.

By splitting the screen names in the monitoring system and matching them with navigation menu buttons, setting highlighted states and color-coded permission prompts, the problems of getting lost in multi-level navigation menus and unintuitive permission display are solved, improving the operational efficiency and security of the monitoring system.

CN123123538APending Publication Date: 2026-11-17HUANENG LONGKAIKOU HYDROPOWER CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610974978.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-01
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing monitoring system's multi-level navigation menus lack linked highlight feedback, leading to disorientation of operation paths and untimely and unintuitive display of operation permission status, which affects operational efficiency and security.

Method used

The system obtains the current screen name, performs hierarchical segmentation, matches the unit and sub-module identifier segments with the navigation menu buttons, and simultaneously sets the highlight status. At the same time, it queries the operation right status data to generate color permission prompts.

Benefits of technology

It enables rapid identification of navigation levels and paths, improves the intuitiveness and security of navigation interaction, avoids the risk of misoperation, and improves operational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123538A_ABST
    Figure CN123123538A_ABST
Patent Text Reader

Abstract

This invention relates to the field of monitoring technology, and in particular to a hierarchical navigation linkage highlighting interaction method, device, equipment, and computer storage medium for a monitoring system. The invention acquires the current screen name and splits it into a unit identifier segment and a sub-module identifier segment; according to a preset mapping relationship, the two identifier segments are matched with the unit button and sub-module button in the navigation menu, respectively; the successfully matched buttons are synchronously highlighted, forming full-path visual feedback; and operation permission status data is queried to generate colored prompt information containing the unit identifier and permission type. This invention realizes automatic linkage highlighting of multi-level navigation menus and visual display of operation permissions, solving the problems of easy getting lost on the operation path and untimely display of permissions in the prior art, and improving the accuracy and security of navigation interaction.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of surveillance technology, and in particular to a hierarchical navigation linkage highlighting interaction method, apparatus, equipment, and computer storage medium for a surveillance system. Background Technology

[0002] As a core device ensuring the safe and stable operation of generating units, the SCADA / DCS monitoring system for hydropower plants is widely used in scenarios involving frequent switching between multiple levels of screens, from the overall plant to unit, unit monitoring, and process control. Among related technologies, a basic screen switching system is constructed through the collaborative operation of static menu navigation and screen transitions. Specifically, this system covers the entire process from menu click to screen loading, including key aspects such as menu display, screen transitions, and status maintenance.

[0003] However, existing navigation interaction methods directly use static menus without selection status feedback or parent-child menu linkage highlighting mechanisms. This may cause operators to be unable to quickly identify the current level and path when switching between multiple screens, requiring repeated verification of screen names, resulting in low operational efficiency and easy misoperation due to visual confusion. At the same time, the operation right status needs to be manually queried, lacking intuitive color differentiation prompts, thus affecting the safety and efficiency of operation and maintenance, and failing to meet the high requirements of intuitive and convenient navigation interaction in the industrial scenario of hydropower plants. Summary of the Invention

[0004] Therefore, the technical problem to be solved by the present invention is to overcome the problems in the prior art where the lack of linked highlight feedback in multi-level navigation menus leads to the loss of operation path and the untimely and unintuitive display of operation permission status.

[0005] To address the aforementioned technical problems, this invention provides a hierarchical navigation linkage highlighting interaction method for a monitoring system, comprising:

[0006] Obtain the complete name of the currently displayed screen, and perform hierarchical splitting of the complete name to obtain the unit identifier segment and the submodule identifier segment; According to the preset mapping relationship, the unit identifier segment and the sub-module identifier segment are matched with the unit button identifier and the sub-module button identifier in the navigation menu, respectively; The display attributes of the successfully matched unit buttons and sub-module buttons are simultaneously set to highlighted state to form a full-path visual feedback from the unit level to the sub-module level. The system queries the current system operation authority status data and generates a prompt message containing the unit identifier and permission type based on the operation authority status data, displaying the prompt message in different colors.

[0007] Preferably, the hierarchical splitting of the complete name includes: The complete name is split using a string splitting function with a preset delimiter to extract the unit identifier segment and the submodule identifier segment.

[0008] Preferably, the preset mapping relationship includes a unit dictionary and a submodule dictionary. The unit dictionary contains a mapping between each unit identifier and its corresponding unit button identifier, and the submodule dictionary contains a mapping between each submodule identifier and its corresponding submodule button identifier.

[0009] Preferably, the step of synchronously setting the display attributes of the successfully matched unit button and submodule button to a highlighted state includes: Call the interface control property setting interface to set the text color of the successfully matched unit button and submodule button to the preset highlight color.

[0010] Preferably, the step of querying the current system's operation right status data and generating a prompt message containing the unit identifier and permission type based on the operation right status data, and displaying the prompt message in different colors, includes: The operation right type value is obtained through the system's real-time data reading interface; The corresponding permission type and display color are determined based on the operation right type value. A prompt text containing the unit identifier and permission type is generated by concatenating the two, and the prompt text is refreshed and displayed with the specified display color.

[0011] Preferably, before obtaining the full name of the currently displayed screen, the method further includes: Set the encoding format to be compatible with Chinese characters to ensure encoding compatibility for Chinese screen names and menu names.

[0012] Preferably, the highlight state is maintained continuously during the current session period, and the screen name is automatically re-parsed to update the highlight state when the screen switches; and / or, the highlight state setting is executed using an asynchronous rendering mechanism, which is executed in parallel with the system's real-time data acquisition and screen refresh.

[0013] The present invention also provides a hierarchical navigation linkage highlighting interactive device for a monitoring system, comprising: The screen name parsing module is used to obtain the complete name of the currently displayed screen and to perform hierarchical splitting of the complete name to obtain the unit identifier segment and the sub-module identifier segment; The menu matching module is used to match the unit identifier segment and the sub-module identifier segment with the unit button identifier and the sub-module button identifier in the navigation menu, respectively, according to a preset mapping relationship. The linked highlight module is used to synchronously set the display attributes of the successfully matched unit buttons and sub-module buttons to the highlighted state, so as to form a full-path visual feedback from the unit level to the sub-module level. The permission prompt module is used to query the current system's operation permission status data and generate prompt information containing the unit identifier and permission type based on the operation permission status data, and display the prompt information in different colors.

[0014] This invention also provides a hierarchical navigation linkage highlighting interactive device for a monitoring system, comprising: Memory, used to store computer programs; A processor is used to implement the hierarchical navigation linkage highlighting interaction method steps of the above-mentioned monitoring system when executing the computer program.

[0015] The present invention also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the hierarchical navigation linkage highlighting interaction method of the above-described monitoring system.

[0016] The technical solution of the present invention has the following advantages over the prior art: The hierarchical navigation linkage highlighting interaction method of the monitoring system described in this invention obtains the current screen name and performs hierarchical decomposition. The resulting unit identifier and sub-module identifier are then matched with corresponding buttons in the navigation menu, and the successfully matched unit and sub-module buttons are simultaneously highlighted. This forms a full-path visual feedback from the unit level to the sub-module level, allowing operators to quickly and accurately identify the current navigation level and complete path without repeatedly checking the screen name, effectively avoiding the risk of misoperation due to path confusion. Simultaneously, by querying operation permission status data and generating color-coded prompts containing unit identifiers and permission types, the abstract operation permission status is presented in an intuitive visual way, enabling operators to immediately grasp the current operation permission ownership, significantly improving the intuitiveness, operational efficiency, and security of navigation interaction. Attached Figure Description

[0017] To make the content of this invention easier to understand, the invention will be further described in detail below with reference to specific embodiments and accompanying drawings, wherein: Figure 1 This is a flowchart illustrating the implementation of a hierarchical navigation linkage highlighting interaction method for a monitoring system provided by the present invention. Figure 2 This is a structural block diagram of a hierarchical navigation linkage highlighting interactive device for a monitoring system provided in an embodiment of the present invention. Detailed Implementation

[0018] The core of this invention is to provide a hierarchical navigation linkage highlighting interaction method, device, equipment, and computer storage medium for a monitoring system, which effectively solves the problems in the prior art where the lack of linkage highlighting feedback in multi-level navigation menus leads to lost operation paths, and the operation permission status is not displayed in a timely and intuitive manner.

[0019] To enable those skilled in the art to better understand the present invention, the invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0020] Please refer to Figure 1. Figure 1 The flowchart illustrates the implementation of a hierarchical navigation linkage highlighting interaction method for a monitoring system provided by this invention; the specific operation steps are as follows: S101: Obtain the complete name of the currently displayed screen, and perform hierarchical splitting of the complete name to obtain the unit identifier segment and the sub-module identifier segment; In the hierarchical navigation interaction of the monitoring system, to determine the current user's specific navigation location, it is first necessary to obtain the complete name of the currently displayed screen. This complete name typically contains key information that uniquely identifies the hierarchical structure to which the current screen belongs. For example, it can be constructed by concatenating the identification information of the unit level and sub-module level with specific separators according to preset naming rules. By performing a hierarchical splitting operation on the obtained complete name, such as parsing based on the preset separators or fixed field positions, the unit identifier segment representing the unit level to which the current screen belongs, and the sub-module identifier segment representing the specific function or monitoring area to which the current screen belongs, can be extracted from the name. This splitting process aims to deconstruct the composite screen name into independent fields with clear hierarchical meanings, thereby providing accurate positioning basis for subsequent menu matching and highlight rendering. As one implementation method, the complete string name of the current screen can be obtained in real time through the interface provided by the system, and the string splitting function can be used to split the name into unit segments, sub-module segments, and other auxiliary segments according to preset separators such as hyphens, thereby obtaining specific identification information such as "Unit 1" and "Unit Monitoring".

[0021] Through the above steps, the hierarchical path information corresponding to the current screen can be automatically and in real time without manual intervention or additional queries, providing a reliable data foundation for subsequent accurate navigation linkage highlighting, thereby improving the automation level and response speed of navigation interaction.

[0022] S102: According to the preset mapping relationship, the unit identifier segment and the sub-module identifier segment are matched with the unit button identifier and the sub-module button identifier in the navigation menu, respectively; Based on a pre-defined mapping relationship, the split unit identifier segment and sub-module identifier segment are matched with the unit button identifier and sub-module button identifier in the navigation menu, respectively. This step aims to establish a correspondence between screen hierarchy information and interface navigation controls. Specifically, the system pre-constructs an identifier mapping library containing at least unit and sub-module levels. This library defines the correspondence between each unit identifier and the unique identifier of the corresponding unit button in the navigation menu, as well as the correspondence between each sub-module identifier and the unique identifier of the corresponding sub-module button. After obtaining the unit identifier segment and sub-module identifier segment through screen name splitting, the system uses these two identifier segments as query keys to search the mapping library to determine the navigation button that matches the current screen level. This matching process can be implemented based on precise string comparison or a pre-defined key-value pair lookup mechanism, thereby ensuring that the unit button and sub-module button corresponding to the currently displayed screen can be accurately located from numerous navigation menu items. As one implementation method, a generator set dictionary and a submodule dictionary can be pre-set. The generator set dictionary contains a mapping between each generator set name and its corresponding button ID, and the submodule dictionary contains a mapping between each submodule name and its corresponding button ID. Matching is accomplished through dictionary lookup.

[0023] This step establishes a mapping and matching mechanism between screen hierarchy information and navigation control identifiers, enabling automatic identification and positioning of the current operation path. This provides a precise control object basis for subsequent linked highlight rendering, avoiding the tedious process of manual searching and confirmation, and significantly improving the automation level and response speed of navigation interaction.

[0024] S103: Synchronously set the display attributes of the successfully matched unit button and submodule button to the highlighted state to form a full-path visual feedback from the unit level to the submodule level. After matching the identifiers of the unit buttons and submodule buttons, this step aims to establish a coherent visual path in the user interface extending from the unit level to the submodule level by synchronously adjusting the display attributes of the successfully matched navigation menu items. Specifically, this method calls the attribute setting interface of the interface controls to simultaneously set the specific display attributes of the currently determined unit-level and submodule-level buttons corresponding to the current display screen to a visual state that distinguishes them from other unselected menu items, i.e., a highlighted state. This highlighted state setting does not act in isolation on a single menu item, but rather coordinates the operation of parent and child-level menu items, so that when a user enters a submodule screen, the parent unit menu item and the current submodule menu item can be highlighted synchronously, thus forming a clear and complete path indication in the navigation bar. This highlighted state can be manifested as changes in visual attributes such as text color, background color, border style, or icon status. Its core is to intuitively reflect the hierarchical relationship and navigation path of the current operation through unified visual markings. As one implementation method, the text color attribute of the successfully matched unit button and sub-module button can be synchronously set to a preset highlight color, such as red, by calling the property setting interface of the interface control. This enables the linked highlight rendering of the parent and child menus, forming a full-path visual feedback from the unit to the sub-module.

[0025] By synchronizing the display attributes of the successfully matched unit buttons and submodule buttons to a highlighted state, this method can construct a coherent visual path from the unit level to the submodule level in the navigation menu. This allows operators to quickly and accurately identify the current navigation level and complete path without relying on repeated verification of screen names, significantly improving the intuitiveness and operational efficiency of navigation interaction and effectively avoiding the risk of misoperation caused by getting lost.

[0026] S104: Query the current system's operation right status data, and generate a prompt message containing the unit identifier and permission type based on the operation right status data, displaying the prompt message in different colors.

[0027] In this method, the current system's operational authority status data is queried, and a prompt message containing the unit identifier and permission type is generated based on this data. This prompt message is displayed in different colors, aiming to present the system's operational authority status to operators in an intuitive visual manner. Specifically, the method obtains the operational authority status data associated with a specific unit by calling the system's real-time data query interface. This data typically represents different permission types in numerical or code form, such as local power plant operational authority, central control center operational authority, or other types of operational authority. After obtaining this status data, the method associates it with predefined unit identifier information and automatically generates a structured prompt message that clearly indicates the unit currently possessing operational authority and the specific permission type. To further enhance the information's recognizability and intuitiveness, the method assigns different color attributes to the generated prompt message based on the obtained operational authority status data, allowing operators to quickly and accurately identify the current operational authority without additional querying or judgment, simply through visual means. As one implementation method, real-time operation right status data can be read through the system interface, and the color of the prompt text can be set according to the returned value (e.g., 0 represents power plant, 1 represents centralized control, and others represent other permissions). At the same time, the prompt text in the format of "XX unit operation right: XXX" can be generated and refreshed for display.

[0028] This step significantly improves the readability and efficiency of accessing operation permission information by transforming abstract operation permission status data into intuitive prompts with color coding. This enables operators to grasp the current operation permission ownership in a timely and accurate manner, thereby effectively avoiding operational security risks caused by misjudgment of permissions and improving the security and convenience of monitoring system operation.

[0029] Based on the above embodiments, in some embodiments, the hierarchical splitting of the complete name includes: The complete name is split using a string splitting function with a preset delimiter to extract the unit identifier segment and the submodule identifier segment.

[0030] In this embodiment, the process of hierarchically splitting the complete name in step S101 is as follows: First, the complete name of the currently displayed screen is obtained through the system-provided interface `graph.CurGraphName()`. This name follows a preset naming convention, such as "Unit 1 - Unit Monitoring - XXX", where each level is separated by a hyphen. After obtaining the complete name, the string splitting function `split("-")` is called to split the complete name using hyphens as separators, resulting in a string array. The first element of this array is the unit identifier segment, such as "Unit 1"; the second element is the submodule identifier segment, such as "Unit Monitoring"; subsequent elements are auxiliary segments and are not processed in this step. To ensure that Chinese screen names are not garbled during the splitting process, the encoding format is set to `gb18030` during program initialization, thereby ensuring the accuracy of the splitting results. If the screen name does not conform to the preset format (such as missing separators or missing levels), subsequent splitting and highlighting operations are not performed to maintain system stability. After the split is completed, the extracted unit identifier segment and submodule identifier segment will be used as output for menu ID matching in subsequent steps.

[0031] By employing the hierarchical splitting method based on the string splitting function described above, automated and accurate parsing of screen names is achieved. Key unit and sub-module identifiers can be extracted from the complete name without manual intervention, providing accurate input data for subsequent menu matching and highlight rendering. This splitting method is simple and efficient, and its reliability in Chinese environments is ensured through encoding compatibility processing, further improving the real-time performance and accuracy of navigation interaction.

[0032] Based on the above embodiments, in some embodiments, and in this embodiment, the specific implementation of obtaining the full name of the currently displayed screen in step S101 is as follows. First, the system obtains the full name string of the currently active screen window in real time by calling the native interface `graph.CurGraphName()` provided by the monitoring system's host computer platform. This interface call does not rely on any manual user input or additional configuration; its input source is the title attribute of the current screen within the system, ensuring that the obtained screen name is completely consistent with the screen currently being operated by the operator, and has millisecond-level real-time response capability. The obtained full name is a string conforming to a preset naming convention, such as "Unit 1 - Unit Monitoring - XXX", which contains multiple fields used to identify the unit level and submodule level, connected by a specific separator (such as a hyphen "-"). Subsequently, the system performs a hierarchical splitting operation on the full name string. Specifically, the string splitting function `split("-")` is used, with a hyphen as the separator, to split the full screen name into a string array. Taking "Unit 1 - Unit Monitoring - XXX" as an example, the resulting array after splitting contains three elements. The first element, "Unit 1," is the unit identifier segment; the second element, "Unit Monitoring," is the submodule identifier segment; and the third and subsequent elements are auxiliary segments used to further distinguish specific screens that are not the core focus of this step. Through this processing, the system transforms the original screen names, which cannot be directly used for menu matching, into structured, identifiable unit identifier segments and submodule identifier segments, providing accurate input data for subsequent menu ID matching steps. In one possible implementation, to ensure compatibility with Chinese screen names, the system pre-sets the encoding format to `gb18030` before splitting to avoid Chinese character parsing errors caused by encoding issues, thereby ensuring the accuracy and stability of the splitting results.

[0033] This specific implementation method achieves automatic, real-time, and accurate acquisition and parsing of the current screen name by calling the system's native interface `graph.CurGraphName()` and combining it with string splitting technology. No manual intervention or additional configuration is required, which provides a reliable data foundation for subsequent menu linkage highlighting and significantly improves the automation level and response speed of navigation interaction.

[0034] Based on the above embodiments, in some embodiments, before obtaining the full name of the currently displayed screen, the method further includes: Set the encoding format to be compatible with Chinese characters to ensure encoding compatibility for Chinese screen names and menu names.

[0035] In this embodiment, before step S101, encoding compatibility processing is first performed to ensure the accuracy of subsequent parsing of Chinese screen names and menu names. Specifically, by calling the system encoding setting interface, the encoding format of the current program is set to gb18030. This encoding format can effectively support the complete representation of Chinese characters, avoiding garbled characters or character truncation problems when splitting and matching strings containing Chinese characters in subsequent operations. The input source is the system's default encoding configuration, the processing action is to switch the encoding format to gb18030 through the encoding setting command, and the output result is that the character encoding in the program's running environment is uniformly set to the gb18030 standard. After completing the encoding setting, the system obtains the complete name of the currently displayed screen through the graphical interface graph.CurGraphName(), and the string returned by this interface is the input source. Subsequently, a hierarchical splitting operation is performed on the complete name, specifically using the string splitting function split("-"), with the preset separator "-" as the boundary, splitting the screen name into multiple fields. For example, for the screen name "Unit 1 - Unit Monitoring - XXX", after splitting, we get the unit identifier segment "Unit 1" and the submodule identifier segment "Unit Monitoring", as well as other auxiliary segments. The output of this splitting action is two key fields, namely the unit identifier segment and the submodule identifier segment, which serve as the input for the subsequent step S2. Through the above encoding compatibility processing and hierarchical splitting, the robustness of screen name parsing is ensured, providing an accurate data foundation for subsequent menu ID matching and linked highlight rendering.

[0036] This specific implementation effectively solves the problem of garbled characters that may occur in the parsing process of Chinese screen names and menu names by pre-setting the GB18030 encoding format, improves the system's compatibility with Chinese environments and the accuracy of data processing, thereby ensuring the reliability of subsequent hierarchical splitting and menu matching.

[0037] Based on the above embodiments, in some embodiments, the preset mapping relationship includes a unit dictionary and a submodule dictionary. The unit dictionary contains a mapping between each unit identifier and the corresponding unit button identifier, and the submodule dictionary contains a mapping between each submodule identifier and the corresponding submodule button identifier.

[0038] In this embodiment, the preset mapping relationship described in step S102 is specifically implemented through a pre-built unit dictionary and submodule dictionary. The input source for the unit dictionary is the object identifier (ID) of all unit-level buttons in the system navigation menu and their corresponding unit names. The processing action involves using each unit name as a key and its corresponding fixed button ID as a value to construct a one-to-one mapping relationship. For example, for unit 1, its corresponding button ID is "HotButton_46_0001," and this mapping relationship is stored in the unit dictionary. Similarly, the input source for the submodule dictionary is the object identifier (ID) of all submodule-level buttons and their corresponding submodule names. The processing action involves using each submodule name as a key and its corresponding button ID as a value to construct a mapping relationship. For example, for the "Unit Monitoring" submodule, its corresponding button ID is "HotButton_47_0001," and this mapping relationship is stored in the submodule dictionary. After the hierarchical splitting of the full name of the current screen is completed in step S101, the unit identifier segment and the submodule identifier segment are obtained. These two identifier segments are used as inputs and matched with the keys in the unit dictionary and the submodule dictionary, respectively. Specifically, the split unit identifier segment (e.g., "Unit 1") is used as the query key to retrieve the corresponding value in the unit dictionary, that is, to match the corresponding unit button identifier (e.g., "HotButton_46_0001"); at the same time, the split submodule identifier segment (e.g., "Unit Monitoring") is used as the query key to retrieve the corresponding value in the submodule dictionary, that is, to match the corresponding submodule button identifier (e.g., "HotButton_47_0001"). The output of this matching process is two clear button identifiers, which are used for the highlight rendering operation in the subsequent step S103. Through this dictionary mapping mechanism, accurate and efficient positioning from the screen name to the specific menu button is achieved, and the dictionary mapping relationship can be flexibly configured, supporting rapid updates when adding new units or submodules without modifying the core code, thus improving the scalability and maintainability of the solution.

[0039] This specific implementation method achieves accurate and efficient matching of screen names and menu button labels by constructing unit dictionaries and sub-module dictionaries, providing an accurate data foundation for subsequent linked highlight rendering. At the same time, the configurability of the dictionaries enhances the system's scalability and ease of maintenance.

[0040] Based on the above embodiments, in some embodiments, the step of synchronously setting the display attributes of the successfully matched unit button and submodule button to a highlighted state includes: Call the interface control property setting interface to set the text color of the successfully matched unit button and submodule button to the preset highlight color.

[0041] In this embodiment, step S103, which involves synchronously setting the display attributes of the successfully matched unit buttons and submodule buttons to a highlighted state, is specifically implemented by calling the interface control attribute setting interface. This interface is a standard attribute setting function provided by the system, and its function prototype is `SetProperty`. In one possible implementation, this interface accepts three parameters, which are used to specify the target control object, the name of the attribute to be modified, and the target value of the attribute. Specifically, after the matching of the unit identifier segment and the submodule identifier segment is completed through step S2, the system will obtain the successfully matched unit button object identifier and the submodule button object identifier, respectively. Subsequently, the program uses these two object identifiers as input to call the `SetProperty` interface, sets the attribute name parameter to "TextColor", and sets the target value parameter to the color code representing red, such as "#FF0000". The color code "#FF0000" is the standard hexadecimal RGB color representation, where "FF" represents the maximum value of the red channel and "00" represents the minimum value of the green and blue channels, thus precisely specifying red. Through this processing action, the system synchronously sets the text color of the successfully matched unit and submodule buttons to red. After this setting operation is completed, the output result is that the text color of the buttons at the corresponding unit and submodule levels in the navigation menu all turn red, thus visually forming a continuous red highlighted path from the unit level to the submodule level. This highlighted state is maintained throughout the current session cycle. When the screen changes, the program will re-execute steps S101 to S103, automatically parsing the name of the new screen and updating the highlighted state to ensure that the highlighted path always corresponds to the currently displayed screen. In addition, to ensure the real-time performance and stability of the system, this highlight rendering operation adopts an asynchronous execution mechanism, running in parallel with the system's core functions such as real-time data acquisition and screen refresh, without consuming critical system resources, thus not affecting the normal operation of the monitoring system.

[0042] This specific implementation method calls the `SetProperty` interface to synchronously set the text color of the successfully matched unit button and sub-module button to red, realizing the linkage highlighting of parent and child menus. This provides operators with intuitive and clear visual feedback throughout the entire path, effectively solving the problems of path confusion and low operation efficiency caused by the lack of selection status feedback in the existing technology.

[0043] Based on the above embodiments, in some embodiments, the highlight state is maintained continuously during the current session period, and the screen name is automatically re-parsed to update the highlight state when the screen switches; and / or, the setting of the highlight state is executed using an asynchronous rendering mechanism, which is executed in parallel with the system's real-time data acquisition and screen refresh.

[0044] In this embodiment, the highlighted state described in step S103 is maintained continuously within the current session period, and the screen name is automatically re-parsed to update the highlighted state when the screen switches. The specific implementation is as follows: After the system obtains the complete name of the currently displayed screen through step S101 and completes the hierarchical splitting, and after step S2 completes the matching of the unit button identifier and the submodule button identifier, the system calls the interface control property setting interface to synchronously set the display attributes of the successfully matched unit buttons and submodule buttons to the highlighted state. Specifically, this highlighted state is achieved by setting the button text color to red. For example, calling the `SetProperty("TextColor", "#FF0000")` interface sets the text color of both the matched unit buttons and submodule buttons to red, thus forming a full-path visual feedback from the unit level to the submodule level. This highlighted state is not a one-time operation but is maintained continuously within the current session period. When the operator switches to another screen, the system automatically re-triggers the complete process from steps S101 to S103. Specifically, the system again obtains the complete name of the new screen through the `graph.CurGraphName()` interface and uses the string splitting function `split("-")` to hierarchically split the name, obtaining new unit identifier segments and submodule identifier segments. Subsequently, the system re-matches the new unit identifier segments and submodule identifier segments with the button identifiers in the navigation menu according to a preset dictionary mapping relationship. Upon successful matching, the system calls the `SetProperty` interface again to set the text color of the newly matched unit and submodule buttons to red. Simultaneously, the text color of the previously highlighted buttons automatically reverts to the default color, thus achieving dynamic updates to the highlighted state. For example, when an operator switches from the "Unit 1 - Unit Monitoring - XXX" screen to the "Unit 1 - Process Control - XXX" screen, the system automatically sets the text color of the "Unit 1" button and the "Process Control" button to red, while the text color of the "Unit Monitoring" button reverts to the default color. This process employs an asynchronous rendering mechanism, executing in parallel with real-time system data acquisition and screen refresh. This ensures that the rendering operation does not consume core system resources and does not affect the real-time performance and stability of the monitoring system. Furthermore, if the screen name resolution is abnormal, such as lacking separators or missing levels, the highlighting operation is not performed to avoid impacting system stability. Through these mechanisms, the highlighted state is maintained continuously within the current session period and automatically updated when the screen switches.

[0045] This specific implementation achieves real-time, dynamic visual feedback of the navigation path through the continuous maintenance and automatic update mechanism of the highlighted state. This enables operators to quickly and accurately identify their current level position when frequently switching screens, effectively avoiding misoperation caused by getting lost, and significantly improving the intuitiveness and operational efficiency of navigation interaction.

[0046] In this embodiment, the highlight setting in step S103 is executed using an asynchronous rendering mechanism to ensure that the rendering operation runs in parallel with the system's real-time data acquisition and screen refresh tasks, without blocking each other. Specifically, after the matching of the unit button identifier and the submodule button identifier is completed in step S2, the system does not immediately execute the color attribute modification synchronously in the main thread. Instead, it encapsulates the highlight rendering task into an independent asynchronous callback function or work item and submits it to the system's asynchronous task queue or rendering scheduler. This asynchronous task is executed in a background thread or idle time slice. Its input source is the matching result output in step S2, namely the determined unit button object name and submodule button object name, as well as the preset highlight color parameters, such as the text color value "#FF0000". The processing action is to call the property setting interface of the interface control, such as `SetProperty("TextColor", "#FF0000")`, to assign values ​​to the text color attributes of the matched unit button and submodule button respectively. The output is an immediate update of the button display attributes, causing the text color of both buttons to synchronously turn red, thus forming a full-path visual feedback from the unit level to the submodule level. Due to the asynchronous mechanism, this highlighting rendering process is decoupled in time from the system's background real-time data acquisition thread (e.g., polling the operation right status via the `graph.QueryDData` interface) and the screen refresh thread (e.g., responding to screen switching events), allowing them to execute in parallel. Even under conditions of high-frequency screen switching or large-scale data acquisition, highlighting rendering will not consume core system resources or block the main interface's responsiveness, thereby ensuring the monitoring system's rapid response to real-time data changes and user operations, maintaining the system's real-time performance and stability. When a screen switch causes a new screen name to be parsed and matched, the system will again submit a new highlighting rendering task asynchronously, automatically overwriting the previous state, achieving dynamic synchronous updates of the highlighting status.

[0047] This specific implementation method effectively avoids interference from highlight rendering operations on the core real-time data acquisition and screen refresh tasks of the monitoring system by adopting an asynchronous rendering mechanism. It significantly improves the system's response smoothness and operational stability in high-frequency operation scenarios, and ensures that the enhanced navigation interaction function will not have a negative impact on the core safety functions of the hydropower plant monitoring system.

[0048] Based on the above embodiments, in some embodiments, querying the current system's operation right status data and generating prompt information containing the unit identifier and permission type based on the operation right status data, and displaying the prompt information in different colors, includes: The operation right type value is obtained through the system's real-time data reading interface; The corresponding permission type and display color are determined based on the operation right type value. A prompt text containing the unit identifier and permission type is generated by concatenating the two, and the prompt text is refreshed and displayed with the specified display color.

[0049] In this embodiment, the specific implementation of querying the current system operation right status data in step S104 is as follows. First, the real-time operation right status data of the system is read through the graph.QueryDData interface provided by the system. This interface returns a value to identify the current operation right type. Specifically, the input parameter of this interface is the data point identifier corresponding to the operation right status data, and the output result is the operation right type value. In one possible implementation, when the operation right type value is 0, it indicates that the current operation right is a power station permission; when the operation right type value is 1, it indicates that the current operation right is a centralized control permission; when the operation right type value is other values, it indicates that the current operation right is other permissions. Subsequently, based on the obtained operation right type value, the corresponding permission type and display color are determined. Specifically, when the operation right type value is 0, the corresponding permission type is "power station", and the display color is set to red; when the operation right type value is 1, the corresponding permission type is "centralized control", and the display color is set to green; when the operation right type value is other values, the corresponding permission type is "other", and the display color is set to orange. Then, based on the unit identifier segment parsed from the current screen, a prompt text containing the unit identifier and permission type is generated, such as "Unit 1 Operation Right: Power Plant". Finally, through the interface control property setting interface, the display color of this prompt text is set to the previously determined color, and the interface display is refreshed, thus displaying the operation right information in a specific color in real time in the interface prompt area. This process ensures the real-time acquisition and intuitive presentation of operation right status data, allowing operators to quickly identify the current operation permission without additional queries.

[0050] This specific implementation achieves intuitive visualization of operation rights information by automatically querying the operation rights status and displaying it in different colors based on numerical mapping. This significantly reduces the operational risks caused by misjudgment of permissions and improves the security and efficiency of human-computer interaction in the monitoring system.

[0051] Based on the above embodiments, this embodiment will describe in detail the complete implementation of a hierarchical navigation linkage highlighting interaction method for a monitoring system. This method is particularly suitable for hydropower plant monitoring systems, and optimizes navigation interaction through low-intrusion coding modifications.

[0052] First, during the system initialization phase, encoding compatibility processing is required. Since the screen names and menu names of hydropower plant monitoring systems typically contain Chinese characters, to avoid garbled characters during subsequent string parsing and matching, this embodiment sets the encoding format to gb18030. This encoding format effectively supports the correct parsing of Chinese characters and other uncommon characters, ensuring the accuracy of hierarchical splitting and identifier matching. After completing the encoding settings, the system enters real-time monitoring mode, waiting for user operation to trigger screen switching events.

[0053] This method automatically activates when an operator clicks any menu item in the navigation bar, and the system navigates to the corresponding monitoring screen. First, it retrieves the full name of the currently open screen in real time using the system's built-in interface `graph.CurGraphName()`. This interface returns the title bar text of the currently active window, ensuring the real-time and accurate acquisition of the screen name. For example, when an operator clicks the "Unit Monitoring" submenu under "Unit 1" in the navigation bar, the system navigates to the "Unit 1 - Unit Monitoring - XXX" screen, and the full name returned by `graph.CurGraphName()` will then be "Unit 1 - Unit Monitoring - XXX".

[0054] After obtaining the complete name of the current screen, it is split into levels. In this embodiment, the default naming convention for screen names is "Unit Identifier - Submodule Identifier - Auxiliary Identifier", with hyphens "-" as separators between levels. The complete name is split using the string splitting function split("-"), resulting in a string array. The first element is extracted from this array as the unit identifier segment, for example, "Unit 1"; the second element is extracted as the submodule identifier segment, for example, "Unit Monitoring"; subsequent elements are used as auxiliary segments, which are not involved in menu matching in this embodiment. If the length of the split array is less than 2, meaning the screen name does not conform to the default convention (e.g., no separator or missing levels), it is determined to be an abnormal screen name. In this case, subsequent highlighting operations are not performed to avoid affecting system stability.

[0055] After hierarchical decomposition, the menu identifier matching and mapping stage begins. In this embodiment, two sets of dictionary mapping relationships are pre-established: a unit dictionary and a submodule dictionary. The unit dictionary contains the mapping relationship between each unit identifier (such as "Unit 1", "Unit 2", etc.) and the object name (ID) of the corresponding unit button in the navigation bar. For example, the button ID corresponding to "Unit 1" is "HotButton_46_0001". The submodule dictionary contains the mapping relationship between each submodule identifier (such as "Unit Monitoring", "Process Control", "Auxiliary Facilities", "Monitoring", etc.) and the object name (ID) of the corresponding submodule button in the navigation bar. For example, the button ID corresponding to "Unit Monitoring" is "HotButton_47_0001". These dictionary mapping relationships can be flexibly configured. When a new unit or submodule is added, only a new mapping entry needs to be added to the dictionary without modifying the core code, thereby improving the scalability and maintainability of the solution. By querying and matching the split unit identifier segment and submodule identifier segment with the unit dictionary and submodule dictionary respectively, the unit button ID and submodule button ID corresponding to the current screen can be obtained.

[0056] After successfully matching the corresponding button ID, multi-level linked highlight rendering is executed. In this embodiment, the SetProperty interface for setting the interface control properties is called to set the text color of the successfully matched unit button and submodule button to red (color code "#FF0000"). Specifically, the SetProperty("TextColor", "#FF0000") interface is called on the unit button and submodule button respectively, so that the text color of these two buttons changes to red synchronously, thereby forming a full-path visual feedback from the unit level to the submodule level in the navigation bar. For example, when the operator opens the "Unit 1 - Unit Monitoring - XXX" screen, the text of the "Unit 1" button and the "Unit Monitoring" button both turn red, and the operator can intuitively identify that the current operation path is "Unit 1 → Unit Monitoring". This highlight state is maintained continuously within the current session cycle. When the operator switches to other screens, the program automatically repeats the above steps, re-parses the name of the new screen and updates the highlight state, thereby achieving dynamic synchronization of the highlight state. In addition, to ensure that the rendering operation does not affect the real-time performance and stability of the monitoring system, this embodiment adopts an asynchronous rendering mechanism. Menu highlight rendering is executed in parallel with core tasks such as real-time data acquisition and screen refresh, without occupying core system resources.

[0057] While highlighting the menu, this method also performs operation right status query and prompt update. It reads real-time operation right status data from the system via the `graph.QueryDData` interface to obtain the current operation right type value. This value means: 0 represents power plant operation right, 1 represents centralized control operation right, and other values ​​represent other permissions. Based on the obtained operation right type value, the corresponding permission type and display color are determined: when the value is 0, the permission type is "Power Plant," and the display color is red; when the value is 1, the permission type is "Centralized Control," and the display color is green; when the value is other, the permission type is "Other," and the display color is orange. Subsequently, a prompt text containing the unit identifier and permission type is automatically generated, in the format "XX Unit Operation Right: XXX," for example, "Unit 1 Operation Right: Power Plant." Finally, the prompt area on the interface is refreshed with the determined display color to display the prompt text, ensuring that the operation right information is synchronized in real time and is clearly visible.

[0058] As an alternative, highlighting can use background color instead of text color, or use methods such as thickening or blinking borders to provide visual feedback on the selected state. Triggering can be achieved by triggering menu highlighting through a screen loading event, replacing the current screen name parsing trigger. The color scheme can be adjusted according to on-site requirements; for example, setting the unit highlight to blue and the central control operation authority to yellow, without altering the core technical logic.

[0059] In summary, this embodiment achieves intuitive path navigation, automated operation, and visualized permissions in the monitoring system by automatically resolving screen names, splitting hierarchical levels, matching dictionary mappings, linking parent and child menus with color rendering, and automatically recognizing and color-coded operation rights. This effectively solves the problems of operators easily getting lost when switching between multiple screen levels and having difficulty obtaining operation rights information, significantly improving the security and efficiency of operation and maintenance.

[0060] Please refer to Figure 2 , Figure 2 A structural block diagram of a hierarchical navigation linkage highlighting interactive device for a monitoring system provided in an embodiment of the present invention; the specific device may include: The screen name parsing module 100 is used to obtain the complete name of the currently displayed screen and to perform hierarchical splitting of the complete name to obtain the unit identifier segment and the sub-module identifier segment; The menu matching module 200 is used to match the unit identifier segment and the sub-module identifier segment with the unit button identifier and the sub-module button identifier in the navigation menu, respectively, according to a preset mapping relationship. Linkage highlight module 300 is used to synchronously set the display attributes of successfully matched unit buttons and sub-module buttons to a highlighted state, so as to form a full-path visual feedback from the unit level to the sub-module level. The permission prompt module 400 is used to query the current system's operation permission status data and generate prompt information containing the unit identifier and permission type based on the operation permission status data, and display the prompt information in different colors.

[0061] The hierarchical navigation linkage highlighting interaction device of the monitoring system in this embodiment is used to implement the aforementioned hierarchical navigation linkage highlighting interaction method of the monitoring system. Therefore, the specific implementation of the hierarchical navigation linkage highlighting interaction device of the monitoring system can be found in the embodiment section of the hierarchical navigation linkage highlighting interaction method of the monitoring system above. For example, the screen name parsing module 100, the menu matching module 200, the linkage highlighting module 300, and the permission prompting module 400 are respectively used to implement steps S101, S102, S103, and S104 in the hierarchical navigation linkage highlighting interaction method of the monitoring system. Therefore, its specific implementation can be referred to the description of the corresponding embodiments, which will not be repeated here.

[0062] A specific embodiment of the present invention also provides a hierarchical navigation linkage highlighting interactive device for a monitoring system, comprising: a memory for storing a computer program; and a processor for executing the computer program to implement the steps of the hierarchical navigation linkage highlighting interactive method for a monitoring system described above.

[0063] A specific embodiment of the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the hierarchical navigation linkage highlighting interaction method of the above-described monitoring system.

[0064] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0065] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0066] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0067] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0068] Obviously, the above embodiments are merely illustrative examples for clear explanation and are not intended to limit the implementation. Those skilled in the art will recognize that other variations or modifications can be made based on the above description. It is neither necessary nor possible to exhaustively list all possible implementations here. However, obvious variations or modifications derived therefrom are still within the scope of protection of this invention.

Claims

1. A hierarchical navigation linkage highlighting interaction method for a monitoring system, characterized in that, Includes the following steps: Obtain the complete name of the currently displayed screen, and perform hierarchical splitting of the complete name to obtain the unit identifier segment and the submodule identifier segment; According to the preset mapping relationship, the unit identifier segment and the sub-module identifier segment are matched with the unit button identifier and the sub-module button identifier in the navigation menu, respectively; The display attributes of the successfully matched unit buttons and sub-module buttons are simultaneously set to highlighted state to form a full-path visual feedback from the unit level to the sub-module level. The system queries the current system operation authority status data and generates a prompt message containing the unit identifier and permission type based on the operation authority status data, displaying the prompt message in different colors.

2. The method according to claim 1, characterized in that, The hierarchical splitting of the complete name includes: The complete name is split using a string splitting function with a preset delimiter to extract the unit identifier segment and the submodule identifier segment.

3. The method according to claim 1, characterized in that, The preset mapping relationship includes a unit dictionary and a submodule dictionary. The unit dictionary contains a mapping between each unit identifier and its corresponding unit button identifier, and the submodule dictionary contains a mapping between each submodule identifier and its corresponding submodule button identifier.

4. The method according to claim 1, characterized in that, The step of synchronously setting the display attributes of the successfully matched unit buttons and sub-module buttons to a highlighted state includes: Call the interface control property setting interface to set the text color of the successfully matched unit button and submodule button to the preset highlight color.

5. The method according to claim 1, characterized in that, The process of querying the current system's operational authority status data and generating a prompt message containing the unit identifier and permission type based on the operational authority status data, displaying the prompt message in different colors, includes: The operation right type value is obtained through the system's real-time data reading interface; The corresponding permission type and display color are determined based on the operation right type value. A prompt text containing the unit identifier and permission type is generated by concatenating the two, and the prompt text is refreshed and displayed with the specified display color.

6. The method according to claim 1, characterized in that, Before obtaining the full name of the currently displayed screen, the process also includes: Set the encoding format to be compatible with Chinese characters to ensure encoding compatibility for Chinese screen names and menu names.

7. The method according to claim 1, characterized in that, The highlighted state is maintained throughout the current session period and the screen name is automatically re-parsed to update the highlighted state when the screen switches; and / or, the setting of the highlighted state is executed using an asynchronous rendering mechanism, which is executed in parallel with the system's real-time data acquisition and screen refresh.

8. A hierarchical navigation linkage highlighting interactive device for a monitoring system, characterized in that, include: The screen name parsing module is used to obtain the complete name of the currently displayed screen and to perform hierarchical splitting of the complete name to obtain the unit identifier segment and the sub-module identifier segment; The menu matching module is used to match the unit identifier segment and the sub-module identifier segment with the unit button identifier and the sub-module button identifier in the navigation menu, respectively, according to a preset mapping relationship. The linked highlight module is used to synchronously set the display attributes of the successfully matched unit buttons and sub-module buttons to the highlighted state, so as to form a full-path visual feedback from the unit level to the sub-module level. The permission prompt module is used to query the current system's operation permission status data and generate prompt information containing the unit identifier and permission type based on the operation permission status data, and display the prompt information in different colors.

9. A hierarchical navigation linkage highlighting interactive device for a monitoring system, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the hierarchical navigation linkage highlighting interaction method of a monitoring system as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the hierarchical navigation linkage highlighting interaction method of a monitoring system as described in any one of claims 1 to 7.