Display method and electronic device

Abstract

The display method comprises the following steps: displaying a first display interface corresponding to a first application task of an application program in a first mode in a display area; receiving a first operation on the first display interface; if the first operation is used to trigger establishment of a second display interface of a second mode, creating the second display interface based on a second task stack different from a first task stack used to create the first display interface, the first mode being different from the second mode, the mode representing a display type of the display interface in the display area; and if the first operation is used to trigger establishment of a third display interface of the first mode, creating the third display interface based on the first task stack used to create the first display interface.

Description

Technical Field

[0001] This disclosure relates to the field of terminal technology, and in particular to a display method and electronic device. Background Technology

[0002] Mobile applications typically employ a multi-Activity (display interface) task stack model for page management and leverage multi-window modes (including split-screen, floating windows, and free-form windows) to enhance user experience. However, when Activities with different window attributes coexist in the same task stack, the system struggles to coordinate their display modes, easily leading to abnormal display issues and negatively impacting the user experience. Summary of the Invention

[0003] In view of the above, this disclosure provides a display method and an electronic device.

[0004] According to a first aspect of this disclosure, a display method is provided, comprising: displaying a first display interface corresponding to a first application task of an application in a display area in a first modality; receiving a first operation on the first display interface, wherein if the first operation is used to trigger the establishment of a second display interface in a second modality, the second display interface is created based on a second task stack different from the first task stack used to create the first display interface, wherein the first modality and the second modality are different, and the modality characterizes the display type of the display interface in the display area; and if the first operation is used to trigger the establishment of a third display interface in the first modality, the third display interface is created based on the same first task stack as the first task stack used to create the first display interface.

[0005] According to an embodiment of this disclosure, the method further includes: in response to an exit operation for the second display interface, exiting the second display interface established based on the second task stack, and restoring the first display interface in the display area in a first mode based on the first task stack, wherein the first display size of the first display interface is smaller than the second display size of the second display interface.

[0006] According to embodiments of this disclosure, if a first operation is used to trigger the establishment of a second display interface in a second modality, creating a second display interface based on a second task stack different from the first task stack used to create the first display interface includes: if the first operation is used to trigger the establishment of a second display interface in a second modality, determining to start the second display interface in a first mode; creating a second task stack, and displaying the second display interface in a second modality in a display area based on the second task stack; if the first operation is used to trigger the establishment of a third display interface in a first modality, creating a third display interface based on the same first task stack as the first task stack used to create the first display interface includes: if the first operation is used to trigger the establishment of a third display interface in a first modality, determining to start the third display interface in a second mode; and displaying the third display interface in a first modality in a display area based on the first task stack.

[0007] According to embodiments of this disclosure, the method further includes: responding to a request to establish a fourth display interface of a third modality for a second application task of an application, displaying the fourth display interface in the third modality in a display area, wherein the first display interface and the fourth display interface at least partially overlap or do not overlap, the fourth display interface corresponds to a third task stack, the functions of the first application task and the second application task are different, and the third modality is the same as or different from the first modality; receiving a third operation for the fourth display interface, wherein if the third operation is used to trigger the establishment of a fifth display interface of the fourth modality, the fifth display interface is created based on a fourth task stack different from the third task stack used to create the fourth display interface, and the fourth modality is different from the third modality; if the third operation is used to trigger the establishment of a sixth display interface of the third modality, the sixth display interface is created based on the same third task stack used to create the fourth display interface; wherein the first task stack and the second task stack belong to a first task group, and the third task stack and the fourth task stack belong to a second task group.

[0008] According to embodiments of this disclosure, the method further includes: determining a first linked list corresponding to a first task group and a second linked list corresponding to a second task group, wherein the linked lists are used to record the display order of multiple display interfaces related to the application task.

[0009] According to embodiments of this disclosure, the application has an initial interface, and the first application task and the second application task are different functions in the initial interface.

[0010] According to embodiments of this disclosure, the method further includes: in response to closing the initial interface of the application, using the first display interface in the first linked list corresponding to the first application task as the first initial interface, using the second display interface in the first linked list as the first branch starting interface, using the first display interface in the second linked list corresponding to the second application task as the second initial interface, and using the second display interface of the second application task as the second branch starting interface, wherein the initial display interface is used to control the lifecycle of the display interfaces of multiple application tasks of the application, and the starting interface is used to control the lifecycle of the display interface of the application task to which it belongs.

[0011] According to an embodiment of this disclosure, the first display interface in the first linked list is the first branch starting point interface of the first application task, and the method further includes: in response to closing the first display interface in the first linked list, using the second display interface in the first linked list as the first branch starting point interface.

[0012] According to an embodiment of this disclosure, the method further includes: in response to deleting the Mth intermediate interface in the first linked list, taking the (M+1)th intermediate interface in the first linked list as the next associated interface of the (M-1)th intermediate interface, wherein the intermediate interface is different from the branch start interface and the branch end interface in the first linked list, and the branch end interface is the current focus interface of the first application task.

[0013] A second aspect of this disclosure provides an electronic device, comprising: a display screen having a display area; a processor configured to display a first display interface corresponding to a first application task of an application in a first modality in the display area; and to receive a first operation on the first display interface, wherein if the first operation is used to trigger the establishment of a second display interface in a second modality, the second display interface is created based on a second task stack different from the first task stack used to create the first display interface, the first modality and the second modality being different, and the modality representing the display type of the display interface in the display area; and if the first operation is used to trigger the establishment of a third display interface in the first modality, the third display interface is created based on the same first task stack as the first task stack used to create the first display interface.

[0014] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0015] The above and other objects, features and advantages of this disclosure will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0016] Figure 1 A schematic diagram of a display method in the related art is shown;

[0017] Figure 2A A flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically;

[0018] Figure 2B One of the schematic diagrams of a display method according to an embodiment of the present disclosure is shown;

[0019] Figure 2C This diagram schematically illustrates an application of a display method according to an embodiment of the present disclosure;

[0020] Figure 3 A second schematic diagram illustrating a display method according to an embodiment of the present disclosure is shown;

[0021] Figure 4 A schematic diagram of a display method according to an embodiment of the present disclosure is shown in Figure 3.

[0022] Figure 5 A schematic diagram of a display method according to an embodiment of the present disclosure is shown in Figure 4.

[0023] Figure 6 A schematic diagram of a display method according to an embodiment of the present disclosure is shown in Figure 5.

[0024] Figure 7 A schematic diagram of a display method according to an embodiment of the present disclosure is shown in Figure 6.

[0025] Figure 8 A schematic diagram of a display method according to an embodiment of the present disclosure is shown in Figure 7.

[0026] Figure 9 The diagram illustrates, for example eight, a display method according to an embodiment of the present disclosure;

[0027] Figure 10 A schematic diagram of a display method according to an embodiment of the present disclosure is shown in Figure 9;

[0028] Figure 11 A schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure is shown.

[0029] Figure 12 A block diagram schematically illustrates an electronic device suitable for implementing a display method according to an embodiment of the present disclosure. Detailed Implementation

[0030] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0031] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0032] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0033] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0034] This disclosure provides a display method and an electronic device. Before introducing the technical solutions provided by this disclosure, the relevant technologies involved in this disclosure will be described first.

[0035] In related technologies, mobile terminal applications generally adopt a standard multi-Activity task stack model for page management. With the evolution of operating system window mechanisms, multi-window modes (including split-screen, floating windows, and free windows) have become a standard feature of mobile platforms. However, different application developers have adopted different compatibility strategies for multi-window scenarios: some applications, based on specific functional interaction design requirements, force full-screen mode to ensure the integrity of core business processes and an immersive user experience; other applications support flexible display modes such as floating windows and split-screen to meet users' needs for multi-tasking in parallel.

[0036] However, such diverse configuration strategies can easily lead to compatibility issues within the same task stack. (See reference...) Figure 1When Activities with different window attribute configurations (including launch mode, resizing attribute, screen orientation restrictions, etc.) coexist in the same task stack, the system struggles to dynamically coordinate display modes and lifecycles. Specifically, this manifests as follows: when returning from full-screen mode to small-window mode, interface 1 is prone to layout errors; conflicts between different window attribute configurations lead to abnormal screen display; window hierarchy becomes disordered during Activity switching within the task stack; and functional response is abnormal during multi-window mode switching. These compatibility defects severely impact the user experience in multi-tasking scenarios.

[0037] Before providing a further detailed description of the embodiments of this disclosure, the nouns and terms involved in the embodiments of this disclosure will be explained, and the nouns and terms involved in the embodiments of this disclosure shall be interpreted as follows.

[0038] The task stack (also known as the back stack) is a last-in-first-out (LIFO) container structure in the Android system used to manage Activities (interfaces). A task stack can hold Activities from different applications (or the same application). In multi-window mode (split-screen, floating window, free window, etc.), multiple Activities can be displayed on one screen simultaneously, which may come from different task stacks or from the same task stack.

[0039] An Activity is a single, interactive screen within an Android application. An application can invoke an Activity to display the corresponding interface of the application on the device's screen.

[0040] The display method of this disclosure is generally performed by an electronic device, which may be a mobile phone, tablet computer, foldable terminal, vehicle terminal, smart wearable device or other terminal device with display function.

[0041] The following will be through Figures 2A to 11 The display method of the embodiments of this disclosure will be described in detail.

[0042] Figure 2A A flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically; Figure 2B One of the schematic diagrams of a display method according to an embodiment of the present disclosure is shown; Figure 2C An application diagram illustrating a display method according to an embodiment of the present disclosure is shown schematically.

[0043] like Figure 2A As shown, the display method of this embodiment includes operations S210 to S240.

[0044] In operation S210, a first display interface corresponding to the first application task of the application is displayed in the display area in a first mode.

[0045] In operation S220, a first operation is received for the first display interface.

[0046] Determine whether the modality of the display interface established by the first operation is the same as the first modality.

[0047] In operation S230, if the first operation is used to trigger the establishment of a second display interface of the second modality, the second display interface is created based on a second task stack that is different from the first task stack used to create the first display interface. The first modality and the second modality are different, and the modality represents the display type of the display interface in the display area.

[0048] In operation S240, if the first operation is used to trigger the establishment of a third display interface of the first mode, the third display interface is created based on the same first task stack as the first task stack used to create the first display interface.

[0049] For example, the display area can be an area used to present application interface content. The extent of the display area can vary depending on the device form factor. For instance, on a smartphone, the display area is the entire displayable area of ​​the phone screen; on a foldable device, the display area can be the entire large screen or a portion of the screen after being divided into sections. The display area can be the entire display area or a partial area of ​​the display screen. For example, the display area can be the entire displayable area of ​​the phone screen, the left half of a split screen, or the middle area of ​​the entire displayable area of ​​the phone screen.

[0050] A modality can be defined as the display type of a user interface within a display area; that is, how the interface is presented on the screen. Different modalities represent different visual presentations and interactive behaviors. For example, modalities include, but are not limited to: full-screen modality, small window modality, split-screen modality, and floating window modality.

[0051] An application task can be an abstract management unit for running instances of an application by the operating system. An application can contain one or more application tasks. The first application task is the specific task instance that is currently running. The first display interface is the interface content (such as an Activity page) currently displayed in the area corresponding to the first application task. For example, when a user opens a video application and enters the video playback page, the video playback page is the first display interface, and the running instance of the video application to which it belongs is the first application task.

[0052] The first action can be an interactive operation performed by the user on the first display interface, the purpose of which is to trigger the opening of a new display interface. For example, the first action includes, but is not limited to, interactive methods such as clicking, long pressing, swiping, and gestures.

[0053] The first mode and the second mode are different, meaning they are two distinct display formats. For example, if the first mode is a full-screen mode, then the second mode can be a small window mode or a floating window mode; the two are not the same.

[0054] The first task stack can be the task stack used to create the first display interface; the second task stack can be the task stack used to create the second display interface. The second task stack is a separate task stack that is different from the first task stack.

[0055] Depending on the type of the new interface modality triggered by the first operation on the first display interface, the system enters different processing branches. For example, when the system determines that the goal of the first operation is to create a new interface (i.e., a second display interface) in a second modality different from the current first modality, the system does not reuse the first task stack, but instead creates a new or uses an independent second task stack to create the second display interface (e.g., ...). Figure 2B (As shown). When the system determines that the goal of the first operation is to create a new interface (i.e., the third display interface) that is the same as the current first modality, the system reuses the existing first task stack to create the third display interface and pushes it into the first task stack for unified management.

[0056] In one example, refer to Figure 2CA user opens a shopping app and enters the page for product A in full-screen mode (first mode). This page is the first display interface, and the running instance of the shopping app is the first application task. If the user clicks the "customer service" option on the product A page, this action triggers a chat window with customer service in a pop-up window (second mode), which is the second display interface. At this point, a separate second task stack is created for the chat window, and the pop-up chat window is pushed into this second task stack for management, without interfering with the first task stack of the full-screen mode. If the user presses the back button, they return to the product A page (first display interface) from the chat window (second display interface). Since the two display interfaces belong to different task stacks, the product A page continues to be displayed in full-screen mode, meeting the user's expected interface navigation experience. If the user clicks the "details" option on the product A page, this action triggers the opening of the product A details page in full-screen mode (first mode), which is the third display interface. The details page is pushed into the first task stack for management, allowing it to share the same task stack as the product A page. If the user presses the back button, they will return from the product details page (third display screen) to the product A page (first display screen). The product A page will then continue to be displayed in full-screen mode, providing the user's expected interface navigation experience.

[0057] Understandably, by determining whether the modal type of the newly created display interface is consistent with the current interface, the system dynamically decides whether to reuse the original task stack or create a new, independent task stack, thus achieving differentiated management of different modal interfaces. On the one hand, when the new interface has the same modality as the current interface, sharing the same task stack ensures the continuity of interface navigation, and users can obtain the expected interactive experience when returning. On the other hand, when the new interface has a different modality, the independent task stack effectively isolates the lifecycle and scheduling logic between different display forms (such as full-screen and small window), avoiding display anomalies or state confusion that may be caused by cross-modal interface mixed management. Thus, in multimodal display scenarios, both system stability and user experience are improved simultaneously.

[0058] As described above, the display method of this embodiment may further include the following operations: in response to an exit operation for the second display interface, exiting the second display interface established based on the second task stack, and restoring the display of the first display interface in the display area in a first mode based on the first task stack, wherein the first display size of the first display interface is smaller than the second display size of the second display interface.

[0059] For example, an exit operation can be an interactive operation performed by the user on the second display interface to exit or close the display interface. For example, an exit operation includes, but is not limited to, pressing the system back button, clicking the interface close button, performing an up or down swipe to close gesture, etc.

[0060] The first display size can be the display area occupied by the first display interface within the display area, and the second display size can be the display area occupied by the second display interface within the display area. A first display size smaller than a second display size means that the display area used by the first display interface is smaller than the display area used by the second display interface. For example, if the first mode is a small window mode, the first display size corresponds to the smaller display area covered by the small window; if the second mode is a full-screen mode, the second display size corresponds to the entire displayable area of ​​the screen, and the first display size is smaller than the second display size.

[0061] When the system receives an exit operation for the second display interface, it responds by exiting the second display interface established by the second task stack and switching back to the first task stack. The first display interface is then restored to its original first modality in the display area. Because the first and second display interfaces are managed by their respective independent task stacks, the internal state of the first task stack during the operation of the second display interface is fully preserved. Therefore, the first display interface can accurately restore its original first modality after responding to the exit operation.

[0062] In one example, a user is currently browsing the article list of a news app in a small window mode (first mode) (first display interface). After clicking the link for News A, the system recognizes that this action will trigger the opening of the News A details page in full-screen mode (second mode) (second display interface). At this time, the system creates an independent second task stack for this full-screen interface. The News A details page in full-screen mode is pushed into the second task stack for management, without interfering with the first task stack in the small window mode. After the user finishes viewing the News A details page, they press the back button (exit operation). The system responds to this exit operation, exiting the full-screen News A details page (second display interface) established based on the second task stack, and restoring the small window news app's article list (first display interface) in the display area based on the first task stack in small window mode (first mode).

[0063] As described above, in operation S230, if the first operation is used to trigger the establishment of a second display interface in a second modality, the second display interface is created based on a second task stack different from the first task stack used to create the first display interface. In one possible implementation, the operation may further include the following operations: if the first operation is used to trigger the establishment of a second display interface in a second modality, determining to start the second display interface in a first mode; creating a second task stack, and displaying the second display interface in a second modality in the display area based on the second task stack.

[0064] For example, the first mode can be the task stack startup mode determined when the system determines that the modality of the target display interface is different from the modality of the current display interface. The first mode instructs the system to create an independent new task stack for the target display interface, so that display interfaces with different modalities run in mutually isolated task environments, avoiding state conflicts caused by differences in lifecycle scheduling between cross-modal interfaces within the same task stack. For example, if the current first mode is full-screen mode, and the target display interface triggered by the first operation is a small window mode, since the two modes are different, the system determines to start the target display interface in the first mode, and then creates an independent second task stack for it.

[0065] In one example, a user browses the page of product A in a shopping application in full-screen mode (first mode). The page of product A is the first display interface, the shopping application browsing task to which it belongs is the first application task, and the task stack where the page of product A is located is the first task stack.

[0066] A user clicks the "Contact Customer Service" button on the product A page (first action). Upon receiving this action, the system identifies the target interface as a small window mode (second mode), which differs from the full-screen mode (first mode) currently used by the product A page. Before creating a task stack, the system first determines to launch the customer service chat window in the first mode (second display interface). After determining the launch mode, the system creates an independent second task stack and displays the customer service chat window in small window mode in the display area based on the second task stack, without interfering with the full-screen mode of the product A page in the first task stack.

[0067] As described above, in operation S240, if the first operation is used to trigger the establishment of a third display interface in a first modality, the third display interface is created based on the same first task stack as the first task stack used to create the first display interface. In one possible implementation, the operation may further include the following operations: if the first operation is used to trigger the establishment of a third display interface in a first modality, determining to start the third display interface in a second mode; and displaying the third display interface in the first modality in the display area based on the first task stack.

[0068] For example, the second mode can be the task stack startup mode determined when the system determines that the modality of the target display interface is the same as that of the current display interface. The second mode instructs the system to reuse the task stack where the current display interface is located, and to include the target display interface in the same task stack for unified scheduling, so as to ensure the continuity of navigation paths between display interfaces of the same modality. For example, if the current first modality is full-screen mode, and the target display interface triggered by the first operation is also full-screen mode, since the two modalities are the same, the system determines to start the target display interface in the second mode, and then reuses the existing first task stack.

[0069] In one example, continuing with the previous example, a user clicks the "View Details" button on the product A page (first operation). Upon receiving this operation, the system identifies the target interface mode as full-screen mode (first mode), the same as the current full-screen mode (first mode) used by the product A page. Before reusing the task stack, the system first determines to launch the product A details page in the second mode (third display interface). After determining the launch mode, the system reuses the first task stack and displays the product A details page in full-screen mode in the display area based on the first task stack. The product A details page and the product A page share the same task stack lifecycle management. After pressing the back button, the user can directly return from the product A details page (third display interface) to the product A page (first display interface), providing a clear and continuous navigation path that meets the user's expectations in full-screen mode.

[0070] Figure 3 A second schematic diagram of a display method according to an embodiment of the present disclosure is shown.

[0071] As described above, the display method of this embodiment may further include the following operations: in response to a request to establish a fourth display interface of a third modality for a second application task of an application, displaying the fourth display interface in the third modality in a display area, wherein the first display interface and the fourth display interface at least partially overlap or do not overlap, the fourth display interface corresponds to a third task stack, the functions of the first application task and the second application task are different, and the third modality is the same as or different from the first modality; receiving a third operation for the fourth display interface, wherein if the third operation is used to trigger the establishment of a fifth display interface of the fourth modality, the fifth display interface is created based on a fourth task stack different from the third task stack used to create the fourth display interface, and the fourth modality is different from the third modality; if the third operation is used to trigger the establishment of a sixth display interface of the third modality, the sixth display interface is created based on the same third task stack used to create the fourth display interface. Wherein, the first task stack and the second task stack belong to a first task group, and the third task stack and the fourth task stack belong to a second task group.

[0072] For example, the second application task can be another running instance within the same application that performs a different function than the first application task. The different functions of the first and second application tasks mean that they are responsible for independent business logic within the application, each corresponding to a different functional entry point. For instance, in a shopping application, the first application task could be a product browsing task responsible for product retrieval and display, while the second application task could be an order management task responsible for order inquiry and payment processing. Functionally independent, they are both different task instances within the application.

[0073] The third modality can be the display type of the fourth display interface in the display area. The third modality being the same as or different from the first modality means that the display interface corresponding to the second application task can adopt the same display format as the first application task, or it can adopt a different display format; the system does not impose any mandatory restrictions on this. For example, if the first modality is full-screen mode, then the third modality can be split-screen mode, floating window mode, or both full-screen modes.

[0074] The first and fourth display interfaces may overlap or not overlap, meaning that the spatial relationship between the display interfaces of the two application tasks in the display area can be different. For example, when the first mode is full-screen mode and the third mode is floating window mode, the fourth display interface is superimposed on the first display interface in the form of a floating window, and the two overlap at least partially; when the third mode is split-screen mode, the first and fourth display interfaces occupy independent partitions in the display area, and the two do not overlap.

[0075] The third action can be an interactive operation performed by the user on the fourth display interface, used to trigger the opening of a new display interface. For example, the third action includes, but is not limited to, interactive methods such as clicking, long pressing, and swiping.

[0076] The fourth mode is different from the third mode, which means that the display form of the fifth display interface is different from that of the fourth display interface. The system needs to create an independent fourth task stack for the fifth display interface, which is different from the third task stack, in order to achieve isolation management between different modes.

[0077] The first task group can be a collection of all task stacks corresponding to the first application task in different modes. Both the first and second task stacks belong to the first task group, and they respectively manage the display interface for different modes under the first application task. The second task group can be a collection of all task stacks corresponding to the second application task in different modes. The third and fourth task stacks both belong to the second task group and are responsible for managing the display interface for different modes under the second application task. For example, the first and second task groups are independent of each other, each responsible for the creation, reuse, and interface lifecycle management of its own task stacks, without interfering with each other.

[0078] Depending on the type of the new interface modality triggered by the third operation on the fourth display interface, the system enters different processing branches. For example, when the system determines that the goal of the third operation is to create a new interface (i.e., a fifth display interface) in a fourth modality different from the current third modality, the system does not reuse the third task stack, but instead creates a new independent fourth task stack to create the fifth display interface (e.g., ...). Figure 3(As shown). When the system determines that the goal of the third operation is to create a new interface (i.e., the sixth display interface) that is identical to the current third modality, the system reuses the existing third task stack to create the sixth display interface and pushes it into the third task stack for unified management. The above processing logic runs independently of the second task group and does not affect the first task group that manages the first application task. Each task group maintains its own task stack relationship and interface lifecycle.

[0079] In one example, continuing the usage scenario of the aforementioned shopping application, the user has already entered the page of product A in full-screen mode (first mode) through the first application task (product browsing task). This page of product A is the first display interface, corresponding to the first task stack. Previously, the user clicked the customer service option on the product A page, triggering the opening of a customer service chat window (second display interface) in a small window mode (second mode). This chat window corresponds to the second task stack. The first and second task stacks belong to the same first task group and jointly manage the display interface of the product browsing task in different modes.

[0080] Based on this, when a user clicks the "My Orders" entry in the bottom navigation bar of the shopping app, this action triggers the creation of the fourth display interface corresponding to the second application task (order management task), namely the order list page. The system responds to this request and displays the order list page in a split-screen mode (third mode) within the display area. At this time, the order list page (fourth display interface) and the page for product A (first display interface) occupy the left and right sides of the display area respectively, without overlapping, and are presented independently. This order list page corresponds to the third task stack, which belongs to the second task group and is independent of the first task group managing product browsing tasks.

[0081] When a user clicks the "Pay Now" button on an order item on the order list page (fourth display interface), this action triggers the opening of a payment confirmation page in full-screen mode (fourth mode), which becomes the fifth display interface. Since the full-screen mode (fourth mode) differs from the split-screen mode (third mode), the system creates a separate fourth task stack for the payment confirmation page and manages it within this stack, which belongs to the second task group. If the user presses the back button, they return from the payment confirmation page (fifth display interface) to the order list page (fourth display interface), which continues to display in split-screen mode, providing the user's expected interface navigation experience.

[0082] When a user clicks the "View Details" button on another order item on the order list page (fourth display screen), this action triggers the opening of the order details page in split-screen mode (third display screen), which becomes the sixth display screen. Since the split-screen mode (third display screen) is the same as the order list page's mode, the system reuses the third task stack to create this order details page and pushes it into the third task stack for unified management. If the user presses the back button, returning from the order details page (sixth display screen) to the order list page (fourth display screen), the order list page continues to be displayed in split-screen mode, meeting the user's expected interface navigation experience.

[0083] Understandably, by creating independent task groups for different application tasks within the same application, these tasks are isolated from each other, ensuring that their modal switching, task stack creation, and interface lifecycle management do not affect each other. This effectively avoids interface state confusion or display abnormalities caused by the mixed use of task stacks when multiple tasks are displayed concurrently, thereby improving both system stability and user experience in complex display scenarios with multiple application tasks coexisting.

[0084] Figure 4 The diagram illustrates a third schematic representation of a display method according to an embodiment of the present disclosure.

[0085] As described above, the display method of this embodiment may further include the operation of: determining a first linked list corresponding to a first task group and a second linked list corresponding to a second task group, wherein the linked lists are used to record the display order of multiple display interfaces related to the application task.

[0086] For example, a linked list can be a data organization structure used to record the order in which multiple display interfaces under the same application task are displayed. Each node in the linked list corresponds to a display interface, and the nodes are arranged sequentially according to the order in which the corresponding display interfaces are created and presented. The node corresponding to the first displayed interface is located at the head of the linked list, and the node corresponding to the currently focused display interface is located at the tail of the linked list. For example, if an application task displays interface A, interface B, and interface C in sequence, the linked list will be recorded as: [interface A] → [interface B] → [interface C], where the node containing interface A is the head of the linked list, and the node containing interface C is the tail of the linked list.

[0087] The first linked list can be a linked list corresponding to the first task group, used to record the display order of multiple display interfaces involved in the switching of various modes of the first application task. The nodes in the first linked list can correspond to display interfaces belonging to the same task stack or to display interfaces belonging to different task stacks. The difference between the two lies in whether the modes of the corresponding display interfaces are the same.

[0088] The second linked list can be a linked list corresponding to the second task group, used to record the display order of multiple display interfaces involved in the second application task during each mode switching process, and its node organization method is the same as that of the first linked list.

[0089] Display order refers to the sequential relationship in which different interfaces are created and presented within the same application task. For example, if a user first enters interface A and then navigates from interface A to interface B, the display order is interface A before interface B, meaning that the node containing interface A in the corresponding linked list precedes the node containing interface B.

[0090] Each time a new display interface is created, the system appends the corresponding node to the end of the relevant linked list based on the application task to which the interface belongs, thereby maintaining the display order of each interface under that application task in real time. The first linked list and the second linked list are independent of each other, each managing the display order record of its own application task without interfering with the other.

[0091] In one example, refer to Figure 4 Continuing the usage scenario of the aforementioned shopping application, the user enters the page of product A in full-screen mode (first mode) through the first application task (product browsing task). The page of product A is the first display interface, corresponding to the first task stack and belonging to the first task group; at this time, the first linked list is established, and the node where the page of product A is located is the head node.

[0092] When a user clicks the "Contact Customer Service" option on the product details page, this action triggers the opening of a customer service chat window in a small window modality (second modality), which serves as the second display interface. Since the small window modality (second modality) differs from the full-screen modality (first modality), the system creates the customer service chat window based on an independent second task stack, which belongs to the first task group. Simultaneously, the system appends the node containing the customer service chat window to the tail of the first linked list. The final structure of the first linked list is: [Product A's Page] → [Customer Service Chat Window], where the node containing the product A's page is the head node, and the node containing the customer service chat window is the tail node.

[0093] Simultaneously, when the user clicks the "My Orders" entry in the bottom navigation bar of the shopping app, it triggers the creation of the fourth display interface corresponding to the second application task (order management task), namely the order list page. The system displays this order list page in the display area in split-screen mode (third mode). This page and the page for product A occupy the left and right sides of the display area respectively, without overlapping, corresponding to the third task stack and belonging to the second task group. At this time, the second linked list is established, with the node containing the order list page as the head node. The current structure of the second linked list is: [order list page]. When the user continues on the order details page and clicks the "Pay Now" button, this operation will trigger the opening of the payment confirmation page in full-screen mode (fourth mode), which is the fifth display interface. Since the full-screen mode (fourth mode) and the split-screen mode (third mode) are different, the system creates the payment confirmation page based on an independent fourth task stack, which belongs to the second task group. The system simultaneously appends the node where the payment confirmation page is located to the end of the second linked list. The final structure of the second linked list is: [Order List Page] → [Payment Confirmation Page], where the node where the order list page is located is the head node and the node where the payment confirmation page is located is the tail node.

[0094] Figure 5 The fourth schematic diagram illustrates a display method according to an embodiment of the present disclosure.

[0095] As described above, in some embodiments, the application has an initial interface, and the first application task and the second application task are different functions in the initial interface.

[0096] For example, the initial interface can be the first page displayed in the display area after a user opens the application. As the application's functional navigation hub, the initial interface centrally displays the various functional entry points included in the application. Users trigger different functions from the initial interface through interactive methods such as clicking and swiping, thereby entering the corresponding application tasks. For instance, the initial interface of a shopping application can be the application's homepage, which centrally displays multiple functional entry points such as product browsing, order management, and user profile. Users can enter their respective independent functional tasks after clicking on the corresponding entry point.

[0097] The first and second application tasks are different functions on the initial interface, meaning they correspond to independent entry points on the initial interface. Users triggering different entry points will launch their respective application tasks. Functionally, they are independent and have no dependency or inclusion relationship. For example, in a shopping application, the product browsing entry point (function A) is responsible for product retrieval and display; triggering this entry point leads to the product browsing task. The order management entry point (function B) is responsible for order inquiry and payment processing; triggering this entry point leads to the order management task. Both are located on the application's homepage (initial interface), but are functionally independent.

[0098] In one example, we continue the use case of the aforementioned shopping application. (Refer to...) Figure 5 When a user opens the shopping app, the system first displays the app's homepage as the initial interface in the display area. This homepage is stored in the root task stack 1. The app's homepage contains multiple function entry points, among which the product browsing function entry point (function A) and the order management function entry point (function B) correspond to two different application tasks within the shopping app, both of which can be triggered directly from the app's homepage.

[0099] When a user clicks the "Product Browsing" entry (Function A) on the application's homepage, the first application task (Product Browsing Task) is triggered. The system displays the main product browsing page in full-screen mode as the first display interface, corresponding to initial task stack 2, which belongs to the first task group. When the user clicks the customer service option on the main product browsing page, this action triggers the opening of a customer service chat window in a small window mode as the second display interface. Since the small window mode differs from the full-screen mode, the system creates the customer service chat window based on an independent intermediate task stack 3, which also belongs to the first task group. When the user clicks a product link shared by customer service in the customer service chat window, this action triggers the opening of a product details overlay in a floating window mode as the sixth display interface. Since the floating window mode differs from the small window mode, the system creates the product details overlay based on an independent leaf task stack 4, which also belongs to the first task group. The first linked list records the display order of the three display interfaces under the first application task: first display interface (initial task stack 2) → second display interface (intermediate task stack 3) → sixth display interface (leaf task stack 4), as follows. Figure 5 The first linked list above is shown.

[0100] When a user clicks the "Order Management" entry (Function B) on the application's homepage, it triggers the launch of the second application task (Order Management task). The system displays the order list page in split-screen mode as the fourth display interface, corresponding to the initial task stack 5, which belongs to the second task group. When the user clicks the "Pay Now" button on an order item in the order list page, this action triggers the opening of the payment confirmation page in full-screen mode as the fifth display interface. Since full-screen mode and split-screen mode are different, the system creates the payment confirmation page based on an independent leaf task stack 6, which also belongs to the second task group. The second linked list records the display order of the two display interfaces under the second application task: fourth display interface (initial task stack 5) → fifth display interface (leaf task stack 6), as follows. Figure 5 The second linked list below is shown.

[0101] For ease of description, the root task stack corresponding to the initial interface is named Root Task Stack 1, the first task stack corresponding to the first display interface is named Initial Task Stack 2, the second task stack corresponding to the second display interface is named Initial Task Stack 3, the fifth task stack corresponding to the sixth display interface is named Leaf Task Stack 4, the third task stack corresponding to the fourth display interface is named Initial Task Stack 5, and the fourth task stack corresponding to the fifth display interface is named Leaf Task Stack 6. Here, the initial task stack is the head node of the linked list, and the leaf task stack is the tail node of the linked list.

[0102] Figure 6 The fifth schematic diagram illustrates a display method according to an embodiment of the present disclosure.

[0103] As described above, the display method of this embodiment may further include the following operations: in response to closing the initial interface of the application, the first display interface in the first linked list corresponding to the first application task is used as the first initial interface, the second display interface in the first linked list is used as the first branch starting interface, the first display interface in the second linked list corresponding to the second application task is used as the second initial interface, and the second display interface of the second application task is used as the second branch starting interface. The initial display interface is used to control the lifecycle of the display interfaces of multiple application tasks of the application, and the starting interface is used to control the lifecycle of the display interface of the application task to which it belongs.

[0104] For example, closing the display interface can refer to the system recognizing the event that the application's display interface lifecycle has ended, including but not limited to situations where the user actively closes the display interface through a system return operation, or the system actively destroys the display interface based on internal mechanisms.

[0105] The initial display interface can be the one corresponding to the root task stack.

[0106] The branch starting point interface can be the display interface of the head node of each linked list.

[0107] Lifecycle can refer to the complete sequence of states a display interface goes through from creation to destruction. Control lifecycle can refer to the system cascading and triggering the lifecycle termination processing of other display interfaces within a specific range when the lifecycle of a certain display interface ends; this range is determined by the role of the control interface—the control range of the initial display interface covers all display interfaces under multiple application tasks of the application, while the control range of the branch starting interface is limited to the display interfaces that follow it within its own application task.

[0108] In one example, refer to Figure 6Continuing the usage scenario of the aforementioned shopping application, after the user opens the shopping application, the system displays the application homepage as the initial interface in the display area. This initial interface is stored in the root task stack 1 and includes the "Product Browsing" function entry (function A) and the "Order Management" function entry (function B).

[0109] When a user clicks on function A, the first application task is triggered. The system displays the product browsing main page in full-screen mode as the first display interface (initial task stack 2). When the user clicks "Contact Customer Service" on the product browsing main page, the system displays the customer service chat window in a small window mode as the second display interface (intermediate task stack 3). When the user clicks on the product link shared by customer service in the customer service chat window, the system displays the product details overlay in a floating window mode as the sixth display interface (leaf task stack 4). All three belong to the first task group. The final structure of the first linked list is: [Product Browsing Main Page] → [Customer Service Chat Window] → [Product Details Overlay].

[0110] When a user clicks on function B, the second application task is triggered. The system displays the order list page in split-screen mode as the fourth display interface (initial task stack 5). When the user clicks "Pay Now" on the order list page, the system displays the payment confirmation page in full-screen mode as the fifth display interface (leaf task stack 6). Both belong to the second task group. The final structure of the second linked list is: [order list page] → [payment confirmation page].

[0111] When both application tasks are running, the user closes the application homepage by pressing the system back button, and root task stack 1 exits the active running state. Upon recognizing the initial interface closing event, the system immediately performs role upgrade processing on the nodes of both linked lists:

[0112] First, the first node of the first linked list, i.e., the first display interface (product browsing main page), is determined as the first initial interface. Second, the second node of the first linked list, i.e., the second display interface (customer service chat window), is determined as the first branch starting interface. Third, the first node of the second linked list, i.e., the fourth display interface (order list page), is determined as the second initial interface. Fourth, the second display interface of the second application task, i.e., the fifth display interface (payment confirmation page), is determined as the second branch starting interface.

[0113] Understandably, on the one hand, even after the application navigation base point is closed, the system can still manage the overall lifecycle of the multi-task display interface through specific nodes in the linked list structure, effectively preventing the problem of not being able to uniformly reclaim multi-task interface resources due to the initial interface being closed; on the other hand, the branch starting point interface manages the lifecycle of its respective application task in a more granular way, precisely controlling the timing of resource reclamation for each display interface within a specific task without affecting the running status of other application tasks. Thus, in complex scenarios of multi-task concurrent operation, it ensures both the accuracy of interface resource management and maintains the operational independence between task groups, further improving the system's stability and resource utilization efficiency.

[0114] Figure 7 A schematic diagram of a display method according to an embodiment of the present disclosure is shown as diagram six.

[0115] As described above, the first display interface in the first linked list is the first branch starting point interface of the first application task. The display method of this embodiment may further include the operation: in response to closing the first display interface in the first linked list, the second display interface in the first linked list is used as the first branch starting point interface.

[0116] In one example, such as Figure 7 As shown, the shopping application scenario continues from the previous embodiment. The user opens the shopping application in full-screen mode (first mode) and enters the page of product A. This page of product A is the first display interface (initial task stack 2). Based on the first task stack, it is created as the first node of the first linked list, that is, the starting point interface of the first branch of the first application task. Subsequently, the user clicks the customer service option on the page of product A. The system recognizes that this operation will trigger the creation of a customer service chat window in small window mode (second mode). This customer service chat window is the second display interface (intermediate task stack 3). Since the small window mode is different from the full-screen mode, the system creates an independent second task stack for the customer service chat window. The customer service chat window becomes the second node of the first linked list. The user clicks the link of product B shared by customer service in the customer service chat window. The system displays the product details overlay in floating window mode as the sixth display interface (leaf task stack 4). All three belong to the first task group. The final structure of the first linked list is: [product browsing page] → [customer service chat window] → [product details overlay].

[0117] Subsequently, the user actively closed the page for product A (i.e., the first display interface in the first linked list, the starting point of the first branch) in the multi-task management interface. In response to this closure, the system destroys the page for product A and its corresponding task stack resources, and upgrades the customer service chat window (second display interface), originally located second in the first linked list, to the new starting point of the first branch (initial task stack 3), which then assumes the management function of the first node (initial interface) for the first application task from the original product A page. The product details overlay (sixth display interface), originally located third, maintains its relative position in the linked list and becomes the next associated node of the new starting point of the first branch. The updated node order of the first linked list is: customer service chat window (new first node, new starting point of the first branch) → product details overlay (new second node, currently focused interface). At this point, if the user presses the back button in the customer service chat window, they will be returned to the application's main page (initial interface).

[0118] Figure 8 The seventh schematic diagram illustrates a display method according to an embodiment of the present disclosure.

[0119] As described above, the display method of this embodiment may further include the operation: in response to deleting the Mth intermediate interface in the first linked list, the M+1th intermediate interface in the first linked list is used as the next associated interface of the M-1th intermediate interface, wherein the intermediate interface is different from the branch start interface and the branch end interface in the first linked list, and the branch end interface is the current focus interface of the first application task.

[0120] For example, the branch endpoint interface can be the display interface that is currently in focus in the first linked list, that is, the interface that the user is currently interacting with and that is presented at the forefront in the display area, or the display interface corresponding to the tail node in the ordered arrangement of the linked list.

[0121] The intermediate interface can be a display interface that is positioned in the first linked list after the branch start interface and before the branch end interface. It does not assume the entry management function of the first node of the linked list, nor is it the focus end node where the current user interaction is located.

[0122] In one example, such as Figure 8 As shown, the shopping application scenario in the previous embodiment continues. The structure of the first linked list is: [Product Browsing Main Page] → [Customer Service Chat Window] → [Product Details Overlay].

[0123] Based on the first linked list established in the aforementioned embodiment, the user continues to operate on the product A details page, sequentially entering the product A specifications selection page and the product A review page. Both pages are displayed in full-screen mode (first mode), created based on their respective task stacks, becoming newly added nodes in the first linked list. Thus, the node order of the first linked list is as follows: Product A page (branch starting point interface) → Customer service chat window (first intermediate interface) → Product B details overlay (branch ending point interface).

[0124] At this point, the user deletes the first intermediate interface (i.e., the customer service chat window, M=1) from the first linked list in the multi-task management interface. The system responds to this deletion operation by removing the details page of product A and its corresponding task stack resources, and designates the branch endpoint interface (i.e., the product B details overlay) as the next associated interface after the initial display interface (i.e., the product A page). A direct sequential association is established between the product A page and the product B details overlay. Subsequently, if the user presses the back button on the product B details overlay, they will be redirected back to the product A page according to the updated linked list order. The return navigation path remains continuous, preventing navigation interruptions or abnormal interface transitions due to the absence of the customer service chat window.

[0125] For handling certain special scenarios, the following will combine... Figure 9 and Figure 10 Please provide an explanation.

[0126] Figure 9 The diagram illustrates, for example eight, a display method according to an embodiment of the present disclosure.

[0127] In some embodiments, refer to Figure 9 If the display interface is in single-top mode (stack top reuse mode): In a linked list, if there are identical instances of leaf tasks (stack top, tail nodes), they are directly reused and the on New Intent callback is triggered.

[0128] In one example, if the launch mode for the second display interface (the details page of product A) is declared as single-top mode and it is currently running as the top node of the leaf task stack, and the system receives a push notification for product A, and the user clicks on the notification, the system attempts to launch the details page of product A again to display the details of product A.

[0129] When processing the launch request, the system first checks the launch mode of product A's details page. Since product A's details page uses the single-top launch mode, the system further checks whether the top node of the current leaf task stack is already an instance of product A's details page. The check confirms that product A's details page is currently at the top of the leaf task stack.

[0130] Since the details page of product A meets both of the following conditions: (1) its launch mode is single top; (2) its instance is currently at the top of the leaf task stack, the system determines that there is no need to create a new instance of the details page of product A. At this time, the system does not execute the creation process of a new instance (i.e., does not trigger onCreate()), but instead directly passes the new Intent carrying the details data of product A back to the existing details page instance of product A through onNewIntent(). The node structure of the leaf task stack remains unchanged during this process, and no new nodes are added.

[0131] Understandably, the display interface, as the top node of the leaf task stack, operates in singleTop mode. When the system attempts to restart the display interface, since the reuse condition has been met, the system abandons the process of creating a new instance and instead passes the new Intent to the existing instance via onNewIntent(). This mechanism avoids the accumulation of redundant nodes in the task stack due to repeatedly starting the same display interface, while ensuring that new data can be correctly received and processed by the current instance, allowing the interface content to be updated in a timely manner, and maintaining a simple and stable overall navigation structure.

[0132] Figure 10 A schematic diagram of a display method according to an embodiment of the present disclosure is shown as diagram number nine.

[0133] In some embodiments, refer to Figure 10 Let's continue with the example of the shopping application's display interface. The structure of the first linked list is: [Product Browsing Page] → [Customer Service Chat Window] → [Product Details Overlay]. When a user browses the product details overlay, the system receives a request to launch the product browsing page via a link at the bottom of the page. In processing this request, firstly, the system checks if an instance of the product browsing page already exists in the current task stack. The search confirms that an instance of the product browsing page already exists in the initial task stack 2, and its launch mode is single task. All nodes in the initial task stack 2 that are after the node in the initial task stack 2 are popped and destroyed sequentially; that is, the customer service chat window and the product details overlay are removed, and their corresponding instance resources are released synchronously. The instance of the product browsing page is reused; the process of creating a new instance is not executed (i.e., onCreate() is not triggered). Instead, the Intent carrying the new category data is directly returned to the existing product browsing page instance through onNewIntent(), making the product browsing page the new top node of the stack.

[0134] In some embodiments, if the display interface is in single instance mode, such as the incoming call interface or alarm clock reminder, it is completely independent of the application's own task stack, and the task stack contains only itself.

[0135] A single-instance incoming call interface is launched from application A, and the incoming call interface is placed in a new task stack. The task stacks of application A and the incoming call interface are independent of each other. If other display interfaces are launched from the incoming call interface, a new task stack will be created if the incoming call interface is not specially handled.

[0136] Based on the above display method, this disclosure also provides an electronic device. The following will be combined with... Figure 11 Provide a detailed description of the electronic device.

[0137] Figure 11 A schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure is shown.

[0138] like Figure 11 As shown, the electronic device 300 of this embodiment includes a display screen 301 and a processor 302.

[0139] Display screen 301 has a display area.

[0140] The processor 302 is configured to display a first display interface corresponding to a first application task of an application in a display area in a first modality; receive a first operation for the first display interface; if the first operation is used to trigger the establishment of a second display interface in a second modality, the second display interface is created based on a second task stack that is different from the first task stack used to create the first display interface, the first modality and the second modality are different, and the modality represents the display type of the display interface in the display area; if the first operation is used to trigger the establishment of a third display interface in the first modality, the third display interface is created based on the same first task stack as the first task stack used to create the first display interface.

[0141] For an explanation of the electronic devices, please refer to the description of the display method above; it will not be repeated here.

[0142] Figure 12 A block diagram schematically illustrates an electronic device suitable for implementing a display method according to an embodiment of the present disclosure.

[0143] like Figure 12As shown, an electronic device 400 according to an embodiment of the present disclosure includes a processor 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage portion 408 into a random access memory (RAM) 403. The processor 401 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 401 may also include onboard memory for caching purposes. The processor 401 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0144] RAM 403 stores various programs and data required for the operation of electronic device 400. Processor 401, ROM 402, and RAM 403 are interconnected via bus 404. Processor 401 executes various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 402 and / or RAM 403. It should be noted that programs may also be stored in one or more memories other than ROM 402 and RAM 403. Processor 401 may also execute various operations of the method flow according to embodiments of the present disclosure by executing programs stored in one or more memories.

[0145] According to embodiments of this disclosure, the electronic device 400 may further include an input / output (I / O) interface 405, which is also connected to a bus 404. The electronic device 400 may also include one or more of the following components connected to the I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 410 as needed so that computer programs read from it can be installed into the storage section 408 as needed.

[0146] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0147] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 402 and / or RAM 403 and / or one or more memories other than ROM 402 and RAM 403 described above.

[0148] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the display methods provided in the embodiments of this disclosure.

[0149] When the computer program is executed by the processor 401, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0150] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via communication section 409, and / or installed from removable medium 411. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0151] In such an embodiment, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by processor 401, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0152] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0153] 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 disclosure. 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 a 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 a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may 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.

[0154] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0155] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A display method, comprising: A first display interface corresponding to the first application task of the application is displayed in the display area in a first modality. Receive a first operation targeting the first display interface. If the first operation is used to trigger the establishment of a second display interface in a second modality, the second display interface is created based on a second task stack that is different from the first task stack used to create the first display interface. The first modality and the second modality are different, and the modality represents the display type of the display interface in the display area. If the first operation is used to trigger the establishment of a third display interface of the first modality, the third display interface is created based on the same first task stack as the first task stack used to create the first display interface.

2. The method according to claim 1, further comprising: In response to an exit operation on the second display interface, the second display interface established based on the second task stack is exited, and the first display interface is restored to display in the display area in the first mode based on the first task stack, wherein the first display size of the first display interface is smaller than the second display size of the second display interface.

3. The method according to claim 1, wherein if the first operation is used to trigger the establishment of a second display interface of a second modality, creating the second display interface based on a second task stack different from the first task stack used to create the first display interface, includes: If the first operation is used to trigger the establishment of a second display interface in a second modality, determine to start the second display interface in the first mode; Create the second task stack, and display the second display interface in the second modality in the display area based on the second task stack; If the first operation is used to trigger the establishment of a third display interface of the first modality, the third display interface is created based on the same first task stack as the first task stack used to create the first display interface, including: If the first operation is used to trigger the establishment of a third display interface in the first mode, determine to start the third display interface in the second mode; Based on the first task stack, a third display interface is displayed in the display area in the first modality.

4. The method according to claim 1, further comprising: In response to a request to establish a fourth display interface in a third modality for a second application task of the application, the fourth display interface is displayed in the display area in the third modality, wherein the first display interface and the fourth display interface at least partially overlap or do not overlap, the fourth display interface corresponds to a third task stack, the first application task and the second application task have different functions, and the third modality is the same as or different from the first modality; Receive a third operation for the fourth display interface. If the third operation is used to trigger the establishment of a fifth display interface in a fourth modality, the fifth display interface is created based on a fourth task stack that is different from the third task stack used to create the fourth display interface, and the fourth modality is different from the third modality; If the third operation is used to trigger the establishment of the sixth display interface of the third modality, the sixth display interface is created based on the same third task stack as the third task stack used to create the fourth display interface; The first task stack and the second task stack belong to the first task group, and the third task stack and the fourth task stack belong to the second task group.

5. The method according to claim 4, further comprising: A first linked list corresponding to the first task group and a second linked list corresponding to the second task group are determined. The linked lists are used to record the display order of multiple display interfaces related to the application task.

6. The method according to claim 1, wherein the application has an initial interface, and the first application task and the second application task are different functions in the initial interface.

7. The method according to claim 6, further comprising: In response to closing the initial interface of the application, the first display interface in the first linked list corresponding to the first application task is used as the first initial interface, the second display interface in the first linked list is used as the first branch starting interface, the first display interface in the second linked list corresponding to the second application task is used as the second initial interface, and the second display interface in the second application task is used as the second branch starting interface. The initial display interface is used to control the lifecycle of the display interfaces of multiple application tasks of the application, and the starting interface is used to control the lifecycle of the display interface of the application task to which it belongs.

8. The method according to claim 6, wherein the first display interface in the first linked list is the first branch starting point interface of the first application task, and the method further includes: In response to closing the first display interface in the first linked list, the second display interface in the first linked list is used as the starting interface of the first branch.

9. The method according to claim 7, further comprising: In response to deleting the Mth intermediate interface in the first linked list, the (M+1)th intermediate interface in the first linked list is taken as the next associated interface of the (M-1)th intermediate interface. The intermediate interface is where the branch start interface and the branch end interface in the first linked list are different, and the branch end interface is the current focus interface of the first application task.

10. An electronic device, comprising: Display screen, having a display area A processor for displaying a first display interface in a first mode in a display area, corresponding to a first application task of an application; Receive a first operation for the first display interface; if the first operation is used to trigger the establishment of a second display interface of a second modality, create the second display interface based on a second task stack that is different from the first task stack used to create the first display interface; the first modality and the second modality are different; the modality represents the display type of the display interface in the display area. If the first operation is used to trigger the establishment of a third display interface of the first modality, the third display interface is created based on the same first task stack as the first task stack used to create the first display interface.

Images