Multi-window display method and device, and storage medium

Abstract

Provided in the present application are a multi-window display method and device, and a storage medium. In the method, when exiting an interface corresponding to a current multi-task, a layout style of a window corresponding to the multi-task is recorded, and on the basis of the layout style, a plurality of currently performed tasks are retained on a multi-task management interface in the form of a task group. In this way, a task group corresponding to a multi-task scenario is operated in the multi-task management interface, such that with one click, a user can switch the tasks from the background back to the foreground to run, and display the tasks in a layout style before switching same to the background.

Description

Multi-window display methods, devices and storage media Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a multi-window display method, device and storage medium. Background Technology

[0002] With the development of terminal technology, the performance of electronic devices has been greatly improved. Currently, in order to enhance user experience, more and more electronic devices are beginning to support multi-window mode.

[0003] However, current multi-window solutions display multiple windows for different applications (APPs), resulting in a cluttered layout, mutual obstruction, and an inability to meet diverse user needs. Furthermore, the entry and exit points for multi-window mode are often deeply hidden, making the operation complex and leading to a poor user experience.

[0004] Summary of the Invention

[0005] To address the aforementioned technical problems, embodiments of this application provide a multi-window display method, device, and storage medium, which aim to facilitate convenient and quick entry and exit from multi-window mode and enable free layout among multiple windows to meet users' needs for multi-window display.

[0006] In a first aspect, embodiments of this application provide a multi-window display method applied to an electronic device. The method includes: displaying a first interface, the first interface including windows corresponding to M tasks, each window including a floating window, where M is an integer greater than 2, the first interface being an interface in a first multi-tasking scenario, each task in the first multi-tasking scenario being displayed as a floating window; responding to an operation to exit the first interface, exiting the first interface and switching the M tasks to run in the background; responding to an operation to enter a multi-tasking management interface, displaying a multi-tasking management interface, the multi-tasking management interface including a split-screen task group and a first task group displayed in a first layout style, the split-screen task group including two tasks displayed in a split-screen format, the first task group including M tasks, the first style being the layout style of the windows corresponding to the M tasks displayed in the first interface, and the split-screen task group... The two tasks in the first task group are different from the M tasks in the second task group. In response to the operation on the split-screen task group, the multitasking management interface is exited and the third interface is displayed. The third interface is the interface for the second multitasking scenario, where tasks are displayed in a split-screen format. The third interface displays the two tasks in the split-screen task group in a split-screen format. In response to the operation on the third interface, the third interface is exited, and the two tasks in the split-screen task group are switched to run in the background. In response to the operation on the multitasking management interface, the multitasking management interface is displayed. The multitasking management interface includes the split-screen task group and the first task group displayed in the first layout style. In response to the operation on the first task group, the multitasking management interface is exited and the first interface is displayed.

[0007] The first interface is, for example, interface 30c, or interface 40a, or interface 40b, or interface 40c, or the interface mentioned in the following embodiments, that is, the interface corresponding to the small window mode.

[0008] The first multitasking scenario can be understood as the multitasking scenario corresponding to the small window mode. In one implementation, all tasks in the interface corresponding to the first multitasking scenario are displayed in a floating window.

[0009] The availability of M is limited by factors such as the screen size of electronic devices, whether multi-screen collaboration is available, external monitors, and performance.

[0010] In one implementation, for example, when the electronic device is a tablet or other device with a large screen, the value of M can be 4 or greater than 4.

[0011] The floating window can also be simply referred to as the floating window.

[0012] The tasks can come from the same application or from different applications.

[0013] This includes actions that respond to exiting the first screen, such as clicking the home screen button or the multitasking management button.

[0014] Among them, the response to exiting the first interface is also, for example, a specific operation performed by the user, such as returning to the home screen (desktop) (swiping up from the bottom edge of the screen), or entering the multitasking management interface (swiping up from the bottom edge of the screen and pausing).

[0015] Background operation refers to a program running in the operating system in a way that is invisible to the user. That is, it is not displayed in the user interface that interacts with the user.

[0016] In some implementations, after switching a foreground task to run in the background, a second interface can be displayed in the foreground.

[0017] The second interface can be the home screen, commonly known as the desktop, or a multitasking management interface. Understandably, when the user clicks the home screen button, the electronic device, in response to this action, will exit the current interface (as in the first interface), switch the M tasks to run in the background, and display the home screen button. Similarly, when the user clicks the multitasking management button, the electronic device, in response to this action, will exit the current interface (as in the first interface), switch the M tasks to run in the background, and display the multitasking management interface.

[0018] The layout style can also be described as window layout or multi-window layout, etc.

[0019] This includes actions that respond to entering the multitasking management interface, such as clicking the multitasking management button or swiping up from the bottom edge of the screen and pausing.

[0020] The third interface, for example, is interface 40L as described in the following embodiment. That is, the interface in the second multitasking scenario corresponding to the split-screen mode.

[0021] Therefore, when exiting the interface corresponding to the current first multitasking scenario, the layout style of the windows corresponding to multiple tasks in that first multitasking scenario is recorded, and the currently running multiple tasks are preserved in the multitasking management interface as a first task group based on this layout style. In this way, by operating on the first task group corresponding to the first multitasking scenario in the multitasking management interface, the user can switch the multiple tasks included in the first task group from the background back to the foreground with one click, and display them in the layout style before switching to the background.

[0022] In addition, when exiting the first multitasking scenario with one click, that is, switching the tasks running in multiple floating windows in the foreground to run in the background, you can directly operate the split-screen task group or the first task group displayed in the multitasking management interface without closing the small window mode, so as to achieve seamless switching between different task scenarios, which better meets the user's needs.

[0023] According to the first aspect, after switching M tasks to run in the background, the method further includes: in response to the operation of opening the first application, displaying a fourth interface, the fourth interface including a window corresponding to any task provided by the first application, the window being a full-screen window; in response to the operation of exiting the fourth interface, exiting the fourth interface and switching the single task provided by the first application to run in the background; wherein, when the single task provided by the first application is different from the two tasks in the split-screen task group and the M tasks in the first task group, the multi-task management interface includes the split-screen task group, the first task group displayed in the first layout style, and the single task provided by the first application.

[0024] The fourth interface is, for example, interface 40j as described in the following embodiments.

[0025] In response to the operation of exiting the fourth interface, the second interface can also be displayed when the single task provided by the first application is switched to run in the background.

[0026] Therefore, after switching the first task group to run in the background, opening a single task can directly display it in full screen without using a floating window. This allows for seamless switching between different task scenarios, such as switching between the first multi-tasking scenario and the full-screen scenario, without the user's awareness.

[0027] Furthermore, switching between different scenarios does not require users to switch between entering and exiting the small window mode separately, greatly improving the user experience.

[0028] According to the first aspect, or any of the implementations of the first aspect above, the method further includes: when the single task provided by the first application is the same as any task in the first task group, the multi-task management interface includes a split-screen task group, a single task provided by the first application, and a second task group displayed in a second layout style; wherein, the second task group includes N tasks, the N tasks are M-1 tasks in the first task group excluding the single task, and the second layout style is the same as the layout style of the windows corresponding to the M-1 tasks in the first task group.

[0029] Therefore, when the first task group is switched to run in the background, if a user uses any task in the first task group alone, the content of that task will be displayed in full screen and the task will be removed from the first task group. This avoids the same task existing as a single task and also existing in the first task group, which would affect the user experience.

[0030] According to the first aspect, or any of the implementations of the first aspect above, when the multitasking management interface includes a split-screen task group, a single task provided by the first application, and a second task group displayed in a second layout style, the method further includes: when the multitasking management interface is displayed, in response to an operation on the second task group, exiting the multitasking management interface and displaying a fifth interface, the fifth interface including windows corresponding to M-1 tasks, the layout style of the windows corresponding to M-1 tasks in the first interface being the same as the layout style of the windows corresponding to M-1 tasks in the fifth interface.

[0031] For example, if the single task is APP-1 in the following embodiment, removing the task of APP-1 will result in the second task group consisting of the tasks of APP-2, APP-3, and APP-4 in the following embodiment.

[0032] Accordingly, after selecting the second task group, the layout of the windows for the three tasks APP-2, APP-3, and APP-4 on the fifth interface displayed on the screen can maintain the layout style of floating windows 403', 404', and 405' as shown in Figure 9, that is, their positions and sizes remain unchanged. Floating window 402' is not displayed; instead, the content of that area on the desktop is displayed.

[0033] For example, in some implementations, the layout style of the second task group can also be automatically updated to a layout style suitable for the number of tasks in the task group, such as the layout style of any three floating windows in the second row shown in the shortcut window layout 406 in Figure 10.

[0034] This avoids conflicts between task groups and individual tasks, enables rapid switching between them, and ensures that the switched tasks can continue to be used.

[0035] According to the first aspect, or any of the implementations of the first aspect above, the method further includes: in response to the operation of entering the multi-window free layout scene, displaying the multi-window free layout entry on the first interface; in response to the operation of the multi-window free layout entry, splitting multiple windows belonging to the same layer into multiple floating windows belonging to different layers; for each floating window, in response to the operation of adjusting the floating window, adjusting the aspect ratio of the floating window from a first ratio to a second ratio.

[0036] In response to the operation of entering the multi-window free layout scene, the multi-window free layout entrance is displayed on the first interface. For example, when the user makes a specific gesture (such as clicking or swiping) in a specific area of ​​the electronic device display screen (such as the left side of the screen, the right side of the screen, the top of the screen, the bottom of the screen, etc.), a multi-window free layout entrance to enter the multi-window free layout scene is brought up, as shown by control 401-1 in interface 40a in Figure 8.

[0037] The aspect ratio of the floating window can be adjusted freely according to the user's finger movements.

[0038] Therefore, by splitting the windows corresponding to different tasks into floating windows of different layers, users can easily adjust the proportion of each floating window as needed, thus realizing the free adjustment of the aspect ratio of the window corresponding to each task.

[0039] According to the first aspect, or any of the implementations of the first aspect above, the aspect ratio of the floating window is adjusted from the first ratio to the second ratio, including: adjusting the aspect ratio of the floating window from the first ratio to the second ratio according to the rasterization adjustment method.

[0040] When adjusting the scale of the floating window based on the grid adjustment method, it can be adjusted according to the horizontal Q setting and the vertical P setting.

[0041] In this case, Q is, for example, 6, and P is, for example, 4.

[0042] Therefore, for electronic devices with poor responsiveness, adjusting the scale of the floating window based on a grid-based adjustment method can achieve any scale to meet the actual user needs.

[0043] According to the first aspect, or any of the implementations of the first aspect above, the first ratio and the second ratio are not the same.

[0044] This allows for free scaling of the floating window, instead of the current limitation of only being able to be scaled proportionally, enabling the adjusted floating window to fill the entire screen.

[0045] According to the first aspect, or any of the implementations of the first aspect above, after splitting multiple windows belonging to the same layer into multiple floating windows belonging to different layers, the method further includes: in response to the operation of quick layout of the windows corresponding to M tasks, displaying a quick layout window on the first interface, the quick layout window including multiple layout styles; in response to the selection operation of the layout style suitable for the M tasks in the quick layout window, switching the layout style of the floating windows corresponding to the M tasks to the selected layout style.

[0046] In response to the operation of quick layout of windows corresponding to M tasks, a quick layout window is displayed on the first interface. For example, when a user makes a specific gesture (such as clicking or swiping) in a specific area of ​​the electronic device display screen (such as the left side, right side, top, or bottom of the screen), the quick layout window 406 is directly displayed on the first interface, as shown in interface 40d in Figure 10, or the quick layout window 406' shown in Figure 12 is displayed.

[0047] Therefore, after the window in the first interface has been split into floating windows belonging to different layers, by bringing up the quick layout window in the current interface, the layout style in the quick layout window can be selected with one click, and the layout of the window corresponding to each task can be switched quickly and easily.

[0048] According to the first aspect, or any of the implementations of the first aspect above, the method further includes: in response to the operation of quick layout of windows corresponding to M tasks, displaying a quick layout window on the first interface, the quick layout window including multiple layout styles; in response to the selection operation of a layout style suitable for M tasks in the quick layout window, splitting multiple windows belonging to the same layer into multiple floating windows belonging to different layers, and switching the layout style of the floating windows corresponding to M tasks to the selected layout style.

[0049] In response to the operation of quickly arranging the windows corresponding to M tasks, a quick layout window is displayed on the first interface. For example, a quick layout entry is brought up by the user making a specific gesture (such as clicking or swiping) in a specific area of ​​the electronic device's display screen (such as the left side, right side, top, or bottom of the screen), as shown in quick layout entry 401-2 in interface 40a of Figure 8. Then, clicking quick layout entry 401-2 displays quick layout window 406 on the first interface, as shown in interface 40d of Figure 10, or displays quick layout window 406' as shown in Figure 12.

[0050] In response to the operation of quick layout of windows corresponding to M tasks, a quick layout window is displayed on the first interface. Alternatively, for example, when a user makes a specific gesture (such as clicking or swiping) in a specific area of ​​the electronic device display screen (such as the left side, right side, top, or bottom of the screen), a quick layout window 406 is directly displayed on the first interface, as shown in interface 40e in Figure 11.

[0051] Therefore, by splitting windows corresponding to different tasks into different layers and switching between multiple window layouts with one click, it not only makes it convenient for users to operate, but also allows users to freely adjust the proportion of each floating window as needed after switching between multiple window layouts with one click, thereby better meeting users' needs for using multiple windows.

[0052] Based on the first aspect, or any of the implementations of the first aspect above, the layout style displayed in the quick layout window is related to the electronic device.

[0053] For example, for electronic devices with relatively small screens, such as regular mobile phones and small foldable phones, the layout styles displayed in the quick layout window can include various styles of two-screen layouts, as well as single floating window layouts.

[0054] For example, for electronic devices with relatively large screens, such as large foldable phones, the layout styles displayed in the quick layout window can include various styles of two-screen layouts, three-screen layouts, single floating window layouts, and two floating window layouts.

[0055] For example, for electronic devices with larger screens such as tri-fold phones, tablets, desktops, laptops, and smart TVs, the layout styles displayed in the quick layout window can include various styles of split-screen layouts and floating window layouts.

[0056] Therefore, determining the layout style displayed in the quick layout window based on the electronic device enables the multi-window display solution to be better applied to different electronic devices, improving the user experience of multi-windows for users of different electronic devices.

[0057] Secondly, embodiments of this application provide an electronic device. The electronic device includes: a memory and a processor, the memory and the processor being coupled; the memory stores program instructions, which, when executed by the processor, cause the electronic device to perform the methods of the first aspect or any possible implementation thereof.

[0058] Thirdly, embodiments of this application provide a computer-readable medium for storing a computer program, the computer program including instructions for performing the method in the first aspect or any possible implementation of the first aspect.

[0059] Fourthly, embodiments of this application provide a computer program including instructions for performing the method in the first aspect or any possible implementation thereof.

[0060] Fifthly, embodiments of this application provide a chip including a processing circuit and transceiver pins. The transceiver pins and the processing circuit communicate with each other via an internal connection path. The processing circuit executes the method in the first aspect or any possible implementation of the first aspect to control the receiving pin to receive signals and to control the transmitting pin to transmit signals. Attached Figure Description

[0061] Figure 1 is a schematic diagram of a second multitasking scenario in a split-screen mode, as exemplarily shown;

[0062] Figure 2 is a schematic diagram illustrating an example of opening and closing a small window;

[0063] Figure 3 is a schematic diagram illustrating yet another mode of opening and closing the small window;

[0064] Figure 4 is an exemplary schematic diagram of the first multitasking scenario after enabling the small window mode;

[0065] Figure 5 is an exemplary schematic diagram showing the proportional adjustment of a floating window in a small window mode;

[0066] Figures 6 and 7 are schematic diagrams illustrating a switching between a multi-task scenario and a single-task scenario;

[0067] Figures 8 and 9 are exemplary schematic diagrams illustrating a multi-window display method based on an embodiment of this application, showing how to split multiple windows and freely adjust their proportions.

[0068] Figure 10 is a schematic diagram illustrating one-click layout based on a multi-window display method provided in an embodiment of this application;

[0069] Figure 11 is an exemplary schematic diagram illustrating another method for implementing one-click layout based on the multi-window display method provided in this application embodiment;

[0070] Figure 12 is an exemplary schematic diagram illustrating another method for implementing one-click layout based on the multi-window display method provided in this application embodiment;

[0071] Figures 13 and 14 are exemplary diagrams illustrating a multi-window display method based on an embodiment of this application, showing the loading of task content in different floating windows when laying out multiple windows with one click;

[0072] Figures 15 and 16 are exemplary schematic diagrams illustrating the implementation of a multi-window display method based on an embodiment of this application to achieve task continuity in different scenarios;

[0073] Figure 17 is an exemplary schematic diagram of the appearance of a conventional mobile phone;

[0074] Figure 18 is an exemplary schematic diagram of the appearance of a small folding mobile phone;

[0075] Figure 19 is a schematic diagram illustrating a quick layout window displayed in a regular mobile phone and a small folding phone;

[0076] Figure 20 is an exemplary schematic diagram of the appearance of a large-fold mobile phone;

[0077] Figure 21 is a schematic diagram illustrating a quick layout window displayed in a large foldable screen phone;

[0078] Figure 22 is an exemplary schematic diagram of the appearance of a tri-fold mobile phone;

[0079] Figure 23 is a schematic diagram of the hardware structure of an electronic device as an example;

[0080] Figure 24 is a schematic diagram of the software structure of an electronic device as an example. Detailed Implementation

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

[0082] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0083] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects. For example, "first target object" and "second target object," etc., are used to distinguish different target objects, not to describe a specific order of target objects.

[0084] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0085] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more. For example, multiple processing units means two or more processing units; multiple systems means two or more systems.

[0086] With the development of terminal technology, the performance of electronic devices has been greatly improved. Currently, to enhance user experience, more and more electronic devices are beginning to support multi-window mode (multi-window functionality). Multi-window mode allows two or more applications to run simultaneously on the screen of an electronic device, enabling users to view and process different information at the same time.

[0087] For example, in some implementations, multi-window mode typically includes split-screen mode and small window (floating window) mode. In the description of the embodiments of this application, split-screen mode is a functional mode that allows users to handle at least two tasks at the same time. It allows an electronic device to run multiple applications on one screen at the same time, and the windows of these multiple applications are displayed side by side to fill the entire screen. Small window mode, on the other hand, allows an electronic device to display one or more applications on one screen in the form of small windows (floating windows).

[0088] Taking split-screen mode supporting two tasks filling the entire screen as an example, it's important to note that in split-screen mode, if a user opens more than three applications, the other applications besides the two in the split-screen window can be displayed as floating windows above the split-screen interface. As shown in interface 30c in Figure 1, there are currently four tasks running in the foreground. Tasks APP-5 and APP-6 are displayed in split-screen mode; for example, split-screen window 306 displays the content of APP-5, and split-screen window 307 displays the content of APP-6. The content of other applications is displayed as floating windows above the layer containing the split-screen windows; for example, floating window 305 displays the content of APP-4, and floating window 304 displays the content of APP-3.

[0089] It should be noted that the content of APP-5 and APP-6 displayed in split-screen mode belong to the same layer (hereinafter referred to as Layer A for easy distinction). In Layer A, the window displaying the content of APP-5 (Window 1) includes a control 306 at the top (which can be understood as a bar), and the window displaying the content of APP-6 (Window 2) includes a control 307 at the top (which can be understood as a bar). When the user presses and holds control 306, or moves control 307 on the screen, the tablet computer responds to the user's operation by swapping the positions of Window 1 and Window 2, that is, moving Window 2 to the position of Window 1 in interface 30c, and moving Window 1 to the position of Window 2 in interface 30c.

[0090] Referring again to Figure 1, in some implementations, layer A includes a control 308 (which can be understood as a bar) located between window 1 and window 2. When a user clicks control 308, the tablet computer responds to this user action by swapping the positions of window 1 and window 2.

[0091] The above description is merely an example provided to better understand the technical solution of this embodiment and is not intended to be the only limitation of this embodiment.

[0092] In other words, both split-screen mode and small window mode involve multitasking scenarios. For ease of distinction, in the embodiments of this application, the multitasking scenario corresponding to small window mode is referred to as the first multitasking scenario (multiple floating windows, or multiple floating windows + 2 split-screen windows), and the multitasking scenario corresponding to split-screen mode is referred to as the second multitasking scenario (only 2 application windows are displayed in split-screen mode).

[0093] In addition, it should be noted that the small window mode can include both the first multitasking scenario and the single-tasking scenario. That is, only one application is running on the display screen, and that application is displayed in a small window.

[0094] The technical solutions provided in this application mainly address the first multitasking scenario corresponding to the small window mode, and the switching method between the first multitasking scenario and the second multitasking scenario.

[0095] To better understand the use of the first multitasking scenario, we will take a tablet computer as an example and provide a detailed explanation with reference to the accompanying diagram.

[0096] Referring to Figure 2, an exemplary schematic diagram of opening and closing a multi-window mode is shown. As shown in Figure 2, in this implementation, the entry point for opening and closing the multi-window mode (the “Smart Multi-Window” option shown in Figure 2(1) or Figure 2(2)) is set in the settings application.

[0097] For example, in some implementations, when a user turns the small window mode on or off as shown in Figure 2, the user can click the icon corresponding to the settings application. Accordingly, the tablet computer responds to the user's operation by launching the settings application and displaying interface 10a as shown in Figure 2(1), or interface 10b as shown in Figure 2(2).

[0098] Referring to Figures 2(1) and 2(2), for example, for electronic devices with relatively large screens, such as tablets and large foldable phones, a portion of the display area, such as the left side of interface 10a, will display the function entrances provided by the settings application, such as the entrance for setting "Login User Account", the entrance for setting "WLAN", the entrance for setting "Bluetooth", the entrance for setting "Mobile Network", and the entrance for setting the small window mode, such as the "Smart Multi-Window" entrance. The right side of interface 10a displays the content corresponding to the currently selected function entrance. Taking the "Smart Multi-Window" entrance displayed in the left side of interface 10a as an example, the right side of interface 10a will display the switch 101 for turning on the small window mode as shown in Figure 2(1), or the switch 101' for turning off the small window mode as shown in Figure 2(2).

[0099] Taking a tablet computer with the default window mode disabled as an example, specifically when the user selects the "Smart Multi-Window" option after launching the settings application, the tablet's display shows interface 10a. In this case, if the user clicks switch 101, the tablet computer will respond to the user's action and enable window mode. At the same time, switch 101 will switch to the style of switch 101' in interface 10b.

[0100] For example, when the small window mode is enabled, if the user clicks switch 101', the tablet computer will respond to the user's operation, close the small window mode, and switch 101' will switch to the style of switch 101 in interface 10a.

[0101] Therefore, by setting the entry point for enabling and disabling the small window mode in the settings app, there is no need to install a separate application for setting the small window mode on the tablet.

[0102] Referring to Figure 3, an exemplary schematic diagram of opening and closing a small window mode is shown. As shown in Figure 3, in this implementation, the entry point for opening and closing the small window mode (the "Smart Multi-Window" option shown in Figure 3(1) or Figure 3(2)) is located in the control center.

[0103] For example, in some implementations, when a user opens or closes the small window mode as shown in Figure 3, the user can perform a swipe operation (swiping operation) from the top of the tablet screen inwards. Accordingly, in response to the user's operation, the tablet will display the interface corresponding to the control center, such as interface 20a shown in Figure 3(1), or interface 20b shown in Figure 3(2).

[0104] Taking a tablet computer with its default window-to-window mode disabled as an example, when a user swipes the screen inwards from the top, the tablet displays interface 20a in response. Interface 20a can display options for the tablet's supported functions / modes. For example, window 201 may display options such as WLAN, ringtone, auto-rotate, wireless sharing, Smart Window option 201-1, and airplane mode. When the user clicks on Smart Window option 201-1, the tablet displays window-to-window mode, and Smart Window option 201-1 changes to the style displayed in window 201' within interface 20b.

[0105] For example, when the small window mode is enabled, if the user clicks the Smart Multi-Window option 201-1', the tablet computer will respond to the user's operation, close the small window mode, and the Smart Multi-Window option 201-1' will switch to the style of Smart Multi-Window option 201-1 in interface 20a.

[0106] Therefore, by placing the entry point for enabling and disabling the small window mode in the control center, users can easily access the control center from any user interface through the aforementioned swipe operation, and then enable or disable the small window mode through the smart multi-window option provided in the control center.

[0107] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended as the only limitation on this embodiment.

[0108] Referring to Figures 4 to 6, an exemplary scenario is shown where the pop-up mode is enabled and used. This scenario assumes that the user needs to use more than three tasks simultaneously, such as four tasks.

[0109] It should be noted that the tasks mentioned in this embodiment can be understood as tasks provided by the same application or tasks provided by different applications. For ease of explanation, the following example uses four tasks provided by different applications, such as online course applications, note-taking applications, dictionary applications, and chat applications.

[0110] For example, in this embodiment, APP-1 is an online course application, APP-2 is a note-taking application, APP-3 is a dictionary application, and APP-4 is a chat application. In a scenario where a user needs to use APP-1 to listen to online courses, use APP-2 to take notes, use APP-3 to look up new words, and use APP-4 to reply to chat messages, the user can click on the application icons of APP-1, APP-2, APP-3, and APP-4 in the taskbar 301 (which can be understood as the DOCK bar) of the interface 30a shown in Figure 4 (1), respectively. Accordingly, in response to the click operation on the four application icons, the tablet will launch APP-1 to APP-4 respectively, and display their respective content in the floating windows corresponding to these four applications. For example, the content of APP-1 (such as online course content) will be displayed in floating window 302, the content of APP-2 (such as user-recorded notes) will be displayed in floating window 303, the content of APP-3 (such as the dictionary lookup interface) will be displayed in floating window 304, and the content of APP-4 (such as the chat interface) will be displayed in floating window 305.

[0111] For example, in some implementations, the interface corresponding to the first multitasking scenario can be shown as interface 30b in Figure 4 (2). That is, in small window mode, when the display screen shows the floating window corresponding to any application, the taskbar 301 can be hidden and not displayed.

[0112] For example, in some other implementations, in small window mode, the taskbar 301 can always be displayed regardless of how many floating windows are displayed, as shown in the interface 30n in Figure 7 (2).

[0113] It should be noted that the area divisions of floating windows 302, 303, and 304 are similar, and the functions of the included controls are also similar. For example, controls 303-1 to 303-5 in floating window 303, controls 304-1 to 304-5 in floating window 304, and controls 305-1 to 305-5 in floating window 305 are similar to controls 302-1 to 302-5 in floating window 302. The following embodiments only take floating window 302 as an example to describe controls 302-1 to 302-5 in detail.

[0114] Referring to Figure 4(2), for example, in some implementations, the floating window 302 includes three areas, such as a taskbar at the top, a taskbar at the bottom, and a display area in between (used to display the content of APP-1, such as the online class interface). Among them, the taskbar at the top includes controls 302-1 to 302-4, and the taskbar at the top includes control 302-5.

[0115] For example, in some implementations, when a user clicks control 302-1, the tablet computer responds to the user's action by switching APP-1 from small window mode to full-screen mode, that is, using the entire screen to display the content of APP-1.

[0116] For example, in some implementations, when a user clicks control 302-2, the tablet computer responds to the user's action by shrinking the floating window 302 so that it does not occupy the display area of ​​the screen. In some implementations, when a user clicks control 302-2, the tablet computer responds to the user's action by bringing the floating window 302 from the foreground to the background. In other implementations, when a user clicks control 302-2, the tablet computer responds to the user's action by collapsing the floating window 302 into a floating ball style, displaying it on the side edge of the screen, such as near the right edge of the floating window 302.

[0117] For example, in some implementations, when a user presses and holds control 302-3 (which can be understood as a bar) and moves it on the screen, the tablet computer responds to the user's operation by moving the floating window 302 in the position of the interface 30b.

[0118] For example, in some implementations, when a user clicks control 302-4, the tablet computer will close the floating window 302 in response to the user's action.

[0119] For example, in some implementations, when the user does not interact with control 302-3, no other controls may be displayed in the top taskbar. For example, when the user clicks control 302-3, the tablet computer responds to the user's action and displays multiple controls in the top taskbar. For example, these multiple controls may include a full-screen control, a small window control, a minimize control, and a close control. The minimize control functions the same as control 302-2, and the close control functions the same as control 302-4. Window 302 is currently selected as a small window, the minimize control is displayed as selected, and the full-screen control functions the same as control 302-1. When the user clicks these controls, the tablet computer controls the display effect of window 302 according to the functions of the controls.

[0120] For example, in some implementations, when a user presses and holds control 302-5 (which can be understood as a bar) and moves it on the screen, the tablet computer responds to the user's operation by scaling the floating window 302 proportionally, or switching APP-1 from small window mode to full-screen mode.

[0121] Understandably, the proportional scaling mentioned in this embodiment means that the aspect ratio of the floating window remains unchanged after scaling. As shown in Figures 4 and 5, for example, when a user presses the control 305-5 in Figure 4 (2) to move the floating window 305, the floating window 305 can only be scaled up proportionally from the style shown in Figure 4 (2) to the style of the floating window 305 shown in the interface 30i in Figure 5 (1). When a user presses the control 304-5 to move the floating window 304, the floating window 304 can also only be scaled up proportionally from the style shown in Figure 5 (1) to the style shown in Figure 5 (2).

[0122] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment and is not intended as the sole limitation of this embodiment. In practical applications, the first multi-tasking scenario, which involves multiple tasks performed simultaneously based on the small window mode, can also be a first multi-tasking scenario where multiple shopping apps are opened simultaneously for multi-platform price comparison. That is, APP-1, APP-2, APP-3, APP-4, etc., can be different shopping apps. Alternatively, it can be a first multi-tasking scenario where game apps, game strategy files or videos, and chat apps are opened simultaneously. That is, APP-1, APP-2, APP-3, APP-4, etc., can be game apps, apps for viewing game strategy files or videos, chat apps, etc. Alternatively, it can be a first multi-tasking scenario where video apps, chat apps, shopping apps, etc., are opened simultaneously. That is, APP-1, APP-2, APP-3, APP-4, etc., can be video apps, chat apps, shopping apps, etc.

[0123] Therefore, the small window mode allows users to simultaneously manage multiple tasks and arrange them freely, as shown in Figure 4 above. Users can drag and drop to adjust the position and size of the four tasks on the screen according to their needs. However, split-screen cannot be enabled in small window mode; users must first exit small window mode to enable split-screen and view the multi-tasking combination in the second multi-tasking scenario. As can be seen from the above discussion of the first multi-tasking scenario, in the current small window mode solution, the entry and exit points for entering and exiting the first multi-tasking scenario (i.e., opening and closing small window mode) are relatively deep, the operation is complex, and the user experience is poor.

[0124] In addition, due to the display of multiple windows of different applications, the layout is messy and they block each other (as shown in interface 30b in Figure 4 (2)). Users need to frequently operate to focus on the target task or drag the window in order to see the content of the target task without obstruction.

[0125] Furthermore, since multiple floating windows can only be scaled proportionally, there is a problem in small window mode where they cannot fill the entire screen. As shown in Figure 5 (2), even when floating windows 304 and 305 are maximized, there are still gaps in the display interface. That is, floating windows 304 and 305 do not fill the entire display screen.

[0126] In addition, it should be noted that, for the convenience of users, electronic devices usually support the setting of virtual buttons, that is, the navigation bar 102 shown at the bottom of the display screen as shown in Figures 2 to 5 and in Figure 7 (2). The navigation bar 102 may include a back button 102-1, a home screen button 102-2, and a multitasking management button 102-3.

[0127] For example, in some implementations, when a user clicks the back button 102-1, the tablet computer responds to the user's action and can exit the current interface.

[0128] For example, in some implementations, when a user clicks the home button 102-2, the tablet computer responds to the user's action and can return to the desktop, such as interface 30a.

[0129] For example, in some implementations, when a user clicks the multitasking management key 102-3, the tablet computer responds to the user's action by displaying the multitasking management interface.

[0130] In other words, users can use control 102-2 to switch the content of the application displayed in the foreground directly to the background, and use control 102-3 to find recently used tasks in the multitasking management interface so that tasks can be restored with one click from the multitasking interface.

[0131] However, in some implementations, when the user clicks the home screen button 102-2 to return to the desktop, and then clicks the multitasking management button 102-3 to enter the multitasking management interface, the multitasking management interface will not display the task group (hereinafter referred to as the first task group) that displays more than two floating windows on the screen at the same time in the first multitasking scenario. For example, the first task group with four tasks running at the same time will only display two tasks in a split-screen style, as shown in interface 30k in Figure 6 (1); or multiple tasks will be grouped in pairs and presented in a split-screen style in the multitasking management interface, as shown in interface 30L in Figure 6 (2); or the target task that is finally focused will be displayed in full screen, and the non-focused multitasking will be presented in a split-screen in the multitasking management interface, as shown in interface 30m in Figure 7 (1); or multiple tasks in the current multitasking scenario will be displayed one by one in the multitasking management interface in the form of a single task. This means that users cannot directly select the previous first task group from the multitasking management interface and restore it to the foreground with one click. Instead, they have to click on each task individually to reassemble it into the previous task group in the foreground, which is cumbersome and results in a poor user experience.

[0132] Furthermore, restoring tasks from the multitasking management interface to the foreground in a small window mode can only be achieved when small window mode is enabled. If a task group or split-screen task group saved in the multitasking management interface is used when small window mode is disabled, the task group saved in the multitasking management interface, such as a split-screen task group, will be split into two separate tasks. Therefore, even after re-entering small window mode, it will not be possible to restore the previous floating window display through tasks saved in the multitasking management interface.

[0133] Furthermore, after enabling the small window mode, if the small window mode is not closed in the manner shown in Figure 2 or Figure 3, any application installed on the tablet that supports small window mode will be displayed in small window mode, i.e., in the form of a floating window, as shown in the floating window 302 in interface 30n of Figure 7 (2). However, in actual applications, users may not want it to be displayed in a floating window, but rather in full screen.

[0134] In view of this, the embodiments of this application provide a multi-window display method, which aims to conveniently and quickly open and close the small window mode (i.e., enter and exit the first multi-tasking scenario), and can realize the free layout between multiple windows (multiple floating windows) and one-click continuation of multi-tasking scenarios to meet the user's needs for multi-window display.

[0135] For example, based on the multi-window display method provided in the embodiments of this application, in some implementations, such as in the scenarios shown in Figure 3 (2) or Figure 8 (1), in order to achieve free layout of the windows corresponding to the four tasks APP-1, APP-2, APP-3 and APP-4, a global entry point for entering the free layout scenario of multi-window can be provided.

[0136] For example, in some implementations, users can bring up the global entry point by making specific gestures (such as clicking or swiping) in specific areas of the display screen (such as the left side, right side, top, or bottom of the screen).

[0137] Taking a user sliding their finger from the bottom of the screen inwards as an example, the tablet computer responds to this user action by displaying the global entry point on the interface corresponding to the current multitasking scenario, as shown by control 401-1 displayed in the taskbar 401 of interface 40a in Figure 8 (1). In this way, the user can call up control 401-1 on any interface.

[0138] For example, in some implementations, when a user clicks control 401-1, the tablet computer responds to the user's action by splitting each task of the current job into a floating window, as shown in interface 40b of Figure 8 (2), floating windows 402, 403, 404, and 405. Furthermore, each floating window belongs to an independent layer. That is, content of APP-1 and APP-2, which were originally on the same layer (e.g., layer A), will be displayed in floating windows on different layers, such as floating window 402 on layer D and floating window 403 on layer E.

[0139] Referring again to Figure 8(2), for example, each floating window split in the multi-window free layout scenario includes controls similar to those in floating window 302, 303, 304, or 305. The difference is that when the user long-presses control 402-1, control 403-1, control 404-1, and control 405-1 and drags the corresponding floating window, the floating window is not scaled proportionally, but can be adjusted to any ratio. For example, by long-pressing control 405-1 and dragging floating window 405, the aspect ratio of floating window 405 can be adjusted from "9:16" to "1:1", "16:9", or "2:3", etc. That is, the size of each floating window can be freely adjusted. In this way, users can freely adjust the size of floating windows 402, 403, 404, and 405 by long-pressing controls 402-1, 403-1, 404-1, and 405-1 in interface 40b. For example, they can adjust floating window 402 to the style of floating window 402' in Figure 9, floating window 403 to the style of floating window 403' in Figure 9, floating window 404 to the style of floating window 404' in Figure 9, and floating window 405 to the style of floating window 405' in Figure 9. This allows the floating windows of multiple tasks currently displayed to fill the entire screen, as shown in interface 40c in Figure 9.

[0140] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the sole limitation of this embodiment. In practical applications, based on the multi-window display method provided in this application embodiment, users can enter a multi-window free layout scenario through a global entry point, such as control 401-1. For any multi-tasking scenario, users can freely adjust the size of the floating window corresponding to each task to achieve a full-screen effect where multiple windows do not collapse, thereby enabling users to view and use multiple tasks simultaneously.

[0141] Furthermore, it should be noted that in some implementations, the free adjustment of the size of each floating window can be a free proportional adjustment based on a grid-based adjustment method. In other implementations, it can also be a manual adjustment based on a free proportional adjustment.

[0142] For example, based on the multi-window display method provided in the embodiments of this application, in some implementations, such as entering the multi-window free layout scenario through a global entry point, each task of the current job is split into a floating window, as shown in interface 40b in Figure 8 (2). In order to switch the windows corresponding to the four tasks APP-1, APP-2, APP-3, and APP-4 to the desired layout style with one click, so that these four tasks fill the entire screen, a quick layout window can be provided. Among them, the quick layout window can display various preset multi-window layouts, so that the user can quickly switch the windows of multiple tasks on the current interface to the selected multi-window layout style by selecting the multi-window layout displayed in the quick layout window with one click.

[0143] For example, in some implementations, users can bring up the quick layout entry by making specific gestures (such as clicking or swiping) in specific areas of the display screen (such as the left side, right side, top, or bottom of the screen).

[0144] Taking the case where a user performs a swipe operation from the bottom of the screen towards the inside of the screen while the display interface 40b is on the display screen, the tablet computer responds to the user's operation by displaying the quick layout window in the interface corresponding to the current multitasking scenario, such as the quick layout window 406 displayed in the interface 40d in Figure 10.

[0145] Referring to Figure 10, for example, the quick layout window 406 includes a slider 406-1 and a multi-window layout supported by a tablet computer, such as a multi-window layout 406-2.

[0146] The user-operated slider 406-1 can slide to display the area of ​​the multi-window layout, bringing multi-window layouts that are not currently displayed into the visible area for the user to select. When the user clicks on any multi-window layout displayed in the quick layout window 406, the tablet computer responds to the user's action by quickly switching between the multiple tasks currently displayed on the interface and the selected multi-window layout.

[0147] For example, when a user clicks on the multi-window layout 406-2, the tablet computer responds to the user's action by quickly switching the windows of the four tasks displayed on interface 40d to the layout of interface 40c.

[0148] For example, based on the multi-window display method provided in the embodiments of this application, in some implementations, such as in the scenarios shown in Figure 3 (2) or Figure 8 (1), in order to achieve quick layout of the windows corresponding to the four tasks APP-1, APP-2, APP-3, and APP-4, so that these four tasks fill the entire screen, a global entry point to enter the free layout scenario of the multi-window can be omitted, and a globally accessible quick layout window can be directly provided. For example, if a user performs a sliding operation from the bottom of the screen towards the inside of the screen when the display screen is displaying interface 30c, the tablet computer can display the quick layout window in response to the user's operation, such as the quick layout window 406 displayed in interface 40e in Figure 11. In this way, when the user clicks on any multi-window layout displayed in the quick layout window 406, the tablet computer can quickly switch the multiple tasks displayed on the current interface to the selected multi-window layout in response to the user's operation.

[0149] For example, in some implementations of the multi-window display method provided in this application, a quick layout entry 401-2 can also be displayed in the taskbar 401. When a user clicks the quick layout entry 401-2, the tablet computer responds to the user's operation by displaying a quick layout window 406. That is, when the display screen is currently on interface 40a, after the user clicks the quick layout entry 401-2, the display screen's interface can change from interface 40a to interface 40d. When the user clicks on any multi-window layout displayed in the quick layout window 406, the tablet computer responds to the user's operation by quickly switching the multiple tasks currently displayed on the interface to the selected multi-window layout.

[0150] For example, based on the multi-window display method provided in the embodiments of this application, in some implementations, the area of ​​the multi-window layout displayed in the brought-up quick layout window 406 can be divided into a recommended area (for displaying recommended multi-window layouts selected by the user) and a full multi-window layout display area (for displaying all multi-window layouts supported by the tablet computer), as shown in Figure 12, in area 406-3' (recommended area) and area 406-4' (full multi-window layout display area). In this way, the user can quickly select a satisfactory multi-window layout based on the multi-window layouts displayed in area 406-3'.

[0151] It should be noted that the multi-window layout displayed in region 406-3' can be determined based on one or more factors such as user habits, multiple tasks in the current multitasking scenario, tablet performance, and screen size. This application does not impose specific rules on this determination.

[0152] In addition, it should be noted that in some implementations, when a user selects a multi-window layout that needs to be switched with one click, the tablet computer responds to the user's operation and can fill the screen with the corresponding number of floating windows according to the selected multi-window layout. In any of the floating windows, such as the floating window 402' in the interface 40f shown in Figure 13 (1), the options corresponding to the four tasks currently being performed are displayed, such as the "APP-1", "APP-2", "APP-3" and "APP-4" options displayed in the floating window 402'. In other floating windows, controls for adding other task content can be displayed, such as controls 403-2', controls 404-2', controls 405-2', etc.

[0153] For example, in some implementations, when a user selects the “APP-1” option displayed in the floating window 402', the tablet computer responds to the user's operation by loading the content of APP-1 into the floating window 402' for display, as shown in the floating window 402' in the interface 40g in Figure 13 (2).

[0154] For example, after displaying the content of APP-1 in the floating window 402', in one implementation, the options corresponding to the currently performed task other than APP-1 can be displayed in a floating window to the right of the floating window 402', such as the floating window 403', in a clockwise direction. For example, the "APP-2", "APP-3" and "APP-4" options are displayed in the floating window 403' in the interface 40g.

[0155] For example, in some implementations, when a user selects the "APP-2" option displayed in the floating window 403', the tablet computer responds to the user's operation by loading the content of APP-2 into the floating window 403' for display, as shown in the floating window 403' in the interface 40h of Figure 14.

[0156] For example, in some other implementations, the options corresponding to the currently performing task other than APP-1 can also be displayed in any of the floating windows other than floating window 402'.

[0157] This application takes as an example a floating window that needs to load task content, which is polled in a clockwise direction.

[0158] For example, after displaying the content of APP-2 in the floating window 403', in one implementation, the options corresponding to the currently performing tasks other than APP-1 and APP-2 can be displayed in a floating window to the right of the floating window 403', such as the floating window 404' in the interface 40h, in a clockwise direction.

[0159] For example, in some other implementations, the options corresponding to the two currently running tasks, APP-1 and APP-2, can also be displayed in either of the floating windows other than floating window 402' and floating window 403'.

[0160] This application takes as an example a floating window that needs to load task content, which is polled in a clockwise direction.

[0161] For example, in some implementations, when a user selects the "APP-3" option displayed in the floating window 404', the tablet computer responds to the user's operation by loading the content of APP-3 into the floating window 404' for display. The last task, such as the content of APP-4, will be automatically loaded into the floating window 405' for display, as shown in the interface 40c in Figure 9.

[0162] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment and is not intended to be the sole limitation of this embodiment. In practical applications, when switching between multiple window layouts with one click, the currently focused task can also be automatically loaded into any floating window or the floating window in the upper left corner. Then, in a clockwise or random manner, the options corresponding to the tasks other than the focused task are displayed in one of the remaining floating windows. That is, the current task is loaded into the floating window as shown in Figures 13 and 14 above. Alternatively, multiple currently running tasks can be randomly loaded into their corresponding floating windows. Alternatively, they can be loaded sequentially according to the relationship between the layers of the floating windows displaying different tasks before the switch. Alternatively, they can be loaded sequentially according to the opening order of each task. This application does not impose any limitations on this.

[0163] Furthermore, it should be noted that the multi-window layout displayed in the quick layout window can be a system preset, meaning it's pre-set at the tablet's factory and cannot be modified or deleted. Alternatively, it can be a user-defined layout added during use. This application does not impose any restrictions on this.

[0164] Furthermore, it should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the sole limitation of this embodiment. In practical applications, the multi-window display method provided by this application embodiment, which allows for one-click switching of multi-window layouts through the multi-window layout displayed in the quick layout window 406, is applicable to any multi-tasking scenario.

[0165] For example, based on the multi-window display method provided in the embodiments of this application, in some implementations, users can directly exit the first multi-tasking scenario using the home screen button 102-2 without needing to enter the control center or set the application to close the small window mode separately. Furthermore, after directly exiting the first task group running in the foreground of the first multi-tasking scenario to the background using the home screen button 102-2 and entering the desktop, users can perform normal single-task usage. For example, clicking on an application will directly display the application's content in full screen, instead of displaying it as a floating window.

[0166] For example, after the user directly exits the first task group running in the foreground in the first multitasking scenario to the background and enters the desktop by using the home screen key 102-2, the user clicks the multitasking management key 102-3 to enter the multitasking management interface, as shown in interface 40i in Figure 15 (1). After the user clicks the single task 408, the tablet computer responds to the user's operation and can directly display the content of the task in full screen, as shown in interface 40j in Figure 15 (2).

[0167] For example, based on the multi-window display method provided in the embodiments of this application, in some implementations, after exiting multitasking directly via the home screen key 102-2, the multitasking management interface will directly display the currently exited task group, and will display it in the layout style presented in the foreground before the task group exited. Taking the layout style presented in the foreground of the currently exited task group as shown in interface 40c, i.e., the style of multi-window layout 406-2, as an example, after the user exits multitasking directly via the home screen key 102-2, the multitasking management interface will display the task group 407 shown in Figure 15 (1).

[0168] For example, based on the multi-window display method provided in the embodiments of this application, in some implementations, when the user directly exits the first task group running in the foreground in the first multi-tasking scenario to the background via the home screen key 102-2 and enters the desktop, and the single task used normally is not one of the tasks in task group 407, when the user enters the multi-tasking management interface via the multi-tasking management key 102-3, such as interface 40i, and the user clicks on task group 407, the tablet computer responds to the user's operation and can directly switch task group 407 back to the foreground and display it in the multi-window layout when it exited the foreground.

[0169] For example, based on the multi-window display method provided in the embodiments of this application, in some implementations, after the user directly exits the first task group running in the foreground in the first multi-task scenario to the background and enters the desktop by using the home screen key 102-2, the user clicks the multi-task management key 102-3 to enter the multi-task management interface, as shown in interface 40k in Figure 16(1). After the user clicks the split-screen task group 409, the tablet computer responds to the user's operation and can directly display the content of APP-5 and APP-6 in the split-screen task group in split-screen form, as shown in interface 40L in Figure 16(2). That is, the second multi-task scenario (the multi-task scenario corresponding to the split-screen mode) can be entered without closing the small window mode.

[0170] For example, in some implementations of the multi-window display method provided in the embodiments of this application, after the user switches the split-screen task group 409 to the background, they can also click on the task group 407 in the interface 40k to switch the task group 407 back to the foreground and display it in the multi-window layout when exiting the foreground.

[0171] In other words, based on the multi-window display method provided in this application embodiment, one can exit the first task group with one click and use it normally as a single task or split-screen task group. Alternatively, after using a single task or split-screen task group, one can restore the first task group with one click from the multi-task management interface, thus enabling the continuous use of single tasks and task groups.

[0172] As can be seen from the description of the above embodiments, the multi-window display method provided by the embodiments of this application can conveniently and quickly enter and exit the small window mode, and can realize the free layout between multiple windows and one-click continuation of multi-task scenarios, thereby better meeting the user's needs for multi-window display.

[0173] Furthermore, it should be understood that the above embodiments are illustrated using a tablet computer as an example. However, in practical applications, electronic devices capable of implementing multi-window display based on the multi-window display method provided in this application embodiment can also be mobile phones, desktop computers, laptops, smart TVs, etc.

[0174] For desktop computers, laptops, and smart TVs with larger screens, the supported quick layout is similar to that of tablets. The number of windows that can be displayed depends on the screen size. For example, tablets can support up to 4 windows, meaning that 4 tasks can be used simultaneously. For desktop computers, laptops, and smart TVs with even larger screens, more (more than 4) tasks can be used simultaneously.

[0175] For mobile phones, the supported quick layouts and number of tasks vary depending on the screen size.

[0176] For example, for a regular mobile phone (a mobile phone whose screen cannot be folded and whose screen remains fixed, as shown in Figure 17), or a small folding phone (as shown in Figure 18, where the screen is folded along the Y-axis and the screen is in an unfolded state, as shown in Figure 18(1), the screen size is basically the same as that of a regular mobile phone; and when the screen is in a folded state, as shown in Figure 18(2), the body size is smaller than that of a regular mobile phone), since the screen size is small, the supported split-screen mode can be a two-screen mode, and the supported small window mode can be a single floating window mode. That is, the quick layout window invoked through the above embodiments can be the quick layout window 409 shown in Figure 19.

[0177] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended as the sole limitation of this embodiment. In practical applications, the split-screen layout in the two-screen mode and the small window layout in the single floating window mode displayed in the quick layout window 409 may be more or less than those shown in Figure 19, and this application does not impose any restrictions on this.

[0178] For example, for a large folding phone (as shown in Figure 20, the screen is folded along the X-axis. When the screen is in the unfolded state, as shown in Figure 20 (1), the screen size is larger than that of a regular phone. When the screen is in the folded state, as shown in Figure 20 (2), the body size is basically the same as that of a regular phone), since the screen size is larger in the unfolded state (but smaller than that of a tablet computer), the supported split-screen modes in the small window mode can be two-screen mode and three-screen mode, and the supported small window modes can be single floating window mode and two floating window mode. That is, the quick layout window invoked through the above embodiments can be the quick layout window 410 shown in Figure 21.

[0179] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended as the sole limitation of this embodiment. In practical applications, the split-screen layouts in two-screen mode and three-screen mode, as well as the small window layouts in single floating window mode and two floating window mode displayed in the quick layout window 410, may be more or fewer than those shown in Figure 21, and this application does not impose any restrictions on this.

[0180] For example, for a tri-fold phone (as shown in Figure 22, the screen can fold twice along the X-axis, and the screen size is larger than that of a large folding phone), due to the large screen size (possibly close to that of a tablet computer), the supported quick layout in small window mode is similar to that of a tablet computer. That is, the quick layout window invoked through the above embodiments can be the quick layout window 406 mentioned in the above embodiments.

[0181] In other words, in a single-screen scenario (with limited screen size), a task group in a multi-tasking scenario can include at least one task, such as displaying only a floating window. As screen sizes gradually increase, or with multi-screen collaboration, external displays, or improved performance and ecosystem of electronic devices, the number of tasks that can be included in a task group can be even greater.

[0182] Therefore, by pre-setting different multi-window layouts in different electronic devices, the multi-window display method provided in this application embodiment can be better adapted to different electronic devices and meet users' multi-window usage needs for different electronic devices.

[0183] The hardware structure of the various electronic devices mentioned above can be shown in Figure 23. Referring to Figure 23, the electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170 (including: a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, etc.), a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0184] The processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, a smart sensor hub, etc., which will not be listed here and this application does not limit them.

[0185] For example, in some implementations, the different processing units can be independent devices. That is, each processing unit can be viewed as a processor. In other implementations, the different processing units can be integrated into one or more processors.

[0186] In addition, the processor 110 may also include one or more interfaces. These interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc., which will not be listed here, and this application does not impose any limitations on them.

[0187] In addition, processor 110 may also include memory for storing instructions and data. In some implementations, the memory in processor 110 is a cache memory. This memory can store instructions or data that processor 110 has just used or is recurring. If processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of processor 110, and thus improves system efficiency.

[0188] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to perform data storage.

[0189] The internal memory 121 can be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function, etc. The data storage area may store data created or needed during the use of the electronic device 100 (such as the multi-window layout displayed in the shortcut layout window in the above embodiment). Furthermore, the internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0190] The charging management module 140 receives charging input from the charger. Furthermore, while charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0191] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, and wireless communication module 160. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance).

[0192] The wireless communication function of the electronic device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0193] The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use on the electronic device 100. The wireless communication module 160 can provide wireless communication solutions, including wireless local area networks (WLANs) (such as Wi-Fi), Bluetooth, Global Navigation Satellite System (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies, for use on the electronic device 100.

[0194] The button 190 may include a power button, volume buttons, etc. The button 190 may be a mechanical button or a touch button. The electronic device 100 can receive button input and generate signal inputs related to user settings and function control of the electronic device 100.

[0195] The motor 191 can generate vibration as a notification. The indicator 192 can be an indicator light, used to indicate charging status, battery level changes, or to indicate messages, missed calls, notifications, etc.

[0196] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some implementations, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0197] The sensor module 180 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, etc., which will not be listed here, and this application does not limit them.

[0198] This concludes the introduction to the hardware structure of electronic device 100. It should be understood that electronic device 100 shown in Figure 23 is merely an example. In specific implementations, electronic device 100 may have more or fewer components than shown in the figure, may combine two or more components, or may have different component configurations. The various components shown in Figure 23 can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0199] The software structure of the various electronic devices mentioned above can be shown in Figure 24. Before describing the software structure of electronic device 100, the architecture that the software system of electronic device 100 can adopt will be explained first.

[0200] Specifically, in practical applications, the software system of electronic device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture.

[0201] Furthermore, it is understood that the software systems used by mainstream electronic devices currently include, but are not limited to, Windows, Android, and iOS systems. For ease of explanation, this application embodiment uses the layered architecture of the Android system as an example to illustrate the software structure of the electronic device 100.

[0202] Furthermore, the multi-window display scheme provided in the embodiments of this application is also applicable to other systems in specific implementations.

[0203] Referring to Figure 24, which shows the software architecture of the electronic device 100, the layered architecture divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some implementations, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer (which can be understood as the system service framework), the Android runtime and system libraries (i.e., the native framework and runtime environment, also known as the Native layer), and the kernel layer.

[0204] The application layer can include a series of application packages. The application framework layer provides application programming interfaces (APIs) and programming frameworks for the applications in the application layer. In some implementations, these APIs and frameworks can be described as functions. The native layer provides some native services and commonly used system libraries. The kernel layer is the operating system's kernel layer, which includes various hardware drivers.

[0205] Referring again to Figure 24, for example, in some implementations, the application layer of the electronic device may include application packages such as Settings, APP-1, APP-2, APP-3, and APP-4 as described in the above embodiments.

[0206] Referring again to Figure 24, for example, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, etc., which will not be listed here, and this application does not limit them.

[0207] The window manager is used to manage window applications. It can obtain the screen size, determine if a status bar is present, lock the screen, and capture screenshots, among other things.

[0208] The content provider stores and retrieves data, making this data accessible to applications. This data may include videos, images, audio, phone calls made and received, browsing history and bookmarks, phone books, and various multi-window layouts supported by electronic devices, etc., which will not be listed here, and this application does not impose any limitations on this.

[0209] The view system includes visual controls, such as controls for displaying text and controls for displaying images. The view system can be used to build applications. A display interface can consist of one or more views. For example, a display interface for a floating window containing multiple tasks can include views for displaying text and views for displaying images.

[0210] The telephone manager is used to provide communication functions for the electronic device 100.

[0211] The resource manager provides various resources for the application, such as localized strings, icons, images, layout files (such as multi-window layouts displayed in the quick layout window), video files, etc., which will not be listed here, and this application does not impose any restrictions on them.

[0212] Referring again to Figure 24, for example, the Android Runtime in the Native layer is responsible for the scheduling and management of the Android system, and may include core libraries and virtual machines.

[0213] The core library consists of two parts: one part contains the functionalities that Java calls, and the other part is the Android core library. The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0214] Referring again to Figure 24, for example, the system libraries in the Native layer may include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0215] The Surface Manager manages the display subsystem and provides 2D and 3D layer blending for multiple applications. The Media Library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG. The 3D Graphics Processing Library implements 3D graphics drawing, image rendering, compositing, and layer processing.

[0216] In addition, it should be noted that the 2D graphics engine mentioned above is a 2D drawing engine.

[0217] Referring again to Figure 24, the kernel layer may, for example, include a display driver, a camera driver, a power management driver, a sensor driver, etc. For example, a sensor driver can be used to output detection signals from a sensor (e.g., a touch sensor) to the view system, so that the view system responds to the detection signals and displays the corresponding application interface.

[0218] This concludes the description of the software structure of the electronic device 100. It is understood that the layers and components contained in each layer of the software structure shown in Figure 24 do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer layers than illustrated, and each layer may include more or fewer components; this application does not impose any limitations.

[0219] Furthermore, it should be understood that, in order to achieve the aforementioned functions, the electronic device includes hardware and / or software modules corresponding to the execution of each function. Based on the algorithmic steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in a hardware-driven or software-driven manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0220] Furthermore, it should be noted that in practical application scenarios, the multi-window display methods provided in the above embodiments implemented by electronic devices can also be executed by a chip system included in the electronic device, wherein the chip system may include a processor. The chip system can be coupled to a memory, enabling the chip system to call computer programs stored in the memory during runtime to implement the multi-window display methods executed by the electronic device. The processor in the chip system can be an application processor or a non-application processor.

[0221] In addition, this application embodiment also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the above-mentioned related method steps to implement the multi-window display method in the above embodiment.

[0222] In addition, this application also provides a computer program product that, when run on an electronic device, causes the electronic device to perform the above-mentioned related steps to implement the multi-window display method in the above embodiments.

[0223] In addition, embodiments of this application also provide a chip (which may also be a component or module), which may include one or more processing circuits and one or more transceiver pins; wherein the transceiver pins and the processing circuits communicate with each other through internal connection paths, and the processing circuits execute the above-mentioned related method steps to implement the multi-window display method in the above embodiments, so as to control the receiving pins to receive signals and control the transmitting pins to transmit signals.

[0224] Furthermore, as can be seen from the above description, the electronic devices, computer-readable storage media, computer program products, or chips provided in the embodiments of this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0225] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A multi-window display method, characterized in that, Applied to electronic devices, the method includes: The first interface is displayed, which includes windows corresponding to M tasks. Each window includes a floating window, where M is an integer greater than 2. The first interface is the interface in the first multi-tasking scenario, and each task in the first multi-tasking scenario is displayed in the floating window. In response to the operation of exiting the first interface, the first interface is exited, and the M tasks are switched to run in the background; In response to the operation of entering the multitasking management interface, the multitasking management interface is displayed. The multitasking management interface includes a split-screen task group and a first task group displayed in a first layout style. The split-screen task group includes two tasks displayed in a split-screen format. The first task group includes the M tasks. The first style is the layout style of the window corresponding to the M tasks displayed in the first interface. The two tasks in the split-screen task group and the M tasks in the first task group are different tasks. In response to the operation on the split-screen task group, the multi-task management interface is exited and a third interface is displayed. The third interface is the interface under the second multi-task scenario. The tasks under the second multi-task scenario are displayed in a split-screen format. The third interface displays two tasks in the split-screen task group in a split-screen format. In response to the operation of exiting the third interface, the third interface is exited, and the two tasks in the split-screen task group are switched to run in the background; In response to the operation of entering the multitasking management interface, the multitasking management interface is displayed, the multitasking management interface including the split-screen task group and the first task group displayed in the first layout style; In response to the operation on the first task group, exit the multi-task management interface and display the first interface.

2. The method according to claim 1, characterized in that, After switching the M tasks to run in the background, the method further includes: In response to the operation of opening the first application, a fourth interface is displayed, the fourth interface including a window corresponding to any task provided by the first application, the window being a full-screen window; In response to the operation of exiting the fourth interface, the fourth interface is exited, and the single task provided by the first application is switched to run in the background. In response to the operation of entering the multitasking management interface, the multitasking management interface is displayed; wherein, when the single task provided by the first application is different from the two tasks in the split-screen task group and the M tasks in the first task group, the multitasking management interface includes the split-screen task group, the first task group displayed in the first layout style, and the single task provided by the first application.

3. The method according to claim 2, characterized in that, The method further includes: When the single task provided by the first application is the same as any task in the first task group, the multitasking management interface includes the split-screen task group, the single task provided by the first application, and a second task group displayed in a second layout style. The second task group includes N tasks, which are M-1 tasks in the first task group excluding the single task. The second layout style is the same as the layout style of the window corresponding to the M-1 tasks in the first task group.

4. The method according to claim 3, characterized in that, When the multitasking management interface includes the split-screen task group, the single task provided by the first application, and the second task group displayed in the second layout style, the method further includes: When the multitasking management interface is displayed, in response to the operation on the second task group, the multitasking management interface is exited and the fifth interface is displayed. The fifth interface includes windows corresponding to the M-1 tasks. The layout style of the windows corresponding to the M-1 tasks in the first interface is the same as the layout style of the windows corresponding to the M-1 tasks in the fifth interface.

5. The method according to claim 1, characterized in that, The method further includes: In response to the operation of entering a multi-window free layout scenario, the multi-window free layout entry is displayed on the first interface; In response to the operation on the multi-window free layout entry, multiple windows belonging to the same layer are split into multiple floating windows belonging to different layers; For each of the floating windows, in response to the operation of adjusting the floating window, the aspect ratio of the floating window is adjusted from a first ratio to a second ratio.

6. The method according to claim 5, characterized in that, Adjusting the aspect ratio of the floating window from the first ratio to the second ratio includes: According to the rasterization adjustment method, the aspect ratio of the floating window is adjusted from the first ratio to the second ratio.

7. The method according to claim 5 or 6, characterized in that, The first ratio and the second ratio are different.

8. The method according to claim 5, characterized in that, After splitting multiple windows belonging to the same layer into multiple floating windows belonging to different layers, the method further includes: In response to the operation of quick layout of the windows corresponding to the M tasks, a quick layout window is displayed on the first interface, and the quick layout window includes a variety of layout styles; In response to the selection operation of the layout style suitable for the M tasks in the quick layout window, the layout style of the floating window corresponding to the M tasks is switched to the selected layout style.

9. The method according to claim 1, characterized in that, The method further includes: In response to the operation of quick layout of the windows corresponding to the M tasks, a quick layout window is displayed on the first interface, and the quick layout window includes a variety of layout styles; In response to the selection operation of the layout style suitable for the M tasks in the quick layout window, the multiple windows belonging to the same layer are split into multiple floating windows belonging to different layers, and the layout style of the floating windows corresponding to the M tasks is switched to the selected layout style.

10. The method according to claim 8 or 9, characterized in that, The layout style displayed in the quick layout window is related to the electronic device.

11. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory and the processor being coupled; the memory stores program instructions, which, when executed by the processor, cause the electronic device to perform the following steps: The first interface is displayed, which includes windows corresponding to M tasks. Each window includes a floating window, where M is an integer greater than 2. The first interface is the interface in the first multi-tasking scenario, and each task in the first multi-tasking scenario is displayed in the floating window. In response to the operation of exiting the first interface, the first interface is exited, and the M tasks are switched to run in the background; In response to the operation of entering the multitasking management interface, the multitasking management interface is displayed. The multitasking management interface includes a split-screen task group and a first task group displayed in a first layout style. The split-screen task group includes two tasks displayed in a split-screen format. The first task group includes the M tasks. The first style is the layout style of the window corresponding to the M tasks displayed in the first interface. The two tasks in the split-screen task group and the M tasks in the first task group are different tasks. In response to the operation on the split-screen task group, the multi-task management interface is exited and a third interface is displayed. The third interface is the interface under the second multi-task scenario. The tasks under the second multi-task scenario are displayed in a split-screen format. The third interface displays two tasks in the split-screen task group in a split-screen format. In response to the operation of exiting the third interface, the third interface is exited, and the two tasks in the split-screen task group are switched to run in the background; In response to the operation of entering the multitasking management interface, the multitasking management interface is displayed, the multitasking management interface including the split-screen task group and the first task group displayed in the first layout style; In response to the operation on the first task group, exit the multi-task management interface and display the first interface.

12. The electronic device according to claim 11, characterized in that, When the program instructions are executed by the processor, the electronic device further performs the following steps: After the M tasks are switched to run in the background, in response to the operation of opening the first application, a fourth interface is displayed. The fourth interface includes a window corresponding to any task provided by the first application, and the window is a full-screen window. In response to the operation of exiting the fourth interface, the fourth interface is exited, and the single task provided by the first application is switched to run in the background. In response to the operation of entering the multitasking management interface, the multitasking management interface is displayed; wherein, when the single task provided by the first application is different from the two tasks in the split-screen task group and the M tasks in the first task group, the multitasking management interface includes the split-screen task group, the first task group displayed in the first layout style, and the single task provided by the first application.

13. The electronic device according to claim 12, characterized in that, When the program instructions are executed by the processor, the electronic device further performs the following steps: When the single task provided by the first application is the same as any task in the first task group, the multitasking management interface includes the split-screen task group, the single task provided by the first application, and a second task group displayed in a second layout style. The second task group includes N tasks, which are M-1 tasks in the first task group excluding the single task. The second layout style is the same as the layout style of the window corresponding to the M-1 tasks in the first task group.

14. The electronic device according to claim 13, characterized in that, When the multitasking management interface includes the split-screen task group, the single task provided by the first application, and the second task group displayed in the second layout style, when the program instructions are executed by the processor, the electronic device further performs the following steps: When the multitasking management interface is displayed, in response to the operation on the second task group, the multitasking management interface is exited and the fifth interface is displayed. The fifth interface includes windows corresponding to the M-1 tasks. The layout style of the windows corresponding to the M-1 tasks in the first interface is the same as the layout style of the windows corresponding to the M-1 tasks in the fifth interface.

15. The electronic device according to claim 11, characterized in that, When the program instructions are executed by the processor, the electronic device further performs the following steps: In response to the operation of entering a multi-window free layout scenario, the multi-window free layout entry is displayed on the first interface; In response to the operation on the multi-window free layout entry, multiple windows belonging to the same layer are split into multiple floating windows belonging to different layers; For each of the floating windows, in response to the operation of adjusting the floating window, the aspect ratio of the floating window is adjusted from a first ratio to a second ratio.

16. The electronic device according to claim 15, characterized in that, Adjusting the aspect ratio of the floating window from the first ratio to the second ratio includes: According to the rasterization adjustment method, the aspect ratio of the floating window is adjusted from the first ratio to the second ratio.

17. The electronic device according to claim 15, characterized in that, When the program instructions are executed by the processor, the electronic device further performs the following steps: After splitting multiple windows belonging to the same layer into multiple floating windows belonging to different layers, in response to the operation of quick layout of the windows corresponding to the M tasks, a quick layout window is displayed on the first interface, and the quick layout window includes multiple layout styles. In response to the selection operation of the layout style suitable for the M tasks in the quick layout window, the layout style of the floating window corresponding to the M tasks is switched to the selected layout style.

18. The electronic device according to claim 11, characterized in that, When the program instructions are executed by the processor, the electronic device further performs the following steps: In response to the operation of quick layout of the windows corresponding to the M tasks, a quick layout window is displayed on the first interface, and the quick layout window includes a variety of layout styles; In response to the selection operation of the layout style suitable for the M tasks in the quick layout window, the multiple windows belonging to the same layer are split into multiple floating windows belonging to different layers, and the layout style of the floating windows corresponding to the M tasks is switched to the selected layout style.

19. A computer-readable storage medium, characterized in that, The method includes a computer program that, when run on an electronic device, causes the electronic device to perform the multi-window display method as described in any one of claims 1 to 10.

Images