Display control method and electronic device

Abstract

The present application provides a display control method and an electronic device, which relates to the technical field of electronic devices and is applied to an electronic device, in which a first application and a second application are installed. The method comprises: the electronic device displays a first application interface of the first application; the electronic device responds to a user's exit operation on the first application and plays an exit animation of the first application; during the process of the electronic device playing the exit animation of the first application, the electronic device responds to a user's start operation on the second application, and the desktop interface of the electronic device keeps displaying a first icon of the first application. This solution can keep the icon of the application continuously displayed when the electronic device receives an operation of starting other applications from the user during the process of exiting the application, thereby improving the visual experience.

Description

Technical Field

[0001] The present application relates to the technical field of electronic equipment, and in particular to a display control method and an electronic equipment. Background Art

[0002] At present, electronic devices have more and more applications (applications, APPs) installed, and their functions are becoming more and more diverse. For example, smart phones usually have various applications installed, such as social, news, finance, entertainment, reading, etc. In response to the user's click operation on the desktop application icon, the electronic device can trigger the application to start. In order to improve the desktop animation experience, the application in the electronic device will be accompanied by a startup animation when it is started, and the application will be accompanied by an exit animation when it is exited.

[0003] When the electronic device exits application 1, if it receives a click operation from the user to start other applications, a brief blank may appear at the icon position of application 1, causing the icon to flicker visually to the user. Summary of the invention

[0004] The embodiments of the present application provide a display control method and an electronic device. When the electronic device is exiting an application, if it receives an operation from the user to start another application, the icon of the application is continuously displayed to improve the visual experience.

[0005] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0006] In a first aspect, a display control method is provided, which can be applied to an electronic device in which a first application and a second application are installed. The method comprises: during the process of the electronic device playing an exit animation of the first application, the electronic device responds to the user's start operation of the second application in the desktop interface, and the first icon of the first application remains displayed in the desktop interface of the electronic device.

[0007] Among them, the exit animation and startup animation of the above electronic device are both transformed with dynamic effects. By adopting the above technical solution, when the electronic device exits application 1 and starts another application 2 in response to the user's operation, the application icon can be continuously displayed on the desktop of the electronic device, which solves the problem of flickering application icons and improves the visual experience.

[0008] In a possible implementation of the first aspect, the electronic device responds to a user's launch operation of a second application in a desktop interface, and keeps displaying a first icon of a first application in the desktop interface of the electronic device, including: the electronic device draws the first icon in response to the user's launch operation of the second application; after detecting that the drawing of the first icon is completed, the electronic device stops playing the exit animation of the first application, and keeps displaying the first icon of the first application in the first interface of the electronic device.

[0009] In this way, this solution adjusts the execution timing of drawing the icon of the first application and stopping playing the exit animation of the first application. The icon of the first application is drawn first, and then the exit animation of the first application is stopped. This allows the icon of the first application to be continuously displayed on the desktop interface without causing visual flickering.

[0010] In a possible implementation of the first aspect, after the electronic device detects that the first icon is drawn and stops playing the exit animation of the first application, the electronic device further includes: playing the startup animation of the second application. In this way, after the first icon is drawn and the startup animation of the second application is played, the first icon will continue to be displayed on the desktop interface of the electronic device.

[0011] In a possible implementation of the first aspect, the electronic device stops playing the exit animation of the first application after detecting that the first icon has been drawn, including: the electronic device registers a monitoring task for monitoring whether the first icon has been drawn; the electronic device stops playing the exit animation of the first application after monitoring that the first icon has been drawn. This solution can monitor whether the first icon has been drawn by registering a monitoring task, and can ensure that the electronic device continues the subsequent process after the first icon has been drawn.

[0012] In a possible implementation of the first aspect, the method further includes: after the electronic device detects that the first icon is drawn, the electronic device removes the monitoring task. In this solution, after the electronic device detects that the first icon is drawn, it no longer needs to continue to monitor other drawing operations, thereby removing the monitoring task and saving power consumption of the electronic device.

[0013] In a possible implementation of the first aspect, the method further includes: the interval between the exit operation and the start operation is less than or equal to 400 milliseconds. In this solution, if the interval between the exit operation and the start operation is too long, the exit animation of the first application may have ended. Therefore, the interval between the start operation and the exit operation detected by the electronic device needs to be controlled within a certain time length, which can ensure that the electronic device is in a scenario where the second application is started during the exit animation of the first application.

[0014] In a possible implementation of the first aspect, stopping the exit animation of the first application includes: the electronic device destroying the application layer and the icon layer mounted on the application layer; the first icon displayed in the exit animation of the first application belongs to the icon layer. Among them, the electronic device stops the exit animation of the first application, which means destroying the application layer of the first application. If the application layer is destroyed, the icon layer mounted on the application layer will be destroyed accordingly, which means that the icon of the first application in the exit animation is no longer displayed. Since the electronic device has already drawn the first icon before stopping the exit animation of the first application, the destruction of the icon layer here will not affect the display of the first icon on the desktop.

[0015] In a possible implementation of the first aspect, in the process of the electronic device playing the exit animation of the first application, before the electronic device responds to the user's startup operation on the desktop of the second application, it also includes: the electronic device determines whether the exit animation of the first application has been played to completion when the user's touch operation on the desktop interface is detected; if the electronic device detects that the exit animation of the first application has not been played to completion when the user's touch operation on the desktop interface is detected, it determines whether the application targeted by the touch operation is the second application; if the application targeted by the touch operation is the second application, the electronic device is in the process of the electronic device playing the exit animation of the first application, and the electronic device detects the user's startup operation on the second application on the desktop. In this way, the electronic device can determine that it is in the process of playing the exit animation of the first application and detects the user's startup operation on the second application on the desktop, and when in this scenario, the first icon of the first application is kept displayed in the desktop interface of the electronic device.

[0016] In summary, when a mobile phone exits an application and receives a user's start-up operation for a new application, it is possible to register a monitoring task and, after monitoring that the original application icon is drawn, perform the end process of the application's swipe-up exit animation. Then, start the startup animation of the new application. In this way, the display control method provided in the embodiment of the present application can make the icon of the original application displayed first, and then destroy the exit animation of the original application, ensuring that the icon position of the original application will not be blank, thereby solving the problem of flickering application icons.

[0017] In a second aspect, the present application provides an electronic device, comprising: a display screen, a memory and one or more processors; the display screen, the memory and the processor are coupled; wherein the memory stores computer program code, the computer program code comprises computer instructions, and when the computer instructions are executed by the processor, the electronic device executes any one of the methods described in the first aspect above.

[0018] In a third aspect, the present application provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is executed on a computer, the computer can execute the charging method described in any one of the first aspects above.

[0019] In a fourth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute any of the methods described in the first aspect.

[0020] It can be understood that the electronic device described in the second aspect provided above, the computer-readable storage medium described in the third aspect and the computer program product described in the fourth aspect are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A schematic diagram of a binder call provided in an embodiment of the present application;

[0022] Figure 2 A schematic diagram of a flashing application icon provided in an embodiment of the present application;

[0023] Figure 3 A software structure diagram of a mobile phone provided in an embodiment of the present application;

[0024] Figure 4 A schematic diagram of an application exit animation provided in an embodiment of the present application;

[0025] Figure 5 A schematic diagram of a time point for drawing an icon provided in an embodiment of the present application;

[0026] Figure 6 A business timing diagram of a display control method provided by an embodiment of the present application;

[0027] Figure 7 A logic diagram of a click-to-start application provided in an embodiment of the present application;

[0028] Figure 8 A schematic diagram of a business timing of a method for switching an application provided in an embodiment of the present application;

[0029] Fig. 9 A schematic diagram for comparing time points of icon drawing provided in an embodiment of the present application;

[0030] Fig.10 A schematic diagram of application icon display in a scenario where a mobile phone starts application 2 in the process of swiping up to exit application 1 provided in an embodiment of the present application;

[0031] Fig.11 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0032] Fig.12 A schematic diagram of the structure of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0034] It should be noted that the following terms "first", "second", etc. are only used for descriptive purposes and should not be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, features defined as "first", "second", etc. may explicitly or implicitly include one or more of the features. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

[0035] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways.

[0036] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0037] In order to better illustrate the technical solution of the present application, the following is a brief overview of the terms involved in the present application.

[0038] (1) Surfaceflinger is an important component of the Android operating system, also known as the display engine. Surfaceflinger is responsible for managing and rendering graphics windows, and displaying applications and system interfaces on the screen of electronic devices. Surfaceflinger uses a double buffering mechanism to create the final display image by synthesizing and mixing multiple layers. Surfaceflinger also handles input events, such as touch screen operations, and passes them to the correct application or system component.

[0039] (2) The Android desktop launcher (Launcher) is one of the main program components in the Android system. The Launcher can be used to start the Android desktop user interface (UI). Without the Launcher, the Android desktop cannot be started.

[0040] In some scenarios, the application startup animation process includes: after each vertical synchronization (vsync) signal arrives, Launcher can calculate the attribute value of the next frame window according to the animation progress, and pass the attribute value of the next frame window to Surfaceflinger through the binder call. Assuming that the duration of the application startup animation is 500ms, and the interval between each frame is 10ms, the number of binder calls reaches 50 times. After Surfaceflinger completes the rendering, synthesis and display of the startup animation, there is another binder callback.

[0041] See also Figure 1 , Figure 1 A schematic diagram of a binder call provided in an embodiment of the present application. Figure 1 As shown in (a), the process of launching an application's startup animation includes three steps. The system service sends the animation parameters to Surfaceflinger frame by frame (step 1). The system service is usually responsible for calling the process of launching Launcher. The animation parameters refer to the attribute values ​​of each frame window. Surfaceflinger only draws one frame (step 2) to complete the rendering, synthesis and display of the animation. After the parameters are sent, Surfaceflinger returns the result to the system service (step 3). Therefore, the number of binder calls required for the startup animation of an application in the above scheme is 51 times.

[0042] Since the above scheme requires a large number of binder calls for the startup animation of an application, the overload scenario causes animation frame loss / excessive frame spacing due to untimely scheduling of the binder thread. The overload scenario here refers to the scenario in which the electronic device, in the process of exiting application 1 and displaying the exit animation, responds to the user's click operation on application 2 and starts the startup animation of application 2; in other words, the overload scenario is the scenario in which the electronic device needs to perform another animation before the end of one animation.

[0043] Therefore, in the embodiment of the present application, the electronic device can perform dynamic effect sinking transformation on the high-frequency use scenarios of the desktop, which can improve the desktop (desktop interface) animation experience and reduce frame loss and jamming problems. Among them, the above-mentioned high-frequency use scenarios of the desktop include: the animation display process during the exit of the application, the animation display process during the opening of the application, the animation display process during the sliding switching of the application, etc. During the application startup process, the electronic device usually completes the drawing of the startup animation effect of the application first, that is, completes the startup dynamic effect drawing, and then the electronic device displays the main interface of the application for user operation.

[0044] In the embodiment of the present application, the process of using the dynamic effect sinking logic in the startup animation of the application is as follows: the electronic device separates the setting process of the startup animation from the execution process, and packages the animation frame window properties that fit the dynamic effect curve and sends them to Surfaceflinger in the initial stage of the startup animation, without sending each frame. Surfaceflinger completes the rendering, synthesis and display of the animation frame by frame according to the vsync signal. After Surfaceflinger completes the rendering, synthesis and display of the startup animation, there is another binder callback.

[0045] like Figure 1 As shown in (b), the process of using the dynamic effect sinking logic for the application startup animation includes three steps. The system service sends the dynamic effect parameters of all frames to Surfaceflinger (step 1). Surfaceflinger draws all frames in a loop (step 2) to complete the rendering, synthesis and display of the animation. After the dynamic effect is played, Surfaceflinger returns the result to the system service (step 3). Therefore, using the dynamic effect sinking solution for window animation requires only two binder calls.

[0046] Therefore, the dynamic effect sinking solution is used for window animation, and the number of binder calls required is only two. Compared with the number of binder calls in the conventional solution, the number of binder calls in the animation process is greatly reduced, and the animation frame loss / excessive frame spacing caused by untimely binder thread scheduling in overload scenarios is reduced.

[0047] It should be noted that, since the icons of the above-mentioned applications are displayed on the desktop of the electronic device, the above-mentioned applications can also be called desktop applications.

[0048] In the case where desktop applications use dynamic sinking logic, if the electronic device has opened application 1, and in the process of exiting application 1, if the electronic device responds to the user's operation to start application 2. In the above process, the icon of application 1 will be briefly blank, causing the icon to flicker in human vision.

[0049] The user can control the closing of the application through gestures. For example, the mobile phone exits the application by responding to the user's swipe up gesture on the application interface. Exiting the application means that the mobile phone exits the application interface and returns to the desktop. In the embodiment of the present application, the mobile phone can also exit the application in response to other operations of the user on the application interface, and the present application does not limit this.

[0050] It should be noted that exiting an application on a mobile phone may mean that the mobile phone closes the application, or the application is not closed but is working in the background.

[0051] Exemplarily, the electronic device in the embodiment of the present application includes at least a display screen, which may specifically include a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook, a cellular phone, a personal digital assistant (personal digital assistant, PDA), an augmented reality (augmented reality, AR) device, a virtual reality (virtual reality, VR) device, an artificial intelligence (artificial intelligence, AI) device, a wearable device, a vehicle-mounted device, a smart home device, or at least one of a smart city device. The embodiment of the present application does not impose any special restrictions on the specific type of the electronic device, and the following embodiment is described by taking the electronic device as a mobile phone as an example.

[0052] See also Figure 2 , Figure 2 A schematic diagram of a flashing application icon provided in an embodiment of the present application. Figure 2 As shown in (a), the mobile phone desktop displays icons corresponding to multiple applications, and the mobile phone can open the application corresponding to the icon by responding to the user's touch operation on the icon. The touch operation can be, for example, single-click, double-click, press, slide, etc. In response to the user's click operation on the memo (application 1) icon 201, the mobile phone opens the application and displays the application interface of the application.

[0053] Among them, during the application startup process, the mobile phone will display the application icon and application window according to the pre-set animation effect, so as to provide users with a better visual effect of starting the application. For example, after the mobile phone detects that the user clicks the application icon, the desktop application process displays the application icon animation, the window management service draws the application window and calls the system service process to display the application window animation after the application icon animation, completing the display process of the application startup animation. The application startup animation preset in the mobile phone contains two parts of animation elements, one is the application icon (icon) animation, and the other is the application window (window) animation. After the mobile phone detects the user's operation of starting the application, it calls the desktop process to execute the application icon animation, and then calls the system service (SystemServer) process to execute the application window animation.

[0054] like Figure 2 As shown in (b), when the mobile phone has opened the memo (application 1), in the application interface 202 of the memo (application 1), the mobile phone responds to the user's upward swipe gesture to exit the memo 2 (application 1). At this time, the mobile phone turns on the exit animation of the memo (application 1).

[0055] like Figure 2 As shown in (c), the mobile phone is in the process of exiting the memo (application 1), or in other words, in the process of exiting the memo (application 1), in response to the user clicking the icon 203 of the recorder (application 2), at this time, the desktop of the mobile phone is as follows Figure 2 As shown in (d) , the icon position 204 of the memo (application 1) is blank.

[0056] Among them, since the mobile phone receives the user's click operation on the recorder (application 2) icon 203 during the exit animation of the memo (application 1), that is, the exit animation of the memo (application 1) has not yet ended, at this time, the memo (application 1) icon 205 has not been displayed normally, such as Figure 2 as shown in (c).

[0057] Since the memo (application 1) icon is blank for a very short time and will be restored soon, the human eye will feel flickering.

[0058] Therefore, an embodiment of the present application provides a display control method, which can continuously display the application icon on the desktop of the electronic device when another application 2 is started in response to a user's operation during the process of the electronic device exiting application 1, thereby improving the visual experience.

[0059] The software system of the mobile phone can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. This application embodiment takes the Android system with a layered architecture as an example to illustrate the software structure of the mobile phone. Figure 3 , Figure 3 A software structure block diagram of a mobile phone provided in an embodiment of the present application.

[0060] like Figure 3 As shown, the layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application (App) layer, application framework (FWK) layer, native service layer and hardware abstract layer (HAL).

[0061] The application layer can include a series of application packages, which can include system applications and third-party applications.

[0062] like Figure 3 As shown, the application package can include memo, gallery and Android desktop launcher. The Android desktop launcher includes AnimBooster. Among them, AnimBooster can be used to register monitoring tasks. The application package can also include camera, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

[0063] The application layer mainly interacts with the application framework layer and defines some window layouts, motion parameters, animation execution logic, etc. During the animation process, the application layer passes the window attribute information to Surfaceflinger through the application framework layer for synthesis, and finally passes it to the HAL layer for interactive display with the hardware.

[0064] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0065] like Figure 3 As shown, the application framework layer may include a window manager, an activity manager, and a view system. The application framework layer may also include a content provider, a resource manager, a notification manager, an input manager, and the like.

[0066] The window manager provides window management services (WMS). WMS can be used for window management, window animation management, surface management, and as a transfer station for the input system.

[0067] The activity manager can provide activity management services (AMS), which can be used to start, switch, and schedule system components (such as activities, services, content providers, and broadcast receivers) as well as manage and schedule application processes.

[0068] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0069] Content providers are used to store and retrieve data and make it accessible to applications. This data can include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0070] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0071] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0072] The input manager can provide input management services (IMS), which can be used to manage system input, such as touch screen input, key input, sensor input, etc. IMS takes events from input device nodes and distributes them to appropriate windows through interaction with WMS.

[0073] The local service layer includes surfaceflinger and rendering engine.

[0074] The hardware abstraction layer runs in user space, encapsulates kernel layer drivers, and provides a calling interface to the upper layer. Figure 3As shown, the hardware abstraction layer includes a hardware composer (HWC) and Gralloc.

[0075] HWC is the HAL layer module for window (layer) synthesis and display in Android, providing hardware support for Surfaceflinger service.

[0076] Gralloc means Graphics Alloc. Gralloc encapsulates all buffer operations on the frame buffer.

[0077] Among them, the solution of the embodiment of the present application mainly involves application layer logic, and the underlying business logic is no longer described in detail.

[0078] In the embodiment of the present application, the mobile phone exits the application in response to the user's gesture operation as an example for explanation. For example, the mobile phone exits the application in response to the user's upward swipe gesture on the application interface.

[0079] In the scenario where the phone exits application 1 in response to the user's swipe-up gesture, the icon animation corresponding to application 1 can be divided into two stages: (1) after the phone detects that the user's finger has left the phone screen, the phone's application layer will calculate the icon's animation parameters in advance and send them to the Surfaceflinger of the application framework layer for drawing; (2) immediately respond to the showicon method to draw the icon view.

[0080] In the first paragraph: The drawing process is carried by the icon layer (also called the icon window layer), so the animation will disappear when the icon layer is destroyed. Among them, the icon layer is mounted on the app layer, so if the app layer is destroyed, the icon layer will also be destroyed. Among them, the icon displayed in the exit animation of application 1 belongs to the icon layer.

[0081] In the second paragraph: The mobile phone can capture Trace logs and screen recording analysis. After the mobile phone executes the showicon method, the icon will be displayed within one frame. When the business is heavy, the time from the showicon method being sent to the icon display is uncontrollable. Among them, the duration is between 40ms and 70ms on average. Among them, heavy business means that when the mobile phone exits application 1, the mobile phone must draw the exit animation of application 1. In the process of executing the exit animation of application 1, the mobile phone responds to the user's click operation on application 2, and immediately stops the exit animation of application 1 and draws the startup animation of application 2.

[0082] Among them, the above paragraph (1) refers to the process of exiting from the application interface to the desktop, and the above paragraph (2) refers to the process of displaying the icon on the desktop. It can be seen that since the exit animation includes the process of displaying the icon on the desktop, it will appear before the end of the exit animation, and the user can open application 2 on the desktop.

[0083] It should be noted that the icon will also be displayed in the above paragraph (1), but will be destroyed later. The icon will also be displayed in the above paragraph (2) after the previous one is destroyed.

[0084] See also Figure 4 , Figure 4 A schematic diagram of an application exit animation provided in an embodiment of the present application. Figure 4 As shown, the above paragraph (1) refers to Figure 4 (a) to Figure 4 (c) process. Figure 4 As shown in (a), in the memo application interface 401, the mobile phone detects the user's upward sliding operation, and at this time, the mobile phone starts to play the exit animation of the memo. Figure 4 As shown in (b), the icon layer 404 is mounted on the app layer 403. During the exit animation, on the desktop layer 402, the icon layer 404 and the app layer 403 are scaled down in proportion. Figure 4 As shown in (c), the icon layer and the app layer return to the original display position corresponding to the memo. At this time, since the exit animation of the memo has not yet ended, the memo icon 405 has not been displayed normally. During this process, the mobile phone detects that the user clicks the recorder icon 406.

[0085] like Figure 4 As shown, the above paragraph (2) refers to Figure 4 (d) to Figure 4 The mobile phone draws the memo icon. When the mobile phone has not completed drawing the memo icon, Figure 4 As shown in (d), the memo icon position 407 is blank. When the mobile phone completes drawing the memo icon, Figure 4 As shown in (e), the memo icon 408 is displayed normally.

[0086] Therefore, during the application exit animation, if the animation between the above-mentioned paragraph (1) and the above-mentioned paragraph (2) is not connected well, the icon position of the above-mentioned memo will be blank first and then redisplayed.

[0087] See also Figure 5 , Figure 5 A schematic diagram of a time point for drawing an icon provided in an embodiment of the present application. Figure 5As shown, the first time point t1 is the time point when showicon is called. The second time point t2 is the time point when the icon disappears, that is, the icon is hidden at time t2. The third time point t3 is the time point when the icon appears, that is, the icon is displayed at time t3. Figure 5 As shown, the duration T between the second time point t2 and the third time point t3 is 37ms. After the showicon method is issued, if the icon cannot be displayed within the preset duration, the icon layer is destroyed, and the icon position of application 1 on the desktop will be blank. The preset duration is related to the duration of a frame, which can be about 20ms.

[0088] Therefore, if the time point of icon drawing is Figure 5 As shown in the figure, the time from the time the icon is hidden to the time the icon is displayed is 37ms, which means that the time from the time the showicon method is issued to the time the icon is displayed exceeds 20ms. Figure 5 During the process shown, the icon may temporarily disappear and then reappear, causing the icon to flicker visually to the user.

[0089] See also Figure 6 , Figure 6 This is a business timing diagram of a display control method provided in an embodiment of the present application. Figure 6 As shown, in the scenario where the mobile phone has opened application 1 and is playing the exit animation of application 1, after the mobile phone receives the user's click operation on application 2, the mobile phone responds to the user's click operation on application 2 and starts application 2. At this time, the mobile phone quickly stops the current swipe-up exit animation of application 1 and executes the startActivity. Then, the mobile phone sends a message to the gesture animation controller (GestureAnimationController) to instruct the mobile phone to stop the swipe-up animation to return to the desktop.

[0090] It should be noted that before the mobile phone receives the user's click operation on application 2, the mobile phone has already displayed the desktop and the icon corresponding to application 2. Therefore, the mobile phone can receive the user's click operation on application 2 to start application 2.

[0091] When the animation ends (onAnimationEnd), the phone sends a message to other activity interfaces using gesture navigation (OtherActivityInputConsumerEx), calls the showicon method, and sends the showicon method to the desktop animation utility class (LauncherAnimUtils).

[0092] Among them, OtherActivityInputConsumerEx can indicate that you are currently in other activities and want to return to the Android system desktop launcher through other gestures.

[0093] Then, the phone executes startActivity, and the specific steps include: the phone destroys the app layer of the original application 1, then the icon layer mounted on the app layer is also destroyed, and the current slide-up exit animation is interrupted. Then, the icon layer is re-mounted on the app layer of the new application 2.

[0094] Among them, the icon layer is destroyed, but at this time, the icon of application 1 has not been drawn yet, so at this time, the icon position of application 1 on the desktop is displayed blank.

[0095] Therefore, in the process of the above-mentioned display control method, since the exit window animation and the display view icon animation are not well connected during the process of stopping the upward sliding exit animation of application 1, as a result, during the exit process of application 1, if the user responds to the click operation of application 2, the icon of application 1 appears blank.

[0096] In the embodiment of the present application, clicking to start an application may include three types: (1) regular clicking to start an application; (2) clicking the original icon to start an application during the exit process; (3) clicking other icons to start an application during the application exit process. Figure 7 , Figure 7 A logical schematic diagram of a click-to-start application provided in an embodiment of the present application.

[0097] like Figure 7 As shown, the mobile phone responds to the user's click operation on the application icon, and the mobile phone determines whether the click operation is a regular click to start the application. Among them, regular click to start the application means that the mobile phone responds to the user's click operation on a certain application. In the process from the mobile phone responding to the user's click operation on the application icon to the mobile phone displaying the first frame interface of the application, the mobile phone does not receive other operations from the user. Then, in response to the user's regular click operation on the application icon, the mobile phone starts the sinking process of the application and starts the startup animation of the application. In other words, the regular click to start the application is the application startup caused by clicking the icon after the previous application exit animation is completely completed.

[0098] It should be noted that the time interval between the moment when the mobile phone exits application 1 and the moment when the user clicks to start other applications is generally no more than 40ms. If the time interval between the moment when the mobile phone exits application 1 and the moment when the user clicks to start other applications is more than 40ms, then it can be considered that at this time, the mobile phone has completed the sliding-up exit animation of application 1, and the icon of application 1 is already in a normal display state. At this time, the situation in which the mobile phone responds to the user's click to start other applications is actually in the above-mentioned conventional click-to-start application scenario.

[0099] If the mobile phone determines that the click operation is not a regular click operation, the mobile phone determines whether the click operation is a click operation on the icon corresponding to the original application during the application exit process. If the mobile phone determines that the mobile phone is a click operation on the icon corresponding to the original application during the application exit process, at this time, the mobile phone responds to the user's click operation on the icon corresponding to the original application and starts the original application. Specifically, the mobile phone pauses the current swipe-up exit animation of the application and executes the reverse startup animation of the application. It should be noted that the reverse startup animation is executed without sinking logic.

[0100] If the mobile phone determines that the click operation is not a click operation on the icon of the original application during the application exit process, the mobile phone determines whether the click operation is a click operation on other application icons during the application exit process. If the mobile phone determines that the click operation is a click operation on other application icons during the application exit process, the mobile phone pauses the current slide-up exit animation and displays the startup animation of other applications using the above-mentioned dynamic sinking transformation method.

[0101] The application switching method in the embodiment of the present application is applied to the third scenario mentioned above, that is, the scenario in which the mobile phone clicks on the icon of other applications in response to the above-mentioned application exit process.

[0102] In the embodiment of the present application, the mobile phone can solve the problem of icon flickering in the above scenario by changing the original animation business logic. Specifically, the mobile phone can decouple the showicon method from the original onAnimationEnd process, register a monitoring task in the application layer, and then perform the end process of the sliding-up exit animation of application 1 after monitoring that the icon drawing of application 1 is completed. Then, start the startActivity process of the new application and destroy the icon layer. In this way, this solution can make the viewicon icon appear first, and then destroy the exit animation drawn by surfaceflinger. Therefore, the above solution can ensure that there will be no blank space in the icon position, thereby solving the problem of flickering application icons.

[0103] In the above process, the time of starting the startup animation of application 2 is delayed. The startup animation of application 2 will be started only after the icon of application 1 is drawn.

[0104] It should be noted that the showicon method is part of the onAnimationEnd process, and in the embodiment of the present application, the showicon method is decoupled from the original onAnimationEnd process, so that the showicon method can draw the icon in advance.

[0105] See also Figure 8 , Figure 8 A business timing diagram of a display control method provided in an embodiment of the present application. Figure 8 As shown, in the scenario where the mobile phone has already opened application 1, if the mobile phone receives a user click operation on application 2 during the process of exiting application 1, the mobile phone responds to the user's click operation on application 2 and starts application 2. At this time, the mobile phone can determine that it is currently in the scenario of clicking to start other applications during the process of exiting application 1.

[0106] At this time, the mobile phone sends a message to the animation utility class (LauncherAnimUtils) on the desktop, calls the showicon method, and draws the view icon.

[0107] In addition, the mobile phone delays starting the startup animation of application 2 (delayStartActivityInner).

[0108] Then, the phone sends a message to AnimBooster to register a frame drawing listener (setFirstDrawListener). "Registration" generally refers to associating an object (usually a callback function or a listener) with an event so that the corresponding operation can be performed when the event occurs.

[0109] In the embodiment of the present application, the mobile phone registers a monitoring task for icon drawing, that is, associates a monitor with the icon drawing completion event of application 1. After the mobile phone monitors that the icon drawing of application 1 is completed, it then performs the end process of the subsequent sliding up exit animation of application 1 (for example, destroying the icon layer). Among them, only one frame is needed to draw the icon. Therefore, when the mobile phone monitors that one frame of image drawing is completed, it means that the icon drawing of application 1 is completed.

[0110] After AnimBooster registers the frame drawing listener, when the second frame starts drawing, the phone removes the listener and executes the subsequent process.

[0111] At this time, the mobile phone sends a message to the gesture animation controller (GestureAnimationController) to instruct to stop the sliding up and returning to the desktop animation (endReturnHomeAnim).

[0112] Then, the phone executes startActivity, and the specific steps include: the phone destroys the app layer of the original application 1, then the icon layer mounted on the app layer is also destroyed, and the current slide-up exit animation is interrupted. Then, the icon layer is re-mounted on the app layer of the new application 2.

[0113] In this way, since the view icon of application 1 has been drawn through the showicon method before the mobile phone destroys the original app layer of application 1, the icon of application 1 can still be displayed on the desktop after the original app layer of application 1 is destroyed, and the icon of application 1 will not be blank.

[0114] In summary, the above display control method can register a monitoring task in the scenario where the user receives a startup operation of application 2 during the process of exiting application 1 on the mobile phone, and after monitoring that the icon of application 1 is drawn, the end process of the sliding-up exit animation of application 1 is performed. Then, the startup animation of application 2 is started. In this way, the display control method provided in the embodiment of the present application can make the icon of application 1 displayed first, and then destroy the exit animation of application 1, ensuring that there will be no blank space in the icon position of application 1, thereby solving the problem of flickering application icons.

[0115] In the embodiment of the present application, the key pseudo code of the above display control method may be:

[0116]

[0117] When a mobile phone starts an application, if it starts another application while swiping up to exit the application, the view icon of application 1 will be displayed first. The mobile phone will register a view drawing listener to monitor whether the view icon has been drawn. If the mobile phone detects that the view icon has been drawn, that is, it is drawing the second frame of the image, then the mobile phone removes the listener and pauses the swipe up exit animation of the application. Then, the mobile phone starts the startup animation of other applications.

[0118] Generally speaking, it only takes one frame to draw a view icon. Therefore, the phone can remove the listener when drawing the second frame of the image and continue the subsequent process.

[0119] In the embodiment of the present application, the key codes of the above display control method can be referred to as follows:

[0120]

[0121] See also Fig. 9 , Fig. 9 A schematic diagram of time point comparison of icon drawing provided in an embodiment of the present application. Fig. 9 As shown in (a), in the existing solution, after the mobile phone calls the showicon method, it takes 80ms to draw a frame. Since the startup animation and exit animation in the existing solution are not displayed in a dynamic sinking transformation manner, in the overload scenario of exiting application 1 and starting application 2, the number of binder calls will be too many, causing the mobile phone to be overloaded, which in turn affects the time to draw a frame.

[0122] Therefore, after the showicon method is issued, it takes too long to draw a frame of image, and the icon layer has been destroyed at this time, so the icon position of application 1 will be blank.

[0123] like Fig. 9 As shown in (b), after applying the display control method provided in the embodiment of the present application, after the mobile phone calls the showicon method, the time it takes to draw a frame is very short, for example, 10ms. Since the startup animation and exit animation in the embodiment of the present application are not displayed in a dynamic sinking transformation manner, the number of binder calls during the animation process is greatly reduced. Therefore, in the overload scenario where application 2 is started again during the process of exiting application 1, the time it takes to draw a frame will not be affected. As a result, when the mobile phone starts application 2 during the process of swiping up to exit application 1, the icon of application 1 can be drawn in advance before the exit animation of application 1 ends, and the icon of application 1 can be always displayed.

[0124] In the embodiment of the present application, if the mobile phone starts application 2 in the process of swiping up to exit application 1, the above display control method is applied, and by registering the view drawing monitor, it is monitored that the view icon has been drawn, and the swipe-up exit animation of the application is paused. Then, the mobile phone starts the startup animation of other applications. Then, in the scenario where the mobile phone starts application 2 in the process of swiping up to exit application 1, the schematic diagram of the application icon display can be referred to Fig.10 .

[0125] like Fig.10 As shown in (a), the mobile phone desktop displays icons corresponding to multiple applications. In response to the user clicking the icon 901 of the memo (application 1), the mobile phone opens the application and displays the application interface of the application.

[0126] like Fig.10 As shown in (b), when the mobile phone has opened the memo (application 1), in the application interface 902 of the memo (application 1), the mobile phone exits the memo 2 (application 1) in response to the user's upward swipe gesture. At this time, the mobile phone turns on the exit animation of the memo (application 1).

[0127] like Fig.10 As shown in (c), the mobile phone is in the process of exiting the memo (application 1), or in the process of exiting the memo (application 1), in response to the user clicking the icon 903 of the recorder (application 2), at this time, the icon 904 of the memo (application 1) is displayed normally, as shown in FIG. Fig.10 as shown in (d).

[0128] The display control method provided in the embodiment of the present application can solve the problem of flickering icon of application A when application B is immediately launched by the electronic device in the process of swiping up to exit application A in the scenario of application dynamic sinking. Among them, dynamic sinking is a unique dynamic effect optimization processing logic, and the problem of flickering icon of application A is also unique to this logic. This solution can keep the icon of application A displayed on the desktop of the electronic device when application B is immediately launched in the process of swiping up to exit application A, thereby improving the visual experience.

[0129] Among them, this solution can register a monitoring task. After monitoring that the icon of application A has been drawn, the swipe-up exit animation of the application will be paused, and the startup animation of application B will be started, thereby effectively controlling the timing and connection between the window animation and the view animation.

[0130] The following will describe the implementation of the embodiment of the present application in detail with reference to the accompanying drawings. Taking the above electronic device as a mobile phone as an example, the hardware structure of the electronic device 100 is introduced. The embodiment of the present application is described by taking the electronic device as a mobile phone as an example. Fig.11 FIG. 1 shows a schematic diagram of the hardware structure of a mobile phone 100. Fig.11 As shown, the mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

[0131] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may include more or fewer components than shown in the figure, or combine some components, or separate some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0132] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0133] The controller may be the nerve center and command center of the mobile phone 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0134] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0135] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0136] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0137] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the mobile phone 100. While the charging management module 140 is charging the battery 142, it may also power the mobile phone 100 through the power management module 141.

[0138] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160.

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

[0140] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in mobile phone 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0141] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the mobile phone 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0142] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate 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 the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0143] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the mobile phone 100. 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 the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0144] In some embodiments, the antenna 1 of the mobile phone 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the mobile phone 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0145] The mobile phone 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

[0146] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the mobile phone 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0147] In the embodiment of the present application, the display screen 194 can display a desktop, on which icons of various applications are displayed.

[0148] The mobile phone 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0149] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0150] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the mobile phone 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the mobile phone 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0151] The mobile phone 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor.

[0152] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

[0153] The pressure sensor is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor can be set on the display screen 194. There are many types of pressure sensors, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor, the capacitance between the electrodes changes. The mobile phone 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation acts on the display screen 194, the mobile phone 100 detects the touch operation intensity according to the pressure sensor. The mobile phone 100 can also calculate the touch position according to the detection signal of the pressure sensor. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0154] The fingerprint sensor is used to collect fingerprints. The mobile phone 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0155] A touch sensor is also called a "touch control device". The touch sensor can be arranged on the display screen 194. The touch sensor and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor is used to detect touch operations acting on or near it. The touch sensor can pass 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 can also be arranged on the surface of the electronic device 100, which is different from the position of the display screen 194.

[0156] In the embodiment of the present application, the touch sensor can detect a click operation, a sliding operation, etc. performed by a user on the display screen.

[0157] The key 190 includes a power key, a volume key, etc. The key 190 can be a mechanical key or a touch key. The mobile phone 100 can receive key input and generate key signal input related to the user settings and function control of the mobile phone 100.

[0158] The methods in the following embodiments can all be implemented in the mobile phone 100 having the above hardware structure.

[0159] The present application also provides a chip system, such as Fig.12 As shown, the chip system 1100 includes at least one processor 1101 and at least one interface circuit 1102. The processor 1101 and the interface circuit 1102 can be interconnected via lines. For example, the interface circuit 1102 can be used to receive signals from other devices (such as a memory of an electronic device). For another example, the interface circuit 1102 can be used to send signals to other devices (such as processor 1101). Exemplarily, the interface circuit 1102 can read instructions stored in the memory and send the instructions to the processor 1101. When the instructions are executed by the processor 1101, the electronic device can execute the various steps in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in the embodiments of the present application.

[0160] An embodiment of the present application also provides a computer storage medium, which includes computer instructions. When the computer instructions are executed on the above-mentioned electronic device, the electronic device executes each function or step executed by the mobile phone in the above-mentioned method embodiment.

[0161] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute each function or step executed by the mobile phone in the above method embodiment.

[0162] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0163] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0164] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0165] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0166] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0167] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A display control method, characterized in that: Applied to an electronic device, the electronic device has a first application and a second application installed therein, the method comprising: The electronic device displays a first application interface of the first application; In response to the user's exit operation on the first application, the electronic device plays an exit animation of the first application; During the process of the electronic device playing the exit animation of the first application, the electronic device responds to the user's start operation of the second application in the desktop interface, and the first icon of the first application continues to be displayed in the desktop interface of the electronic device.

2. The method according to claim 1, characterized in that The electronic device responds to a user's start operation on the second application in the desktop interface, and the desktop interface of the electronic device keeps displaying the first icon of the first application, including: The electronic device draws the first icon in response to a user's start-up operation on the second application; After detecting that the first icon is drawn, the electronic device stops playing the exit animation of the first application, and the first icon of the first application continues to be displayed in the desktop interface of the electronic device.

3. The method according to claim 2, characterized in that After the electronic device detects that the first icon is drawn and stops playing the exit animation of the first application, the method further includes: The electronic device plays a startup animation of the second application.

4. The method according to claim 2 or 3, characterized in that: After detecting that the first icon is drawn, the electronic device stops playing the exit animation of the first application, including: The electronic device registers a monitoring task for monitoring whether the first icon is drawn; After detecting that the first icon is drawn, the electronic device stops playing the exit animation of the first application.

5. The method according to claim 4, characterized in that The method further comprises: After monitoring that the first icon is drawn, the electronic device removes the monitoring task.

6. The method according to any one of claims 1, 2, 3 and 5, characterized in that: The method further comprises: The interval between the exit operation and the start operation is less than or equal to 400 milliseconds.

7. The method according to any one of claims 2, 3 and 5, characterized in that: The stopping playing the exit animation of the first application includes: The electronic device destroys the application layer and the icon layer mounted on the application layer; the first icon displayed in the exit animation of the first application belongs to the icon layer.

8. The method according to any one of claims 2, 3 and 5, characterized in that: In the process of the electronic device playing the exit animation of the first application, before the electronic device responds to the user's start operation of the second application in the desktop interface, the electronic device further includes: The electronic device determines whether the exit animation of the first application has finished playing when detecting a touch operation of the user on the desktop interface; If the electronic device detects that the exit animation of the first application has not finished playing when the user performs a touch operation on the desktop interface, determining whether the application targeted by the touch operation is a second application; If the application targeted by the touch operation is a second application, the electronic device is in the process of playing an exit animation of the first application, and the electronic device detects a user's startup operation on the second application in the desktop interface.

9. An electronic device, characterized in that: The electronic device comprises: a display screen, a memory and one or more processors; the display screen, the memory and the processor are coupled; the memory is used to store computer program code, and the computer program code comprises computer instructions, and when the computer instructions are executed by the electronic device, the electronic device executes the method as described in any one of claims 1-8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed in an electronic device, the electronic device executes the method according to any one of claims 1 to 8.

11. A computer program product, characterized in that The computer program product includes instructions, and when the instructions are executed in an electronic device, the electronic device executes the method according to any one of claims 1 to 8.

Images