Display method and electronic device

Abstract

This disclosure provides a display method, including: obtaining a first operation; responding to the first operation, determining a target application in a running state; the target application in a running state displaying running data through a first window; configuring a binding relationship between the first window and a target interface; wherein the target interface is an interactive operating interface of the operating system of an electronic device; the target interface is capable of being displayed on the screen of the electronic device in response to a sliding operation along a first direction on the current interface; and the first window is displayed when the target interface is displayed based on the binding relationship.

Description

Technical Field

[0001] This disclosure relates to the field of electronic device displays, and more specifically, to a display method and an electronic device. Background Technology

[0002] With the development of mobile devices, operating systems can provide a system-level interface that can be quickly accessed to assist in displaying relevant content of application windows. However, this system-level interface can only support preset widgets or message notifications, and cannot support running application windows. Summary of the Invention

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

[0004] One aspect of this disclosure provides a display method, comprising: obtaining a first operation; in response to the first operation, determining a target application in a running state; the target application in a running state displaying running data through a first window; configuring a binding relationship between the first window and a target interface; wherein the target interface is an interactive operating interface of an electronic device's operating system; the target interface is capable of being displayed on the electronic device's screen in response to a sliding operation along a first direction on the current interface; and the first window is displayed when the target interface is displayed based on the binding relationship.

[0005] According to embodiments of this disclosure, the display method further includes: in response to configuration, migrating a first window from the current interface to a target interface based on a binding relationship; the current interface is the default display interface on the system desktop of the electronic device, and the current interface is used to display the user interface window of the target application.

[0006] According to embodiments of this disclosure, configuring the binding relationship between the first window and the target interface includes any of the following: adding the first window to the target interface so that the target interface includes the first window; creating the target interface and using the running data displayed in the first window as the display content of the target interface; obtaining the indicator of the target interface and establishing the binding relationship between the first window and the target interface based on the indicator.

[0007] According to embodiments of this disclosure, the display method further includes: in response to the target application changing from a running state to a non-running state, unbinding the relationship.

[0008] According to embodiments of this disclosure, configuring the binding relationship between the first window and the target interface further includes: configuring triggering conditions; and migrating the first window to the target interface based on the binding relationship in response to the electronic device meeting the triggering conditions.

[0009] According to embodiments of this disclosure, an electronic device includes a first screen, a second screen, a first body, and a second body. The first screen is disposed on a first surface of the first body and the second body, and the second screen is disposed on a second surface of the first body or the second body. In response to the electronic device meeting a trigger condition, a first window is migrated to a target interface based on a binding relationship, including: in response to the change angle of the relative position of the first body and the second body meeting a target threshold, a first window of the first screen is migrated to the target interface based on the binding relationship, or a first window of the second screen is migrated to the target interface.

[0010] According to embodiments of this disclosure, the electronic device includes a first screen and a second screen. The first operation is an opening and closing operation. The electronic device is able to switch between an unfolded state and a folded state in response to the opening and closing operation. In response to the first operation, a target application in a running state is determined, including: in response to the opening and closing operation, determining the application currently displayed on the first screen or the second screen that is in a running state as the target application, and establishing a binding relationship between the first window and the target interface.

[0011] According to embodiments of this disclosure, configuring the binding relationship between the first window and the target interface includes: if the first screen displays the first window, obtaining a virtual screen created based on the size of the second screen; adapting the running data displayed in the first window based on the size of the virtual screen to generate the display content of the target interface.

[0012] Another aspect of this disclosure provides a display device, comprising: a determining module for obtaining a first operation, and in response to the first operation, determining a target application in a running state; the target application in a running state displays running data through a first window; a configuring module for configuring a binding relationship between the first window and a target interface; wherein the target interface is an interactive operating interface of an electronic device's operating system; the target interface is capable of being displayed on the electronic device's screen in response to a sliding operation along a first direction on the current interface; and the first window is displayed when the target interface is displayed based on the binding relationship.

[0013] Another aspect of this disclosure provides an electronic device, including: a display screen for displaying a user interface; a sensor for acquiring user operations; and a processor coupled to the display screen and the sensor, respectively. The processor is configured to: acquire a first operation acquired by the sensor; and in response to the first operation, determine a target application in a running state; the target application in a running state displays running data through a first window; and configure a binding relationship between the first window and the target interface; wherein the target interface is an interactive operating interface of the electronic device's operating system; the target interface is capable of being displayed on the display screen in response to a sliding operation along a first direction on the current interface; and the first window is displayed when the target interface is displayed based on the binding relationship.

[0014] According to embodiments of this disclosure, the electronic device further includes a first body and a second body, and the display screen includes a first screen and a second screen. The first screen is disposed on a first surface of the first body and the second body, and the second screen is disposed on a second surface of the first body or the second body. Configuring the binding relationship between a first window and a target interface includes: configuring trigger conditions; responding to a change in the relative position angle of the first body and the second body satisfying a target threshold, based on the binding relationship, migrating the first window of the first screen to the target interface, or migrating the first window of the second screen to the target interface.

[0015] According to embodiments of this disclosure, the display screen includes a first screen and a second screen. The first operation is an opening and closing operation, and the electronic device is able to switch between an unfolded state and a folded state in response to the opening and closing operation. In response to the first operation, a target application in a running state is determined, including: in response to the opening and closing operation, determining the application currently displayed on the first screen or the second screen that is in a running state as the target application, and establishing a binding relationship between the first window and the target interface.

[0016] Another aspect of this disclosure provides a computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to perform a display method according to any of the foregoing embodiments.

[0017] Another aspect of this disclosure provides a computer program product, including a computer program / instructions, characterized in that the computer program / instructions, when executed by a processor, implement the operation of the method shown in any of the foregoing embodiments. Attached Figure Description

[0018] 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:

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

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

[0021] Figure 3 Another flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically;

[0022] Figure 4 Another flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically;

[0023] Figure 5 A flowchart illustrating the interface migration process in a display method according to an embodiment of the present disclosure is shown schematically.

[0024] Figure 6Another flowchart illustrating the mid-transition interface of the display method according to an embodiment of the present disclosure is shown schematically;

[0025] Figure 7 Another flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically;

[0026] Figure 8 A flowchart illustrating the configuration of binding relationships in a display method according to an embodiment of the present disclosure is shown schematically.

[0027] Figure 9 A block diagram schematically illustrates a display device according to an embodiment of the present disclosure; and

[0028] Figure 10 A block diagram of an electronic device suitable for implementing the methods described above, according to embodiments of the present disclosure, is illustrated schematically. Detailed Implementation

[0029] 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.

[0030] 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 the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0031] 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.

[0032] 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.).

[0033] In the embodiments disclosed herein, the collection, updating, analysis, processing, use, transmission, provision, disclosure, and storage of data (e.g., including but not limited to user personal information) comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. In particular, necessary measures have been taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0034] Embodiments of this disclosure provide a display method applied to an electronic device, comprising: obtaining a first operation; in response to the first operation, determining a target application in a running state; the target application in a running state displaying running data through a first window; configuring a binding relationship between the first window and a target interface; wherein the target interface is an interactive operating interface of the electronic device's operating system; the target interface is capable of being displayed on the electronic device's screen in response to a sliding operation along a first direction on the current interface; and the first window is displayed when the target interface is displayed based on the binding relationship.

[0035] Figure 1 A flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically.

[0036] like Figure 1 As shown, the display method may include at least operations S110 to S120.

[0037] In operation S110, a first operation is obtained, and in response to the first operation, the target application in the running state is determined; the target application in the running state displays running data through the first window.

[0038] The first operation can be an interactive command used to initiate content anchoring or task state transition. The target application in a running state can be an application whose current task process remains active in memory, and whose associated functional modules are within an execution cycle that can be scheduled by the processor. The first window acts as the graphical interface carrier for interaction between the target application and the user, used to present runtime data generated by the application logic in real time, ensuring that application state information can be visually perceived. Runtime data can be understood as contextual information during application execution, reflecting the application's current business processing progress or content presentation status; its format depends on the functional attributes of the target application.

[0039] By capturing trigger signals generated by input devices to obtain the first operation, the application that currently occupies the active focus or maintains execution logic in the foreground can be identified. This anchors a unique target for subsequent UI transitions, ensuring that the application maintains a true foreground active state rather than providing static snapshots in subsequent scheduling.

[0040] For example, capturing a specific gesture (such as a long press or double tap) performed at the edge of the display screen as the first operation, the target application is identified as the video playback application currently occupying the input focus of the main display area, whose first window is continuously displaying operational data including the currently decoded video frame, playback progress bar, and real-time bullet comments; or, when a press action on a physical function key is detected, the target application is identified as the instant messaging application currently in the foreground interaction, whose first window is fully displaying operational data including historical chat history, input box focus, and text content to be sent.

[0041] In operation S120, the binding relationship between the first window and the target interface is configured. The binding relationship is used to indicate the collaborative state of the first window and the target interface in terms of rendering hierarchy and visibility. Configuring the binding relationship involves mapping the display attributes of the first window to the view tree structure of the target interface, so that the display output and interaction handles of the first window are attached to the display logic of the target interface. Establishing the binding relationship allows the independent application window to be mounted to the view node of the target interface, thereby causing the first window to detach from the current display layout (such as exiting a multi-window split-screen layout or the regular desktop task flow) and become an associated part of the target interface. This configuration process reuses the operating system's window management and interface rendering mechanism, maintains the complete interactive attributes of the first window as an active task, ensures that the target application can be presented along with the target interface without reloading the process, and the first window is not a widget or desktop widget detached from the application process in traditional window control.

[0042] For example, in the system's window manager, an association identifier can be established between the first window of a document editing application and the negative one screen interface, making the first window a child node in the layout hierarchy of the negative one screen; or, by modifying the display hierarchy attribute of the first window, the first window of an email application can be configured to carry the content of the drop-down notification bar interface.

[0043] The target interface is the interactive user interface of the electronic device's operating system. It responds to a swipe operation along a first direction on the current interface and is displayed on the electronic device's screen. The first window is displayed when the target interface is shown, based on a binding relationship. The target interface can be a system interface uniformly managed and scheduled across applications by the operating system, independent of the application window layout of the current interface. The current interface is the system interface used to display application windows (e.g., the system's main screen), serving as the system-level display carrier for the application windows, and is presented on the electronic device's screen before the target interface is invoked. The swipe operation in the first direction identifies a displacement vector along a specific trajectory through the input device, triggering the rendering and display of the target interface.

[0044] When a swipe operation is received, the operating system schedules the rendering output of the target interface to the display screen. Based on the aforementioned binding relationship, the display attributes of the first window are updated synchronously with the visibility of the target interface, thus appearing in the target interface. Since the display hierarchy of the target interface is usually higher than or independent of the application window of the current interface, the process of the first window being displayed along with the target interface will not trigger changes in the lifecycle state of other applications in the current interface, thereby providing a continuous interactive entry point for the first window without interrupting the execution of the current foreground task.

[0045] For example, the target interface may appear as the negative one screen of an operating system. In response to a horizontal swipe to the right in the full-screen display of a reading application (the current interface), the negative one screen slides into the display area from one side of the screen. At this time, the first window of the shopping application with a binding relationship is displayed in the negative one screen, and the user can continue to swipe the interface in the first window to browse product details. Alternatively, the target interface may appear as a system notification bar. In response to a swipe down from the top of the screen in the game application interface (the current interface), as the notification bar expands, the first window of the navigation application with a binding relationship is displayed as part of the notification bar, showing real-time map location and route guidance data.

[0046] According to embodiments of this disclosure, by binding the first window of a running target application to the target interface of the operating system, the target interface can accommodate the running application window, rather than being limited to displaying static information or simplified interactive content, thereby expanding the content capacity of the system-level target interface. Furthermore, any running application window can be fixed to the system-level target interface through configuration binding and can be displayed along with the target interface during the interaction process of switching from the current interface to the target interface, thus reducing the user's steps of switching or re-entering the application to view the target application. On the other hand, when no specific instructions such as swiping are received, the first window can be hidden or collapsed based on the target interface, avoiding the direct display of application running data on the screen during screen switching scenarios, thereby reducing the risk of information exposure.

[0047] Figure 2 Another flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically.

[0048] like Figure 2 As shown, based on the foregoing embodiments, the display method may further include operation S210.

[0049] In operation S210, in response to configuration, the first window is migrated from the current interface to the target interface based on the binding relationship. The current interface is the default display interface on the system desktop of the electronic device, used to display the user interface window of the target application. Responding to configuration can be understood as establishing the binding relationship and performing window hierarchy transfer as continuous scheduling actions. The current interface can be the default view hierarchy controlled by the operating system's desktop management program, such as the main screen, second screen, or third screen—common display areas. The target application's user interface window originally relied on the system desktop's view hierarchy for rendering output by default. Migration can be understood as the spatial displacement and node transfer of the window in the display coordinate system or view hierarchy structure.

[0050] The process of migrating the first window from the current interface to the target interface based on the binding relationship involves updating the ownership node of the first window in the window manager. By modifying the layout parameters of the first window, the display container of the first window is switched from the default foreground view of the system desktop to the view container of the target interface. At this time, the first window is removed from the original desktop display layout in terms of physical coordinates and logical ownership, and is instead constrained by the layout protocol of the target interface. This migration behavior does not change the background survival status and business logic of the target application, but rather, through redirection in the graphics compositing stage, it transfers the entire running application window to the system-level content dock.

[0051] For example, a web browsing application that is currently displayed in full screen on the system's main screen (current interface) will have its browsing window removed from the main screen's display area after a configuration operation is triggered, and will be redrawn synchronously in a specified coordinate area on the system's negative one screen (target interface), while maintaining the webpage's scrolling progress and loading state. Alternatively, a document editing application that is running in windowed mode on the system desktop's second screen (current interface) will have its editing window extracted from the system desktop's view tree and rearranged in a specific task-carrying area of ​​the operating system's drop-down notification bar (target interface).

[0052] According to embodiments of this disclosure, after establishing the binding relationship between the first window and the target interface, the first window can be migrated from the current interface to the target interface in response to configuration. This allows application windows that were originally displayed on the system desktop's default display interface to be transferred to the target interface for continued display, simplifying the content of the default display interface and expanding the content capacity of the target interface. Simultaneously, this migration process targets the first window itself while it is running, without altering the target application's operational status or business logic. Therefore, it maintains the continuity of the target application's running data and avoids impacting the current usage state due to exiting the current interface or re-entering the application.

[0053] Figure 3 Another flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically.

[0054] like Figure 3 As shown, based on the aforementioned embodiments, operation S210 may include any one of operations S310 to S330. Any one of S310 to S330 is used to configure the binding process to be executed between the first window and the target interface. For example, after configuration is completed, the target interface, display area, hierarchy parameters, or interface identifier corresponding to the first window can be recorded first, without immediately executing the actual binding between the first window and the target interface; the corresponding binding process is then activated when a call instruction, confirmation instruction, or display instruction for the target interface is received subsequently. In this way, the association preparation between the first window and the target interface can be completed in advance while maintaining the current interface display state.

[0055] In operation S310, a first window is added to the target interface, making the target interface include the first window. Adding to the target interface can be achieved by dynamically embedding the first window as an active node or subview within the target interface's view hierarchy. The target interface itself typically has original display content (such as system-provided service cards or notification lists). Making the target interface include the first window means that the first window coexists with the target interface as part of it without disrupting its original layout framework. The configuration process of adding the first window to the target interface means that after configuration, the system can pre-record the first window's container position, hierarchy order, and layout relationship with the target interface's original components without performing actual binding and view transfer. When a command to invoke the target interface is received subsequently, the binding process is activated, directly mounting the first window with full interactive capabilities and real-time running status, and displaying it coexisting with the target interface without disrupting its original layout framework.

[0056] This method of adding widgets differs from pushing limited static widgets (such as notification cards) to the system interface. Instead, it directly mounts the native application window, which has full interactive capabilities and real-time running status. During the addition process, the target interface's layout engine can adaptively adjust (e.g., move existing components down or scale them) to create a dedicated area for the first window, thus achieving unobstructed simultaneous display.

[0057] For example, a user configures a pending execution process on the current desktop to embed the first window of an application playing a video into the top area of ​​the negative one screen. After configuration, the video application continues to run on the current desktop. When it receives a subsequent instruction from the user to swipe right on the main screen to bring up the negative one screen, the first window is added to the negative one screen. This results in the negative one screen containing both the first window that renders the video frame in real time and the original weather and calendar components of the negative one screen, which are displayed together in the same system interface without overlapping.

[0058] When operating the S320, a target interface is created, using the runtime data displayed in the first window as the content displayed on the target interface. Creating the target interface can be achieved by the operating system dynamically generating a completely new display container independent of the existing interface framework. This newly created container, initially, can be a blank carrier (or "shell") with specific specifications and hierarchical identifiers, specifically designed to hold the target application's runtime data. The configuration process of creating the target interface and using runtime data as display content means that after configuration, the independent container is not immediately generated; instead, the hierarchical identifiers, display area, and memory allocation method of the target interface are pre-saved. When a specific subsequent call instruction is received, the target interface is dynamically generated based on the saved configuration parameters, and the real-time rendering data and interaction handles of the first window are extracted and filled into the new interface, providing the target application with exclusive storage space.

[0059] This process is equivalent to extending a new, independent layer into the operating system's interface sequence. After allocating the memory and display coordinates of this blank space, the system extracts the real-time rendering data and interaction handles of the first window and directly fills them into the new interface, providing the target application with an exclusive storage space and avoiding mixing with existing system components.

[0060] For example, when a user configures a binding process to create a "second negative screen" while the document editing application is running, the operating system dynamically generates a new interface container with a "second negative screen" identifier on the side of the first negative screen according to the configuration, and fills the layout content and real-time running data such as the editing cursor into the new container for display; or, in the scenario of a pull-down notification bar, by receiving the user's second pull-down action command, a dedicated task layer is triggered to create, and the first window of the document editing application is filled and displayed in the task layer.

[0061] During operation of S330, an indicator of the target interface is obtained, and a binding relationship between the first window and the target interface is established based on the indicator. The indicator can be a system-level parameter used to uniquely define the identity, memory address, or visual region coordinates of the target interface at the system level. Obtaining the indicator means that the system has received clear directional input information, and thus knows which specific system interface should be logically associated with the first window.

[0062] This operation focuses on describing the triggering and execution mechanism of the binding relationship establishment. Compared with operations S310~S320, it can be understood as an explanation of the binding from different perspectives. Operation S330 focuses on describing the binding relationship from the perspective of the underlying data operation process. It can identify the interface identifier corresponding to the area where the drag endpoint is located by capturing the user's drag interaction on the graphical interface; it can also extract the identifier by parsing the text or tab configuration entered in the system settings menu. Establishing a binding relationship based on the indicator means establishing a clear mapping relationship between the application process of the first window and the rendering queue of the target interface. After obtaining the indicator, the mapping logic between the application process and the specific memory address or rendering queue can be recorded at the underlying level without immediately switching the graphics rendering context; when the system receives the display instruction of the target interface later, the underlying window manager activates the binding according to the pre-stored mapping relationship, completing the formal transfer of the underlying display node of the first window.

[0063] For example, when a user long-presses the first window of a chat application on the home screen and drags it above the "negative one screen" overlay that pops up at the edge of the screen, the system obtains the negative one screen indicator corresponding to that overlay area and records the pending mapping relationship between the chat application window and the negative one screen at the underlying level. When the user actually slides out the complete negative one screen later, the binding is established and activated at the underlying level based on this indicator. Alternatively, in the system's multitasking management settings, the user selects the "Associate with Notification Bar" option for a game auxiliary application through the drop-down menu, thereby obtaining the notification bar indicator and saving the mapping relationship. When the user performs a pull-down gesture to bring up the notification bar later, the underlying window manager establishes the rendering queue binding between the first window of the application and the notification bar.

[0064] According to embodiments of this disclosure, by providing three parallel configuration mechanisms—adding windows to an existing interface, creating a completely new host interface, and explicitly establishing bindings based on indicators—the system is directly endowed with extremely high cross-screen storage flexibility. Adding to an existing interface (operation S310) allows for high-density integration of the application's foreground running state with native system information, improving the efficiency of cross-task information retrieval. Creating a new interface (operation S320) provides complex applications with an interference-free, independent content space, avoiding visual conflicts with existing system components. Establishing bindings based on indicators (operation S330) provides intuitive and definitive interactive configuration methods (such as drag-and-drop). Furthermore, the system is allowed to wait for subsequent instructions, such as sliding to open or pulling down to expand, before triggering and activating the corresponding binding relationship after configuration without immediately executing the actual binding action. This "pre-configured, activated when needed" mechanism ensures that the configuration phase does not interrupt the normal display of the first window on the current interface or the user's current task operation. Furthermore, by preparing the interface layout parameters, container information, or underlying process mapping in advance, the application window can be quickly loaded when a switch in display state is actually needed, significantly improving the efficiency of retrieving the target interface and the smoothness of cross-interface interaction.

[0065] Figure 4 Another flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically.

[0066] like Figure 4 As shown, based on the foregoing embodiments, the display method may include operation S410.

[0067] When operating S410, in response to the target application changing from a running state to a non-running state, the binding relationship is released. The non-running state can be a state where the target application's task process is actively terminated by the user, actively reclaimed by the system background, or its associated functional modules are removed from the active execution sequence in memory. Releasing the binding relationship can involve revoking the collaborative and interactive logic between the first window and the target interface at the rendering level and lifecycle, causing the interaction handles and display output of the first window to be detached from the target interface's view tree or layout container.

[0068] In response to the target application changing from a running state to a non-running state, the execution logic for unbinding is automatically triggered by listening for the end of the application's lifecycle. This unbinding logic will adaptively reverse the recovery based on the specific way the binding relationship was configured: if the first window was added to the target interface, unbinding is manifested by deleting the first window from the display node of the target interface and dynamically reconstructing the layout of the target interface to restore its original display content; if the target interface is a new container specifically created to host the first window, unbinding is manifested by deleting the newly created target interface and canceling the independent display layer; if a binding relationship was established based on an indicator and covered the original interface, unbinding is manifested by canceling the underlying mapping association and causing the target interface to re-present its obscured or replaced initial system components.

[0069] For example, when a user manually closes a video playback application added to the negative one screen (target interface) through the multitasking management interface, the application becomes inactive, and its first window is automatically removed from the layout of the negative one screen. The weather and calendar components, which were originally moved down to avoid this, automatically slide up and return to their default positions on the negative one screen. Alternatively, when the process of a document editing application that was originally hosted independently by creating a completely new "negative two screen" (target interface) is cleaned up by the system, the dedicated "negative two screen" hierarchy is deleted entirely, and the system interface structure is restored to the regular desktop and single-layer negative one screen. As another example, when an email application associated with the drop-down notification bar (target interface) is completely exited, the binding between its first window and the notification bar indicator is released, and the notification bar then reverts to displaying the default system notification list.

[0070] According to embodiments of this disclosure, a system-level interface cleanup and view self-healing mechanism based on the actual lifecycle of an application is directly established by automatically unbinding the target application when it changes from a running state to a non-running state. Since the carrying state of the target interface is strictly consistent with the underlying survival state of the application, automatically unbinding the target application when it changes to a non-running state effectively avoids leaving invalid static images or unresponsive windows in system-level content spaces (such as the negative one screen) after the application exits, improving the utilization rate of interface resources and visual cleanliness. Furthermore, by providing precise reverse recovery logic for different binding methods, it ensures that the operating system can smoothly and automatically revert to the initial normal layout after the target application ends its cross-screen or storage use.

[0071] Figure 5 A flowchart illustrating the interface migration process in a display method according to an embodiment of the present disclosure is shown schematically.

[0072] like Figure 5 As shown, based on the aforementioned embodiments, operation S120 may further include operations S510 to S520.

[0073] When operating the S510, configure trigger conditions. Trigger conditions can be preset system state change events, environmental parameter thresholds, or specific non-real-time interactive commands, serving as prerequisite logic for the operating system to execute window space hierarchy transfers. The essence of configuring trigger conditions is to logically decouple the "destination" (i.e., the target interface) of content migration from the "execution timing." This means that when establishing the binding relationship between the first window and the target interface, the first window will not immediately undergo a physical display position shift or visual disappearance. Instead, it enters a preparatory state where it is anchored by the system but migration is temporarily suspended, continuously maintaining normal interaction and operation on the current interface until it waits for a specific contextual trigger. For example, the trigger condition can be configured for the electronic device's system to enter a screen-off lock state; or, the trigger condition can be configured for detecting that the electronic device has successfully connected to a specific external terminal (such as pairing with a vehicle Bluetooth system); or, the trigger condition can be configured for another full-screen application task with a higher display priority to be opened on the current interface.

[0074] When operating the S520, in response to the electronic device meeting a trigger condition, the first window is migrated to the target interface based on the binding relationship. Meeting the trigger condition means that the underlying hardware sensors or software state machine has successfully captured an event signal that matches the preset logic. Once the event signal is captured, the operating system immediately activates the previously suspended configuration logic and schedules the underlying window manager to formally execute the view tree node changes. At this time, the first window is automatically detached from the currently active view container and dynamically mounted to the corresponding display area of ​​the target interface strictly according to the mapping pointer recorded in the binding relationship. The entire migration process is automatically driven by the trigger condition, without needing to obtain explicit drag-and-drop or gesture input from the user at that specific moment, and the running data within the first window maintains real-time continuity at the frame level during the automated migration process.

[0075] For example, when the screen lock state is detected (the trigger condition is met), based on the pre-established binding relationship, the first window of the music application currently running in the foreground is automatically moved from the main screen (current interface) to the system's pull-down notification bar (target interface), so that the playback interface can be directly continued when the screen is turned on again or the notification bar is pulled down; or, when the device is detected to be connected to the vehicle's Bluetooth (the trigger condition is met), the first window of the full-screen map navigation application is automatically moved to the system's negative one screen, thereby automatically giving the display space of the current interface to the newly connected driver assistance application.

[0076] According to embodiments of this disclosure, by introducing a configuration mechanism for triggering conditions, the time span between window binding actions and the actual physical migration process is decoupled. This directly empowers the operating system with the ability to perform interface containment based on context-delayed execution, avoiding forced interface jumps or visual rearrangements at the moment the binding relationship is established. This ensures that the user's current immersive foreground task is not abruptly interrupted. Simultaneously, by automatically driving the smooth migration of native windows based on specific system states or environmental changes, not only is manual intervention by the user during multitasking reduced, but the intelligence and scene adaptability of system-level content scheduling are also significantly improved, constructing a more efficient interactive flow that aligns with user expectations.

[0077] Figure 6 Another flowchart illustrating the mid-transition interface of the display method according to an embodiment of the present disclosure is shown schematically.

[0078] like Figure 6 As shown, based on the aforementioned embodiments, the electronic device includes a first screen, a second screen, a first body, and a second body. The first screen is disposed on the first side of the first body and the second body, and the second screen is disposed on the second side of the first body or the second body.

[0079] The first and second bodies can be physical support shells in electronic devices that are connected by mechanical structures such as hinges, pivots, or flexible connectors and are capable of relative movement. The first screen can be a flexible, foldable display module that spans the first surface (e.g., the inner surface of the electronic device) of the first and second bodies; the second screen can be an independent display module that is set on the second surface (e.g., the outer surface of the device) of the first or second body. Since the first screen usually has a large display area, it is often used in multi-window parallel interaction scenarios. In conjunction with the determination of the target application in the running state in the aforementioned embodiment (i.e., operation S110), when the first screen is in a multi-window display state, the content migration control module can determine a unique main content unit as the target application according to specific rules, and the other windows will not participate in cross-screen migration. The specific rules can be: preferentially select the application window where the user has most recently interacted; if it cannot be determined, select the application window where the user currently has input focus; if it still cannot be determined, select the application window where the user has the largest display area.

[0080] For example, consider an electronic device that is an inward-folding folding screen device. The first body and the second body are the left and right sides of the device, respectively. The first screen is a large, flexible inner screen visible when unfolded, and the second screen is an external secondary screen visible when folded. When an instant messaging application, a document editing application, and a floating calculator application are displayed side-by-side on the first screen, if it is detected that the user has just entered text in the document editing application (i.e., the most recent interaction or input focus), then the document editing application is identified as the target application, and the other two applications are not involved in the subsequent binding and migration logic.

[0081] Operation S520 may include operation S610.

[0082] In operation S610, in response to the change in the relative position angle between the first and second bodies satisfying a target threshold, the first window of the first screen is migrated to the target interface, or the first window of the second screen is migrated to the target interface, based on the binding relationship. The change in relative position angle can be characterized by real-time data acquired by a Hall sensor, gyroscope, or hinge angle sensor built into the electronic device, reflecting the opening and closing posture between the first and second bodies. The target threshold can be a system-preset critical angle value used to determine when a substantial form change occurs in the device (such as from unfolded to folded, or from folded to unfolded).

[0083] When the angle change meets the target threshold, the aforementioned triggering conditions are activated. At this point, the system's underlying window manager, based on the pre-established binding relationship, extracts the first window displayed on the currently active physical screen (first or second screen) and transfers its ownership node to the target interface. Thus, after completing the logical ownership switch and spatial transfer of the application window to a specific level of the target interface, the first window is detached from its original desktop display layout and becomes part of the target interface, awaiting subsequent invocation.

[0084] For example, when the sensor detects that the angle between the first and second bodies decreases from 180 degrees to less than 30 degrees (meeting the target threshold, i.e., performing a folding action), based on a preset binding relationship, the first window of the email application, which was originally displayed in full-screen or split-screen mode on the first screen (inner screen), is directly migrated to the target interface (such as the system's negative one screen). When the folding action is completed and the second screen (outer screen) is activated, the email application is no longer forcibly displayed as the foreground application on the outer screen desktop, but is instead contained in the target interface and presented when the user subsequently invokes the target interface. Conversely, if performing an unfolding action causes the angle to increase and meets the threshold for the unfolding action, the first window on the second screen can also be migrated to the target interface corresponding to the first screen.

[0085] According to embodiments of this disclosure, by configuring the relative angle change between different parts of the device as a trigger condition, an execution logic between application window migration and device physical form change is established. Utilizing the inherent physical opening and closing action of foldable screen devices as the interaction entry point, users do not need to perform additional multi-finger swiping, long-press dragging, or other touch configuration operations on the screen. The window collapsing logic is naturally triggered during daily device form switching, improving the ease of operation and interaction efficiency of transferring application windows across interfaces. Furthermore, when a folding operation occurs, the first window is in a specific collapsible layer, preventing the application interface running on the first screen from being directly displayed full-screen on the second screen, reducing the probability of exposing screen running data during device form switching.

[0086] Figure 7 Another flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically.

[0087] like Figure 7 As shown, based on the aforementioned embodiments, the electronic device includes a first screen and a second screen. The first operation is an opening and closing operation, and the electronic device can switch between an unfolded form and a folded form in response to the opening and closing operation. The opening and closing operation is a physical form transformation process that occurs in the electronic device under the action of mechanical structures such as hinges or flexible rotating shafts. It detects changes in the relative position between the body parts through built-in displacement sensors or angle sensors, and then reports the state switching event to the system. The first screen and the second screen correspond to the main display carriers of the electronic device in the unfolded and folded forms, respectively. The description of the first screen, the second screen, the first body, and the second body in the previous embodiment can be referred to here, and the description of this structural part is also applicable to this embodiment.

[0088] In this embodiment, the electronic device no longer relies on purely software-level touch interactions (such as long press, drag, or menu configuration) to record the execution flow of the binding relationship in subsequent independent configuration steps. Instead, the opening and closing operation of the hardware is directly used as the triggering time to determine the target application and synchronously establish the binding relationship.

[0089] For example, in a horizontally folding electronic device, the first screen is the large flexible screen on the inside that is visible when the device is unfolded, and the second screen is the independent display screen on the outside that is visible when the device is folded. The opening and closing operation is manifested as a folding action of bringing the two parts of the device together, or an action of unfolding the two parts of the device.

[0090] Operation S110 may include operation S710.

[0091] When operating the S710, in response to an opening / closing operation, the application currently displayed and running on the first or second screen is identified as the target application, and a binding relationship is established between the first window and the target interface. "Currently displayed and running" indicates that the target application's interface not only maintains an active execution process in memory, but its window is also located in the top-level display sequence of the screen that was active before the opening / closing operation. The synchronous execution of application identification and binding in response to the opening / closing operation means that when the system's underlying window manager detects a hardware interrupt signal indicating a change in form, it immediately traverses the display stack of the screen (first or second screen) that has lost visual focus, extracts applications that meet the aforementioned visible and active characteristics, and automatically generates logical mapping information between the application's first window and the target interface.

[0092] This process essentially compresses the extraction of the target object and the configuration of interface organization rules into a single physical action. It eliminates the need to maintain a static application whitelist beforehand and eliminates the need for users to manually perform additional configuration settings before folding / unfolding. Instead, it directly establishes the intermediary relationship between the application window and the system target interface (such as the negative one screen) based on the actual usage scenario at the moment of opening / closing. Since it only establishes a binding relationship, the first window is transferred to the target interface's view tree at the underlying level. This processing mechanism replaces the conventional rendering rearrangement process of forcibly stretching or scaling full-screen applications across screens at the moment of opening / closing on folded screens.

[0093] For example, when a user is checking emails on the first screen (inner screen), and the user performs a close-up action (closing the lid), the system detects that the email application is displayed and running, accurately identifies it as the target application, and immediately establishes a binding relationship between the first window of the email application and the second screen (outer screen), the system's negative one screen (target interface). If, when the user closes the lid, the first screen only displays the system desktop and there are no application windows in a top-level active state, the target application identification and binding process is not executed.

[0094] According to embodiments of this disclosure, by directly using physical opening and closing operations as a composite trigger source to determine the target application and establish a binding relationship, hardware form conversion is directly mapped to window-level configuration logic at the software level. The binding relationship is recorded synchronously when the first operation is captured. Unlike methods that rely on subsequent independent configuration steps, this timing-based pre-processing effectively eliminates cumbersome manual settings or drag-and-drop preprocessing steps. Simultaneously, utilizing the dual constraints of "currently displayed" and "in running state," it has the ability to filter background silent tasks or non-focus windows, ensuring that state transition preprocessing is performed only on the user's currently visually focused object. This instant binding mechanism based on a single physical action provides direct rule input for the orderly placement of application windows into system-level content docks (target interfaces), improving the automation and interactive consistency of application state placement in multi-form switching scenarios for foldable screen devices.

[0095] Figure 8 A flowchart illustrating the configuration of binding relationships in a display method according to an embodiment of the present disclosure is shown schematically.

[0096] like Figure 8 As shown, based on the aforementioned embodiments, operation S120 may include operations S810~S820.

[0097] When operating the S810, if the first window is displayed on the first screen, a virtual screen created based on the dimensions of the second screen is retrieved. The virtual screen can be a logical display area created by the system in memory, and its size parameters correspond to those of the second screen. Retrieving a virtual screen created based on the dimensions of the second screen means that when the first window is currently displayed on the first screen, the system pre-creates a virtual screen for screen adaptation according to the screen width, height, resolution, aspect ratio, and pixel density parameters of the second screen, providing a size reference for the subsequently generated content displayed on the target interface.

[0098] It should be noted that the timing of acquiring the virtual screen may vary depending on the specific embodiments described above. Specifically, in conjunction with the aforementioned... Figure 6 In the case of the combined implementation examples, since the prerequisite is the configuration trigger condition, the virtual screen is pre-created and acquired during the process of configuring the binding relationship between the first window and the target interface; while in conjunction with the aforementioned Figure 7 In the case of the combined implementation, since the prerequisite is to directly reuse the opening and closing action as an interactive instruction, the virtual screen is created and acquired immediately when the target application is established and the binding relationship is established simultaneously during the execution of the opening and closing operation as the first operation.

[0099] For example, when the device is in an unfolded state, the document editing application is currently displayed on the first screen, and a virtual screen corresponding to the size of the second screen is pre-obtained based on the resolution and aspect ratio of the second screen.

[0100] When operating the S820, the runtime data displayed in the first window is adapted based on the size of the virtual screen to generate the content displayed on the target interface. The size of the virtual screen corresponds to the second screen; therefore, adapting the runtime data displayed in the first window based on the virtual screen size means that, when the first window is currently displayed on the first screen, the interface layout, content arrangement, or display ratio of the first window is adapted to the screen size based on the virtual screen size to obtain the display content for display on the target interface. It should be noted that the adaptation process involves the visual mapping and compositing logic between the virtual screen output in the graphics rendering framework and the target interface (such as the system's negative one screen or the drop-down notification bar), and the specific triggering mechanism varies in different situations. (This is related to the aforementioned...) Figure 6 In the combined implementation, during the independent trigger condition configuration process, i.e., before the device's physical form changes, the rendering output handle of the first window is redirected to the virtual screen; while in conjunction with the aforementioned Figure 7 In the case of a combination of embodiments, the rendering output handle of the first window is redirected to the virtual screen at the instant when the opening and closing operation that causes a change in physical form is captured.

[0101] In both cases, the underlying system initiates collaborative rendering and adaptation processing without exiting the original application process. At the rendering level, without exiting the original application process, the target application logically determines that it is now in the target screen environment after the size change, and accordingly redraws and renders the UI interface in the virtual memory buffer according to the virtual screen's size ratio, thereby generating source graphics frames that conform to the characteristics of the next screen's size. Next, at the adaptation level, the underlying graphics compositor extracts the complete graphics pixel frames rendered from the virtual screen. Through texture mapping, matrix transformation, or adaptive scaling calculations, it converts the rendered pixel frames into graphics data suitable for presentation in a specific layout container of the target interface, and uses this as a dynamic texture to be composited in real-time into the area reserved on the system's negative one screen or the dedicated task layer of the pull-down notification bar.

[0102] For example, when the first window of a document editing application is currently displayed on the first screen, the display ratio of the document editing area, toolbar area, and page layout content in the document editing application is adapted according to the virtual screen created based on the size of the second screen. Then, through the underlying graphics compositing stage of the system, the complete view frame rendered in the virtual screen after adaptation is mapped and drawn onto the reserved task area in the system's negative one screen or drop-down notification bar according to the preset ratio, generating the display content displayed in the target interface.

[0103] In some embodiments, if the second screen displays the first window, a virtual screen created based on the size of the first screen can be obtained, and the running data displayed in the first window can be adapted based on the size of the virtual screen to generate the display content of the target interface. That is, when the first window is currently displayed on the second screen, the first window is pre-adapted to the size of the first screen so that after switching to the first screen, the first window displayed in the target interface matches the size of the first screen.

[0104] According to embodiments of this disclosure, by pre-acquiring a virtual screen created based on the size of another screen when the first window is currently displayed on a screen, and adapting the running data displayed in the first window to the size of the virtual screen, screen adaptation for the next screen can be completed before the form switch. Thus, when switching to the next screen and displaying the target interface, the first window displayed in the target interface can match the size of the next screen, reducing temporary adaptation processing caused by screen size changes, avoiding problems such as unbalanced window content or inconsistent layout, and helping to maintain the continuity of application window display.

[0105] Figure 9 A block diagram of a display device according to an embodiment of the present disclosure is shown schematically.

[0106] like Figure 9 As shown, the display device 900 may include a determination module 910 and a configuration module 920.

[0107] The determining module 910 is used to obtain a first operation and, in response to the first operation, determine a target application in a running state; the target application in a running state displays running data through a first window. In some embodiments, the determining module 910 may be used to perform operation S110 in the above display method, which will not be elaborated here.

[0108] The configuration module 920 is used to configure the binding relationship between the first window and the target interface. The target interface is the interactive operating interface of the electronic device's operating system; the target interface is displayed on the electronic device's screen in response to a swipe operation along a first direction on the current interface; the first window is displayed when the target interface is displayed based on the binding relationship. In some embodiments, the configuration module 920 can be used to perform operation S120 in the above display method, which will not be elaborated here.

[0109] Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure, or at least part of the functions of any one or more of them, can be implemented in one module. Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be implemented by dividing them into multiple modules. Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be at least partially implemented as hardware circuitry, such as a Field-Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a System-on-Chip, a System-on-a-Substrate, a System-on-Package, an Application-Specific Integrated Circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be at least partially implemented as computer program modules, which, when run, can perform corresponding functions.

[0110] For example, any plurality of the determining module 910 and the configuration module 920 can be combined into one module / unit / subunit, or any one of the modules / units / subunits can be split into multiple modules / units / subunits. Alternatively, at least part of the functionality of one or more of these modules / units / subunits can be combined with at least part of the functionality of other modules / units / subunits and implemented in one module / unit / subunit. According to embodiments of this disclosure, at least one of the determining module 910 and the configuration module 920 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the determining module 910 and the configuration module 920 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0111] It should be noted that the data processing system part in the embodiments of this disclosure corresponds to the data processing method part in the embodiments of this disclosure. The specific description of the data processing system part is referred to in the data processing method part, and will not be repeated here.

[0112] Figure 10 A block diagram of an electronic device suitable for implementing the methods described above, according to embodiments of the present disclosure, is illustrated schematically. Figure 10The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0113] like Figure 10 As shown, an electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage portion 1008 into a random access memory (RAM) 1003. The processor 1001 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 1001 may also include onboard memory for caching purposes. The processor 1001 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.

[0114] RAM 1003 stores various programs and data required for the operation of electronic device 1000. Processor 1001, ROM 1002, and RAM 1003 are interconnected via bus 1004. Processor 1001 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 1002 and / or RAM 1003. It should be noted that the programs may also be stored in one or more memories other than ROM 1002 and RAM 1003. Processor 1001 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0115] According to embodiments of this disclosure, the electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to a bus 1004. The electronic device 1000 may also include one or more of the following components connected to the input / output (I / O) interface 1005: an input section 1006 including a touch panel, physical buttons, a microphone, and a keyboard, mouse, etc.; an output section 1007 including a cathode ray tube (CRT), liquid crystal display (LCD), organic light-emitting diode (OLED) display, flexible display, etc., and a speaker, etc.; a storage section 1008 including a hard disk, flash memory (such as UFS, eMMC), etc.; a sensor 1012 coupled to a processor 1001 for acquiring user operations (e.g., a first operation, a swipe operation along a first direction on the current interface, and a device opening / closing operation, etc.); and a communication section 1009 including a network interface card such as a cellular network module, a Wi-Fi module, a Bluetooth module, a LAN card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. The drive 1010 is also connected to the input / output (I / O) interface 1005 as needed. Removable media 1011, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on the drive 1010 as needed so that computer programs read from them can be installed into the storage section 1008 as needed.

[0116] In some embodiments, the electronic device 1000 further includes a first body and a second body. The display screen includes a first screen and a second screen, the first screen being disposed on a first surface of the first body and the second body, and the second screen being disposed on a second surface of either the first body or the second body. The electronic device is capable of switching between an unfolded mode and a folded mode in response to an opening and closing operation between the first body and the second body.

[0117] According to embodiments of this disclosure, processor 1001 is coupled to both a display screen and sensor 1012. When processor 1001 executes a program, it is used to: obtain a first operation collected by sensor 1012; in response to the first operation, determine a target application in a running state; the target application in a running state displays running data through a first window; configure a binding relationship between the first window and the target interface; wherein the target interface is an interactive operating interface of the operating system of electronic device 1000; the target interface is capable of being displayed on the display screen in response to a sliding operation along a first direction on the current interface; and the first window is displayed when the target interface is displayed based on the binding relationship.

[0118] In some embodiments, when configuring the binding relationship between the first window and the target interface, the processor 1001 is configured to: configure trigger conditions; in response to the sensor 1012 detecting that the angle of change in the relative position of the first body and the second body meets the target threshold, based on the binding relationship, migrate the first window of the first screen to the target interface, or migrate the first window of the second screen to the target interface.

[0119] In some embodiments, the first operation is an opening / closing operation; when a target application in a running state is determined in response to the first operation, the processor 1001 is configured to: in response to the opening / closing operation, determine the application currently displayed on the first screen or the second screen that is in a running state as the target application, and establish a binding relationship between the first window and the target interface.

[0120] According to embodiments of this disclosure, the method flow according to embodiments of this disclosure can be implemented as a computer software program. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1009, and / or installed from removable medium 1011. When the computer program is executed by processor 1001, it performs the functions defined in the system of embodiments of this disclosure. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0121] 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.

[0122] According to embodiments of this disclosure, the computer-readable storage medium can be a non-volatile computer-readable storage medium. Examples include, but are 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 can 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.

[0123] For example, according to embodiments of this disclosure, a computer-readable storage medium may include the ROM 1002 and / or RAM 1003 described above and / or one or more memories other than ROM 1002 and RAM 1003.

[0124] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods provided in the embodiments of this disclosure. When the computer program product is run on an electronic device, the program code is used to enable the electronic device to implement the display methods provided in the embodiments of this disclosure.

[0125] When the computer program is executed by the processor 1001, 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.

[0126] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices or magnetic storage devices. 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 1009, and / or installed from removable medium 1011. 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. 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 may be executed entirely on a user computing device, partially on a user 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 devices can be connected to user computing devices via any type of network, including local area networks (LANs) or wide area networks (WANs), or they can be connected to external computing devices (e.g., via the Internet using an Internet service provider).

[0127] 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 the present 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. Those skilled in the art will understand that the features described in the various embodiments of the present disclosure can be combined and / or combined in various ways, even if such combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments of this disclosure may be combined and / 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.

[0128] 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. 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 applied to an electronic device, comprising: Obtain the first operation, and in response to the first operation, determine the target application that is in a running state; The target application in operation displays its running data through a first window; Configure the binding relationship between the first window and the target interface; The target interface is the interactive operating interface of the electronic device's operating system. The target interface is displayed on the screen of the electronic device in response to a swipe operation along a first direction on the current interface; the first window is displayed when the target interface is displayed based on the binding relationship.

2. The method according to claim 1, further comprising: In response to the configuration, the first window is migrated from the current interface to the target interface based on the binding relationship; The current interface is the default display interface on the system desktop of the electronic device, and the current interface is used to display the user interface window of the target application.

3. The method according to claim 2, wherein configuring the binding relationship between the first window and the target interface includes any one of the following: Add the first window to the target interface such that the target interface includes the first window; Create the target interface, and use the running data displayed in the first window as the display content of the target interface; Obtain the indicator of the target interface, and establish a binding relationship between the first window and the target interface based on the indicator.

4. The method according to claim 3, further comprising: In response to the target application changing from a running state to a non-running state, the binding relationship is released.

5. The method according to claim 3, wherein configuring the binding relationship between the first window and the target interface further includes: Configure trigger conditions; In response to the electronic device meeting the triggering condition, the first window is migrated to the target interface based on the binding relationship.

6. The method according to claim 5, wherein the electronic device comprises a first screen, a second screen, a first body, and a second body, wherein the first screen is disposed on a first surface of the first body and the second body, and the second screen is disposed on a second surface of the first body or the second body; The step of migrating the first window to the target interface based on the binding relationship in response to the electronic device meeting the trigger condition includes: In response to the change in the relative position angle between the first body and the second body satisfying the target threshold, based on the binding relationship, the first window of the first screen is migrated to the target interface, or the first window of the second screen is migrated to the target interface.

7. The method according to claim 2, wherein the electronic device includes a first screen and a second screen, the first operation is an opening and closing operation, and the electronic device is capable of switching between an unfolded form and a folded form in response to the opening and closing operation; The step of determining the target application in a running state in response to the first operation includes: In response to the opening and closing operation, the application currently displayed and running on the first screen or the second screen is determined as the target application, and the binding relationship between the first window and the target interface is established.

8. The method according to any one of claims 6 or 7, wherein configuring the binding relationship between the first window and the target interface includes: If the first screen displays the first window, obtain the virtual screen created based on the size of the second screen; The running data displayed in the first window is adapted to the size of the virtual screen to generate the display content of the target interface.

9. An electronic device, comprising: A display screen used to show the user interface; Sensors are used to collect user actions; The processor is coupled to both the display screen and the sensor. The processor is used for: The sensor acquires a first operation, and in response to the first operation, a target application in a running state is determined; the target application in a running state displays running data through a first window. Configure the binding relationship between the first window and the target interface; wherein, the target interface is an interactive operating interface of the operating system of the electronic device; the target interface can be displayed on the display screen in response to a sliding operation along a first direction on the current interface; The first window is displayed when the target interface is displayed based on the binding relationship.

10. The electronic device according to claim 9, further comprising a first body and a second body, the display screen comprising a first screen and a second screen, the first screen being disposed on a first surface of the first body and the second body, and the second screen being disposed on a second surface of the first body or the second body; The configuration of the binding relationship between the first window and the target interface includes: Configure trigger conditions; In response to the change in the relative position angle between the first body and the second body satisfying the target threshold, based on the binding relationship, the first window of the first screen is migrated to the target interface, or the first window of the second screen is migrated to the target interface.

11. The electronic device according to claim 9, wherein the display screen includes a first screen and a second screen, the first operation is an opening and closing operation, and the electronic device is capable of switching between an unfolded state and a folded state in response to the opening and closing operation; The step of determining the target application in a running state in response to the first operation includes: In response to the opening and closing operation, the application currently displayed and running on the first screen or the second screen is determined as the target application, and the binding relationship between the first window and the target interface is established.

Images