A display control method, electronic device, and related apparatus

Abstract

The application provides a display control method, an electronic device and related apparatuses. The electronic device has at least two modes, which are a multitask scheduling mode and a non-multitask scheduling mode. In the non-multitask scheduling mode, the electronic device does not display a floating window of an application in response to an operation on an application icon. In the multitask scheduling mode, the electronic device displays the floating window of the application in a multitask scheduling interface in response to a user operation on the application icon. In the multitask mode, the electronic device displays an icon of a task group. In response to a click operation on the task group icon, the electronic device displays an application window according to one or more of a window size, a window position and a window level corresponding to the task group icon. The displayed content meets the user's expectation, thereby improving the user's experience.

Description

Technical Field

[0001] This application relates to the field of electronic technology, and in particular to a display control method, electronic device and related apparatus. Background Technology

[0002] With the continuous development of electronic technology, the processing performance of electronic devices is also constantly improving. Currently, electronic devices can support multitasking, running different applications simultaneously. Different applications correspond to different application windows, and the electronic device can display multiple application windows. If the user wants to display these multiple application windows again during subsequent use, the electronic device needs to respond to and launch each application individually, resulting in complex operations and a poor user experience. Summary of the Invention

[0003] This application provides a display control method, electronic device, and related apparatus. In response to a click operation on a task group icon, the electronic device can display an application window according to one or more of the window size, window position, and window hierarchy corresponding to the task group icon, thereby improving the user experience.

[0004] In a first aspect, embodiments of this application provide a display control method applied to an electronic device, the method including:

[0005] Display a first interface, wherein the first interface includes an icon of a first task group, the first task group includes application windows in a first application group, and the application windows in the first application group have one or more of a first window size, a first window position, and a first window hierarchy, and the first application group includes at least two applications.

[0006] Based on the operation on the icon of the first task group, the hierarchy of the application windows in the first application group is set according to the first window hierarchy;

[0007] A first switching animation is displayed. After the first switching animation is displayed, a second interface is displayed. The second interface includes the application window of the first application group. The application window of the first application group in the second interface includes one or more of the following: the first window size, the first window position, and the first window hierarchy.

[0008] In this embodiment, when the electronic device responds to a click on the icon of a task group, it does not set the application window hierarchy according to the startup order of the applications when launching the corresponding applications. Instead, it sets the application window hierarchy according to the window hierarchy saved when the icon of the task group was created. In this way, after the switching animation is displayed in response to the click on the icon of the task group, the application windows can be displayed in the second interface according to the previously stored window hierarchy, which meets the user's expectations and can improve the user experience.

[0009] In one possible implementation of the first aspect, prior to displaying the first interface, the method further includes:

[0010] The third interface is displayed, wherein the third interface includes a first function icon of a first state, and the electronic device is in a first mode when the third interface is displayed.

[0011] After operating on the first function icon in the first state, the electronic device switches from the first mode to the second mode and displays a fourth interface, wherein the fourth interface includes an icon of at least one application and the first function icon of the second state.

[0012] In response to an operation on the first application in the fourth interface, a fifth interface is displayed, wherein the fifth interface includes a window of the first application, and the display area of ​​the window of the first application is smaller than the display area of ​​the display screen.

[0013] In the above method, the electronic device can provide a function icon. In response to an operation on this function icon, the electronic device can enter another working mode, thereby displaying a fourth interface. Optionally, the working mode of the electronic device when displaying the third interface is different from the working mode when displaying the fourth interface. In this embodiment, different working modes are provided to the user, allowing the user to use the corresponding working mode based on their needs, thus improving the user experience. For example, in the working mode after clicking the first function icon in the first state, if the user clicks an application icon (for example, the icon of a second application), the electronic device can display the application's floating window in response to this operation. It can be seen that in this working mode, the application's floating window can be quickly launched / opened, improving the user's efficiency in using the floating window.

[0014] In one possible implementation of the first aspect, after displaying the fifth interface, the method further includes:

[0015] The sixth interface is displayed, wherein the sixth interface includes the application window in the first application group, the first function icon and the second function icon in the second state, and the application windows in the first application group are displayed in the sixth interface according to one or more of the first window size, the first window position and the first window level.

[0016] After the second function icon is operated, a layout window is displayed in the sixth interface. The layout window includes a first control and a second control. The first control is a control for creating a window layout, and the second control includes a control for creating task group icons.

[0017] After the second control is operated on, the third control is displayed in the first area of ​​the layout window;

[0018] After the third control is operated, the icon of the first task group corresponding to the first application group is displayed in the second area of ​​the layout window.

[0019] For example, the first function icon and the second function icon can be displayed in the taskbar, or in the drop-down notification bar, sidebar, etc. In this embodiment of the application, the display position of the function icon is not specified.

[0020] In the above method, in the multi-task scheduling mode, the electronic device may also provide a function icon. In response to an operation on the function icon, the electronic device may provide one or more layouts and a control (third control) for creating task group icons. For example, when at least one application window is displayed, in response to an operation on the third control, a task group icon may be created, and the window size, window dimensions, and window hierarchy corresponding to the application window may be saved.

[0021] In one possible implementation of the first aspect, the first interface further includes application windows in a second application group, wherein the application windows in the second application group each have one or more of a second window size, a second window position, and a second window hierarchy, the second application group includes at least two applications, the first switching animation includes a startup animation of a first type of application, the first type of application includes applications in the first application group that do not overlap with applications in the second application group, and the method further includes:

[0022] In response to an operation on the icon of the first task group, the first type of application is set to a first type, wherein the first type is used to indicate that the application is set to run in the foreground.

[0023] In one possible implementation of the first aspect, displaying the first switching animation includes:

[0024] The first switching animation is displayed according to the first type, and during the display of the first switching animation, the first type of application is set to run in the foreground.

[0025] In the above method, when the application window of the second application group is displayed, in response to the operation of clicking the icon of the first task group, since there may be applications switching to the foreground and applications switching to the background in this scenario, it is necessary to set the application type to distinguish between applications switching to the foreground and applications switching to the background. Furthermore, the startup animation of the application that needs to switch to the foreground can be displayed according to the set change type.

[0026] In one possible implementation of the first aspect, the method further includes:

[0027] In the process of responding to the operation of the icon of the first task group, if there is a second type of application, the second switching animation is encapsulated in the window container transaction object where the first switching animation is located. The second switching animation includes the exit animation of the second type of application, and the second type of application includes applications in the second application group that do not overlap with applications in the first application group.

[0028] In one possible implementation of the first aspect, the method further includes:

[0029] The second switching animation is displayed simultaneously with the first switching animation, and the second interface is displayed after the first switching animation and the second switching animation are displayed.

[0030] In the above method, when multiple applications are launched in response to the operation of the icon of the first task group, since the application launch time is relatively long compared to the application window exit time, in order to ensure that the foreground and background switching animations are displayed synchronously, the foreground and background switching animations can be encapsulated into the same window container transaction object. This can ensure that the foreground and background switching animations start synchronously, avoid the problem of animation fragmentation and asynchrony, and improve the user experience.

[0031] In one possible implementation of the first aspect, the method further includes:

[0032] In the process of responding to the operation of the icon of the first task group, if a second type of application exists, the second type of application is set to a second type, wherein the second type is used to indicate that the second type of application needs to be set to run in the background.

[0033] In one possible implementation of the first aspect, the method further includes:

[0034] The second switching animation is displayed based on the second type, and during the display of the second switching animation, the second type of application is set to run in the background.

[0035] In the above method, since there may be applications switching to the foreground and applications switching to the background in this scenario, it is necessary to set the application type to distinguish between applications switching to the foreground and applications switching to the background. Furthermore, the startup animation of the application that needs to switch to the background can be displayed according to the set change type.

[0036] In one possible implementation of the first aspect, the method further includes:

[0037] In the presence of a third type of application, the third type of application is set as the first type, wherein the third type of application includes applications in the second application group that overlap with applications in the first application group.

[0038] In one possible implementation of the first aspect, the method further includes:

[0039] When the first transformation animation is displayed, the first transformation animation is displayed based on the first type. During the display of the first transformation animation, the third type of application continues to run in the foreground. The first transformation animation is used to indicate that the display position of at least one application in the third type of application is moved to the first window position and / or the window size of at least one application in the third type of application is scaled to the first window size.

[0040] In the above method, since there may be applications switching to the foreground and applications switching to the background in this scenario, and there may be applications that are already open in the applications that are switched to the foreground and overlap with the applications that are opened later, it is necessary to set the application type to distinguish between applications that are already open in the applications that are switched to the foreground. Furthermore, the window's translation and scaling animation can be displayed according to the set change type.

[0041] In one possible implementation of the first aspect, setting the hierarchy of application windows in the first application group according to the first window hierarchy based on operations on the icons of the first task group includes:

[0042] Based on the operation of the icon of the first task group, it is determined whether there is an end flag in the application window of the first application group, wherein the application window with the end flag is used to indicate that it has been drawn.

[0043] If each application window in the first application group has an end flag, the layer of the application windows in the first application group is set according to the first window layer.

[0044] In the above method, during the process of launching the first group of applications corresponding to the multi-task group icon, since there are many applications launched, there are also many application windows that need to be drawn. In order to improve the response time of the multi-task group icon, it is possible to determine whether there is an end flag in the application windows of the first application group. If there is an end flag in the application window corresponding to each application, it means that all windows have been prepared and there is no need to wait for all application windows to be drawn, thereby shortening the response time and improving the smoothness of use.

[0045] In one possible implementation of the first aspect, displaying a first switching animation, followed by displaying a second interface, includes:

[0046] During the preparation of the first switching animation, when starting the application in the first application group, the transaction start parameters and transaction end parameters corresponding to the application are saved respectively, and the view of the application is not created.

[0047] After displaying the first switching animation, and after confirming that the application windows in the first application group have been drawn, a view of the application in the first application group is created according to the transaction start parameters and transaction end parameters corresponding to the application, and the second interface is displayed.

[0048] For example, during the preparation of the first switching animation, when launching an application in the first application group, the transaction start parameters and transaction end parameters corresponding to each application are saved, and the view corresponding to the decorative layer in the application window of the application is not created.

[0049] In the above method, during the application window startup process, the view corresponding to the decorative layer in the application window is not created. Instead, the transaction start parameters and transaction end parameters are saved. After the animation ends, the view corresponding to the application window is created based on the transaction start parameters and transaction end parameters. That is, the decoration view corresponding to the decorative layer in the application window is created. In this way, the entire application window can be created and displayed, thereby shortening the time interval between clicking to display the application window and the animation starting, providing users with a smooth and fast response experience.

[0050] Secondly, an electronic device is provided in the embodiments of this application, the electronic device comprising: one or more processors; a memory; wherein the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code including computer instructions, and the one or more processors call the computer instructions to cause the electronic device to execute the display control method described in the first aspect or any possible implementation of the first aspect.

[0051] Thirdly, this application provides a chip or chip system including at least one processor and a communication interface. The communication interface and the at least one processor are interconnected via a circuit. The at least one processor is used to run computer programs or instructions to execute the display control method described in the first aspect or any possible implementation thereof. The communication interface in the chip can be an input / output interface, pins, or circuits, etc.

[0052] In one possible implementation, the chip or chip system described above in the embodiments of this application further includes at least one memory, in which instructions are stored. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).

[0053] Fourthly, embodiments of this application provide a computer storage medium storing a computer program that, when executed by a processor, causes the computer to perform the display control method as described in the first aspect or any possible implementation thereof.

[0054] Fifthly, embodiments of this application provide a computer program product that, when run on a communication device, causes the communication device to execute the display control method as described in the first aspect or any possible implementation thereof.

[0055] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single embodiment. Rather, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution, or beneficial effect is included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions, and beneficial effects described in this embodiment can be combined in any suitable manner. Those skilled in the art will understand that embodiments can be implemented without one or more specific technical features, technical solutions, or beneficial effects of a particular embodiment. In other embodiments, additional technical features and beneficial effects may be identified in specific embodiments that do not embody all embodiments. Attached Figure Description

[0056] The accompanying drawings used in the embodiments of this application are described below.

[0057] Figures 1A to 1H This is a schematic diagram of the interface of an electronic device switching from a non-multi-task scheduling mode to a multi-task scheduling mode, provided in an embodiment of this application.

[0058] Figure 2 A schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application is shown;

[0059] Figure 3 An exemplary schematic diagram of the software architecture of an electronic device 100 is shown;

[0060] Figure 4A and Figure 4B A timing interaction diagram of a display control method provided in an embodiment of this application is shown;

[0061] Figure 5 This is a schematic diagram illustrating an application window being ready, provided in an embodiment of this application.

[0062] Figure 6 This is a flowchart illustrating a display control method provided in an embodiment of this application. Detailed Implementation

[0063] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to and includes any or all possible combinations of one or more of the listed items.

[0064] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0065] The term "user interface (UI)" used in the specification, claims, and drawings of this application refers to the medium through which an application or operating system interacts and exchanges information with a user. It converts the internal form of information into a form acceptable to the user. The user interface is also called an interface. An application's user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). This source code is parsed and rendered on the terminal device, ultimately presenting user-recognizable content such as images, text, and buttons. Controls, also called widgets, are the basic elements of the user interface. Typical controls include toolbars, menu bars, text boxes, buttons, scroll bars, images, and text. The attributes and content of controls in the interface are defined through tags or nodes, such as in XML. <textview> 、 <imgview> 、 <videoview>Nodes define the controls contained in the interface. A node corresponds to a control or property in the interface, and after parsing and rendering, the node is presented as the content visible to the user. In addition, many applications, such as hybrid applications, often contain web pages within their interfaces. A web page, also known as a page, can be understood as a special control embedded in the application interface. Web pages are source code written in a specific computer language, such as Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), JavaScript (JS), etc. Web page source code can be loaded and displayed as user-readable content by a browser or a web page display component with browser-like functionality. The specific content contained in a web page is also defined through tags or nodes in the web page source code; for example, HTML uses tags or nodes to define the content. 、 、 <video> 、 <canvas>To define the elements and attributes of a webpage.

[0066] The most common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an icon, window, control, or other interface element displayed on the screen of an electronic device. Controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0067] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0068] 1. Touch events

[0069] For example, when an object touches the display screen, the electronic device receives the touch operation and generates a touch event in response. Optionally, the electronic device can receive the touch operation via a touchscreen. Here, the touch object refers to the object performing the operation on the display screen, such as a finger. The touchscreen can be a display screen capable of detecting touch operations. In the following embodiments, a display screen is mainly used as an example. It is understood that in the following embodiments, the display screen can be considered as a touchscreen capable of detecting touch operations.

[0070] Alternatively, a touch event can also be referred to as a touch control event, and a touch operation can also be referred to as a touch control operation.

[0071] For example, a touch event includes at least one of a down event, a move event, and an up event. The touch event includes a touch event type and touch coordinates. The touch coordinates include the coordinates of the touch operation applied to the contact point on the display screen and the timestamp of the timestamp.

[0072] The touch operations in this application include at least one of the following: single-click operation, double-click operation, long-press operation, single-finger long-press operation, multi-finger long-press operation, single-finger swipe operation, multi-finger swipe operation, and knuckle swipe operation. In one embodiment, the electronic device generates a touch event in response to a touch operation applied to a first position. The first position can be located on the display screen (also called the screen) of the electronic device, such as the location of icons or other controls, or the edge of the display screen, or the first position can be located on the side, back, or other positions of the electronic device. The first position can be a preset position of the electronic device, or the first position can be a position determined by the electronic device in response to a user operation. Optionally, the swipe-type touch operation can be simply referred to as a swipe operation. Swipe operations include, but are not limited to, left-right swipe operations, up-down swipe operations, and swipes towards a preset position. This application does not limit the trajectory of the swipe operation.

[0073] 2. Press event

[0074] For example, when the object being operated on changes from a non-touchscreen display to a touchscreen display, the electronic device generates a press event in response to the touch operation. Exemplarily, the press event includes a touch event type "down" and a first touch coordinate, which includes the coordinates corresponding to the touch operation performed on the display screen when the object changes from a non-touchscreen display to a touchscreen display, and a timestamp indicating when the press event acquired those coordinates.

[0075] 3. Applications running in the foreground and applications running in the background

[0076] An application running in the foreground can be an application visible on the user interface. For example, if an electronic device displays the user interface of an application, that application can be considered to be running in the foreground. Optionally, a user can interact with the electronic device through the interface of an application running in the foreground.

[0077] An application running in the background can be an application that runs without displaying a user interface. For example, if an electronic device responds to a user action by making the application interface of application D invisible, then application D can be considered an application running in the background. Optionally, the user cannot interact with the electronic device through the interface of an application running in the background.

[0078] 4. First and Second Modes of Electronic Devices

[0079] The operating modes of electronic devices include, but are not limited to, a first mode and a second mode. Optionally, the first mode may be a non-multitasking mode, and the second mode may be a multitasking mode. For example, the multitasking mode may be referred to as a free-screen mode or a multi-window mode, and the non-multitasking mode may be referred to as a non-free-screen mode or a normal mode. For a description of "non-multitasking mode" and "multitasking mode," please refer to the following... Figures 1A to 1H .

[0080] Please see Figures 1A to 1H , Figures 1A to 1H This is a schematic diagram of the interface of an electronic device switching from a non-multitasking scheduling mode to a multitasking scheduling mode, provided in an embodiment of this application.

[0081] Figure 1A An example is shown of the user interface 200 of the electronic device 100 in a non-multitasking scheduling mode, such as... Figure 1A As shown, the user interface 200 includes, but is not limited to: a first interface 230, a status bar 211, and a first taskbar 231. The first interface 230 includes, but is not limited to: a desktop background, a search box 221, multiple application icons, folders, etc. In this embodiment, the first interface 230 can be the system main interface in a non-multitasking scheduling mode, and the main interface can be referred to as the desktop. In this embodiment, the desktop background can also be referred to as desktop wallpaper, wallpaper, screen pattern, background image, etc.

[0082] The status bar 211 may include a wireless fidelity (Wi-Fi) signal strength indicator, a battery status indicator, a time indicator, etc. In some scenarios, the status bar 211 may also include one or more signal strength indicators for mobile communication signals (also known as cellular signals). Figure 1A (Not shown).

[0083] Search box 221 can be used to provide the ability to search for applications across multiple pages hosting multiple applications. In some scenarios, search box 221 can be replaced by a page indicator, which can be used to indicate which page among multiple pages hosting multiple applications the user is currently viewing. Users can browse other pages using left and right swipe touch gestures.

[0084] For example, the first taskbar 231 includes, but is not limited to, multiple application icons and / or folder shortcuts, providing users with access to these applications and files. Optionally, the application icons displayed by the electronic device 100 in the first taskbar 231 may be icons of applications that have been launched more than or equal to a preset number of times. Applications that have been launched more than or equal to a preset number of times may be referred to as frequently used applications. Optionally, the taskbar may also be referred to as the Dock.

[0085] In one implementation, the electronic device 100 may display a first taskbar 231 at the bottom of the display screen. In another implementation, the electronic device 100 displays the first taskbar 231 at the bottom of the screen in response to a user's swipe-up operation from the bottom area of ​​the display screen. Optionally, the electronic device 100 may also display the first taskbar 231 on the side of the display screen. This application does not impose any restrictions on the display position of the first taskbar 231.

[0086] For example, such as Figure 1A As shown, the first taskbar 231 may include a first sub-bar 2311 and a second sub-bar 2312. Optionally, when the electronic device 100 is facing the user, from the user's perspective, the electronic device 100 may display the first sub-bar 2311 and the second sub-bar 2312 in a side-by-side manner from left to right. Optionally, the horizontal length of the first sub-bar 2311 is greater than the horizontal length of the second sub-bar 2312.

[0087] In one implementation, the first sub-column 2311 includes application icons that are not displayed on the page (such as the main interface or other pages), such as the multitasking icon 231A in the first state, video application icons, music application icons, reading application icons, browser application icons, camera application icons, gallery application icons, etc. The second sub-column 2312 includes application icons that are displayed on the page (such as the main interface or other pages), such as settings application icons, note-taking application icons, alarm clock application icons 231B, etc.

[0088] Optionally, the electronic device 100 may delete the application icon displayed in the first taskbar 231 in response to a delete operation. Optionally, the electronic device 100 may replace the application icon displayed in the first taskbar 231 in response to a replace operation. Optionally, the electronic device 100 may add an application icon to the first taskbar in response to an add operation. For example, the horizontal length of the first taskbar 231 is less than or equal to the horizontal length of the display screen, and as the number of application icons displayed in the first taskbar 231 increases, the horizontal length of the first taskbar 231 may gradually increase until it occupies the length of the display screen.

[0089] For example, the first interface 230 may also include multiple application icons (e.g., a memo application icon, a file application icon, a note application icon, a settings application icon, etc.). The first interface 230 may also include cards (e.g., a weather application card, a date application card, a combined application card, etc.). These cards may display partial functional information of a specified application, which can be used to trigger the electronic device 100 to display a specified page of the specified application. Cards may be displayed on the desktop or other specified shortcut interfaces (e.g., the negative one screen, the service center, etc.), and cards can be added or deleted by the user. Some cards may be referred to as widgets.

[0090] For example, Figure 1A The user interface 200 shown includes at least one application icon, such as the application icon included in the first interface 230 and / or the application icon included in the first taskbar 231. Optionally, in the user interface 200, at least one application icon includes at least one first-class icon and at least one second-class icon. Optionally, the application icon displayed on the system main interface (e.g., the first interface 230) may be referred to as the first-class icon. Optionally, the application icon displayed on the taskbar (e.g., the first interface 230) may be referred to as the second-class icon. Figure 1A The application icons in the first taskbar (231) shown are called second-class icons. Alternatively, the application icons displayed in the taskbar in the user interface 200 are called second-class icons, and the application icons displayed outside the taskbar in the user interface 200 are called first-class icons.

[0091] For example, such as Figure 1A As shown, the note-taking application icons include a first type of icon and a second type of icon. For example, the note-taking application displayed on the first interface 230 can be referred to as a first type of icon, and the note-taking application displayed on the first taskbar 231 can be referred to as a second type of icon. It should be noted that the types of first type and second type icons include, but are not limited to, application icons, folders, application cards, etc.

[0092] For example, Figure 1A The multitasking icon 231A in the first taskbar 231, which is the first state shown, provides an entry point to the multitasking mode.

[0093] In one possible implementation, the electronic device 100 receives an action on Figure 1A A click operation on the multitasking scheduling icon 231A in the first state of the first taskbar 231 in the user interface 200 shown triggers the following response: Figure 1B The user interface 300 shown.

[0094] like Figure 1B As shown, the user interface 300 includes, but is not limited to, a desktop background and a multitasking animation 310, which indicates that the electronic device 100 is starting / entering a multitasking mode. For example, the multitasking animation 310 is displayed above the desktop background. Optionally, the style and shape of the multitasking animation 310 are similar to... Figure 1A The multitasking scheduling icon 231A shown has the same shape but different size, and the multitasking scheduling animation 310 can have a gradient effect. Optionally, it can be played on electronic device 100. Figure 1B After the multi-task scheduling animation 310 shown ends, it can be displayed Figure 1C The user interface 301 shown.

[0095] like Figure 1C As shown, the user interface 301 is the interface in multi-tasking mode. The user interface 301 includes, but is not limited to, a second interface 311, a second taskbar 232, and a status bar 211. For example, the second interface 311 includes, but is not limited to, a desktop background, multiple application icons, and a pop-up notification 222, which includes the message: "Entered multi-tasking mode." Optionally, the second interface 311 can be the system's main interface in multi-tasking mode, and the display area of ​​the second interface 311 includes the area of ​​the display screen excluding the status bar 211 and the second taskbar 232.

[0096] For example, combined Figure 1A and Figure 1C As can be seen, the system's main interface in multi-task scheduling mode (for example) Figure 1C The second interface 311 shown includes one or more of the application icons, folders, and application cards that are similar in number and display format to the system main interface in non-multitasking mode (e.g., Figure 1A The first interface 230 shown is consistent with this. Optionally, Figure 1A The search box 221 shown in the non-multitasking scheduling mode can be replaced with Figure 1C The prompt pop-up window 222 is shown. Optionally, in multi-tasking mode, after a preset time, the electronic device 100 can display the prompt pop-up window 222 and then change it to display a search box. Figure 1C (Not shown).

[0097] For example, Figure 1C The second taskbar 232 in the multi-task scheduling mode shown is compared to Figure 1A In the first taskbar 231 of the non-multitasking scheduling mode shown, the number of application icons and the display style of the multitasking scheduling icon 231A have changed. For example, from... Figure 1C As can be seen, the second taskbar 232 in the user interface 301 includes a first sub-bar 2321 and a second sub-bar 2322. For example, in multi-task scheduling mode, Figure 1C The first sub-column 2321 shown includes a multitasking schedule icon 231A (second state), a quick layout icon 231C, a video application icon, a music application icon, a reading application icon, a browser application icon, a camera application icon, a gallery application icon, etc. Optionally, in non-multitasking schedule mode, the multitasking schedule icon 231A (first state) is displayed in the first style; in multitasking schedule mode, the multitasking schedule icon 231A (second state) is displayed in the second style. Optionally, the first style and the second style are different in color; for example, the first style is light and the second style is dark. Optionally, the quick layout icon 231C is a newly added function icon displayed in multitasking schedule mode. For example, Figure 1C The second sub-column 2322 shown includes settings application icon, note application icon, alarm clock application icon 231B, folder 231D, etc. Optionally, folder 231D is a newly added folder in multi-task scheduling mode. For example, folder 231D includes multiple application icons. Optionally, electronic device 100 can display 9 application icons in folder 231D. Optionally, the multiple application icons included in folder 231D belong to the application icons displayed in the second interface 311, such as first-type icons and / or second-type icons.

[0098] Optionally, in this embodiment of the application, function icons (such as multi-task scheduling icon 231A and / or quick layout icon 231c) may be displayed in areas such as drop-down notification bars and sidebars.

[0099] In one implementation, in multi-task scheduling mode, electronic device 100 responds to clicking the multi-task scheduling icon 231A in the second state, and can display... Figure 1A The user interface 200 shown.

[0100] In one implementation, the electronic device 100, in response to a click on the folder 231D, can display the application window of the folder 231D. Figure 1C (Not shown). For example, the application window includes multiple application icons and a page indicator. The multiple application icons can be displayed in a paginated manner within the application window, and are not necessarily fully displayed on a single page of the application window. For example, the page indicator can be used to indicate which of the multiple pages currently being viewed is the one containing the multiple applications. Optionally, the electronic device 100 can switch from displaying the current page to displaying another page in response to a swipe operation performed on the application window.

[0101] In one possible implementation, in a multi-task scheduling mode, the electronic device 100 responds to an application icon (e.g., Figure 1C Clicking the application icon displayed in the second interface 311, the application icon displayed in the second taskbar 232, or the application icon displayed in the application window of folder 231D will display a floating window of that application. For example, displaying Figure 1D At least one of the floating window 3121 of the Contacts app, the floating window 3122 of the Notes app, and the floating window 3123 of the Alarm Clock app shown.

[0102] In one possible implementation, in a multi-task scheduling mode, the electronic device 100 responds to an application icon (e.g., Figure 1C The application icon displayed in the second interface 311, the second taskbar 232, or the application icon displayed in the application window of folder 231D, after a long press and move operation, displays the drag window of the application at the moved location. In response to a lift-up gesture, the electronic device 100 can display a floating window of the application. For example, displaying... Figure 1D At least one of the floating window 3121 of the Contacts app, the floating window 3122 of the Notes app, and the floating window 3123 of the Alarm Clock app shown.

[0103] For example, please see Figure 1D , Figure 1D The user interface 302 shown includes, but is not limited to: a multitasking interface 312, a second taskbar 232, and a status bar. Optionally, the multitasking interface 312 includes, but is not limited to: a floating window 3121 for the Contacts application, a floating window 3122 for the Notes application, a floating window 3123 for the Alarm Clock application, and a desktop background, excluding the first type of icons. Optionally, the floating windows 3121, 3122, and 3123 of the Contacts application are displayed floatingly on the desktop background. Optionally, the floating windows 3121, 3122, and 3123 of the Contacts application, Notes application, and Alarm Clock application each have their own corresponding size, display position, and display hierarchy. Figure 1D As can be seen, when the electronic device 100 is facing the user, from the user's perspective, the floating windows 3121 of the Contacts application, 3122 of the Notes application, and 3123 of the Alarm Clock application are displayed on the screen of the electronic device 100 from left to right. Optionally, for Figure 1D Regarding the floating windows in the user interface 302 shown, the floating window 3121 of the Contacts application has the highest layer, the floating window 3122 of the Notes application has the second highest layer, and the floating window 3123 of the Alarm Clock application has the lowest layer. In one implementation, a higher-layer window will cover a lower-layer window. When the floating window 3122 of the Notes application and the floating window 3123 of the Alarm Clock application overlap, the floating window 3122 of the Notes application is covered above the floating window 3123 of the Alarm Clock application; when the floating window 3121 of the Contacts application and the floating window 3122 of the Notes application overlap, the floating window 3121 of the Contacts application is covered above the floating window 3122 of the Notes application.

[0104] For example, the floating window 3122 of a note-taking application is used as an example to illustrate the controls of the floating window, such as... Figure 1D As shown, the floating window 3122 of the note-taking application includes one or more of the following: a full-screen display control 3122A, a minimize control 3122B, a top bar 3122C, and a close control 3122D. Optionally, in response to a user operation on the full-screen display control 3122A, the electronic device 100 can display the full-screen display interface corresponding to the alarm clock application. Optionally, in response to a user operation on the minimize control 3122B, the electronic device 100 can shrink the floating window 3122 of the note-taking application to an invisible size or shrink it to a floating ball. Optionally, in response to a user operation on the top bar 3122C, the electronic device can move the display position of the floating window 3122 of the note-taking application and / or adjust the size of the floating window 3122 of the note-taking application. In response to a user operation on the close control 3122D, the electronic device 100 can close the floating window 3122 of the note-taking application.

[0105] For example, in a multi-task scheduling mode, the electronic device 100 can provide an entry point for a quick management / layout floating window, such as... Figure 1D The shortcut layout icon 231C shown is used to provide an entry point for quick management / layout floating windows.

[0106] In one possible implementation, the electronic device 100 can display a shortcut layout icon 231C in response to a click operation on the shortcut layout icon 231C in the second taskbar 232. Figure 1E The user interface 303 shown.

[0107] like Figure 1E As shown, the user interface 303 includes, but is not limited to: a multitasking interface 312, a second taskbar 232, a quick layout window 410 corresponding to the quick layout icon 231C, a status bar, and a desktop background. Optionally, the multitasking interface 312 includes, but is not limited to: a floating window 3121 for the contacts application, a floating window 3122 for the notes application, a floating window 3123 for the alarm clock application, and a desktop background.

[0108] For example, from Figure 1E As can be seen, the quick layout window 410 includes a first control 411 and a second control 412. The first control 411 is a control for creating a task area (such as a floating window) layout, and the second control 412 includes a control for creating task group icons. For example, the floating window layout can be used to provide a display layout of at least two floating windows in a multi-tasking scheduling mode, and the multi-tasking group icons can be used in a multi-tasking scheduling mode to indicate the number of application windows displayed in the interface and the relationship between the display positions of the application windows.

[0109] In one implementation, the electronic device 100 displays one or more floating window layouts under the first control 411 in the first area 4101 of the quick layout window 410, such as a two-window layout, a three-window layout, and a four-window layout, etc. In one implementation, the two-window layout includes a left-right layout 411A and a top-bottom layout; the three-window layout includes a left-center-right layout 411B, a left-side and right-top-right-bottom layout 411C, and a left-top-left-bottom-right layout 411D; the four-window layout includes a left-top-right-top and left-bottom-right-bottom layout 411F, a four-window layout from left to right 411E, and a four-window layout from top to bottom. For example, in response to an operation acting on any layout in the first area 4101, the electronic device 100 can display at least two of the floating windows from the Contacts application's floating window 3121, the Notes application's floating window 3122, and the Alarm Clock application's floating window 3123 in the display interface corresponding to that layout.

[0110] In one implementation, the electronic device 100 responds to a click operation on the second control 412 by displaying, as shown below. Figure 1F The shortcut layout window 410 is shown. From Figure 1F As can be seen, the first area 4101 of the quick layout window 410 includes, but is not limited to, the creation control 413 under the second control 412. Optionally, the creation control 413 is used to create the multitasking group icon corresponding to the floating window. Optionally, if a multitasking group icon has already been created, the electronic device 100 can... Figure 1F At least one multitasking group icon is displayed under the second control 412 in the first area 4101 shown.

[0111] like Figure 1F As shown, the multitasking group icons under the second control 412 include, but are not limited to: first task group icon 412A, second task group icon 412B and third task group icon 412C.

[0112] Optionally, the first task group icon 412A is used to indicate the floating windows of the note-taking application and the calculator application displayed in the multi-task scheduling interface, and the display positions of the floating windows of the note-taking application and the calculator application in the interface. For example, if the electronic device 100 is facing the user, from the user's perspective, the first task group icon 412A is used to indicate that the floating window of the note-taking application is displayed on the left side of the display screen of the electronic device 100, and the floating window of the calculator application is displayed on the right side of the display screen.

[0113] Optionally, the second task group icon 412B is used to indicate the window of the gallery application, the window of the note-taking application, and the window of the calculator application displayed in the multi-task scheduling interface, as well as the positional relationship of the window of the gallery application, the window of the note-taking application, and the window of the calculator application in the interface. For example, if the electronic device 100 is facing the user, from the user's perspective, the second task group icon 412B is used to indicate that the floating window of the gallery application is displayed on the left side of the display screen of the electronic device 100, the floating windows of the note-taking application and the floating windows of the calculator application are displayed on the right side of the display screen of the electronic device 100, and the floating window of the note-taking application is displayed on the upper right side of the display screen, and the floating window of the calculator application is displayed on the lower right side of the display screen.

[0114] Optionally, the third task group icon 412C is used to indicate the display positions of the windows of the note-taking application, the gallery application, the calculator application, and the browser application in the multi-task scheduling interface, as well as their positional relationship within the interface. For example, if the electronic device 100 is facing the user, from the user's perspective, the third task group icon 412C indicates that the floating windows of the note-taking application and the calculator application are displayed on the left side of the screen of the electronic device 100, with the floating window of the note-taking application displayed on the upper left side of the screen and the floating window of the calculator application displayed on the lower left side of the screen; the floating windows of the gallery application and the browser application are displayed on the right side of the screen of the electronic device 100, with the floating window of the gallery application displayed on the upper right side of the screen and the floating window of the browser application displayed on the lower right side of the screen.

[0115] In one implementation, when displaying the floating window 3121 of the Contacts application, the floating window 3122 of the Notes application, and the floating window 3123 of the Alarm Clock application, the electronic device 100, in response to a click operation on the creation control 413, can save the size, display position, and display layer of the floating window 3121 of the Contacts application, the floating window 3122 of the Notes application, and the floating window 3123 of the Alarm Clock application, respectively. It can also create task group icons 412D corresponding to the aforementioned multiple floating windows, and... Figure 1G The task group icon 412D is displayed under the second control 412 in the shortcut layout 410 shown. Figure 1G As shown, the task group icon 412D is used to indicate the display position of the floating window 3121 of the Contacts application, the floating window 3122 of the Notes application, and the floating window 3123 of the Alarm Clock application in the multitasking scheduling interface. The positional relationship of these floating windows in the interface is as follows: if the electronic device 100 is facing the user, from the user's perspective, the floating window 3121 of the Contacts application, the floating window 3122 of the Notes application, and the floating window 3123 of the Alarm Clock application are displayed on the screen in order from left to right.

[0116] For example, such as Figure 1G As shown, when the electronic device 100 is facing the user, the creation control 413 and at least one task group icon can be displayed in a row-by-row manner in the first area 4101 of the shortcut layout window 410. Optionally, the creation control 413 can be fixedly displayed in the first row of the first area 4101. Optionally, as a newly created task group icon is displayed in the first area 4101, the display position of the already created task group icon can be moved. For example, if a new task group icon is created, the electronic device 100 can move one task group icon to the right. If there is not enough display space in the row, one task group icon can be moved to the next row. Optionally, the task group icon whose creation time is closest to the current time can be displayed at the position closest to the creation control 413 in terms of horizontal distance. For example, when the electronic device 100 is facing the user, this task group icon can be displayed to the right of the creation control 413; the task group icon whose creation time is farthest from the current time can be displayed at the position farthest from the creation control 413 in terms of horizontal distance.

[0117] Optionally, the second control 412 in the first area 4101 includes multiple task group icons and a page indicator. The multiple task group icons can be displayed in a paginated manner in the first area 4101, and are not necessarily fully displayed on a single page in the first area 4101. For example, the page indicator can be used to indicate which page is currently being viewed and which contains multiple pages. Optionally, the electronic device 100 can switch from displaying the current page to displaying another page in response to a swipe operation in the first area 4101.

[0118] In one possible implementation, if there is an uninstalled application among the applications corresponding to the task group icon, the task group icon can be deleted.

[0119] In one possible implementation, if one or more of the size, display position, and display level of the application window corresponding to the task group icon in the first area 4101 changes, the electronic device 100 can save the existing task group icon again. For example, if task group icon 1 in the first area 4101 corresponds to the size 1, display position 1, and display level 1 of the floating window of the first application, and the size 2, display position 2, and display level 2 of the floating window of the second application, and if the electronic device 100 displays the size 3, display position 3, and display level 3 of the floating window of the first application, and the size 4, display position 4, and display level 4 of the floating window of the second application in the current display interface, the electronic device 100 can create task group icons 2 corresponding to the first application and the second application in the first area 4101 in response to a click operation on the creation control in the first area 4101. For example, the applications corresponding to task group icon 2 and task group icon 1 respectively include a first application and a second application. However, the size, display position and display level of the floating window of the first application corresponding to task group icon 2 and task group icon 1 are different, and / or the size, display position and display level of the floating window of the second application corresponding to task group icon 2 and task group icon 1 are different.

[0120] In one possible implementation, in response to a click on a task group icon, the electronic device 100 can display a foreground animation, and then display the floating windows of each application in the multitasking interface according to the size, display position, and display level of the floating window corresponding to the task group icon. Optionally, during the process of launching each application and displaying the floating windows of each application, if the electronic device 100 does not have any application overlapping with the newly launched application in the currently displayed applications, it needs to set the non-overlapping applications to run in the background. During the process of setting the non-overlapping applications to run in the background, the electronic device 100 can display a background switching animation. If the electronic device 100 has an application overlapping with the newly launched application in the currently displayed applications, it can continue to run the overlapping application in the foreground. During the process of continuing to run the overlapping application in the background, if the current display position of the application's floating window is different from the pre-saved display position, the electronic device 100 can pan and scale the application's floating window to the pre-saved display position.

[0121] For example, electronic device 100 responds to... Figure 1G The click operation of task group icon 412C shown refers to the following applications: note-taking application, photo album application, calculator application, and browser application, which are displayed on the current screen. Figure 1G If the user interface 303 shown contains applications that overlap with the application corresponding to the task group icon 412C (such as a note-taking application) and applications that do not overlap (such as a contacts application and an alarm clock application), then the electronic device 100 will set the contacts application and the alarm clock application to run in the background and display the corresponding background switching animation. Figure 1G (Not shown), it also displays the foreground animations of the photo album app, calculator app, and browser app, and then displays the photo album app, calculator app, and browser app in the form of floating windows according to the pre-stored size, display position, and display layer. It also uses panning and scaling according to the size, display position, and display layer corresponding to the task group icon 412C. Figure 1G (Not shown) The note-taking application is displayed; the final display is... Figure 1H The user interface 304 is shown. Figure 1H As shown, the user interface 304 includes, but is not limited to: a multitasking interface 314, a second taskbar 232, a status bar, and a desktop background. For example, the multitasking interface 314 includes, but is not limited to: a floating window 3141 for a note-taking application, a floating window 3142 for a photo album application, a floating window 3143 for a calculator application, and a floating window 3144 for a browser application.

[0122] However, this application found the following problem in the research: In scenarios where the electronic device 100 displays multiple application windows in response to a click on a task group icon, the following issues exist:

[0123] (1) When the current display interface includes application floating windows, if the number of applications launched is greater than or equal to the preset number (for example, 3) when the electronic device 100 responds to the click operation of the task group icon, the floating windows of the above applications may be displayed after the background switching animation is displayed because the response time of the applications is greater than or equal to the preset time. This results in a long time interval between the display time of the background switching animation and the display time of the application floating windows, which brings a bad user experience.

[0124] (2) When launching multiple applications, if the display positions of the application windows overlap, the window of the later-launched application will be displayed on top of the window of the earlier-launched application. This may result in an inconsistency with the display hierarchy corresponding to the previously stored task group icons. For example, if the application window of application 1 is displayed above and overlapped with the application window of application 2 in the pre-stored process, and application 1 is launched first and application 2 is launched later, then the application window of application 2 launched later will be displayed on top of the application window of application 1 launched earlier, which is inconsistent with the pre-stored display format.

[0125] (3) Among the applications that have been launched, there may be applications that overlap with the application that will be launched and applications that do not overlap with the application that will be launched. It is necessary to distinguish between overlapping applications and non-overlapping applications. For example, overlapping applications indicate that the application to be launched includes the application that has been launched, while non-overlapping applications refer to applications that will be launched but do not include the application that has been launched.

[0126] (4) For non-overlapping applications, a background switching operation needs to be performed on them. Since the background switching animation is displayed earlier than the foreground switching animation, there is a problem of disconnection and asynchrony with the foreground switching animation of newly launched applications.

[0127] In view of this, this application provides a display control method for an electronic device having at least two modes: a multi-task scheduling mode and a non-multi-task scheduling mode. For example, in the non-multi-task scheduling mode, the electronic device does not display the application's floating window in response to a touch operation (such as a click or move operation) on the application icon. In the multi-task scheduling mode, the electronic device can display the application's floating window in the multi-task scheduling interface in response to a user's touch operation (such as a click or move operation) on the application icon.

[0128] In one implementation, the electronic device displays a first interface, which includes icons for a first task group and application windows (e.g., floating windows) within a first application group. Each application window in the first application group has one or more of the following: a first window size, a first window position, and a first window hierarchy. The first application group includes at least two applications. Based on operations (e.g., clicks) on multiple icons from the first task group, the electronic device sets the hierarchy of the application windows in the first application group according to the first window hierarchy, then displays a first switching animation. After displaying the first switching animation, a second interface is displayed, where the second interface includes application windows displayed according to one or more of the first window size, first window position, and first window hierarchy. Therefore, when a user clicks a task group icon, and the electronic device responds by opening multiple applications simultaneously, the inconsistency between the window hierarchy of the opened applications and the previously stored display hierarchy corresponding to the task group icon can be avoided because the hierarchy of each application window was set according to the stored window hierarchy before starting the switching animation.

[0129] In one implementation, the first interface further includes application windows in a second application group. The application windows in the second application group each have one or more of the following: second window size, second window position, and second window hierarchy. The second application group includes at least two applications. The first switching animation includes the startup animation of a first type of application. The first type of application includes applications in the first application group that do not overlap with applications in the second application group.

[0130] In one implementation, during the process of an electronic device responding to an operation on the icon of the first task group, if a second type of application exists in the second application group, the second switching animation is encapsulated within the window container transaction object where the first switching animation resides. The second switching animation includes the exit animation of the second type of application, which includes applications in the second application group that do not overlap with applications in the first application group. It can be seen that because the exit animation for switching to the background (i.e., the second switching animation) and the application startup animation (i.e., the first switching animation) are encapsulated within the same window container transaction object, the animations to be executed will be synchronized using the native synchronization mechanism. The animation callback will be executed once the required animation is ready, thus ensuring that the background switching animation and the application startup animation remain synchronized, avoiding animation desynchronization issues.

[0131] In one implementation, the electronic device can set a first type of application to a first type during the operation of an icon in a first task group. Optionally, if a third type of application exists in a second application group, the third type of application is set to the first type. Optionally, if a second type of application exists in the second application group, the second type of application is set to the second type, wherein the third type of application includes applications in the second application group that overlap with applications in the first application group, the first type is used to indicate that the application is running in the foreground, and the second type is used to indicate that the second type of application needs to be set to run in the background.

[0132] Optionally, when the electronic device displays the first switching animation, it may display the first switching animation based on a first type, and during the display of the first switching animation, the first type of application is set to run in the foreground. Optionally, when the electronic device displays the second switching animation, it may display the second switching animation based on a second type, and during the display of the second switching animation, the second type of application is set to run in the background. Optionally, when the electronic device displays the first transformation animation, it may display the first transformation animation based on a first type, and during the display of the first transformation animation, the third type of application continues to run in the foreground, the first transformation animation being used to indicate that the display position of at least one application in the third type of application is moved to the first window position and / or the window size of at least one application in the third type of application is scaled to the first window size. Therefore, in the callback animation, the change type of each application window is read (for example, the first type (TRANSIT_OPEN) or the second type (TRANSIT_TO_BACK)) to distinguish between applications that need to be switched to the background and applications that need to be opened. For the application window that needs to be switched to the background, an animation is performed to make the transparency disappear (second switching animation). For the application window that needs to be opened, an icon enlargement transition animation and an entry interface animation are performed (first switching animation). Alternatively, for windows that are already open and overlap with the application that needs to be opened later, a translation and scaling animation is performed (first transformation animation).

[0133] In one implementation, the electronic device determines whether an end flag exists in the application windows of the first application group based on operations on the icons of the first task group. An application window with an end flag indicates that its drawing is complete. If each application window in the first application group has an end flag, the layer of the application windows in the first application group is set according to the first window hierarchy. Then, during the display of the first switching animation, when an application in the first application group is launched, the start and end parameters of the transaction corresponding to each application are saved, and no view corresponding to the application is created, such as the view corresponding to the decorative layer in the application window. After the first switching animation is displayed, and after confirming that the application windows in the first application group have been drawn, the views of the applications in the first application group are created according to the start and end parameters of the transaction corresponding to each application, and the second interface is displayed. As can be seen, during the synchronous waiting process of the startup animation, an end flag (such as a starting window) can be used to determine in advance whether the application window's preparation work (such as drawing) is ready. If a starting window already exists under the application window, it means that the application window and all windows under it are ready, thus allowing the preparation work to end early and shortening the time interval between clicking and the animation starting. Furthermore, loading the application's decorview after the animation starts can further shorten the time interval between clicking and the animation starting, providing users with a smooth and fast response experience.

[0134] First, let's introduce the electronic device in the embodiments of this application. The electronic device can be a smart screen device, a smart TV, a mobile phone, a tablet computer, an ultra-mobile personal computer (UMPC), a netbook, as well as a cellular phone, a personal digital assistant (PDA), a wearable device (such as a smartwatch, a smart bracelet), and other devices with display functions. The embodiments of this application do not impose any special restrictions on the specific form of the electronic device.

[0135] Figure 2 A schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application is shown.

[0136] It should be understood that, Figure 2 The electronic device 100 shown is merely an example, and the electronic device 100 may have more than Figure 2 The more or fewer components shown can be combined into two or more components, or they can have different component configurations. Figure 2 The various components shown 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.

[0137] Electronic device 100 may include: processor 110, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, camera 193, and display screen 194. The sensor module 180 may include a touch sensor 180K, etc.

[0138] It is understood that the structures illustrated in the embodiments of the present invention 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 components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0139] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0140] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

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

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

[0143] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0144] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0145] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0146] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0147] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0148] Electronic device 100 can perform shooting functions through an ISP, camera 193, video codec, GPU, display 194, and application processor. The ISP is used to process data fed back by the camera 193. The camera 193 is used to capture still images or videos.

[0149] Electronic device 100 can implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, and an application processor. The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The speaker 170A, also called a "loudspeaker," is used to convert audio electrical signals into sound signals. The receiver 170B, also called a "handpiece," is used to convert audio electrical signals into sound signals. When electronic device 100 answers a phone call or voice message, the receiver 170B can be brought close to the user's ear to hear the voice. The microphone 170C, also called a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. The headphone jack 170D is used to connect wired headphones. The touch sensor 180K is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K may also be located on the surface of the electronic device 100, in a different position than the display screen 194.

[0150] The following describes the software architecture of an electronic device 100 provided in an embodiment of this application.

[0151] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. For example, a layered architecture software system can be the Android system, the Harmony operating system (OS), or other software systems, or a system jointly constructed by multiple software systems. This application embodiment uses the layered architecture Android system as an example to illustrate the software structure of electronic device 100.

[0152] Figure 3 An exemplary schematic diagram of the software architecture of an electronic device 100 is shown.

[0153] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In one implementation, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0154] The application layer can include a series of application packages.

[0155] like Figure 3 As shown, the application package may include applications such as a desktop launcher, task groups, messaging, calls, notes, files, videos, a browser, and a gallery. The applications in this application can also be replaced with other software such as mini-programs or atomic services.

[0156] The task group includes at least two application groups, such as a first application group and a second application group. For example, the first application group corresponds to... Figure 1F The icons for the first task group (412A), the second task group (412B), and the third task group (412C) are shown below. Figure 1G The fourth task group icon 412D shown corresponds to the second application group. Figure 1F The user interface 303 shown includes a contacts application, a notes application, and an alarm clock application.

[0157] A desktop launcher is a component of a system, also known as a desktop application, used to launch and manage the system's desktop UI. It is one of the main interfaces through which users interact with the system.

[0158] For example, a desktop launcher is an application loaded after an electronic device starts its system. It is used to launch other applications and is displayed on the desktop via an icon. Thus, the electronic device 100 can launch the corresponding application in response to a click on the application icon through the desktop launcher.

[0159] For example, in this embodiment of the application, the electronic device 100 can launch at least two applications corresponding to a task group in response to a click operation on the task group icon via a desktop launcher, and display a first switching animation of the application via the desktop launcher. The first switching animation includes, but is not limited to, a transition animation of the application icon enlarging and an animation of entering the interface. In one implementation, when an application window is displayed, while displaying the first switching animation, the electronic device 100 can also display a second switching animation and / or a first transition animation via the desktop launcher.

[0160] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0161] like Figure 3 As shown, the application framework layer may include system UI, system server, window manager service (WMS), content providers, view system, resource manager, input module, notification manager, etc.

[0162] The system user interface (UI) refers to the user interface of the operating system, which provides the basic GUI for the system. Examples include the status bar at the top of the screen, the navigation bar at the bottom of the screen, the quick settings bar in the drop-down menu, the notification bar, the lock screen, the desktop interface, the volume control dialog box, the screenshot display interface, the power interface, and the recent tasks interface (also known as the background running window).

[0163] For example, in this embodiment, the system user interface is used to register remote animations, such as transitions. Optionally, the system user interface is also used to create a Window ContainerTransaction (WCT) object and encapsulate the data corresponding to the first transition animation into the newly created WCT object. Optionally, when a second transition animation needs to be executed, the second transition animation is encapsulated into the WCT object where the first transition animation resides. Optionally, the system user interface is also used to manage / store one or more of the following: window size, window position, and window hierarchy of the application windows in the application groups corresponding to the icons of the task groups from the desktop launcher.

[0164] A system server refers to a background process or program that runs in the system to support the execution of other programs or system functions.

[0165] For example, in this embodiment of the application, the system service is used to determine whether there is an end flag in the application windows of the first application group, wherein the application window with the end flag is used to indicate that it has been drawn. Optionally, if each application window in the first application group has an end flag, the hierarchy of the application windows in the first application group is set according to the first window hierarchy. Optionally, the system service is also used to invoke a remote animation when the application window is ready.

[0166] The Window Management Service is used to manage window applications. It can obtain the screen size, determine whether to display in full-screen mode, whether to use split-screen mode, and whether there are floating windows, status bars, screen lock, or screen captures. The Window Management Service is a service, also known as the Window Manager Service (WMS).

[0167] A window can be understood as an area on a display screen that shows the user interface (UI) and allows user interaction. In some embodiments, a window can also hide the user interface (i.e., the software's operating interface), quickly revealing application navigation and functions when the user needs to interact, or reopening the application's operating interface based on triggered commands. From a system perspective, a window is essentially a canvas. A display screen can include multiple windows, and the layout, order, and animations of these windows are managed by the Window Management Service (WMS). Windows are layered; higher-level windows are displayed on top of lower-level windows, obscuring them. For example, floating windows are always displayed on the top layer.

[0168] Content providers store and retrieve data, making that data accessible to the window management service. This data can include files, folders, text, videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0169] A view system includes visual controls, such as text controls that display text and image controls that display images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon can include a view that displays text and a view that displays images.

[0170] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and so on.

[0171] The input module is used to obtain the raw input events (including touch coordinates, timestamps of touch operations, etc.) corresponding to touch operations from the kernel layer and identify the control corresponding to the input event.

[0172] The notification manager allows applications to display notifications in the status bar. These can be used to convey informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the system's top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting alert sounds, vibrating electronic devices, and flashing indicator lights.

[0173] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0174] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

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

[0176] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), rendering modules, etc.

[0177] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

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

[0179] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0180] A 2D graphics engine is a graphics engine for 2D drawing.

[0181] The rendering module can be used to draw and render images on the draggable window of the first object. For example, when the first object is text or a file, it can draw and render shadows and backgrounds on the draggable window of the text or file. When the first object is an image, it can draw and render shadows on the draggable window of the image.

[0182] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0183] The following example, using a drag-and-drop window scenario, illustrates the workflow of the software and hardware of electronic device 100.

[0184] Assume display screen 194 shows the application window. When touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, touch operation timestamp, etc.). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the object corresponding to the input event. Taking the touch operation as a click on a task group icon as an example, the task group icon corresponds to the first application group, and the application windows in the first application group have a first window hierarchy. Exemplarily, the desktop launcher calls the system user interface to create a WCT object for the first switching animation, sets the hierarchy of the application windows in the first application group according to the first window hierarchy, the system user interface calls the system service, and after the system service determines that the application windows in the first application group are ready, it calls the remote animation of the system user interface. The system user interface passes the first switching animation to the desktop launcher, and then the desktop launcher controls the display driver by calling the kernel layer to display the first switching animation on display screen 194.

[0185] exist Figure 2 The hardware architecture of the electronic device shown Figure 3 Based on the software architecture of the electronic device shown, the display control provided in this application will be described below with reference to specific embodiments. Please refer to... Figure 4A and Figure 4B , Figure 4A and Figure 4B A timing interaction diagram of a display control method provided in an embodiment of this application is shown. Figure 4A Including steps S401-S414, Figure 4B This includes steps S415 to S430.

[0186] S401: The desktop launcher registers a listener with the window management service.

[0187] Optionally, the desktop launcher can register a listener with the window management service using the Registerlistener() function. A listener can also be called a subscriber. For example, after registering a listener, when the window management service detects a touch event (such as a press event), it can pass that touch event to the desktop launcher.

[0188] S402: The input module obtains the pressed event of the icon in the first task group.

[0189] For example, the icons for the first task group could be the icons corresponding to at least two applications created in a multi-task scheduling mode, such as in... Figure 1F The task group icon created in the process.

[0190] In one implementation, the electronic device displays a first interface, which includes icons for a first task group. When an object operates on the icons of the first task group, the input module can obtain the press event of the icons of the first task group.

[0191] It is understandable that when an electronic device creates task group icons for at least two applications, it may save one or more of the window size, window position, and window hierarchy of the application windows of those at least two applications.

[0192] S403: The input module transmits the press event to the window management service.

[0193] For example, the input module sends a press event to the window service in response to an action (such as a click) on the icon of the first task group.

[0194] S404: The window management service passes press events to the desktop launcher.

[0195] For example, the desktop launcher has a listener registered in the window management service, so when the window management service detects a touch operation (such as an action), it can pass a press event to the desktop launcher.

[0196] S405: After receiving a press event, the desktop launcher creates a remote animation for the first task group based on the press event.

[0197] For example, upon receiving a press event, the desktop launcher may, in response to a press event on the icon of the first task group, create desktop tasks and a remote animation for the first task group. Optionally, a runner object may be created to generate the remote animation for the first task group.

[0198] S406: The desktop launcher transmits remote animations to the system user interface, including the application information of the application windows in the first application group of the first task group.

[0199] It is understandable that when creating the icon for the first task group, one or more of the window size, window position, and window hierarchy of the application windows in the corresponding application group can be saved.

[0200] For example, when the desktop launcher launches the icon of the first task group, it can start desktop tasks, call the system user interface through cross-process, and pass in the application information to be opened, as well as the window size, window position and hierarchy of the application after it is opened.

[0201] For example, if the first application group corresponding to the icon of the first task group includes the first application, the second application, the third application, and the fourth application, then the application information passed to the system user interface includes, but is not limited to: the window size, window position, and window hierarchy corresponding to the first application, the second application, the third application, and the fourth application, respectively.

[0202] S407: Register remote animation in the system user interface.

[0203] For example, the system user interface calls the registerRemote method to register a remote animation in a system service. Optionally, the remote animation may include a transition, which is used to provide a smooth transition animation effect.

[0204] S408: The system user interface creates a window container transaction object based on the registered remote animation.

[0205] For example, a system container transaction (WCT) object is an object used in the system to manage transactions related to window containers, such as layout adjustments, view additions, deletions, or updates. Furthermore, by encapsulating these changes in a WCT object, these operations can be handled efficiently through WCT.

[0206] S409: The system user interface is set to the first type of application.

[0207] For example, the first type is used to indicate that an application is running in the foreground, and the first type of applications includes applications in the first application group. Optionally, when a press event of the first task group is received, if the first interface also includes application windows of the second application group, the first type of applications includes applications in the first application group that do not overlap with applications in the second application group. For example, with Figure 1G For example, the first task group icon is task group icon 412C. The first application group includes the applications corresponding to task group icon 412C (note application, gallery application, calculator application, and browser application). The second application group includes... Figure 1G The user interface 303 shown includes the Contacts app, Notes app, and Alarm Clock app. The first category of apps includes the Photo app, Calculator app, and Browser app.

[0208] S410: The system user interface encapsulates the first switching animation corresponding to the first type of application into a window container transaction object, wherein the first switching animation includes the application window's startup animation.

[0209] For example, in order to better execute the switching animation, the system user interface can encapsulate the first switching animation to be executed into a WCT object based on one or more of the received application information, the application's window size, window position, and hierarchy. The first switching animation includes the application's startup animation and the animation of the application window entering the display area.

[0210] S411: If a second type of application exists, the system user interface sets the second type of application to the second type.

[0211] For example, the second type of application includes applications in the second application group that do not overlap with applications in the first application group. The second type is used to indicate that the second type of application needs to be set to run in the background. For example, with Figure 1G For example, the second category of applications includes contact applications and alarm clock applications.

[0212] In one implementation, if a second type of application exists, which is an application that needs to be switched to the background, the system user interface can remove the second type of application.

[0213] S412: The system user interface encapsulates the second switching animation corresponding to the second type of application into the window container transaction object where the first switching animation is located, wherein the second switching animation includes the exit animation of the application window.

[0214] For example, in order to better execute the first switching animation and the second switching animation, and to display the first switching animation and the second switching animation synchronously, the second switching animation to be executed can be encapsulated into the WCT object where the first switching animation is located, based on one or more of the obtained application information of the second type of application, the application's window size, window position, and hierarchical relationship.

[0215] In one implementation, by encapsulating the second switching animation corresponding to the second type of application into the window container transaction object where the first switching animation is located, new panel data can be created for the second type of application.

[0216] S413: In the presence of a third type of application, the system user interface sets the third type of application to the first type.

[0217] For example, the third category of applications includes applications that overlap with applications in the first application group within the second application group. That is, the first category of applications includes applications that have already been launched, and these launched applications overlap with applications to be launched later (which belong to the first category of applications). For example, with... Figure 1G For example, the third category of applications includes note-taking applications.

[0218] Optionally, the first transformation animation for the third type of application can be encapsulated in the WCT object where the first switching animation is located, or it can be left unencapsulated; this application does not impose any restrictions on this.

[0219] S414: The system user interface passes a window container transaction object to the system service.

[0220] For example, the window container transaction object includes one or more of the following: application information corresponding to the first switching animation, application window size, window position, and window hierarchy.

[0221] For example, in the case of a second type of application, the window container transaction object includes one or more of the following: application information corresponding to the first switching animation, application window size, window position, and window hierarchy, as well as one or more of the following: application information corresponding to the second switching animation, application window size, window position, and window hierarchy.

[0222] For example, in the case of a third type of application, the window container transaction object includes one or more of the following: application information corresponding to the first switching animation, application window size, window position, and window hierarchy, as well as one or more of the following: application information corresponding to the first transformation animation, application window size, window position, and window hierarchy.

[0223] For example, in the presence of a second type of application and a third type of application, the window container transaction object includes one or more of the following: application information corresponding to the first switching animation, application window size, window position, and window hierarchy; application information corresponding to the second switching animation, application window size, window position, and window hierarchy; and application information corresponding to the first transformation animation, application window size, window position, and window hierarchy.

[0224] In one implementation, the system user interface can pass the WCT object to the system service by calling the startNewTransition method through an interface provided by the window service kernel (WM core) in the window management service (such as the apply transaction interface), thereby enabling the system service to perform preparation work for opening the application and switching the application to the background.

[0225] S415: System service receives window container transaction object.

[0226] For example, system services can access

[0227] Collect and save the system container transaction (WCT) object, and then perform preparation work for opening the application and switching the application to the background based on the WCT object, such as steps S416-S418.

[0228] S416: The system service determines whether the application windows in the first application group are ready.

[0229] For example, when the system service starts the application and draws the first frame of the application window in the first application group, it determines whether the application window in the first application group is ready by checking whether there is an end flag. If it is ready, step S417 is executed; if it is not ready, it returns to step S416. The end flag indicates that the application window has been drawn.

[0230] Optionally, the end flag can be the Starting Window, also known as the Preview Window. This is a temporary window with a Window Type of TYPE_APPLICATION_STARTING. It is typically displayed before the application process is successfully created and initialized to inform the user that the system is processing an operation. In one implementation, this window is removed after the application initialization is complete, and the actual UI is displayed.

[0231] Please see Figure 5 , Figure 5 This is a schematic diagram illustrating an application window being ready, as provided in an embodiment of this application. Figure 5 As shown, during the process of launching applications in the first application group, the system service can create a task for each application. When creating the task for an application, application information can be obtained from the system user interface, such as one or more of the following: first window size, first window position, and first window hierarchy. For example, taking a first application group including a first application, a second application, a third application, and a fourth application, the system service can create task 1 for the first application, task 2 for the second application, task 3 for the third application, and task 4 for the fourth application based on the application information obtained from the system user interface. Figure 5 As can be seen, a task corresponds to at least one activity record, and an activity record stores all the information of an activity.

[0232] For example, during the startup of various applications, if the activity record in the task corresponding to each application contains a completed activity record, it can add the currently completed activity record to the preparation list. Then, it checks whether there is a completed activity record under each task. If there is a completed activity record under each task, it indicates that the task and the windows under that task are ready. Here, the completion of an activity record loading can mean that its corresponding window (such as the launch window, main window, etc.) has been drawn. For example, such as... Figure 5 As shown, with the increase of WCT collection time, the number of activity records corresponding to Task 1 increases from one activity record (e.g., activity record 1) to two activity records (e.g., activity record 1 and activity record 2). According to existing logic, Task 1 is only indicated to be ready when both activity record 1 and activity record 2 have been loaded. However, in this embodiment, Task 1 can be indicated to be ready when activity record 1 under Task 1 has been loaded. Similarly, when activity record 10 corresponding to Task 2 has been loaded, Task 2 can be indicated to be ready; when activity record 100 corresponding to Task 3 has been loaded, Task 3 can be indicated to be ready; and when activity record 1000 corresponding to Task 4 has been loaded, Task 4 can be indicated to be ready. Therefore, when Task 1, Task 2, Task 3, and Task 4 are all ready, the application window in the first application group can be indicated to be ready.

[0233] For example, when the system service starts drawing application windows, if the startup window is drawn, it calls the `onStartingWindowDrawn` method to inform the TransitionController that the current window's display content is ready. If the main window is drawn, it calls the `onFirstWindowDrawn` method to inform the TransitionController that the current window's display content is ready. Further, the system service can add the current display content to the `mReadyGroup` list. Even further, the system service checks that all tracked subtree objects are ready and sets the `SyncGroup`'s `Ready` state to true. For example, all tracked subtree objects include application windows in the first application group. Furthermore, the system service can check whether all tracked subtrees have been synchronized. For example, it can check whether the WindowState node has been synchronized. When the mSyncState state of WindowState has been set from SYNC_STATE_WAITING_FOR_DRAW to SYNC_STATE_READY, it indicates whether all tracked subtrees have been synchronized, that is, whether the application windows in the first application group are ready.

[0234] S417: The system service does not set the application window hierarchy according to the application startup order, but sets the application window hierarchy in the first application group according to the first window hierarchy.

[0235] For example, according to existing logic, the hierarchical relationship of applications is related to the startup order of applications. Applications that are started later can be set to a higher level, and applications that are started earlier can be set to a lower level. However, in this embodiment, the system service does not set the application window hierarchy according to the application startup order. Instead, it obtains the hierarchy (i.e., the first window hierarchy) that should be saved in advance from the system user interface and resets the application window hierarchy in the first application group according to the first window hierarchy.

[0236] For example, consider four applications that are launched: Application 1, Application 2, Application 3, and Application 4. The pre-stored level of Application 1 is Level 1, Application 2 is Level 2, Application 3 is Level 4, and Application 4 is Level 3. Level 4 is higher than Level 3, which is higher than Level 2, which is higher than Level 1. During the launch of these applications, because Application 1 has a decorative layer, loading the decorative layer takes a long time. Therefore, Application 1 is launched last, Application 2 is launched first, Application 3 is launched second, and Application 4 is launched third. However, the system service does not set the level according to the launch time, but still sets the application window level according to the level obtained from the system user interface.

[0237] S418: The system service transmits the configured application window hierarchy information and the application window control handle to the system user interface.

[0238] For example, when all participants in a Transition are ready, a remote animation can be called back by invoking the onTransitionReady method, which returns the hierarchical information of the application window after setup and the control handle of the application window.

[0239] S419: During the preparation of the first switching animation, the system user interface saves the transaction start parameters and transaction end parameters when the application is started, and does not create a view of the application.

[0240] For example, in this embodiment of the application, not creating a view for the application means not creating a view corresponding to the decorative layer in the application window of the application, such as the view of the layer where the floating window control is located. Figure 1D For example, the views corresponding to the decoration layer in the application window include: Figure 1D The layer containing one or more of the following controls in the floating window 3122 of the note application shown: full-screen display control 3122A, minimize control 3122B, top bar 3122C, and close control 3122D.

[0241] For example, during the application startup process, the system service can delegate all window decoration operations to the system user interface. In the `onTransitionReady` phase, i.e., during the preparation of the first transition animation, the system user interface can store `TransitionToken`, `TransitionInfo`, and `transaction` in `ActiveTransaction`, and call the `dispatchReady` method to process each `mObserver` object. `mObserver` corresponds to the listener of the floating window, and it iterates through each `change`. Optionally, during a cold start of the application, the WM core will pass a `change` of type `TRANSIT_OPEN`, storing the transaction start parameters (`startT`) and transaction end parameters (`finishT`) of the application when it is cold started, without creating a view for the application. Optionally, during application startup or warm start, the WM core will pass a `change` of type `TRANSIT_TO_FRONT`, storing the transaction start parameters and transaction end parameters of the application when it is started or warm started, without creating a view for the application.

[0242] S420: The system user interface passes the configured application window hierarchy information, application information, and control handle to the desktop launcher.

[0243] For example, the system user interface can pass in the remote animation Binder by calling the startAnimation method, which will call back to the desktop launcher and return the hierarchical information of each application window after the settings, animation start and end callback notifications to assemble and start the remote animation.

[0244] S421: The system user interface passes at least one of the following to the desktop launcher: the first type of the first type of application, the second type of the second type of application, and the first type of the third type of application.

[0245] For example, in the presence of a second type of application, the system user interface passes the first type of the first type of application and the second type of the second type of application to the desktop launcher.

[0246] For example, in the presence of a third type of application, the system user interface passes the first type of the first type of application and the first type of the third type of application to the desktop launcher.

[0247] For example, in the presence of a second type of application and a third type of application, the system user interface passes the first type of the first type of application, the second type of the second type of application, and the first type of the third type of application to the desktop launcher.

[0248] S422: The desktop launcher determines whether the application window's conversion type is the second type and whether it is an application that does not need to be launched.

[0249] For example, each application window carries a conversion type, such as a first type or a second type. When the desktop launcher determines that the conversion type of the application window is the second type and it is an application that does not need to be launched, step S423 is executed; when the desktop launcher determines that the conversion type of the application window is not the second type and it is an application that does not need to be launched, step S424 is executed; when the desktop launcher determines that the conversion type of the application window is not the second type and it is not an application that does not need to be launched, step S425 is executed.

[0250] It should be noted that one or more of steps S423, S424 and S425 can be executed simultaneously.

[0251] S423: The desktop launcher displays a second switching animation based on the second type and applications that do not need to be launched.

[0252] For example, the second switching animation includes an animation in which the transparency of a second type of application disappears as it is switched to the background and exits the display area.

[0253] S424: The desktop launcher displays a first transformation animation based on the first type and applications that do not need to be launched.

[0254] For example, the first transformation animation includes window panning and scaling animations for a third type of application.

[0255] S425: The desktop launcher displays the first switching animation based on the first type and the application that needs to be launched.

[0256] For example, the first switching animation includes a zoom-in transition animation of the icon of the first task group and an animation of the first type of application being switched to the front and entering the display area.

[0257] In one implementation, in the presence of a second type of application, the desktop launcher simultaneously displays the first and second switching animations based on the same WCT object corresponding to the first and second switching animations.

[0258] In one implementation, in the presence of a third type of application, the desktop launcher may display a first switching animation and a first transformation animation.

[0259] S426: After the animation is completed, the desktop launcher sends an animation end callback to the system user interface.

[0260] S427: During the animation end callback phase, the system user interface creates a view of the application in the first application group based on the transaction start parameters and transaction end parameters corresponding to the application, and displays the second interface.

[0261] For example, in the animation end callback phase, such as the `on finish` phase, the system user interface can call the `finish` phase at each observer through the `onTransitionFinished` method, set the `finish` flag, and iterate through the tasks corresponding to all opened application windows to confirm that the windows and views under each task can be displayed normally. The `ensureTaskVisibility` method is used to schedule `DeskTopModeXXX` according to the current multi-task scheduling mode. Then, it determines that the current mode is multi-task scheduling and is in the `finish` phase. The previously saved transaction start parameters (`startT`) and transaction end parameters (`finishT`) are passed to `onTaskChanging` to create the view, that is, to create the view corresponding to the decorative layer in the application window, such as the view of the layer containing the floating window control. After creation, the second interface is displayed. For example, the second interface includes application windows displayed according to one or more of the first window size, first window position, and first window hierarchy. For example, using... Figure 1H For example, the second interface includes a floating window 3141 for the note-taking application, a floating window 3142 for the photo album application, a floating window 3143 for the calculator application, and a floating window 3144 for the browser application.

[0262] S428: The system user interface sends an animation end callback to the system service.

[0263] S429: The system service sends a response to the animation end callback to the system user interface.

[0264] S430: The system user interface sends a response to the animation end callback to the desktop launcher.

[0265] Please see Figure 6 , Figure 6 This is a flowchart illustrating a display control method provided in an embodiment of this application. The method includes, but is not limited to, the following steps:

[0266] Step S601: Display the first interface, which includes the icon of the first task group.

[0267] For example, the first task group includes application windows in a first application group, and the application windows in the first application group each have one or more of the following: a first window size, a first window position, and a first window hierarchy. The first application group includes at least two applications. For example, the first interface may be... Figure 1G In user interface 303, the icon for the first task group can be... Figure 1G The task group icon 412C can also be... Figure 1G The task group icon 412D is provided. This application does not impose any restrictions on the icon of the first task group.

[0268] In one implementation, before displaying the first interface, the electronic device displays a third interface, wherein the third interface includes a first function icon in a first state, and the electronic device is in a first mode when displaying the third interface. After an operation (e.g., a click) is performed on the first function icon in the first state, the electronic device switches from the first mode to a second mode and displays a fourth interface. In response to an operation on a first application in the fourth interface, the electronic device displays a fifth interface, which includes the window of the first application, the display area of ​​which is smaller than the display area of ​​the screen. For example, the third interface could be... Figure 1A In the user interface 200, the first function icon in the first state can be... Figure 1A The multi-task scheduling icon 231A allows for several modes: the first mode can be a non-multi-task scheduling mode, the second mode can be a multi-task scheduling mode, and the fourth interface can be... Figure 1C The user interface 301, the first application can be Figure 1C In an alarm clock application, the first application window can be a floating window of the alarm clock application.

[0269] In one implementation, the electronic device displays a sixth interface. The sixth interface includes application windows in a first application group, a first function icon in a second state, and a second function icon. The application windows in the first application group are displayed on the sixth interface according to one or more of the following: first window size, first window position, and first window hierarchy. After an operation on the second function icon, a layout window is displayed on the sixth interface. The layout window includes a first control and a second control. The first control is used to create a window layout, and the second control includes a control for creating task group icons. After an operation on the second control, a third control is displayed in the first area of ​​the layout window. After an operation on the third control, the icon of the first task group corresponding to the first application group is displayed in the second area of ​​the layout window. For example, the sixth interface could be... Figure 1D The user interface 302 includes application windows in the first application group, such as a floating window 3121 for the Contacts application, a floating window 3122 for the Notes application, and a floating window 3123 for the Alarm Clock application. The second function icon can be... Figure 1D Quick layout icon 231C, the layout window can be Figure 1E In the quick layout window 410, the first control can be Figure 1E The first control 411 (i.e., the layout control), the second control can be Figure 1E The second control 412 (i.e., the favorites control), the third control can be Figure 1F The first area of ​​the control 413 can be... Figure 1F The icon for the first task group corresponding to the first application group in the first area 4101 can be... Figure 1G The task group icon is 412D.

[0270] For example, a description of step S601 can be found here. Figure 4A S401 to S406 are shown.

[0271] Step S602: Based on the operation on the icon of the first task group, set the hierarchy of the application windows in the first application group according to the first window hierarchy.

[0272] For example, the first window hierarchy is the hierarchy saved when the icon for the first task group is created.

[0273] In one implementation, the first interface further includes application windows in a second application group. These application windows in the second application group each possess one or more of the following: a second window size, a second window position, and a second window hierarchy. The second application group includes at least two applications. The first switching animation includes a startup animation for a first type of application. The first type of application includes applications in the first application group that do not overlap with applications in the second application group. Optionally, in response to an operation on an icon in the first task group, the electronic device can set the first type of application to a first type, where the first type indicates that the application is set to run in the foreground.

[0274] For example, with Figure 1G For example, the application windows in the second application group include Figure 1G The floating window 3121 of the Contacts app, the floating window 3122 of the Notes app, and the floating window 3123 of the Alarm Clock app, the first group of apps includes Figure 1G The task group icon 412C corresponds to the note-taking application, the gallery application, the calculator application, and the browser application. The first category of applications includes the gallery application, the calculator application, and the browser application.

[0275] In one implementation, during the response to an operation on the icon of the first task group, if a second type of application exists, the second switching animation is encapsulated within the window container transaction object where the first switching animation resides. The second switching animation includes the exit animation of the second type of application, which includes applications in the second application group that do not overlap with applications in the first application group. For a detailed description of this part, please refer to [reference needed]. Figure 4A The S412.

[0276] In one implementation, during the response to an operation on the icon of the first task group, if a second type of application exists, the electronic device sets the second type of application to a second type, where the second type indicates that the second type of application needs to be set to run in the background. For example, with Figure 1G For example, the second category of applications includes contact applications and alarm clock applications.

[0277] In one implementation, when a third type of application exists, the electronic device sets the third type of application as the first type, wherein the third type of application includes applications in the second application group that overlap with applications in the first application group. For example, with Figure 1G For example, the third category of applications includes note-taking applications.

[0278] In one implementation, based on the operation on the icon of the first task group, it is determined whether there is an end flag in the application windows of the first application group. An application window with an end flag indicates that it has been drawn successfully. If each application window in the first application group has an end flag, the hierarchy of the application windows in the first application group is set according to the first window hierarchy. For a detailed description of this part, please refer to [reference needed]. Figure 4B S416 to S418.

[0279] For example, a description of step S602 can be found here. Figure 4A S407 to S414 and shown Figure 4B S415 to S418 are shown.

[0280] Step S603: Display the first switching animation, and after displaying the first switching animation, display the second interface.

[0281] In one implementation, the electronic device displays a first switching animation based on a first type, and during the display of the first switching animation, the first type of application is set to run in the foreground.

[0282] In one implementation, the electronic device displays a second switching animation simultaneously with a first switching animation, and then displays a second interface after displaying both the first and second switching animations. Optionally, the second switching animation is displayed based on a second type, and during the display of the second switching animation, the second type of application is set to run in the background.

[0283] In one implementation, when displaying the first transformation animation, the electronic device displays the first transformation animation based on a first type. During the display of the first transformation animation, a third type of application continues to run in the foreground. The first transformation animation is used to indicate that the display position of at least one application in the third type of application is moved to the first window position and / or the window size of at least one application in the third type of application is scaled to the first window size.

[0284] In one implementation, during the preparation of the first switching animation, when launching applications in the first application group, the electronic device saves the transaction start and end parameters corresponding to each application, but does not create views for the applications, such as views corresponding to decorative layers in the application windows. After displaying the first switching animation, and after confirming that the application windows in the first application group have been drawn, the electronic device creates views for the applications in the first application group based on the transaction start and end parameters, such as views corresponding to decorative layers in the application windows of each application in the first application group. This completes the creation of the entire application window, leading to the display of the second interface, which includes the application windows (e.g., floating windows) corresponding to the applications in the first application group. For example, the second interface could be... Figure 1H The user interface shown is 304.

[0285] For example, a detailed description of step S603 can be found here. Figure 1B S419 to S430 are shown.

[0286] It should be understood that the steps in the above-described method embodiments provided in this application can be implemented by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.

[0287] This application also provides an electronic device that may include a memory and a processor. The memory may be used to store a computer program; the processor may be used to invoke the computer program in the memory to cause the electronic device to perform the methods in any of the above embodiments.

[0288] This application also provides a chip system including at least one processor for implementing the functions involved in the methods performed by the electronic device in any of the above embodiments.

[0289] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0290] The chip system can consist of chips or include chips and other discrete components.

[0291] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0292] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application embodiment does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application embodiment does not specifically limit the type of memory or the arrangement of the memory and processor.

[0293] For example, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0294] This application also provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the method executed by the electronic device in any of the above embodiments.

[0295] This application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is run, it causes the computer to perform the method executed by the electronic device in any of the above embodiments.

[0296] The various embodiments of this application can be combined arbitrarily to achieve different technical effects.

[0297] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive).

[0298] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0299] In summary, the above description is merely an embodiment of the technical solution of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made according to the disclosure of the present invention should be included within the scope of protection of the present invention.< / canvas> < / video> < / videoview> < / imgview> < / textview>

Claims

1. A display control method, characterized in that, Applied to electronic devices, the method includes: Display a first interface, wherein the first interface includes an icon of a first task group, the first task group includes application windows in a first application group, and the application windows in the first application group have one or more of a first window size, a first window position, and a first window hierarchy, and the first application group includes at least two applications. Based on the operation on the icon of the first task group, the hierarchy of the application windows in the first application group is set according to the first window hierarchy; A first switching animation is displayed. After the first switching animation is displayed, a second interface is displayed. The second interface includes the application windows of the first application group. The application windows of the first application group in the second interface are displayed according to one or more of the first window size, the first window position, and the first window hierarchy.

2. The method according to claim 1, characterized in that, Before displaying the first interface, the method further includes: The third interface is displayed, wherein the third interface includes a first function icon of a first state, and the electronic device is in a first mode when the third interface is displayed. After operating on the first function icon in the first state, the electronic device switches from the first mode to the second mode and displays a fourth interface, wherein the fourth interface includes an icon of at least one application and the first function icon of the second state. In response to an operation on the first application in the fourth interface, a fifth interface is displayed, wherein the fifth interface includes a window of the first application, and the display area of ​​the window of the first application is smaller than the display area of ​​the screen.

3. The method according to claim 2, characterized in that, After displaying the fifth interface, the method further includes: The sixth interface is displayed, wherein the sixth interface includes the application window in the first application group, the first function icon and the second function icon in the second state, and the application windows in the first application group are displayed in the sixth interface according to one or more of the first window size, the first window position and the first window level. After the second function icon is operated, a layout window is displayed in the sixth interface. The layout window includes a first control and a second control. The first control is a control for creating a window layout, and the second control includes a control for creating task group icons. After the second control is operated on, the third control is displayed in the first area of ​​the layout window; After the third control is operated, the icon of the first task group corresponding to the first application group is displayed in the second area of ​​the layout window.

4. The method according to any one of claims 1 to 3, characterized in that, The first interface also includes application windows in a second application group, wherein each application window in the second application group has one or more of the following: second window size, second window position, and second window hierarchy. The second application group includes at least two applications. The first switching animation includes a startup animation for a first type of application. The first type of application includes applications in the first application group that do not overlap with applications in the second application group. The method further includes: In response to an operation on the icon of the first task group, the first type of application is set to a first type, wherein the first type is used to indicate that the application is set to run in the foreground.

5. The method according to claim 4, characterized in that, The first switching animation is displayed, including: The first switching animation is displayed according to the first type, and during the display of the first switching animation, the first type of application is set to run in the foreground.

6. The method according to claim 4 or 5, characterized in that, The method further includes: In the process of responding to the operation of the icon of the first task group, if there is a second type of application, the second switching animation is encapsulated in the window container transaction object where the first switching animation is located. The second switching animation includes the exit animation of the second type of application, and the second type of application includes applications in the second application group that do not overlap with applications in the first application group.

7. The method according to claim 6, characterized in that, The method further includes: The second switching animation is displayed simultaneously with the first switching animation, and the second interface is displayed after the first switching animation and the second switching animation are displayed.

8. The method according to claim 6 or 7, characterized in that, The method further includes: In the process of responding to the operation of the icon of the first task group, if a second type of application exists, the second type of application is set to a second type, wherein the second type is used to indicate that the second type of application needs to be set to run in the background.

9. The method according to claim 8, characterized in that, The method further includes: The second switching animation is displayed based on the second type. During the display of the second switching animation, the second type of application is set to run in the background, and the second interface does not include the application window of the second type of application.

10. The method according to any one of claims 4 to 9, characterized in that, The method further includes: In the presence of a third type of application, the third type of application is set as the first type, wherein the third type of application includes applications in the second application group that overlap with applications in the first application group.

11. The method according to claim 10, characterized in that, The method further includes: When the first transformation animation is displayed, the first transformation animation is displayed based on the first type. During the display of the first transformation animation, the third type of application continues to run in the foreground. The first transformation animation is used to indicate that the display position of at least one application in the third type of application is moved to the first window position and / or the window size of at least one application in the third type of application is scaled to the first window size.

12. The method according to any one of claims 1 to 11, characterized in that, The step of setting the hierarchy of application windows in the first application group according to the first window hierarchy based on the operation on the icon of the first task group includes: Based on the operation of the icon of the first task group, it is determined whether there is an end flag in the application window of the first application group, wherein the application window with the end flag is used to indicate that it has been drawn. If each application window in the first application group has an end flag, the layer of the application windows in the first application group is set according to the first window layer.

13. The method according to any one of claims 1 to 12, characterized in that, The process of displaying a first switching animation and then displaying a second interface after displaying the first switching animation includes: During the preparation of the first switching animation, when starting the application in the first application group, the transaction start parameters and transaction end parameters corresponding to the application are saved respectively, and the view of the application is not created. After displaying the first switching animation, and after confirming that the application windows in the first application group have been drawn, a view of the application in the first application group is created according to the transaction start parameters and transaction end parameters corresponding to the application, and the second interface is displayed.

14. An electronic device, characterized in that, The electronic device includes: one or more processors; a memory; wherein the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code including computer instructions, and the one or more processors call the computer instructions to cause the electronic device to perform the method as described in any one of claims 1-13.

15. A computer program product containing instructions, characterized in that, When the computer program product is run on an electronic device, it causes the electronic device to perform the method as described in any one of claims 1-13.

16. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-13.

Images