Picture display method and device, configuration screen, storage medium and program product

Abstract

The invention relates to the technical field of picture display, and discloses a picture display method and device, a configuration screen, a storage medium and a program product, the method is applied to the configuration screen provided with a cache region, the method comprises the steps that a current running picture is acquired from the cache region and displayed, and the current running picture and a historical running picture of last switching are cached in the cache region; when a switching instruction triggered based on the current running picture is detected, determining a predicted running picture of next switching according to the switching instruction, and replacing a historical running picture of previous switching in the cache region with the predicted running picture; and taking the current operation picture as a new historical operation picture of previous switching, taking the predicted operation picture of next switching as a new current operation picture, and displaying the new current operation picture. Only the current running picture and the historical running picture are reserved in the cache region, and the content of the cache region is dynamically updated according to the switching instruction, so that the memory occupation of the configuration screen is effectively reduced.

Description

Technical Field

[0001] This application relates to the field of screen display technology, and in particular to a screen display method, device, configuration screen, storage medium and program product. Background Technology

[0002] With the development of industrial automation technology, automated monitoring systems are playing an increasingly important role in industrial production. In these systems, the configuration panel, as a crucial human-machine interface, directly impacts the user experience and operational efficiency. Currently, when displaying engineering screens on configuration panels in automated monitoring systems, the process typically involves the configuration panel first acquiring PLC operating data and uploading it to a PC as an engineering file. The PC then generates the corresponding operating screen based on this file and sends it to the configuration panel, where the configuration software displays the screen.

[0003] In existing technologies, configuration screens typically load all project files and display the running screen simultaneously during page loading. This allows users to smoothly switch to the corresponding target running screen when clicking buttons on the current running interface. However, because configuration screens have limited memory, loading all running screens simultaneously can lead to excessive memory consumption, causing the configuration software to lag or even crash. This is especially true when project files contain a large number of images and audio resources, as the configuration screen's memory is often insufficient to support the simultaneous loading of all screens. Furthermore, if the target screen contains many images, data loading slows down, resulting in noticeable lag during screen transitions. Summary of the Invention

[0004] The main purpose of this application is to provide a screen display method that aims to solve the technical problem of excessive memory usage when a configuration screen displays a screen.

[0005] To achieve the above objectives, this application proposes a screen display method, which is applied to a configured screen with a buffer area, and the method includes: The current running screen is retrieved and displayed from the cache area, which contains the current running screen and the previously switched historical running screen. When a switching instruction triggered based on the current running screen is detected, the expected running screen for the next switching is determined according to the switching instruction, and the expected running screen is used to replace the historical running screen of the previous switching in the buffer. The current running screen is used as the new previous historical running screen, and the expected running screen for the next switch is used as the new current running screen, and the new current running screen is displayed.

[0006] In one embodiment, the cache area stores a first graphic attribute related to the current running screen and a second graphic attribute related to the previously switched historical running screen. The current running screen is generated by obtaining the corresponding first screen component based on the first graphic attribute. The step of retrieving and displaying the currently running screen from the cache includes: Obtain the first graphic attribute corresponding to the currently running screen in the cache area; Based on the first graphic attribute, obtain the first screen component corresponding to the currently running screen, and store the first screen component in the cache area; The currently running screen is constructed and displayed based on the first screen component stored in the cache.

[0007] In one embodiment, the step of displaying the new currently running screen includes: Obtain the third graphic attribute corresponding to the new current running screen, and obtain the third screen component corresponding to the new current running screen based on the third graphic attribute; The third screen component is stored in the cache area, and the first screen component is deleted from the cache area; The new currently running screen is constructed and displayed based on the third screen component stored in the cache.

[0008] In one embodiment, the cache area further includes a resource database, which stores resource data corresponding to each graphic attribute. The step of obtaining the first screen component corresponding to the currently running screen based on the first graphic attribute includes: Determine the first resource data corresponding to the first graphic attribute in the resource database, and construct a first screen component according to the first resource data and the first graphic attribute; The step of obtaining the third screen component corresponding to the new currently running screen based on the third graphic attribute includes: The third resource data corresponding to the third graphic attribute in the resource database is determined, and a third screen component is constructed according to the third resource data and the third graphic attribute.

[0009] In one embodiment, before the step of retrieving and displaying the currently running screen from the cache, the method further includes: When a start command is detected, a preset running screen is obtained and displayed, and the preset running screen is stored as the current running screen in the cache area; Determine whether the currently running screen is the preset boot screen; If so, the running screen to be displayed after the preset boot screen is obtained based on the preset screen running order, and the running screen to be displayed is stored in the cache area as the previous switching history running screen; If not, the preset boot screen is stored in the cache area as the previously switched historical running screen.

[0010] In one embodiment, before the step of replacing the previously switched historical running screen in the cache with the expected running screen, the method further includes: Determine whether the expected running screen is the historical running screen from the previous switch; If not, then the step of replacing the previously switched historical running screen in the cache with the expected running screen is performed; If so, the old current running screen is used as the new previous historical running screen, and the old previous historical running screen is used as the new current running screen, and the new current running screen is displayed.

[0011] Furthermore, to achieve the above objectives, this application also proposes a screen display device, the device comprising: The display module is used to retrieve and display the current running screen from the cache area, which caches the current running screen and the previously switched historical running screen. The caching module is used to determine the expected running screen for the next switch based on the switch instruction when a switch instruction triggered based on the current running screen is detected, and to replace the historical running screen of the previous switch in the cache with the expected running screen; The switching module is used to use the current running screen as the new historical running screen of the previous switch, use the expected running screen of the next switch as the new current running screen, and display the new current running screen.

[0012] In addition, to achieve the above objectives, this application also proposes a configuration screen, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. The memory also has a cache area, and the computer program is configured to implement the steps of the screen display method described above.

[0013] In addition, to achieve the above objectives, this application also proposes a storage medium that is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the screen display method described above.

[0014] In addition, to achieve the above objectives, this application also proposes a computer program product comprising a computer program that, when executed by a processor, implements the steps of the screen display method described above.

[0015] This application discloses a screen display method, apparatus, configuration screen, storage medium, and program product. The method, applied to a configuration screen, includes: retrieving and displaying the currently running screen from a buffer, wherein the buffer stores the current running screen and the previously switched historical running screen; upon detecting a switching command triggered based on the current running screen, determining the expected running screen for the next switch according to the switching command, and replacing the previously switched historical running screen in the buffer with the expected running screen; using the current running screen as the new previously switched historical running screen, using the expected running screen for the next switch as the new current running screen, and displaying the new current running screen. This application effectively reduces the memory usage of the configuration screen and prevents lag or crashes caused by loading all running screens simultaneously by retaining only the current running screen and the historical running screen in the buffer and dynamically updating the buffer content according to the switching command. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart of the first embodiment of the screen display method proposed in this application; Figure 2 This is a flowchart of the second embodiment of the screen display method proposed in this application; Figure 3 This is a flowchart of the third embodiment of the screen display method proposed in this application; Figure 4 A diagram of a screen display device provided in an embodiment of this application; Figure 5 This is a schematic diagram of a screen display configuration panel suitable for implementing the embodiments of this application.

[0019] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0020] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of this application and are not intended to limit this application.

[0021] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0022] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of this application are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0023] Understandably, with the development of industrial automation technology, automated monitoring systems are playing an increasingly important role in industrial production. Within these systems, the configuration panel, as a crucial human-machine interface, directly impacts the user experience and operational efficiency. Currently, when displaying engineering screens on configuration panels in automated monitoring systems, the process typically involves the configuration panel first acquiring PLC operating data and uploading it to a PC as an engineering file. The PC then generates the corresponding operating screen based on this file and sends it to the configuration panel, where the configuration software displays the screen.

[0024] In existing technologies, configuration screens typically load all project files and display the running screen simultaneously during page loading. This allows users to smoothly switch to the corresponding target running screen when clicking buttons on the current running interface. However, because configuration screens have limited memory, loading all running screens simultaneously can lead to excessive memory consumption, causing the configuration software to lag or even crash. This is especially true when project files contain a large number of images and audio resources, as the configuration screen's memory is often insufficient to support the simultaneous loading of all screens. Furthermore, if the target screen contains many images, data loading slows down, resulting in noticeable lag during screen transitions.

[0025] Therefore, to address the technical problem of excessive memory consumption when displaying screens in a configuration panel, this embodiment proposes a screen display method. This method, applied to a configuration panel, includes: retrieving and displaying the current running screen from a buffer containing both the current running screen and the previously switched historical running screen; upon detecting a switching command triggered by the current running screen, determining the expected running screen for the next switch based on the switching command, and replacing the previously switched historical running screen in the buffer with the expected running screen; using the current running screen as the new previously switched historical running screen, using the expected running screen for the next switch as the new current running screen, and displaying the new current running screen. This embodiment effectively reduces the memory consumption of the configuration panel by retaining only the current running screen and the historical running screen in the buffer and dynamically updating the buffer content according to the switching command, preventing lag or crashes caused by loading all running screens simultaneously.

[0026] For ease of understanding, the following is combined with Figures 1 to 5 The present application provides a detailed description of the screen display method provided in the embodiments of this application, as well as the screen display method, device, configuration screen, storage medium, and program product provided in the following embodiments.

[0027] This application provides a screen display method, referring to... Figure 1 , Figure 1 This is a flowchart of the first embodiment of the screen display method proposed in this application.

[0028] like Figure 1 As shown, the method includes: Step S10: Obtain and display the current running screen from the cache area, where the cache area stores the current running screen and the previously switched historical running screen.

[0029] It should be noted that the executing entity in this embodiment can be a device with a screen display, such as a configuration screen, or a configuration screen device capable of performing the above functions. This embodiment uses a configuration screen device (hereinafter referred to as the device) for explanation. The configuration screen device has a buffer area, which can be the entire memory or a region of memory. In this embodiment, since the configuration screen memory is small, the entire memory is used as the buffer area for explanation, but this does not impose specific limitations on this embodiment.

[0030] It should also be noted that the aforementioned cache only stores two running screens: the current running screen and the previously switched historical running screen. The current running screen can be the screen the user is currently viewing and operating on the configuration screen, containing various components, graphics, text, and other elements. The previously switched historical running screen can be a screen the user viewed before the current running screen, or it can be a running screen stored in the cache along with the current running screen based on preset instructions. This data is stored in the cache so that it can be quickly rolled back or switched when needed.

[0031] In its implementation, the device first loads the current screen and its required resources into a cache to ensure fast display. When a user-issued switching command is detected, the device determines the next expected screen to be displayed and pre-loads the core resources required for that screen into the cache using asynchronous loading technology in a sub-thread. Simultaneously, the device allocates memory resources efficiently, prioritizing loading tasks according to a resource priority queue to ensure core resources are loaded first, while non-core resources are loaded on demand, reducing memory usage and improving screen switching smoothness. During screen switching, the device retrieves pre-loaded core resources from the cache for display while continuing to load remaining resources in a sub-thread. After loading is complete, the cache is updated, releasing unnecessary resources to maintain memory balance. Throughout the process, the device monitors memory usage and user actions in real time, dynamically adjusting resource loading strategies to ensure smooth screen switching and efficient use of system resources.

[0032] For ease of understanding, the following example illustrates the concept, but does not impose specific limitations on this embodiment. Assume a user is viewing a monitoring screen (the currently running screen) containing multiple buttons and icons. When the user clicks a button, intending to switch to another screen with detailed parameter settings, the device predicts the user's intention based on the switching command and preloads the core resources of the target screen, such as parameter setting forms and buttons, in a sub-thread. During loading, the device prioritizes loading core elements like forms and buttons according to a resource priority queue, while loading decorative elements such as background images as non-core resources on demand. After the user completes the switch, the device retrieves the pre-loaded core resources from the cache for display, while continuing to load the remaining resources to ensure complete screen display. Throughout this process, the device dynamically manages the cache, releasing unused historical screen resources to maintain memory balance and smooth screen switching.

[0033] Step S20: When a switching instruction triggered based on the current running screen is detected, the expected running screen for the next switching is determined according to the switching instruction, and the expected running screen is used to replace the historical running screen of the previous switching in the buffer.

[0034] It should be noted that the aforementioned switching command can be an operation command triggered by the user on the currently running interface, such as a click, touch, gesture, or button command, used to trigger the screen switching. The aforementioned predicted running screen can be the next screen that may be displayed based on the user's operation intention and the context information of the current running screen.

[0035] In its implementation, the device first loads the current screen and its required resources into a cache to ensure fast display. When a user-issued switching command is detected, the device determines the next expected screen to be displayed and pre-loads the core resources required for that screen into the cache using asynchronous loading technology in a sub-thread. Simultaneously, the device allocates memory resources efficiently, prioritizing loading tasks according to a resource priority queue to ensure core resources are loaded first, while non-core resources are loaded on demand, reducing memory usage and improving screen switching smoothness. During screen switching, the device retrieves pre-loaded core resources from the cache for display while continuing to load remaining resources in a sub-thread. After loading is complete, the cache is updated, releasing unnecessary resources to maintain memory balance. Throughout the process, the device monitors memory usage and user actions in real time, dynamically adjusting resource loading strategies to ensure smooth screen switching and efficient use of system resources.

[0036] For ease of understanding, the following example illustrates the concept, but does not impose specific limitations on this embodiment. Assume a user is viewing a monitoring screen (current running screen) containing multiple buttons and icons on a configuration panel of an industrial monitoring system. When the user clicks a button, intending to switch to another screen with detailed parameter settings, the device predicts the user's intention based on the switching command and preloads the core resources of the target screen, such as parameter setting forms and buttons, in a sub-thread. During loading, the device prioritizes loading core elements like forms and buttons according to a resource priority queue, while loading decorative elements such as background images as non-core resources on demand. After the user completes the switch, the device retrieves the pre-loaded core resources from the cache for display, while continuing to load the remaining resources to ensure complete screen display. Throughout this process, the device dynamically manages the cache, releasing unused historical screen resources to maintain memory balance and smooth screen switching.

[0037] Step S30: Use the current running screen as the new previous historical running screen, use the expected running screen for the next switching as the new current running screen, and display the new current running screen.

[0038] In its implementation, the device first identifies and records the currently displayed screen as the previous historical screen, ensuring the recording of historical screens for possible rollback later. Simultaneously, the device determines the expected screen for the next switch based on the switching command and loads and displays it as the new current screen. Before displaying the new current screen, the device retrieves pre-loaded core resources from the cache and uses these resources to build and display the new current screen. During this process, the device dynamically updates the cache content, releasing resources from older historical screens that are no longer needed to maintain a balanced memory usage and ensure efficient system operation. The device continuously monitors memory usage and user operations to dynamically adjust resource loading strategies, ensuring smooth screen switching and efficient use of system resources.

[0039] For ease of understanding, the following example illustrates the concept, but does not impose specific limitations on this embodiment. Assume a user is viewing a monitoring screen (current running screen) containing multiple buttons and icons on an industrial monitoring system's configuration panel. When the user clicks a button, intending to switch to another screen with detailed parameter settings, the device predicts the user's intention based on the switching command and pre-loads the core resources of the target screen, such as parameter setting forms and buttons, in a sub-thread. During loading, the device prioritizes loading core elements like forms and buttons according to a resource priority queue, while loading decorative elements such as background images as non-core resources on demand. After the user completes the switch, the device retrieves the pre-loaded core resources from the cache for display, while continuing to load remaining resources to ensure complete screen display. Throughout this process, the device dynamically manages the cache, releasing unused historical screen resources to maintain memory balance and smooth screen switching. This mechanism not only improves the user experience but also optimizes the system's memory usage efficiency.

[0040] Furthermore, to further reduce memory waste, the running screen can be characterized by screen attributes. The components corresponding to the screen attributes are only retrieved and used to construct the running screen when needed. When a screen needs to be displayed, the device dynamically retrieves the corresponding components from the resource library or storage based on the screen's attribute information and constructs the complete screen. After construction, the screen components are temporarily stored in a cache for quick display. After a screen is switched or hidden, the device can choose whether to retain the screen's components in the cache, or only retain its attribute information for subsequent reconstruction, based on set strategies (such as cache size limits or memory pressure).

[0041] In one embodiment, the cache stores a first graphic attribute related to the current running screen and a second graphic attribute related to the previously switched historical running screen. The current running screen is generated by obtaining the corresponding first screen component based on the first graphic attribute. The step of retrieving and displaying the currently running screen from the cache includes: Step S11: Obtain the first graphic attribute corresponding to the currently running screen in the cache area; Step S12: Obtain the first screen component corresponding to the current running screen based on the first graphic attribute, and store the first screen component in the cache area; Step S13: Construct and display the currently running screen based on the first screen component stored in the cache area.

[0042] It should be noted that the aforementioned first graphic attribute can describe the characteristic information of each graphic element in the currently running screen, such as color, position, size, and type. The aforementioned first screen component can be a specific graphic element constructed based on the first graphic attribute, such as a button, icon, or text box; these are the basic units that constitute the screen. In the specific implementation, the relevant information of the currently running screen, including its graphic attributes, is first retrieved from the cache. The device uses these attributes to extract the corresponding screen components from the resource library or storage and temporarily stores these components in the cache for rapid screen construction. Subsequently, the device combines and renders the screen components in the cache into a screen visible to the user. This process optimizes the screen loading speed and reduces the consumption of device resources.

[0043] For ease of understanding, the following example illustrates the concept, but does not impose specific limitations on this embodiment. Assume a user is using a smart monitoring application, currently viewing an interface containing live feeds from multiple cameras and control buttons. The device first retrieves the graphical attributes of the interface from its cache, such as the position and size of each camera feed and the style of the buttons. Next, based on these attributes, the device extracts the corresponding screen components from its resource library, such as video windows and button graphics, and stores them in the cache. Finally, the device combines these components to construct and display the current monitoring interface. When the user switches to other functional interfaces, such as the settings interface, the device repeats a similar process to ensure that each new feed is presented quickly and efficiently. This mechanism not only improves the user experience but also optimizes the system's resource management.

[0044] This embodiment retrieves and displays the current running screen from a cache, which stores the current running screen and the previously switched historical running screen. When a switching command triggered based on the current running screen is detected, the expected running screen for the next switch is determined according to the switching command, and the expected running screen replaces the previously switched historical running screen in the cache. The current running screen is used as the new previously switched historical running screen, and the expected running screen for the next switch is used as the new current running screen, which is then displayed. This application effectively reduces the memory usage of the configuration screen and prevents lag or crashes caused by loading all running screens simultaneously by retaining only the current and historical running screens in the cache and dynamically updating the cache content according to the switching command.

[0045] Based on the first embodiment, in the second embodiment, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 , Figure 2 This is a flowchart of a second embodiment of the screen display method proposed in this application. Further, based on the aforementioned technical means of characterizing the running screen using screen attributes, the step of displaying the new current running screen includes: Step S31: Obtain the third graphic attribute corresponding to the new current running screen, and obtain the third screen component corresponding to the new current running screen based on the third graphic attribute.

[0046] It should be noted that the aforementioned new currently running screen can be the screen that the user is about to view or is switching to, such as a monitoring interface containing real-time data updates or a new settings page. The aforementioned third graphic attribute can be characteristic information describing various graphic elements in the new currently running screen, such as color, position, size, type, transparency, and border style. The aforementioned third screen components can be specific graphic elements constructed based on the third graphic attribute, such as buttons, icons, text boxes, and charts; these are the basic units that constitute the screen.

[0047] In its implementation, the device first acquires the third-party graphical attributes corresponding to the new currently running screen. These attributes are stored in a cache and describe the appearance and behavior of each component in the upcoming screen. Next, based on these third-party graphical attributes, the device retrieves the corresponding third-party screen components from a resource library or storage. These components can be pre-designed graphical elements or dynamically generated elements at runtime. To optimize memory usage, the device stores the acquired third-party screen components in a cache for quick access and use during screen construction. If the cache space is insufficient, the device releases no longer needed components according to a certain strategy (such as Least Recently Used), making room for new components. When constructing a new currently running screen, the device reads the third-party screen components from the cache and combines them to form a complete screen.

[0048] For ease of understanding, the following example illustrates the concept, but does not impose specific limitations on this embodiment. Assume a user is using an industrial automation monitoring system and is currently viewing a screen containing multiple sensor data points and control buttons. When the user clicks a button to switch to a new screen containing detailed historical data charts, the device executes the above process. First, the device retrieves the third-party graphical attributes of the new screen from the cache. These attributes describe the chart type, coordinates, size, color, and other information. Next, the device retrieves the corresponding chart components, axis components, data point components, etc., from the resource library based on these attributes and stores them in the cache. If some components already exist in the cache, the device reuses these components to reduce memory usage. Finally, the device constructs a new currently running screen based on the third-party screen components in the cache and displays it on the screen. When the user switches back to the previous screen, the device can quickly read the corresponding components from the cache without reloading, thus improving the speed and efficiency of screen switching.

[0049] Step S32: Store the third screen component in the cache area and delete the first screen component in the cache area.

[0050] In its implementation, the device acquires the third-view attributes corresponding to the new currently running screen. Then, based on these attributes, it retrieves the corresponding third-view components from a resource library or storage. To optimize memory usage, the device stores the acquired third-view components in a cache for quick access and use during screen construction. Simultaneously, the device deletes the first-view components from the cache to free up memory. If the cache is insufficient, the device releases unnecessary components according to a strategy (such as Least Recently Used), making room for new components. When constructing a new currently running screen, the device reads the third-view components from the cache and combines them to form a complete screen.

[0051] For ease of understanding, the following example illustrates the concept, but does not limit the scope of this embodiment. Assume a user is using an industrial automation monitoring system and is currently viewing a screen containing multiple sensor data points and control buttons. When the user clicks a button to switch to a new screen containing detailed historical data charts, the device executes the above process. First, the device retrieves the third graphic attributes of the new screen from the cache. These attributes describe the chart type, coordinates, size, color, and other information. Next, the device retrieves the corresponding chart components, axis components, data point components, etc., from the resource library based on these attributes and stores them in the cache. Simultaneously, the device deletes the first screen components from the cache, such as the previously displayed sensor data and control button components. If some components already exist in the cache, the device reuses them to reduce memory usage. Finally, the device constructs a new currently running screen based on the third screen components in the cache and displays it on the screen. When the user switches back to the previous screen, the device can quickly read the corresponding components from the cache without reloading, thus improving the speed and efficiency of screen switching.

[0052] Step S33: Construct and display the new currently running screen based on the third screen component stored in the cache area.

[0053] In its implementation, the device retrieves the third-view attributes corresponding to the new currently running screen from the cache. Then, based on these attributes, it retrieves the corresponding third-view components from the resource library or storage. To optimize memory usage, the device stores the retrieved third-view components in the cache for quick access and use during screen construction. Simultaneously, the device deletes the first-view components from the cache to free up memory. If the cache is insufficient, the device releases unnecessary components according to a strategy (such as Least Recently Used), making room for new components. When constructing a new currently running screen, the device reads the third-view components from the cache and combines them to form a complete screen.

[0054] Furthermore, to reduce memory usage, all images and audio can be treated as resource data, with different components referencing the corresponding resource data. This avoids duplicate space usage by image and audio resources, thereby reducing project file size and required runtime memory resources.

[0055] In one embodiment, the cache area further includes a resource database, which stores resource data corresponding to each graphic attribute. The step of obtaining the first screen component corresponding to the currently running screen based on the first graphic attribute includes: Determine the first resource data corresponding to the first graphic attribute in the resource database, and construct a first screen component according to the first resource data and the first graphic attribute; The step of obtaining the third screen component corresponding to the new currently running screen based on the third graphic attribute includes: The third resource data corresponding to the third graphic attribute in the resource database is determined, and a third screen component is constructed according to the third resource data and the third graphic attribute.

[0056] It should be noted that the aforementioned resource database can be a database storing all resource data, including multimedia resources such as images, audio, and video. The aforementioned first resource data can be specific resource data in the resource database corresponding to the first graphic attribute, such as button images or icon images. The aforementioned third resource data can be specific resource data in the resource database corresponding to the third graphic attribute, such as button images or icon images.

[0057] In its implementation, the device retrieves the first graphical attributes of the currently running screen from the cache. Next, it queries the resource database to determine the first resource data corresponding to these first graphical attributes. Based on the retrieved first resource data, the device constructs first screen components according to the requirements of the first graphical attributes. These first screen components are then stored in the cache for rapid construction and display of the currently running screen.

[0058] When switching to a new currently running screen is required, the device repeats a similar process. First, the device retrieves the third graphic attributes of the new currently running screen from the cache. Next, the device queries the resource database to determine the third resource data corresponding to these third graphic attributes. Based on the retrieved third resource data, the device constructs the third screen components according to the requirements of the third graphic attributes. These third screen components are then stored in the cache for rapid construction and display of the new currently running screen.

[0059] For ease of understanding, the following example illustrates the concept, but does not limit the scope of this embodiment. Assume a user is using an industrial automation monitoring system and is currently viewing a screen containing multiple sensor data points and control buttons. When the user clicks a button to switch to a new screen containing detailed historical data charts, the device executes the above process. The device first retrieves the first graphic attributes of the current screen from the cache, such as the button's position, size, and color. Next, the device queries the resource database to obtain the first resource data corresponding to these attributes, such as the button's image file. Based on this resource data, the device constructs the first screen components and stores them in the cache. Subsequently, the device constructs and displays the current screen based on the first screen components in the cache.

[0060] When a user switches to a new screen, the device retrieves the third-party graphical attributes of the new screen from the cache, such as the chart type, coordinates, and size. Next, the device queries the resource database to obtain the corresponding third-party resource data, such as the chart's image file. Based on this resource data, the device constructs third-party screen components and stores them in the cache. Finally, the device constructs and displays the new currently running screen based on the third-party screen components in the cache. Through this mechanism, the device can efficiently manage resources, reduce memory usage, and ensure smooth screen transitions and accurate display.

[0061] Based on the first and second embodiments, in the third embodiment, the content that is the same as or similar to that in Embodiments 1 and 2 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 3 , Figure 3 The flowchart below shows a third embodiment of the screen display method proposed in this application. Further, before the step of retrieving and displaying the currently running screen from the cache, the method includes: Step S01: When a start command is detected, a preset running screen is obtained and displayed, and the preset running screen is stored as the current running screen in the cache area.

[0062] It should be noted that the aforementioned startup command can be a user-triggered startup command, such as clicking an application icon or pressing a start button. The aforementioned preset running screen can be a screen that the user has pre-set to be displayed when the device starts up, such as the main interface.

[0063] In its implementation, the device retrieves relevant information about the preset running screen from a resource database. This information includes the graphical attributes of the preset running screen, such as color, position, size, and type. Next, based on these graphical attributes, the device obtains corresponding resource data from the resource library, such as images, icons, and text. The device then uses this resource data to construct components for the preset running screen, such as buttons, icons, and text boxes. After construction, the device combines these components to form a complete preset running screen and displays it on the screen. Simultaneously, the device stores the preset running screen as the current running screen in a cache for quick access and switching later.

[0064] Step S02: Determine whether the current running screen is the preset boot screen; Step S03: If so, then obtain the running screen to be displayed after the preset boot screen based on the preset screen running order, and store the running screen to be displayed as the previous switching historical running screen in the cache area; Step S04: If not, store the preset boot screen as the previous historical running screen in the cache area.

[0065] It should be noted that the aforementioned preset boot screen can be a specific screen that is displayed by default when the device is powered on, such as a welcome screen. The aforementioned preset screen execution order can be a pre-set screen display sequence within the device. The aforementioned screen to be displayed can be the screen to be displayed after the preset boot screen, according to the preset screen execution order. For example, if the main screen appears after the boot screen, then the main screen is the screen to be displayed.

[0066] In its implementation, upon startup, the device first determines whether the currently displayed screen is the preset boot screen. If it is, the device determines the next screen to be displayed, i.e., the pending boot screen, based on the preset screen execution order. At this point, the device stores this pending boot screen as a historical boot screen in its cache. If the current boot screen is not the preset boot screen, the device directly stores the preset boot screen as a historical boot screen in its cache.

[0067] To facilitate understanding, the following example illustrates the concept, but does not impose specific limitations on this embodiment. Assume a smart device whose default boot screen is a welcome screen, followed by the main interface, settings interface, and so on, in sequence. When the device starts, the welcome screen is displayed first. The device then determines that the current screen is the default boot screen and, based on the default screen sequence, identifies the main interface as the next screen to be displayed, storing it as a historical screen in the cache. If the user directly enters a specific application interface instead of starting from the default boot screen, the device will store the default boot screen as a historical screen in the cache. For example, if the user directly launches a video playback interface via a shortcut, the device determines that this interface is not the default boot screen and stores the welcome screen as a historical screen in the cache.

[0068] Furthermore, before the step of replacing the previously switched historical running screen in the cache with the expected running screen, the method further includes: Determine whether the expected running screen is the historical running screen from the previous switch; If not, then the step of replacing the previously switched historical running screen in the cache with the expected running screen is performed; If so, the old current running screen is used as the new previous historical running screen, and the old previous historical running screen is used as the new current running screen, and the new current running screen is displayed.

[0069] It should be noted that the aforementioned expected running screen can be a screen predicted to be displayed based on user operation or preset logic. The aforementioned previously switched historical running screen can be the screen that was previously displayed before the current running screen. The aforementioned cache area can be a region in memory used to temporarily store screen data for quick retrieval and switching. The aforementioned old current running screen can be the screen that the user is currently viewing. The aforementioned new previously switched historical running screen can be the previous current running screen that becomes a historical running screen after the switch. The aforementioned old previously switched historical running screen can be the historical running screen before the switch. The aforementioned new current running screen can be the screen that is being displayed after the switch.

[0070] In its implementation, when performing a screen switching operation, the device first determines whether the expected running screen is a previous historical running screen. The device makes this determination by comparing the identifiers or attributes of the expected running screen and the historical running screen. If the expected running screen is not a historical running screen, the device replaces the historical running screen from the previous switching screen in the cache with the expected running screen. Specifically, the device loads the expected running screen into the cache and updates the data structure within the cache, making the new expected running screen the historical running screen currently in the cache. If the expected running screen is a historical running screen, this usually means the user is switching back and forth between two screens. In this case, the device optimizes the switching process, using the old current running screen as the new previous historical running screen, and simultaneously using the old previous historical running screen as the new current running screen, displaying the new current running screen.

[0071] For ease of understanding, the following example illustrates the concept, but does not impose specific limitations on this embodiment. Assume a user is using a configuration screen of an industrial monitoring system, currently viewing screen A (the old current running screen), while the previously switched historical running screen was screen B (the old previously switched historical running screen). When the user triggers a switch command, the expected running screen is screen C. The device determines that screen C is not the historical running screen B, so it loads screen C into the cache and replaces screen B. At this point, screen C becomes the new current running screen, and screen A becomes the new previously switched historical running screen. If the user triggers a switch command again, and the expected running screen is screen B, the device determines that screen B is the historical running screen, so it uses screen A as the new previously switched historical running screen and displays screen B as the new current running screen. This mechanism allows users to switch back and forth between the two screens without reloading screen resources, thereby improving switching speed, reducing memory usage, and optimizing the user experience.

[0072] This embodiment also provides a first embodiment of a screen display device, please refer to... Figure 4 , Figure 4 This is a diagram of a screen display device provided in an embodiment of this application. The screen display device includes: The display module is used to retrieve and display the current running screen from the cache area, which caches the current running screen and the previously switched historical running screen. The caching module is used to determine the expected running screen for the next switch based on the switch instruction when a switch instruction triggered based on the current running screen is detected, and to replace the historical running screen of the previous switch in the cache with the expected running screen; The switching module is used to use the current running screen as the new historical running screen of the previous switch, use the expected running screen of the next switch as the new current running screen, and display the new current running screen; The display module is further configured to obtain a first graphic attribute corresponding to the currently running screen in the cache area; obtain a first screen component corresponding to the currently running screen based on the first graphic attribute, and store the first screen component in the cache area; and construct and display the currently running screen according to the first screen component stored in the cache area.

[0073] Referring to the first embodiment of the screen display device, this embodiment also proposes a second embodiment of the screen display device. The contents that are the same as or similar to those in the first embodiment of the screen display device can be referred to the above description, and will not be repeated hereafter.

[0074] The switching module is further configured to obtain the third graphic attribute corresponding to the new current running screen, and obtain the third screen component corresponding to the new current running screen based on the third graphic attribute; store the third screen component in the cache area, and delete the first screen component in the cache area; construct and display the new current running screen based on the third screen component stored in the cache area; The display module is further configured to determine the first resource data corresponding to the first graphic attribute in the resource database, and construct a first screen component according to the first resource data and the first graphic attribute; The switching module is further configured to determine the third resource data corresponding to the third graphic attribute in the resource database, and construct a third screen component according to the third resource data and the third graphic attribute.

[0075] Referring to the first embodiment and the second embodiment of the screen display device, this embodiment also proposes a third embodiment of the screen display device. The contents that are the same as or similar to the first embodiment and the second embodiment of the screen display device can be referred to the above description, and will not be repeated hereafter.

[0076] The display module is further configured to, upon detecting a startup command, acquire and display a preset running screen, and store the preset running screen as the current running screen in the cache area; determine whether the current running screen is a preset boot screen; if so, acquire the running screen to be displayed after the preset boot screen based on the preset screen running order, and store the running screen to be displayed as the previously switched historical running screen in the cache area; if not, store the preset boot screen as the previously switched historical running screen in the cache area. The caching module is further configured to determine whether the expected running screen is the previous switching historical running screen; if not, then execute the step of replacing the previous switching historical running screen in the cache with the expected running screen; if yes, then use the old current running screen as the new previous switching historical running screen, use the old previous switching historical running screen as the new current running screen, and display the new current running screen.

[0077] The screen display device provided in this embodiment, employing the screen display method described in the above embodiments, can solve the technical problem of excessive memory usage when a configured screen displays images. Compared with the prior art, the beneficial effects of the screen display device provided in this embodiment are the same as those of the screen display method described in the above embodiments, and other technical features in the screen display device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0078] This embodiment provides a screen display configuration panel, which includes: at least one processor; and a memory communicatively connected to the at least one processor, the memory further comprising a cache area; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute the screen display method in the above embodiment one.

[0079] The following is for reference. Figure 5 , Figure 5 This is a schematic diagram of a screen display configuration panel suitable for implementing the embodiments of this application. The screen display configuration panel in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), vehicle terminals (such as vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The screen display shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0080] like Figure 5As shown, the screen display configuration panel may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the screen display configuration panel. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the display configuration panel to communicate wirelessly or wiredly with other configuration panels to exchange data. Although the figures show display configuration panels with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented alternatively.

[0081] Specifically, according to this embodiment, the process described above with reference to the flowchart can be implemented as a computer software program. For example, this embodiment includes a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the disclosed embodiments of this embodiment.

[0082] The screen display configuration panel provided in this embodiment adopts the screen display method in the above embodiments, which can solve the technical problem of excessive memory consumption when the configuration panel displays screens. Compared with the prior art, the beneficial effects of the screen display configuration panel provided in this embodiment are the same as the beneficial effects of the screen display method provided in the above embodiments, and other technical features in this screen display configuration panel are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0083] It should be understood that the various parts disclosed in this embodiment can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0084] The above description is merely a specific implementation of this embodiment, but the protection scope of this embodiment is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this embodiment should be included within the protection scope of this embodiment. Therefore, the protection scope of this embodiment should be determined by the protection scope of the claims.

[0085] This embodiment provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the screen display method in the above embodiment.

[0086] The computer-readable storage medium provided in this embodiment may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0087] The aforementioned computer-readable storage medium may be included in the screen display configuration panel; or it may exist independently and not be assembled into the screen display configuration panel.

[0088] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the screen display configuration panel, cause the screen display configuration panel to perform screen display.

[0089] Computer program code for performing the operations of this embodiment can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—and conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0090] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this embodiment. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0091] The modules described in this embodiment can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0092] The readable storage medium provided in this embodiment is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-described screen display method, thereby solving the technical problem of excessive memory usage when the configured screen displays a screen. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this embodiment are the same as those of the screen display method provided in the above embodiments, and will not be repeated here.

[0093] The above descriptions are only some embodiments and do not limit the patent scope of this embodiment. All equivalent structural transformations made based on the technical concept of this application and the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included within the patent protection scope of this application.

Claims

1. A method for displaying a screen, characterized in that, The method is applied to a configuration screen with a buffer area, and the method includes: The current running screen is retrieved and displayed from the cache area, which contains the current running screen and the previously switched historical running screen. When a switching instruction triggered based on the current running screen is detected, the expected running screen for the next switching is determined according to the switching instruction, and the expected running screen is used to replace the historical running screen of the previous switching in the buffer. The current running screen is used as the new previous historical running screen, and the expected running screen for the next switch is used as the new current running screen, and the new current running screen is displayed.

2. The method as described in claim 1, characterized in that, The cache area stores the first graphic attributes involved in the current running screen and the second graphic attributes involved in the previously switched historical running screen. The current running screen is generated by obtaining the corresponding first screen component based on the first graphic attributes. The step of retrieving and displaying the currently running screen from the cache includes: Obtain the first graphic attribute corresponding to the currently running screen in the cache area; Based on the first graphic attribute, obtain the first screen component corresponding to the currently running screen, and store the first screen component in the cache area; The currently running screen is constructed and displayed based on the first screen component stored in the cache.

3. The method as described in claim 2, characterized in that, The step of displaying the new currently running screen includes: Obtain the third graphic attribute corresponding to the new current running screen, and obtain the third screen component corresponding to the new current running screen based on the third graphic attribute; The third screen component is stored in the cache area, and the first screen component is deleted from the cache area; The new currently running screen is constructed and displayed based on the third screen component stored in the cache.

4. The method as described in claim 3, characterized in that, The cache area also includes a resource database, which stores resource data corresponding to each graphic attribute. The step of obtaining the first screen component corresponding to the currently running screen based on the first graphic attribute includes: Determine the first resource data corresponding to the first graphic attribute in the resource database, and construct a first screen component according to the first resource data and the first graphic attribute; The step of obtaining the third screen component corresponding to the new currently running screen based on the third graphic attribute includes: The third resource data corresponding to the third graphic attribute in the resource database is determined, and a third screen component is constructed according to the third resource data and the third graphic attribute.

5. The method as described in claim 1, characterized in that, Before the step of retrieving and displaying the currently running screen from the cache, the method further includes: When a start command is detected, a preset running screen is obtained and displayed, and the preset running screen is stored as the current running screen in the cache area; Determine whether the currently running screen is the preset boot screen; If so, the running screen to be displayed after the preset boot screen is obtained based on the preset screen running order, and the running screen to be displayed is stored in the cache area as the previous switching history running screen; If not, the preset boot screen is stored in the cache area as the previously switched historical running screen.

6. The method as described in claim 1, characterized in that, Before the step of replacing the previously switched historical running screen in the cache with the expected running screen, the method further includes: Determine whether the expected running screen is the historical running screen from the previous switch; If not, then the step of replacing the previously switched historical running screen in the cache with the expected running screen is performed; If so, the old current running screen is used as the new previous historical running screen, and the old previous historical running screen is used as the new current running screen, and the new current running screen is displayed.

7. A screen display device, characterized in that, The device includes: The display module is used to retrieve and display the current running screen from the cache area, which caches the current running screen and the previously switched historical running screen. The caching module is used to determine the expected running screen for the next switch based on the switch instruction when a switch instruction triggered based on the current running screen is detected, and to replace the historical running screen of the previous switch in the cache with the expected running screen; The switching module is used to use the current running screen as the new historical running screen of the previous switch, use the expected running screen of the next switch as the new current running screen, and display the new current running screen.

8. A configuration panel, characterized in that, The configuration screen includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. The memory also includes a cache area. The computer program is configured to implement the steps of the screen display method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the screen display method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the screen display method as described in any one of claims 1 to 6.

Images