Page display interaction method of embedded device, embedded device and storage medium
By determining the page display mode based on the rotation angle parameters in the configuration file in the embedded device, the problem of limited page interaction flexibility in the Qt framework is solved, realizing the separation of the development environment and the runtime environment, and improving the flexibility of page interaction and development efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- POWEROAK INNOVATION CO
- Filing Date
- 2026-03-20
- Publication Date
- 2026-06-02
AI Technical Summary
In existing Qt-based embedded graphical user interface applications, the flexibility of page interaction is limited, and there are problems such as insufficient adaptability to human-computer interaction system development environments, insecure page resource management, lack of centralized control of page navigation logic, low efficiency of cross-page communication mechanisms, and high coupling between pages.
By obtaining the rotation angle parameter in the configuration file, the page display mode is determined, and the current page is closed and candidate pages are displayed according to the mode, realizing the separation of development environment and runtime environment, and improving the flexibility and adaptability of page interaction.
It significantly improves the flexibility and ease of development of embedded device page interaction, simplifies the UI logic verification and debugging process, and shortens the development iteration cycle.
Smart Images

Figure CN122131938A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of device page display technology, and in particular to a page display interaction method for embedded devices, an embedded device, and a storage medium. Background Technology
[0002] In embedded graphical user interface (GUI) applications developed using the Qt framework, such as industrial control panels, smart terminals, and human-computer interaction systems for medical devices, navigation and switching between multiple functional pages are required. These applications have high demands for interface stability and responsiveness. However, the Qt framework itself does not provide an official page routing component similar to web front-end frameworks (such as Vue Router or React Router). That is, the Qt framework does not have a standard class called QRouter or QNavigationManager to manage page navigation, history stacks, parameter passing, etc. (e.g., switching from QWidgetA to QWidgetB).
[0003] Currently, the relevant technology uses the standard QStackedWidget component provided by the Qt framework, combined with the signal and slot mechanism, to implement page switching. QStackedWidget is a container class in the Qt Widgets module that allows multiple QWidget child pages to be stacked together, and the currently displayed page can be controlled via index or pointer.
[0004] In addition, some developers manually manage the show() / hide() methods of QWidget for page control, or maintain a QList.<QWidget*> Implementing simple page stack logic. These methods constitute the mainstream page navigation technology route in current embedded Qt framework applications. Although the above technical solutions can realize the basic page switching function of embedded devices, they have the following significant drawbacks in practical engineering applications: insufficient adaptability to human-computer interaction system development environments, insecure page resource management, lack of centralized control of page navigation logic, low efficiency of cross-page communication mechanisms, and high coupling between pages, which severely limit the flexibility of page interaction in embedded device human-computer interaction systems. Summary of the Invention
[0005] In view of this, one objective of the embodiments of this application is to provide a page display interaction method, an embedded device, and a storage medium for an embedded device, aiming to improve the situation where the flexibility of page interaction in the human-computer interaction system of an embedded device is severely limited in the related art.
[0006] In a first aspect, embodiments of this application provide a page display interaction method for an embedded device, comprising: obtaining a configuration file of the embedded device; determining a page display mode of the interactive page of the embedded device according to a rotation angle parameter in the configuration file, wherein the page display mode is used to characterize the display direction of the interactive page of the embedded device; responding to a close display operation received by the current page, closing the display of the current page according to the page display mode, wherein the current page is the interactive page displayed at the current moment; and displaying a candidate page according to the page display mode, wherein the candidate page is any one of a plurality of interactive pages of the embedded device to be displayed.
[0007] Secondly, embodiments of this application provide an embedded device, including a processor and a memory. The processor is communicatively connected to the memory, and the memory stores computer program instructions executable by the processor. When the computer program instructions are executed by the processor, the embedded device performs the page display interaction method for the embedded device provided in the first aspect.
[0008] Thirdly, embodiments of this application provide a computer-readable storage medium storing processor-executable computer program instructions, which, when executed by the processor, cause the processor to perform the page display interaction method for the embedded device provided in the first aspect.
[0009] The embodiments of this application have the following beneficial effects: Unlike related technologies, the embodiments of this application determine the page display mode of the interactive page according to the rotation angle parameters of the configuration file, and close the display of the current page and the display of candidate pages according to the page display mode. In this way, the development environment and operating environment of the human-computer interaction system can be flexibly distinguished and adapted according to the display direction of the interactive page. At the same time, the page interaction logic is centrally controlled, improving the flexibility of page interaction of embedded devices. Attached Figure Description
[0010] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the accompanying drawings used in the description of the related technologies or embodiments will be briefly introduced below. Obviously, the drawings described below only show some embodiments of this application and should not be considered as limiting the scope of protection. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0011] Figure 1A This is a schematic diagram illustrating an application scenario for displaying an interactive page of an interactive embedded device in some embodiments of this application; Figure 1B This is a schematic diagram of an interactive page of an embedded device in some embodiments of this application, wherein the interactive page is displayed in landscape orientation; Figure 1C This is a schematic diagram of another interactive page of an embedded device in some embodiments of this application, wherein the interactive page is displayed in landscape orientation; Figure 1D This is a schematic diagram of another interactive page of an embedded device in some embodiments of this application, wherein the interactive page is displayed in portrait orientation; Figure 1E This is a schematic diagram of another interactive page of an embedded device in some embodiments of this application, wherein the interactive page is displayed in portrait orientation; Figure 2 These are schematic diagrams of the structure of embedded devices provided in some embodiments of this application; Figure 3 This is a flowchart illustrating the page display and interaction method for an embedded device provided in some embodiments of this application; Figure 4 yes Figure 3 A schematic diagram of a sub-process of step S32 in the page display interaction method of the embedded device shown in the embodiment; Figure 5A yes Figure 3 A schematic diagram of a sub-process of step S33 in the page display interaction method of the embedded device shown in the embodiment; Figure 5B This is a schematic diagram of the interactive view popping from the stack in some embodiments of this application; Figure 5C This is a schematic diagram of the popping of interactive pages from the stack in some embodiments of this application; Figure 6A yes Figure 3 A schematic diagram of a sub-process of step S34 in the page display interaction method of the embedded device shown in the embodiment; Figure 6B This is a schematic diagram of the structure of the second stack in some embodiments of this application; Figure 7 This is a schematic diagram of interactive view being pushed onto the stack in some embodiments of this application; Figure 8 This is a schematic diagram of interactive pages being pushed onto the stack in some embodiments of this application; Figure 9A This is a schematic diagram showing candidate views in some embodiments of this application; Figure 9B This is a schematic diagram showing the candidate page in some embodiments of this application. Detailed Implementation
[0012] To make the objectives and advantages of the embodiments of this application more readily understood, 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 them. The detailed description of the embodiments of this application in the accompanying drawings is not intended to limit the scope of protection claimed by this application, but only represents selected embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0013] It should be noted that, unless there is a conflict, the various technical features involved in the embodiments of this application described below can be combined with each other, and all are within the protection scope of this application. Furthermore, although functional modules are divided in the device or structural schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. In addition, the terms "first," "second," "third," and other similar expressions used herein do not limit the data or execution order, but are only for illustrative purposes and to distinguish identical or similar items with substantially the same function and effect, and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features.
[0014] Unless otherwise defined, the technical and scientific terms used in this specification have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. It should be understood that the term "and / or" as used in this specification includes any and all combinations of one or more of the listed items.
[0015] The technical solution for implementing basic page switching functions of embedded devices in embedded graphical user interface (GUI) applications based on the Qt framework, as introduced in the background technology, still has the following defects in practical engineering applications: insufficient adaptability of human-computer interaction system development environment, insecure page resource management, lack of centralized control of page navigation logic, low efficiency of cross-page communication mechanism, and high coupling between pages, which seriously limits the flexibility of page interaction in the human-computer interaction system of embedded devices.
[0016] In view of this, embodiments of this application provide a page display interaction method for embedded devices. By determining the page display mode of the interactive page according to the rotation angle parameters in the configuration file, and closing the display of the current page and displaying candidate pages according to the page display mode, it is possible to flexibly distinguish and adapt to the development and operation environment of the human-computer interaction system according to the display direction of the interactive page, while centrally controlling the page interaction logic, thereby improving the flexibility of page interaction in embedded devices.
[0017] Please see Figure 1A , Figure 1A The illustrations depict application scenarios of displaying interactive pages on interactive embedded devices in some embodiments of this application.
[0018] like Figure 1A As shown, this application scenario includes embedded device 100, which includes any suitable device or apparatus such as a smartphone, electronic dictionary, or tablet computer. Figure 1A The embedded device 100 shown is a tablet computer.
[0019] For example, this application embodiment obtains a configuration file 101 of the embedded device 100. The configuration file 101 includes a rotation angle parameter, which characterizes the rotation angle of the interactive page of the embedded device 100. The value of the rotation angle parameter Rotation is 0°, 90°, 180°, or 270°. The page display mode of the interactive page is determined based on the rotation angle parameter, and whether the interactive page should be rotated entirely is determined based on the page display mode. This allows the interactive page to be displayed in a standard landscape mode in the development environment, allowing developers to intuitively view and debug the page. It also allows the interactive page to be displayed in a portrait mode in the runtime environment, thus adapting to the vertical physical screen of the embedded device 100 and presenting a visual effect consistent with the development environment.
[0020] In this embodiment, when the rotation angle parameter Rotation = 90° or 270°, the interactive page is displayed in the first display mode, requiring the entire interactive page of the embedded device 100 to be rotated. When the rotation angle parameter Rotation = 0° or 180°, the interactive page is displayed in the second display mode, requiring no overall rotation of the interactive page of the embedded device 100.
[0021] In this embodiment, when the current page receives a close display operation, it responds to the operation by closing the display of the current page according to the page display mode. The current page is the interactive page currently displayed. For example, when the rotation parameter is 0° or 180°, the interactive page of the embedded device 100 is in the second display mode, and it is not necessary to rotate the interactive page of the embedded device 100 as a whole. In this case, the interactive page currently displayed (i.e., the current page) is as follows: Figure 1B As shown, Figure 1B The current page shown receives a close display operation. In this embodiment of the application, the response is as follows: Figure 1B The current page receives a close display operation, and the display is closed according to the second display mode. Figure 1B The current page is shown. For example, when the angle parameter Rotation = 90° or 270°, the interactive page of the embedded device 100 is displayed in the first display mode. If the entire interactive page of the embedded device 100 needs to be rotated, the currently displayed interactive page (i.e., the current page) will look like this. Figure 1D As shown, Figure 1D The current page shown receives a close display operation, and this application embodiment responds accordingly. Figure 1D The current page receives a "close display" operation and closes the display according to the second display mode. Figure 1D The current page shown.
[0022] For example, when the display is turned off Figure 1B Following the current page shown, candidate pages are displayed according to the page display mode. A candidate page is any one of multiple interactive pages on the embedded device to be displayed. For example, when the rotation parameter is 0° or 180°, the page display mode of the interactive page of the embedded device 100 is the second display mode, and it is not necessary to rotate the entire interactive page of the embedded device 100. In this case, the candidate page is as follows: Figure 1C As shown, this embodiment of the application displays according to the second display mode. Figure 1C The candidate pages are shown below. For example, when the rotation parameter is 90° or 270°, the interactive page of the embedded device 100 is displayed in the first display mode. The interactive page of the embedded device 100 needs to be rotated entirely; in this case, the candidate pages are as follows: Figure 1E As shown, this embodiment of the application displays the following according to the second display mode: Figure 1E The candidate pages shown.
[0023] By employing the above methods, a separate development model is achieved where "the development environment does not need to be rotated, while the runtime environment rotates automatically." This allows for convenient closed-loop verification of UI logic and page layout issues within the development environment, avoiding frequent flashing and restarting of embedded devices. This significantly improves development convenience and debugging efficiency, effectively shortening the development iteration cycle. Furthermore, the development and runtime environments of the human-computer interaction system (i.e., embedded graphical user interface (GUI) applications based on the Qt framework) are flexibly differentiated and adapted according to the display orientation of the interactive page. Centralized control of page interaction logic enhances the flexibility of page interaction on embedded devices.
[0024] It should be understood that, Figures 1A to 1E The illustrated embodiments are merely illustrative of one scenario in which an interactive page of an embedded device is displayed in some embodiments of this application, and do not limit the structure, type, or number of embedded devices in other embodiments. For example, in some other embodiments, the embedded device may be an electronic dictionary, a smartphone, or any other suitable type of device or apparatus. Furthermore, the embedded device in some other embodiments may also include... Figure 1A The tablet shown has more or fewer components, or has the same... Figure 1A The tablets shown have different configurations.
[0025] To facilitate understanding of the page display and interaction method of the embedded device provided in the embodiments of this application, the embedded device provided in the embodiments of this application will be described in detail first.
[0026] Please see Figure 2 , Figure 2 The schematic diagram illustrates the structure of an embedded device provided in some embodiments of this application.
[0027] See Figure 2 As shown, the embedded device 100 includes at least one processor 110 and a memory 120 that are communicatively connected. Figure 2 Taking a bus system 130 and a processor 110 as an example, the various components in the embedded device 100 are coupled together through the bus system 130, which is used to realize the connection and communication between the various components. It is easy to understand that the bus system 130 includes not only a data bus, but also a power bus, a control bus, and a status signal bus, etc. However, for the sake of clarity and brevity, in... Figure 2 The general labels all buses as Bus System 130. This is understandable. Figure 2 The structures shown in the embodiments are merely illustrative and do not limit the structure of the embedded devices described above. For example, the embedded devices described above may also include... Figure 2 The structure shown has more or fewer components, or has the same Figure 2The diagram shows different configurations of the structure.
[0028] Specifically, processor 110 is configured to provide computational and control capabilities to support embedded device 100 in executing corresponding business logic and functions. For example, it supports embedded device 100 in executing the page display interaction method for embedded devices provided in the embodiments of this application, or in executing the steps in any possible implementation of the page display interaction method for embedded devices provided in the embodiments of this application. It should be understood that processor 110 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.
[0029] The memory 120, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, instructions, and modules, such as the program, instructions, and modules corresponding to the page display interaction method of the embedded device in the embodiments of this application. In some embodiments, the memory 120 may include a program storage area and a data storage area. The program storage area may store the operating system and an application program required for at least one function, and the data storage area may store data created according to the use of the processor 110. The processor 110 executes various functional applications and data processing of the embedded device 100 by running the non-transitory software programs, instructions, and modules stored in the memory 120, thereby implementing the page display interaction method of the embedded device provided in the embodiments of this application, or executing the steps in any possible implementation of the page display interaction method of the embedded device provided in the embodiments of this application. In some embodiments, the memory 120 may include high-speed random access memory and may also include non-transitory memory. For example, at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory 120 may also include memory remotely located relative to the processor 110, and these remotely located memories may be connected to the processor 110 through a communication network. It is understood that examples of the aforementioned communication networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0030] As can be understood from the above, the entity implementing the embedded device page display interaction method provided in this application embodiment can be any suitable type of embedded device with certain computing and control capabilities, such as the embedded device 100 described above. In some feasible implementations, the embedded device page display interaction method provided in this application embodiment can be implemented by a processor executing computer program instructions stored in the memory.
[0031] The following will describe in detail the page display and interaction method of the embedded device provided in the embodiments of this application, with reference to the exemplary applications and implementations of the embedded device provided in the embodiments of this application.
[0032] It is understood that the page display interaction method for embedded devices provided in this application embodiment can be applied to the aforementioned embedded devices (such as embedded device 100). Specifically, the execution entity of the page display interaction method for embedded devices is one or at least two processors of the embedded device.
[0033] See Figure 3 As shown, in this embodiment of the application, the display and interaction of the embedded device page are realized through steps S31 to S34.
[0034] Step S31: Obtain the configuration file of the embedded device.
[0035] For example, the configuration file of the embedded device can be stored in any suitable storage medium such as a server or storage device. This embodiment of the application obtains the configuration file of the embedded device from any suitable storage medium such as a server or storage device. The configuration file includes a rotation angle parameter, which characterizes the rotation angle of the interactive page of the embedded device. The value of the rotation angle parameter is 0°, 90°, 180°, or 270°.
[0036] In this embodiment, when the rotation angle parameter is equal to 90° or 270°, it indicates that the entire interactive page of the embedded device needs to be rotated. When the rotation angle parameter is equal to 0° or 180°, it indicates that the entire interactive page of the embedded device does not need to be rotated.
[0037] Step S32: Determine the page display mode of the interactive page of the embedded device according to the rotation angle parameter in the configuration file.
[0038] The page display mode represents the display orientation of the interactive page on the embedded device. When the page display mode is set to standard display mode, the interactive page of the embedded device is displayed in standard landscape mode. When the page display mode is set to reference display mode, the interactive page of the embedded device is displayed in reference portrait mode.
[0039] For example, in this embodiment of the application, the rotation angle parameter is extracted from the configuration file, and the page display mode of the interactive page of the embedded device is determined according to the value of the rotation angle parameter. For example, when the value of the rotation angle parameter is equal to 0° or 180°, the standard display mode is determined as the page display mode of the interactive page of the embedded device. When the value of the rotation angle parameter is equal to 90° or 270°, the reference display mode is determined as the page display mode of the interactive page of the embedded device.
[0040] Step S33: In response to the close display operation received by the current page, close the display of the current page according to the page display mode.
[0041] In this embodiment, the current page is the interactive page currently displayed on the embedded device. The close operation can be a page close action triggered when the user clicks the close button on the current page, for example, see [link to example]. Figure 1B When the user clicks on such Figure 1B When the user clicks the interactive button within the red rectangle 102 on the current page, a corresponding close / display operation is triggered, and the current page receives the close / display operation. It should be understood that the close / display operation can also be a page close operation triggered when the user clicks any other suitable button on the current page; this embodiment does not limit this in any way.
[0042] For example, in response to a closed display operation received by the current page, this embodiment of the application closes the display of the current page according to the page display mode. For instance, when the page display mode is the standard display mode, the current page is closed according to the standard display mode, that is, the current page is closed in standard landscape mode. When the page display mode is the reference display mode, the current page is closed according to the reference display mode, that is, the current page is closed in reference portrait mode.
[0043] Step S34: Display candidate pages according to the page display mode.
[0044] In this embodiment, the candidate page is any one of the multiple interactive pages to be displayed on the embedded device.
[0045] For example, in this embodiment of the application, any one of the multiple interactive pages to be displayed from the multiple interactive pages of the embedded device is selected as a candidate page, such as selecting... Figure 1C The interactive page shown is used as a candidate page, and the candidate page is displayed according to the page display mode. For example, when the page display mode is the standard display mode, the candidate page is displayed according to the standard display mode, that is, the candidate page is displayed in the standard landscape mode. When the page display mode is the reference display mode, the candidate page is displayed according to the reference display mode, that is, the candidate page is displayed in the reference portrait mode.
[0046] In summary, this application embodiment determines the page display mode of the interactive page based on the rotation angle parameters in the configuration file, and closes the display of the current page and displays candidate pages according to the page display mode. In this way, the development environment and operating environment of the human-computer interaction system can be flexibly distinguished and adapted according to the display direction of the interactive page. At the same time, the page interaction logic is centrally controlled, improving the flexibility of page interaction in embedded devices.
[0047] See Figure 4 As shown, in this embodiment of the application, steps S321 to S322 are used to determine the page display mode of the interactive page of the embedded device according to the rotation angle parameter in the configuration file.
[0048] Step S321: In response to the value of the rotation angle parameter being equal to the first preset angle value, determine the first display mode as the page display mode of the embedded device.
[0049] In this embodiment, the first display mode is used to characterize the display direction of the interactive page as a first direction, which is a portrait orientation. That is, when the page display mode is the first display mode, the interactive page of the embedded device is displayed in portrait mode. The first preset angle values include 90° and 270°.
[0050] For example, when the value of the rotation angle parameter is equal to the first preset angle value (i.e., 90° or 270°), the embodiment of this application determines the first display mode as the page display mode of the embedded device.
[0051] Step S322: In response to the value of the rotation angle parameter being equal to the second preset angle value, determine the second display mode as the page display mode of the embedded device.
[0052] In this embodiment, the second display mode is used to characterize the display direction of the interactive page as a second direction, which is the landscape orientation. That is, when the page display mode is the second display mode, the interactive page of the embedded device is displayed in landscape mode. Obviously, the first direction is different from the second direction. The second preset angle value includes 0° and 180°.
[0053] For example, when the value of the rotation angle parameter is equal to the second preset angle value (i.e., 0° or 180°), the embodiment of this application determines the second display mode as the page display mode of the embedded device.
[0054] See Figure 5A As shown, in this embodiment of the application, steps S331 to S332 are used to close the current page display according to the page display mode.
[0055] Step S331: In response to the page display mode being the first display mode, close the display of the current view in the first stack and close the display of the current page in the second stack according to the number of interactive views in the first stack.
[0056] In this embodiment, the interactive view is a view encapsulating the interactive page of the embedded device, and the current view is an interactive view encapsulating the current page. It is understood that, based on the characteristics of the Qt framework, in embedded graphical user interface (GUI) applications developed based on the Qt framework, when displaying the interactive page in portrait orientation / portrait mode, the interactive page needs to be encapsulated in a view to display the view encapsulating the interactive page (i.e., the interactive view), thus achieving the purpose of displaying the interactive page. It is understood that the first stack is configured to store the interactive view, and the second stack is configured to store the interactive page of the embedded device. In this embodiment, the first stack and the second stack are created in advance, and the first stack is configured to store the interactive view, and the second stack is configured to store the interactive page of the embedded device.
[0057] For example, when the page display mode is the first display mode, it means that the interactive page needs to be displayed in portrait orientation / portrait mode. The display of the current page is turned off according to the number of interactive views in the first stack. For example, when there are interactive views in the first stack (i.e., the number of interactive views is greater than or equal to the preset number threshold 1), according to the first-in-last-out and last-in-first-out characteristics of the stack structure, the interactive view containing the current page (i.e., the current view) needs to be taken out from the top of the first stack, and then the display of the interactive view containing the current page is turned off. Then the current page is taken out from the top of the second stack, and finally the display of the current page is turned off.
[0058] Specifically, in this embodiment of the application, steps S3311 to S3314 are used to close the display of the current view in the first stack and close the display of the current page in the second stack according to the number of interactive views in the first stack.
[0059] Step S3311: In response to the number of interactive views in the first stack being greater than or equal to a first quantity threshold, retrieve the current view located at the top of the first stack.
[0060] Step S3312: Turn off the display of the current view.
[0061] In this step, the first quantity threshold is 1. For example, when the number of interactive views in the first stack is detected to be greater than or equal to the first quantity threshold of 1, this embodiment of the application removes the current view located at the top of the first stack and turns off the display of the current view.
[0062] Step S3313: Retrieve the current page located at the top of the second stack.
[0063] Step S3314: Close the display of the current page.
[0064] For example, after retrieving and closing the display of the current view, this embodiment of the application retrieves the current page located at the top of the second stack and closes the display of the current page.
[0065] For example, please see Figure 5B and Figure 5C The first stack stores three interactive views: the Settings-Advanced Settings page view, the Settings page view, and the Home page view. The Settings-Advanced Settings page view is the current view (i.e., the interactive view encapsulating the current page) and is located at the top of the first stack. The second stack stores three interactive pages: the Settings-Advanced Settings page, the Settings page, and the Home page. The Settings-Advanced Settings page is the current page (i.e., the interactive page currently displayed) and is located at the top of the second stack. The Settings-Advanced Settings page view is the current view (also an interactive view encapsulating the current page) and is located at the top of the first stack. Clearly, the number of interactive views in the first stack (3) is greater than the first threshold (1). In this embodiment, the Settings-Advanced Settings page view is retrieved from the first stack, and then its display is closed. After retrieving and closing the Settings-Advanced Settings page view, this embodiment retrieves the Settings-Advanced Settings page from the second stack and closes its display.
[0066] Step S332: In response to the page display mode being the second display mode, close the display of the current page according to the number of interactive pages in the second stack.
[0067] For example, when the page display mode is the second display mode, it means that the interactive page needs to be displayed in landscape orientation / landscape mode. The display of the current page is turned off according to the number of interactive pages in the second stack. For example, when there are interactive pages in the second stack (i.e., the number of interactive pages is greater than or equal to the preset number threshold 1), according to the first-in-first-out and last-in-first-out characteristics of the stack structure, the current page needs to be taken out from the top of the second stack first, and then the display of the current page is turned off.
[0068] Specifically, in this embodiment of the application, steps S3321 to S3322 are used to close the display of the current page based on the number of interactive pages in the second stack.
[0069] Step S3321: In response to the number of interactive pages in the second stack being greater than or equal to the second quantity threshold, retrieve the current page located at the top of the second stack.
[0070] Step S3322: Close the display of the current page.
[0071] In this embodiment, the second quantity threshold is 1. For example, when the number of interactive pages in the second stack is detected to be greater than or equal to the second quantity threshold of 1, this embodiment of the application will remove the current page located at the top of the second stack and turn off the display of the current page.
[0072] For example, please see Figure 5C The second stack stores three interactive pages: the Settings-Advanced Settings page, the Settings page, and the Home page. The Settings-Advanced Settings page is the current page (i.e., the interactive page currently displayed) and is located at the top of the second stack. Clearly, the number of interactive pages in the second stack (3) is greater than the second threshold (1). In this embodiment, the Settings-Advanced Settings page is retrieved from the second stack and its display is turned off.
[0073] In some embodiments, after closing the display of the current page, the page display interaction method for embedded devices provided in this application embodiment further includes step S301.
[0074] Step S301: Delete the current page and release the memory resources occupied by the current page.
[0075] For example, after closing the current page, this embodiment of the application destroys the current page to release the memory resources occupied by the current page. For instance, please refer to... Figure 5C In this embodiment of the application, the current page is safely delayed by calling the deleteLater() function, so as to ensure that the occupied memory resources are released only after the page events are processed, thus effectively avoiding memory leaks and runtime crashes.
[0076] See Figure 6A As shown, in this embodiment of the application, steps S341 to S342 are used to display candidate pages according to the page display mode.
[0077] Step S341: Determine the page storage type of the candidate page.
[0078] In this embodiment, the page storage type is used to characterize the storage state of the candidate page, that is, to characterize whether the candidate page is stored in the second stack and the way it is stored in the second stack.
[0079] In this embodiment, when a candidate page is not stored in the second stack, its page storage type is determined to be the first storage type. When a candidate page is stored in the second stack but is not permanently residing in the second stack, its page storage type is determined to be the second storage type. When a candidate page is stored in the second stack and is permanently residing in the second stack, its page storage type is determined to be the third storage type.
[0080] In this context, "resident in the second stack" refers to interactive pages that remain in memory and are not removed from the second stack. Based on actual business needs, one or more interactive pages are identified as residing in the second stack. For faster response times, these pages are placed at the top of the second stack (this page will not be popped from the stack, for example...). Figure 6B In page 1) of the second stack shown, this method can be understood as creating an internal page stack within the page. Since there's no need to release the occupied memory resources, it allows for direct and convenient management of interactive pages residing in the second stack, achieving the goal of quickly switching between residing memory pages. See also... Figure 6B As shown, page 1 and pages 1-1, 1-2, 1-3, and 1-4 in the page stack within page 1 will not be removed from the second stack and will not be destroyed. In some embodiments, pages 1-1, 1-2, 1-3, and 1-4 are respectively the homepage, a form or data page, a device settings page, and a system settings page.
[0081] Step S342: Display candidate pages according to page storage type and page display mode.
[0082] According to the embodiments of this application, candidate pages are adaptively displayed based on different page storage types and page display modes to match different display directions and storage types of interactive pages.
[0083] In some embodiments, the present application implements displaying candidate pages according to page storage type and page display mode through steps S3421 to S3423.
[0084] Step S3421: When the response page storage type is the first storage type and the page display mode is the first display mode, the candidate page is encapsulated in the interactive view to obtain the candidate view.
[0085] In this embodiment, the candidate view is an interactive view that encapsulates candidate pages, and the first storage type is used to indicate that the candidate pages are not stored in the second stack.
[0086] For example, when the page storage type is the first storage type and the page display mode is the first display mode, it indicates that the candidate page is not stored in the second stack and the candidate page needs to be rotated as a whole. In this embodiment, the candidate page is encapsulated in an interactive view to obtain a candidate view. In some embodiments, the ShowRotation function is called to rotate and encapsulate the candidate page to obtain a candidate view. The specific process is as follows: a blank scene is created, the background color of the scene is set to pure black, the candidate page is placed in the scene, the scene with the candidate page is rotated as a whole according to the value of the rotation angle parameter, a blank view is created, the rotated scene with the candidate page is encapsulated in the view, the name of the view is named after the candidate page, and finally the candidate view is obtained.
[0087] Step S3422: Add the candidate view to the top of the first stack and add the candidate page to the top of the second stack.
[0088] Step S3423: Display the candidate view to show the candidate page encapsulated in the candidate view.
[0089] For example, after encapsulating the candidate page in the interactive view to obtain the candidate view, the candidate view is added to the top of the first stack, and the candidate page is added to the top of the second stack. This embodiment of the application displays the candidate view to show the candidate page encapsulated within the candidate view, thereby displaying the candidate page.
[0090] For example, please see Figure 7 and Figure 8 The Settings-Advanced Settings-Factory Reset page is selected as a candidate page, and the Settings-Advanced Settings-Factory Reset page view is selected as a candidate view. The Settings-Advanced Settings-Factory Reset page view is added to the top of the first stack, and the Settings-Advanced Settings-Factory Reset page is added to the top of the second stack. The Settings-Advanced Settings-Factory Reset page view is then displayed to show the Settings-Advanced Settings-Factory Reset page encapsulated within the Settings-Advanced Settings-Factory Reset page view.
[0091] In some embodiments, the present application implements displaying candidate pages according to page storage type and page display mode through steps S3424 to S3425.
[0092] Step S3424: If the response page storage type is the first storage type and the page display mode is the second display mode, add the candidate page to the top of the second stack.
[0093] Step S3425: Display the candidate page.
[0094] For example, when the page storage type is the first storage type and the page display mode is the second display mode, it means that the candidate page is not stored in the second stack and there is no need to rotate the candidate page as a whole. In this embodiment of the application, the candidate page is added to the top of the second stack and the candidate page is displayed.
[0095] For example, please see Figure 8 The Settings-Advanced Settings-Factory Reset page is a candidate page. In this embodiment, the Settings-Advanced Settings-Factory Reset page is added to the top of the second stack and displayed.
[0096] In some embodiments, the present application implements displaying candidate pages according to page storage type and page display mode through steps S342A to S342C.
[0097] Step S342A: When the response page storage type is the second storage type and the page display mode is the first display mode, obtain the candidate view from the first stack.
[0098] Step S342B: Move the candidate view to the top of the first stack.
[0099] Step S342C: Display the candidate view to show the candidate page encapsulated within the candidate view.
[0100] In this embodiment, the candidate view is an interactive view that encapsulates candidate pages, and the second storage type is used to indicate that the candidate page has been stored in the second stack and is not permanently resident in the second stack.
[0101] For example, when the page storage type is the second storage type and the page display mode is the first display mode, it means that the candidate page has been stored in the second stack, but is not permanently residing in the second stack, and needs to be rotated as a whole. In this embodiment, the candidate view is obtained from the first stack, and the candidate view is moved to the top of the first stack and displayed to show the candidate page encapsulated in the candidate view. It can be understood that when the candidate page has been stored in the second stack, the first stack correspondingly stores an interactive view (i.e., a candidate view) encapsulating the candidate page.
[0102] For example, see Figure 9A As shown, the Settings-Advanced Settings-Factory Reset page view is a candidate view. In this embodiment, the Settings-Advanced Settings-Factory Reset page view is obtained from the first stack, and the Settings-Advanced Settings-Factory Reset page view is moved to the top of the first stack to display the Settings-Advanced Settings-Factory Reset page view, so as to display the Settings-Advanced Settings-Factory Reset page encapsulated in the Settings-Advanced Settings-Factory Reset page view.
[0103] In some embodiments, the present application implements displaying candidate pages according to page storage type and page display mode through steps S342D to S342E.
[0104] Step S342D: If the response page storage type is the second storage type and the page display mode is the second display mode, retrieve the candidate page from the second stack.
[0105] Step S342E: Move the candidate page to the top of the second stack and display the candidate page.
[0106] For example, when the page storage type is the second storage type and the page display mode is the second display mode, it means that the candidate page has been stored in the second stack, does not reside in the second stack, and does not need to be rotated as a whole. In this embodiment of the application, the candidate page is obtained from the second stack, moved to the top of the second stack, and displayed.
[0107] For example, please see Figure 9B The Settings-Advanced Settings-Factory Reset page is a candidate page. In this embodiment, the Settings-Advanced Settings-Factory Reset page is obtained from the second stack, moved to the top of the second stack, and then displayed.
[0108] In some embodiments, the present application implements displaying candidate pages according to page storage type and page display mode through steps S342F to S342L.
[0109] Step S342F: When the response page storage type is the third storage type and the page display mode is the first display mode, close the interactive pages in the second stack except for the reference page.
[0110] The third storage type is used to represent that the candidate page has been stored in the second stack and resides in the second stack, and the reference page is the interactive page that is stored in the second stack and resides in the second stack.
[0111] For example, when the page storage type is the third storage type and the page display mode is the first display mode, it means that the candidate page has been stored in the second stack, resides in the second stack, and needs to be rotated as a whole. In this embodiment of the application, the interactive pages in the second stack except for the reference page are turned off.
[0112] For example, please see Figure 6BPage 1 and its sub-pages 1-1, 1-2, 1-3, and 1-4 are all reference pages. When the page storage type is the third storage type and the page display mode is the first display mode, the interactive pages in the second stack other than the reference pages are closed, that is, pages 2, 3, 4, and N are closed.
[0113] Step S342G: Obtain the interactive view located at the top of the first stack as the target view.
[0114] The target view is an interactive view that encapsulates the target page. The target page and the candidate page may be the same or different. In this embodiment, the target page and the candidate page are compared to determine whether they are the same.
[0115] It is understandable that after closing the interactive pages in the second stack except for the reference page, the system compares and determines whether the target page encapsulated in the target view is the same as the candidate page, thereby determining whether to switch the display of the candidate page. That is, when the target page and the candidate page are the same, the target page encapsulated in the target view is the candidate page and the display of the candidate page is not switched. When the target page and the candidate page are different, the target page encapsulated in the target view is not the candidate page and the display of the candidate page is switched.
[0116] Step S342H: In response that the name of the target page is the same as the name of the candidate page, display the target view to show the target page encapsulated in the target view.
[0117] For example, in this application embodiment, the name of the target page and the name of the candidate page are obtained, and the name of the target page and the name of the candidate page are compared. When the name of the target page and the name of the candidate page are the same, it indicates that the target page is the candidate page, and the target view is displayed to show the target page encapsulated in the target view.
[0118] Step S342I: In response to the difference between the name of the target page and the name of the candidate page, close the display of the target view and close the display of the target page.
[0119] Step S342J: Encapsulate the candidate page in the interactive view to obtain the candidate view.
[0120] In this context, the candidate view is an interactive view that encapsulates candidate pages. For example, when the name of the target page is different from the name of the candidate page, it indicates that the target page is not a candidate page. In this embodiment, the target view and the target page are turned off, and the candidate pages are encapsulated in the interactive view to obtain the candidate view.
[0121] Step S342K: Add the candidate view to the top of the first stack and move the candidate page to the top of the second stack.
[0122] Step S342L: Display the candidate view to show the candidate page encapsulated within the candidate view.
[0123] For example, after encapsulating the candidate page in the interactive view to obtain the candidate view, the candidate view is added to the top of the first stack, and the candidate page is moved to the top of the second stack. This embodiment of the application displays the candidate view to show the candidate page encapsulated within the candidate view, thereby displaying the candidate page.
[0124] For example, see Figure 6B As shown, pages 1-2 are the target pages, and pages 1-4 are candidate pages. The names of pages 1-2 and 1-4 are different. Pages 1-4 are encapsulated in an interactive view to obtain a candidate view containing pages 1-4. The candidate view containing pages 1-4 is added to the top of the first stack, and pages 1-4 are added to the top of the second stack. Finally, the candidate view containing pages 1-4 is displayed to show pages 1-4.
[0125] In some embodiments, the present application implements displaying candidate pages according to page storage type and page display mode through steps S342M to S342Q.
[0126] Step S342M: When the response page storage type is the third storage type and the page display mode is the second display mode, close the interactive pages in the second stack except for the reference page.
[0127] For example, when the page storage type is the third storage type and the page display mode is the second display mode, it means that the candidate page has been stored in the second stack and resides in the second stack, and there is no need to rotate the candidate page as a whole. In this embodiment of the application, the interactive pages in the second stack other than the reference page are turned off.
[0128] Step S342N: Obtain the interactive page located at the top of the second stack as the base page.
[0129] The benchmark page and the candidate page may be the same or different. In this embodiment, the benchmark page and the candidate page are compared to determine whether they are the same.
[0130] It is understandable that after closing the interactive pages in the second stack other than the reference page, the comparison is used to determine whether the baseline page and the candidate page are the same, thereby determining whether it is necessary to switch the display of the candidate page. That is, when the baseline page and the candidate page are the same, the baseline page is the candidate page and there is no need to switch the display of the candidate page; when the baseline page and the candidate page are different, the baseline page is not the candidate page and the display of the candidate page is switched.
[0131] Step S342O: If the name of the baseline page is the same as the name of the candidate page, display the baseline page.
[0132] For example, in this application embodiment, the name of the baseline page and the name of the candidate page are obtained, and the names of the baseline page and the candidate pages are compared. When the names of the baseline page and the candidate pages are the same, it means that the baseline page is the candidate page, and the baseline page is displayed directly.
[0133] Step S342P: In response to the fact that the name of the baseline page is different from the name of the candidate page, turn off the display of the baseline page.
[0134] Step S342Q: Move the candidate page to the top of the second stack and display the candidate page.
[0135] For example, when the name of the baseline page is different from the name of the candidate page, it means that the baseline page is not a candidate page. In this embodiment of the application, the baseline page is turned off, the candidate page is moved to the top of the second stack, and the candidate page is displayed.
[0136] For example, see Figure 6B As shown, pages 1-3 are the base pages, and pages 1-4 are candidate pages. The names of pages 1-3 and 1-4 are different. Page 1-3 is turned off, and pages 1-4 are moved to the top of the second stack and then displayed.
[0137] In some embodiments, the page display interaction method for embedded devices provided in this application further includes step S310.
[0138] Step S310: Respond to the request access operation of the first page and access the first page according to the page display mode.
[0139] In this embodiment, the first page is any one of the multiple interactive pages of the embedded device, excluding the candidate page.
[0140] For example, after displaying the candidate pages, when a request to access the first page is received, this embodiment of the application accesses the first page according to the page display mode. That is, when the page display mode is the first display mode, the first page is accessed in portrait orientation / portrait mode, and when the page display mode is the second display mode, the first page is accessed in landscape orientation / landscape mode.
[0141] For example, in this embodiment of the application, the name of the first page is obtained, and a search is performed in the second stack to determine whether an interactive page with a name corresponding to the name of the first page exists. When an interactive page with a name corresponding to the name of the first page is found, the first page is accessed according to the page display mode. When no interactive page with a name corresponding to the name of the first page is found, a prompt message indicating that the first page cannot be accessed is displayed.
[0142] In some embodiments, the present application implements access to the first page according to the page display mode through steps S311 to S313.
[0143] Step S311: When the response page display mode is the first display mode and the first stack stores at least one interactive view, traverse all interactive views.
[0144] Step S312: In response to the fact that the name of the interactive page encapsulated in the base view is consistent with the name of the first page, jump to access the interactive page encapsulated in the base view to access the first page.
[0145] The baseline view is any one of the at least one interactive views.
[0146] For example, when the page display mode is the first display mode and the first stack stores at least one interactive view, it means that the first page is accessed in portrait orientation / portrait mode. All interactive views are traversed, and the name of the interactive page encapsulated in the base view is compared with the name of the first page. When the name of the interactive page encapsulated in the base view matches the name of the first page, it means that the first page (i.e., the interactive page encapsulated in the base view) is stored in the second stack, and the user jumps to access the first page.
[0147] Step S313: If the names of the interactive pages encapsulated in all interactive views are different from the name of the first page, display an access failure message.
[0148] The access failure message indicates that navigation to the first page failed. For example, when the names of the interactive pages encapsulated in all interactive views are different from the name of the first page (i.e., the names of the interactive pages encapsulated in each base view are different from the name of the first page), it means that the first page is not stored in the second stack, and navigation to the first page is impossible. The access failure message is then displayed to indicate that navigation to the first page failed.
[0149] In some embodiments, the present application implements access to the first page according to the page display mode through step S314.
[0150] Step S314: If the response page display mode is the first display mode and the first stack does not store an interactive view, display an access failure message.
[0151] For example, when the page display mode is the first display mode and the first stack does not store any interactive views, it means that the first page is accessed in portrait orientation / portrait mode and the second stack does not store anything encapsulated in the first page. Therefore, it is impossible to jump to the first page and an access failure message is displayed to indicate that the jump to the first page failed.
[0152] In some embodiments, the present application implements access to the first page according to the page display mode through steps S315 to S317.
[0153] Step S315: If the response page display mode is the second display mode and the second stack stores at least one interactive page, traverse all interactive pages.
[0154] Step S316: If the name of the second page is the same as the name of the first page, redirect to the second page to access the first page.
[0155] The second page can be any one of the at least one interactive page.
[0156] For example, when the page display mode is the second display mode and the second stack stores at least one interactive page, it means that the first page is accessed in landscape orientation / landscape mode. All interactive pages are traversed, and the name of the second page is compared with the name of the first page. When the name of the second page matches the name of the first page, it means that the first page is stored in the second stack, and the user jumps to access the first page.
[0157] Step S317: If the names of all interactive pages are different from the name of the first page, display an access failure message.
[0158] The access failure message indicates that the jump to access the first page failed. For example, when the names of all interactive pages are different from the name of the first page (i.e., the name of any interactive page is different from the name of the first page), it means that the first page is not stored in the second stack, and the jump to access the first page cannot be performed. The access failure message is then displayed to indicate that the jump to access the first page failed.
[0159] In some embodiments, the present application implements access to the first page according to the page display mode through step S318.
[0160] Step S318: If the response page display mode is the second display mode and the second stack does not store an interactive page, display an access failure message.
[0161] For example, when the page display mode is the second display mode and the second stack does not store any interactive pages, it means that the first page is accessed in landscape orientation / landscape mode and there are no interactive pages stored in the second stack. Therefore, it is impossible to jump to the first page and an access failure message is displayed to indicate that the jump to the first page failed.
[0162] In summary, the embodiments of this application have at least the following beneficial effects: 1) By introducing a page encapsulation mechanism and combining it with rotation angle parameters, the system flexibly adapts to the rotation of the physical screen of embedded devices, improving the consistency of user interface display. When the user interface application is deployed on an embedded device and the rotation angle parameter is 90° or 270°, the system encapsulates the entire interactive page in an interactive view and rotates the interactive view to ensure that the correct landscape user interface is presented on a portrait screen device. When running in a desktop development environment and the rotation angle parameter is 0° or 180°, the system displays the user interface in a standard landscape mode to maintain an intuitive interface layout and convenient operation. One set of user interface code can correctly present user interfaces in different display directions, ensuring display consistency during runtime and avoiding debugging difficulties caused by frequent rotation during the development phase. Most page function development, interface adjustments, and problem fixing can be completed quickly in the desktop environment without frequent flashing or remote deployment, significantly shortening the development cycle, significantly improving cross-platform development efficiency and debugging efficiency, user experience consistency, and reducing iteration costs and cycles. 2) Implemented secure management of the page lifecycle, reducing or even avoiding memory leaks and crashes. It implemented an automatic page memory resource reclamation mechanism, preventing memory leaks caused by repeated page creation and program crashes due to premature release, thus enhancing system stability and reliability. 3) Enabled quick switching between navigation bar pages (generally important or frequently used pages, i.e., resident memory pages). All navigation switching operations for interactive pages are centrally controlled, supporting jumps from any interactive page. This facilitates advanced navigation behaviors such as "return to homepage" and "clear stack," improving code readability, maintainability, and extensibility. It also enhances the flexibility of page display interactions and allows for convenient retrieval of interactive pages based on page names, effectively alleviating the difficulties of cross-page communication.
[0163] This application provides a computer-readable storage medium storing processor-executable computer program instructions. When executed by a processor, the computer program instructions cause the processor to perform the page display interaction method of the embedded device provided in this application, or to perform the steps in any possible implementation of the page display interaction method of the embedded device provided in this application.
[0164] Those skilled in the art will understand that the embodiments provided in this application are merely illustrative. The order in which the steps in the methods of the embodiments are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The order can be adjusted, merged, and deleted according to actual needs. Modules or sub-modules, units or sub-units in the apparatus or system of the embodiments can be merged, divided, and deleted according to actual needs. For example, the division of units is only a logical functional division, and there may be other division methods in actual implementation. For another example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.
[0165] Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, and of course, it can also be implemented using hardware. Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. It should be understood that the storage medium can be flash memory, hard disk, optical disk, register, magnetic surface memory, removable disk, CD-ROM, random access memory (RAM), read-only memory (ROM), electrically programmable ROM, and electrically erasable programmable ROM, etc.
[0166] It should be noted that the above embodiments are for illustrating the technical concept and features of this application, and are intended to enable those skilled in the art to understand the content of this application and implement it accordingly. They should not be construed as limiting the scope of protection of this application. Those skilled in the art can understand that all or part of the processes of the above embodiments can be implemented, modified according to the technical solutions described in the embodiments of this application, or equivalent substitutions can be made to some of the technical features. It is understood that these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application, and should be considered as equivalent changes and modifications made based on the embodiments of this application, all of which should fall within the scope of the claims of this application.
Claims
1. A page display interaction method for an embedded device, characterized in that, include: Obtain the configuration file of the embedded device; Based on the rotation angle parameters in the configuration file, the page display mode of the interactive page of the embedded device is determined, wherein the page display mode is used to characterize the display direction of the interactive page of the embedded device; In response to a close display operation received on the current page, the current page is closed and displayed according to the page display mode, wherein the current page is the interactive page currently displayed; Candidate pages are displayed according to the page display mode, and the candidate page is any one of the multiple interactive pages to be displayed from the multiple interactive pages of the embedded device.
2. The page display interaction method according to claim 1, characterized in that, The step of determining the page display mode of the embedded device's interactive page based on the rotation angle parameters in the configuration file includes: In response to the value of the rotation angle parameter being equal to a first preset angle value, the first display mode is determined to be the page display mode of the embedded device, wherein the first display mode is used to characterize the display direction of the interactive page as a first direction; In response to the value of the rotation angle parameter being equal to the second preset angle value, the second display mode is determined to be the page display mode of the embedded device. The second display mode is used to characterize the display direction of the interactive page as a second direction, which is different from the first direction.
3. The page display interaction method according to claim 1, characterized in that, The page display mode includes a first display mode and a second display mode, and the step of turning off the current page display according to the page display mode includes: In response to the page display mode being the first display mode, the current view in the first stack is closed and the current page in the second stack is closed according to the number of interactive views in the first stack. The interactive view is a view that encapsulates the interactive page of the embedded device, and the current view is an interactive view that encapsulates the current page. The first stack is configured to store the interactive views. In response to the page display mode being the second display mode, the current page is turned off based on the number of interactive pages in the second stack, which is configured to store the interactive pages of the embedded device.
4. The page display interaction method according to claim 3, characterized in that, The step of closing the display of the current view in the first stack and closing the display of the current page in the second stack based on the number of interactive views in the first stack includes: If the number of interactive views in the first stack is greater than or equal to a first quantity threshold, the current view located at the top of the first stack is retrieved. Turn off the display of the current view; Retrieve the current page located at the top of the second stack; The current page will be closed.
5. The page display interaction method according to claim 3, characterized in that, The step of closing the display of the current page based on the number of interactive pages in the second stack includes: If the number of interactive pages in the second stack is greater than or equal to a second quantity threshold, the current page located at the top of the second stack is retrieved. The current page will be closed.
6. The page display interaction method according to claim 4 or 5, characterized in that, After closing the display of the current page, the method further includes: Delete the current page to release the memory resources occupied by the current page.
7. The page display interaction method according to claim 3, characterized in that, The step of displaying candidate pages according to the page display mode includes: Determine the page storage type of the candidate page, wherein the page storage type is used to characterize the storage status of the candidate page; The candidate pages are displayed according to the page storage type and the page display mode.
8. The page display interaction method according to claim 7, characterized in that, Displaying the candidate page according to the page storage type and the page display mode includes: In response to the page storage type being the first storage type and the page display mode being the first display mode, the candidate page is encapsulated in an interactive view to obtain a candidate view, wherein the candidate view is an interactive view encapsulating the candidate page, and the first storage type is used to indicate that the candidate page is not stored in the second stack; Add the candidate view to the top of the first stack, and add the candidate page to the top of the second stack; Display the candidate view to show candidate pages encapsulated within the candidate view; or, In response to the page storage type being the first storage type and the page display mode being the second display mode, the candidate page is added to the top of the second stack; The candidate page is displayed.
9. The page display interaction method according to claim 7, characterized in that, Displaying the candidate page according to the page storage type and the page display mode includes: In response to the page storage type being the second storage type and the page display mode being the first display mode, a candidate view is obtained from the first stack, wherein the candidate view is an interactive view encapsulating the candidate page, and the second storage type is used to indicate that the candidate page has been stored in the second stack and is not permanently resident in the second stack; Move the candidate view to the top of the first stack; Display the candidate view to show candidate pages encapsulated within the candidate view; or, In response to the page storage type being the second storage type and the page display mode being the second display mode, the candidate page is retrieved from the second stack; Move the candidate page to the top of the second stack and display the candidate page.
10. The page display interaction method according to claim 7, characterized in that, Displaying the candidate page according to the page storage type and the page display mode includes: In response to the page storage type being the third storage type and the page display mode being the first display mode, the interactive pages in the second stack other than the reference page are closed. The third storage type is used to indicate that the candidate page has been stored in the second stack and is permanently resident in the second stack. The reference page is an interactive page that is stored in the second stack and is permanently resident in the second stack. Obtain the interactive view located at the top of the first stack as the target view, wherein the target view is an interactive view that encapsulates the target page; If the name of the target page is the same as the name of the candidate page, the target view is displayed to show the target page encapsulated in the target view; If the name of the target page is different from the name of the candidate page, the target view and the target page will be closed. The candidate page is encapsulated in an interactive view to obtain a candidate view, wherein the candidate view is an interactive view that encapsulates the candidate page; Add the candidate view to the top of the first stack, and move the candidate page to the top of the second stack; Display the candidate view to show the candidate page encapsulated within the candidate view; or, In response to the page storage type being the third storage type and the page display mode being the second display mode, the interactive pages in the second stack other than the reference page are closed. Obtain the interactive page located at the top of the second stack as the base page; If the name of the benchmark page is the same as the name of the candidate page, the benchmark page is displayed. If the name of the benchmark page is different from the name of the candidate page, the display of the benchmark page will be turned off. Move the candidate page to the top of the second stack and display the candidate page.
11. The page display interaction method according to any one of claims 3-5, characterized in that, The method further includes: In response to the request to access the first page, the first page is accessed according to the page display mode. The first page is any interactive page other than the candidate page among the multiple interactive pages of the embedded device.
12. The page display interaction method according to claim 11, characterized in that, Accessing the first page according to the page display mode includes: In response to the page display mode being the first display mode and the first stack storing at least one interactive view, all the interactive views are traversed. If the name of the interactive page encapsulated in the baseline view is consistent with the name of the first page, the user is redirected to access the interactive page encapsulated in the baseline view in order to access the first page. The baseline view is any one of the at least one interactive view. If the names of all interactive pages encapsulated in the interactive views are different from the name of the first page, an access failure message is displayed, indicating that the attempt to access the first page failed; or... If the page display mode is the first display mode and the first stack does not store an interactive view, the access failure information is displayed.
13. The page display interaction method according to claim 11, characterized in that, Accessing the first page according to the page display mode includes: In response to the page display mode being the second display mode and the second stack storing at least one interactive page, all the interactive pages are traversed. If the name of the second page is the same as the name of the first page, the user is redirected to access the second page in order to access the first page, wherein the second page is any one of the at least one interactive page; If the names of all the interactive pages are different from the name of the first page, an access failure message is displayed, indicating that the redirection to the first page failed; or... If the page display mode is the second display mode and the second stack does not store an interactive page, the access failure information is displayed.
14. An embedded device, characterized in that, The device includes a processor and a memory, the processor being communicatively connected to the memory, the memory storing computer program instructions executable by the processor, the computer program instructions being executed by the processor to cause the embedded device to perform the page display interaction method of the embedded device as described in any one of claims 1-13.
15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores processor-executable computer program instructions, which, when executed by the processor, cause the processor to perform the page display interaction method of the embedded device as described in any one of claims 1-13.