Display device and method of configuring a transition
Patent Information
- Application Number
- CN202510884069.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-27
- Publication Date
- 2026-10-30
- Estimated Expiration
- 2045-06-27
AI Technical Summary
[0005]本申请提供一种显示设备及过场动画配置方法,以解决显示设备在应用切换过程中,因各应用对应的过场动画资源ID不统一容易导致动画效果加载错乱的问题
Smart Images

Figure CN120803582B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of display device technology, and in particular to a display device and a method for configuring transition animations. Background Technology
[0002] Applications running on the display device can execute animated entrance and exit effects when switching between them, and these animations are synchronized to ensure smooth and visually appealing application transitions. The animation effects can be predefined; during the transition, the application only needs to access the corresponding configuration file to implement the animation.
[0003] However, due to the iterative updates of the Android system, application switching is implemented in cross-application stack scenarios. In order to ensure the stability and security of operation in cross-task stack switching scenarios, the Android system will forcibly take over the animation control, that is, use the system's default animation effect as the switching animation.
[0004] To avoid the system forcing the default animation, custom animation effects can be implemented by compiling independently based on a plug-in framework. However, in this approach, different plug-ins may assign different resource IDs to the same animation effect resources, causing the plugins of different applications to access inconsistent animation effect resources during the switching process, resulting in incorrect animation effect loading. Summary of the Invention
[0005] This application provides a display device and a method for configuring transition animations to solve the problem that the inconsistent transition animation resource IDs of different applications can easily lead to disordered animation loading during application switching.
[0006] In a first aspect, this application provides a display device, including a display and a controller. The controller is configured to: In response to an application switching command, obtain the developer identifiers of the first and second applications. The first application is the one currently running in the foreground, and the second application is the one about to be switched to the foreground. The developer identifiers are used to identify the developers of the first and second applications.
[0007] If the developer identifiers of the first application and the second application are the same, then the first animation effect configuration file is obtained from the shared resource library of the first application and the second application. The exit animation configuration information of the first animation effect configuration file is configured according to the exit animation configuration information of the first animation effect configuration file, and the entrance animation of the second application is configured according to the entrance animation configuration information of the first animation effect configuration file.
[0008] If the developer identifiers of the first application and the second application are different, then the second animation effect configuration file is obtained from the default resource library of the first application or the third animation effect configuration file is obtained from the default resource library of the second application; the exit animation of the first application is configured according to the entrance animation configuration information of the second animation effect configuration file or the third animation effect configuration file, and the entrance animation of the second application is configured according to the exit animation configuration information of the second animation effect configuration file or the third animation effect configuration file.
[0009] This ensures that in application switching scenarios, the entrance and exit animations for the first and second applications belong to the same animation resources, thereby avoiding the problem of inconsistent animation resource IDs caused by different applications, which leads to animation loading errors.
[0010] In some feasible embodiments, the controller retrieves a first animation effect configuration file from a shared resource library of the first and second applications, specifically configured as follows: Obtain the name of the first animation resource and the first resource query interface for the first application.
[0011] Access the shared resource table through the first resource query interface.
[0012] The first animation resource ID is retrieved from the shared resource table based on the first animation resource name. The first animation resource ID is a unique identifier for the animation resource used by the first application when it enters or exits the foreground. The shared resource table includes a mapping between resource names and resource IDs.
[0013] Retrieve the first animation effect configuration file from the shared resource library based on the first animation resource ID.
[0014] In this way, when the developer identifiers of the first application and the second application are the same, the first application can decide which animation effect to use. The first application can access the shared resource table to obtain the first animation resource ID based on the resource name, and then request the animation effect configuration file from the shared resource library based on the first animation resource ID. Based on the shared resource table and the shared resource library, it can be ensured that the first application and the second application use the same animation resources, avoiding animation errors caused by resource ID mismatch.
[0015] In some feasible embodiments, the controller is configured to retrieve the first animation effect configuration file from the shared resource library based on the first animation resource ID, and is further configured to: Obtain the resource sharing interface.
[0016] The first animation resource ID is sent to the second application via the resource sharing interface.
[0017] The second application is controlled to retrieve the first animation effect configuration file from the shared resource library based on the first animation resource ID.
[0018] In this way, the first application can share the animation resource ID to the second application through the resource sharing interface. The second application can then directly obtain the animation effect configuration file from the shared resource library based on the animation resource ID. This allows the first and second applications to use the same animation effect configuration file when the developer identifier is consistent, thus avoiding animation effect loading errors.
[0019] In some feasible embodiments, the controller is further configured to: (If the developer identifiers of the first application and the second application are different) Retrieve the API version number of the system used to support the operation of the first and second applications. The system API version is used to characterize the methods supported by the system for obtaining animation resources.
[0020] If the API version number is within the first preset range, then the third animation effect configuration file provided by the second application is obtained.
[0021] If the API version number is in the second preset range, then the second animation effect configuration file is obtained from the default resource library of the first application. The API version number in the second preset range is lower than the API version number in the first preset range.
[0022] In this way, even when the developers of the first and second applications have different identifiers, the configuration method for animation effects can be determined by judging the system's API version. Specifically, in higher version systems, the second application can act as the animation effect decision-maker to synchronize animation effects. In relatively lower version systems, the first application can act as the animation effect decision-maker to synchronize animation effects, adapting to the animation resource requirements of different system environments and ensuring the continuity and consistency of animation effects.
[0023] In some feasible embodiments, after the controller retrieves the third animation effect configuration file from the default resource library of the first application, it is further configured to: Configure the exit animation of the first application according to the entrance animation configuration information in the second animation effects configuration file.
[0024] Configure the entrance animation of the second application according to the exit animation configuration information in the second animation effects configuration file.
[0025] In this way, when the system's API version is within the second preset range, the first application can decide which animation effect to use and synchronize the animation effect to the second application to ensure that the animation effects of the first application and the second application are consistent.
[0026] In some feasible embodiments, the controller is further configured to: (If the developer identifiers of the first application and the second application are different) Retrieve the animation effect policy token and animation effect policy verification information. The animation effect policy token includes animation effect policy metadata. The animation effect policy metadata is data provided by the first application to limit the execution policy of the animation effect. The animation effect policy verification information is used to characterize the valid operating range of the animation effect.
[0027] If the animation effect strategy metadata is within a valid operating range, obtain the API version number of the system used to support the operation of the first and second applications.
[0028] If the animation effect strategy metadata is not in a valid operating range, retrieve the system's default animation effect configuration file. Configure the exit animation for the first application and the entrance animation for the second application based on the default animation effect configuration file.
[0029] In this way, the first application can provide an animation effect strategy token during the application switching process, so as to provide an animation effect execution strategy through the animation effect strategy token, to ensure that the animation effect will not affect the normal operation of the system during the execution process, thereby ensuring the stability of the system during application switching.
[0030] In some feasible embodiments, the controller is further configured to: obtain the animation effect policy token and animation effect policy verification information before performing the following steps: Control the first application to create animation effects strategy tokens.
[0031] The first application sends an animation effect policy token to the second application. This token is used to enable the second application to call the animation policy verification interface.
[0032] When the second application calls the animation strategy verification interface, it obtains the animation effect strategy token and animation effect strategy verification information.
[0033] In this way, the first and second applications can synchronize animation effect policy tokens, forming a two-layer animation effect policy verification process. On the one hand, it ensures that the animation effects of the first and second applications are consistent, and on the other hand, it ensures the stability and security of the animation effects when jumping across application stacks, as well as the operational stability of the system during application switching.
[0034] In some feasible embodiments, the animation effect policy metadata includes system-level policy metadata, application-level policy metadata, and window-level policy metadata. System-level policy metadata is used to limit the system memory required for the animation effect. Application-level policy metadata is used to limit the developer's execution permissions for the animation effect. Window-level policy metadata is used to limit the animation effect display permissions for the animation running window.
[0035] The controller executes the process of obtaining the animation effect policy token and animation effect policy verification information, and is also configured as follows: If any of the system-level policy metadata, application-level policy metadata, or window-level policy metadata is not in a valid operating range, obtain the system's default animation effect configuration file.
[0036] In this way, through multi-level strategy verification, the consistency and stability of animation effects across different applications and windows are ensured, avoiding animation failures due to insufficient permissions or resources, and further guaranteeing the overall efficiency of system operation and the smoothness of user experience.
[0037] In some feasible embodiments, the controller is also configured to: If the API version number is within the third preset range, retrieve the system's default animation effect configuration file. API version numbers within the third preset range are lower than those within the second preset range.
[0038] Configure the exit animation for the first application based on the entrance animation configuration information in the default animation effects configuration file.
[0039] Configure the entrance animation of the second application based on the exit animation configuration information in the default animation effects configuration file.
[0040] In this way, even if the API version is low, the system can automatically adapt to the default animation configuration, ensuring the continuity and stability of animation effects when switching between applications, and further optimizing the user experience.
[0041] Secondly, this application provides a method for configuring transition animations in an application, including: In response to an application switching command, obtain the developer identifiers of the first and second applications. The first application is the one about to be switched to the foreground, and the second application is the one currently running in the foreground. The developer identifiers are used to identify the developers of the first and second applications.
[0042] If the developer identifiers of the first application and the second application are the same, then the first animation effect configuration file is obtained from the shared resource library of the first application and the second application. The exit animation configuration information of the first animation effect configuration file is configured according to the exit animation configuration information of the first animation effect configuration file, and the entrance animation of the second application is configured according to the entrance animation configuration information of the first animation effect configuration file.
[0043] If the developer identifiers of the first and second applications are different, the second animation effect configuration file is obtained from the default resource library of the second application. The exit animation of the first application is configured according to the entrance animation configuration information in the second animation effect configuration file, and the entrance animation of the second application is configured according to the exit animation configuration information in the second animation effect configuration file. Attached Figure Description
[0044] To more clearly illustrate the technical solution of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0045] Figure 1 This is a schematic diagram illustrating the operation scenarios of a display device provided in some embodiments of this application; Figure 2 This is a schematic diagram of the hardware configuration of a display device provided in some embodiments of this application; Figure 3 This is a schematic diagram of the software configuration of a display device provided in some embodiments of this application; Figure 4 A schematic diagram illustrating the architecture of plug-ins, hosts, and software products provided in some embodiments of this application; Figure 5 Flowcharts illustrating the transition animation configuration provided in some embodiments of this application; Figure 6 A flowchart illustrating the first application for obtaining a first animation effect configuration file, provided in some embodiments of this application; Figure 7 Flowcharts illustrating the coordinated animation effects of a first application and a second application provided in some embodiments of this application; Figure 8 A flowchart illustrating the animation effect configuration of the first and second applications when the API version number provided in some embodiments of this application is within a first preset range; Figure 9 A flowchart illustrating the animation effect configuration of the first and second applications when the API version number provided in some embodiments of this application is within a second preset range; Figure 10 Animation effect verification flowchart provided for some embodiments of this application; Figure 11 This is a schematic diagram of the animation effect strategy token provided in some embodiments of this application; Figure 12 A flowchart for verifying single-layer animation effects provided in some embodiments of this application; Figure 13 A flowchart for verifying the two-layer animation effect provided in some embodiments of this application. Detailed Implementation
[0046] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application as detailed in the claims.
[0047] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.
[0048] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.
[0049] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.
[0050] The term "module" refers to any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.
[0051] In this embodiment, display device 200 generally refers to a device with screen display and data processing capabilities. For example, display device 200 includes, but is not limited to, smart TVs, mobile terminals, computers, monitors, advertising screens, wearable devices, virtual reality devices, augmented reality devices, etc.
[0052] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application. For example... Figure 1 As shown, users can operate the display device 200 via touch operation, mobile terminal 300, and control device 100. For example, control device 100 can be a remote control, stylus, gamepad, etc.
[0053] The mobile terminal 300 can function as a control device for human-computer interaction between the user and the display device 200. It can also function as a communication device for establishing a communication connection with the display device 200 and exchanging data. In some embodiments, the mobile terminal 300 can have software applications installed on it and communicate with the display device 200 via network communication protocols to achieve one-to-one control and data communication. Furthermore, it can transmit audio and video content displayed on the mobile terminal 300 to the display device 200 for synchronized display.
[0054] like Figure 1 The diagram also shows that the display device 200 communicates with the server 400 via various communication methods. This allows the display device 200 to communicate via a local area network (LAN), a wireless local area network (WLAN), and other networks.
[0055] Display device 200 can provide broadcast television reception function, and can also be equipped with intelligent network television function that provides computer support function, including but not limited to network television, smart television, Internet Protocol television (IPTV), etc.
[0056] Figure 2 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of display device 200.
[0057] In some embodiments, the display device 200 may include at least one of a tuner 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.
[0058] In some embodiments, detector 230 is used to collect signals from the external environment or signals interacting with the outside world. For example, detector 230 may include millimeter-wave radar, which can be used to detect whether a user is present within a preset range. Detector 230 may also include a voice acquisition unit to collect voice commands input by the user.
[0059] In some embodiments, the display 260 includes display function components for presenting images and driving components for driving image display. The display 260 is used to receive and display image signals output from the controller 250. For example, the display 260 can be used to display video content, image content, menu control interface components, and user control UI interfaces, etc.
[0060] In some embodiments, the communication device 220 is a component used to communicate with external devices or the server 400 according to various communication protocol types. The display device 200 may have multiple communication devices 220 depending on the supported communication methods. For example, when the display device 200 supports wireless network communication, it may have a communication device 220 with WiFi functionality. When the display device 200 supports Bluetooth connectivity, it needs to have a communication device 220 with Bluetooth functionality.
[0061] The communication device 220 enables the display device 200 to communicate with external devices or the server 400 via wireless or wired connections. Wired connections utilize data cables, interfaces, or other components to connect the display device 200 to external devices. Wireless connections utilize wireless signals or wireless networks. The display device 200 can directly establish a connection with external devices or indirectly through gateways, routers, or other connection devices.
[0062] In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and a first to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in memory. The controller 250 controls the overall operation of the display device 200.
[0063] In some embodiments, the controller 250 and the tuner 210 may be located in different separate devices, that is, the tuner 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.
[0064] In some embodiments, a user can input user commands through a graphical user interface (GUI) displayed on a display 260, and the user input interface receives user input commands through the graphical user interface (GUI).
[0065] In some embodiments, the audio output device 270 can be a built-in speaker of the display device 200 or an external audio output device connected to the display device 200. For the external audio output device connected to the display device 200, the display device 200 may also be provided with an external audio output terminal, through which the audio output device can be connected to the display device 200 to output sound from the display device 200.
[0066] In some embodiments, the user input interface 280 can be used to receive instructions input by a user. The user input interface 280 may include at least one of a microphone, touchpad, sensor, remote control, etc. The display device 200 can then receive user-input instructions based on the user input interface 280 to perform interactive functions with the user.
[0067] In some embodiments, to enable user interaction, the display device 200 may run an operating system. An operating system is a computer program that manages and controls the hardware and software resources of the display device 200. The operating system can control the display device to provide a user interface; for example, the operating system can directly control the display device to provide a user interface, or it can provide a user interface by running applications. The operating system also allows users to interact with the display device 200.
[0068] It should be noted that the operating system can be a native operating system based on a specific operating platform, a third-party operating system that is deeply customized based on a specific operating platform, or an independent operating system specifically developed for display devices.
[0069] An operating system can be divided into different modules or levels based on the functions it implements, for example... Figure 3 As shown, in some embodiments, the system is divided into four layers, from top to bottom: the Applications layer (referred to as the "Application Layer"), the Application Framework layer (referred to as the "Framework Layer"), the System Library layer, and the Kernel layer.
[0070] In some embodiments, the application layer provides services and interfaces for applications, enabling the display device 200 to run applications and interact with the user based on the applications. The application layer may contain at least one application, which may be a built-in Windows program, system settings program, or clock program of the operating system; or it may be an application developed by a third-party developer. In specific implementations, the application packages in the application layer are not limited to the examples above.
[0071] The framework layer provides application programming interfaces (APIs) and a programming framework for applications. The application framework layer includes predefined functions. It acts as a central processing unit, determining the actions taken by applications within the application layer. Through the API, applications can access system resources and obtain system services during execution.
[0072] like Figure 3As shown, the application framework layer in this embodiment includes a view system, managers, and content providers. The view system designs and implements the application's interface and interactions, and includes lists, grids, text boxes, and buttons. The managers include at least one of the following modules: an activity manager for interacting with all running activities in the system; a location manager for providing system services or applications with access to system location services; a package manager for retrieving various information related to application packages currently installed on the device; a notification manager for controlling the display and clearing of notification messages; and a window manager for managing icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.
[0073] In some embodiments, the Activity Manager manages the lifecycle of individual applications and common navigation and back functions, such as controlling application exit, opening, and back actions. The Window Manager manages all window programs, such as obtaining the screen size, determining if a status bar is present, locking the screen, capturing the screen, and controlling changes to the display window, such as shrinking the display window, shaking the display, or distorting the display.
[0074] In some embodiments, the system runtime library layer can provide support for the framework layer. When the framework layer is used, the operating system runs the instruction library contained in the system runtime library layer, such as the C / C++ instruction library, to implement the functions to be performed by the framework layer.
[0075] In some embodiments, the kernel layer is a functional layer situated between the hardware and software of the display device 200. The kernel layer can implement functions such as hardware abstraction, multitasking, and memory management. For example, ... Figure 3 As shown, hardware drivers can be configured in the kernel layer. The kernel layer can contain at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver, etc.
[0076] like Figure 4As shown, in the display device 200, a complete software product can consist of a host and multiple plugins forming a functional set during operation. For example, taking an e-commerce app as an example, the host can provide the overall framework for the e-commerce app, such as product display and user system. Plugins are responsible for specific functional modules, such as payment interfaces, logistics tracking, customer service chat, recommendation algorithms, etc. Through the collaborative work of various plugins, a smooth user experience is ensured when using the software product.
[0077] The host, as the core application framework, primarily provides the runtime environment, manages the lifecycle of plugins, and defines interfaces and communication protocols between plugins. Plugins correspond to independent functional modules and typically exist as APK (Android Application Package) files. Plugins require the host to load and provide context to function correctly. In some scenarios, the functional module corresponding to a plugin can be a function within an application of the software product; that is, a plugin can correspond to an application within the software product.
[0078] In this way, during application switching, the plugin can achieve seamless application switching through the host's coordination. Furthermore, the application switching process is not limited to foreground-to-background transitions. To ensure smoothness and visual appeal during switching, developers can pre-set transition animations for the application switching process. For example, when an application enters the foreground, it can use a left-slide-in animation effect, while when the switched-out application exits the foreground, it can use a right-slide-out animation effect to hide.
[0079] For ease of description, the application currently running in the foreground will be referred to as the first application, i.e., the caller, as described here and in the subsequent embodiments. The application about to enter the foreground will be referred to as the second application, i.e., the target.
[0080] It's understandable that there's a certain timing and coordination between the animation effects of the first and second applications to ensure a natural and smooth transition. This necessitates maintaining consistency in the animation effects during the configuration phase between the first and second applications.
[0081] The plugins corresponding to the first and second applications can access the animation effect configuration files prepared by the developer to configure the animation effects. To ensure the consistency of the animation effects, the developer can set the exit animation required by the first application and the entrance animation required by the second application in the animation effect configuration files. This allows the first and second applications to obtain the corresponding animation configuration information based on the identity parameters assigned by the system framework when switching applications, and then configure the animation effects according to the animation configuration information.
[0082] For example, when switching applications, the Android system framework can assign an "exit" identity parameter to the first application and an "entry" identity parameter to the second application. In this way, the first application can obtain the entry animation configuration information based on the exit identity parameter, and the second application can obtain the exit animation configuration information based on the entry identity parameter.
[0083] However, during the process of obtaining animation effect configuration files, the resource IDs corresponding to the plugins for the first and second applications can only be used internally. Therefore, if the resource IDs corresponding to the animation effect configuration files are different during plugin development, it will be difficult for the host to provide the same animation effect configuration for the application using different resource IDs provided by different plugins when the plugins for the first and second applications request resource IDs from the host. Even in scenarios where the resource IDs are the same, different resource ID settings by the plugins can lead to different configuration files for the same resource ID. Therefore, it is difficult to guarantee the consistency of animation effects between the first and second applications.
[0084] To address the above problems, this application provides a display device 200, which includes a display 260 and a controller 250. The display 260 can display transition animations corresponding to the application switching process during application switching. The controller 250 can configure transition animations for a first application and a second application during application switching. Figure 5 As shown, the controller is configured as follows: S100: In response to an application switching command, obtain the developer identifiers of the first and second applications.
[0085] In some embodiments, a developer identifier can be used to distinguish the developers of the first application and the second application. The developer identifier may include identifiers such as the application package name and application signing certificate. Based on these identifiers, it can be determined whether the first application and the second application belong to the same developer; that is, if the first application and the second application belong to the same developer, their corresponding developer identifiers are also the same; if the first application and the second application belong to different developers, their corresponding developer identifiers are different.
[0086] In this way, the corresponding animation can be executed based on the developer affiliation of the first and second applications. Effect configuration strategy.
[0087] S200: If the developer identifiers of the first application and the second application are the same, then obtain the first animation effect configuration file from the shared resource library of the first application and the second application. Configure the exit animation of the first application according to the exit animation configuration information in the first animation effect configuration file, and configure the entrance animation of the second application according to the entrance animation configuration information in the first animation effect configuration file.
[0088] In some embodiments, a first application and a second application belonging to the same developer can share some resources. That is, the developer can pre-set a shared resource library to store resources that the first application and the second application need to share, such as animation effect configuration files. The animation effect configuration files obtained by the first application and the second application from the shared resource library are collectively referred to as the first animation effect configuration file.
[0089] In this way, during the switching process between the first application and the second application, they can obtain the first animation effect configuration file from the shared resource library and configure their respective animation effects according to the first animation effect configuration file.
[0090] It is understandable that the first animation effect configuration file can include entrance configuration information and exit configuration information. The first application can obtain the exit configuration information based on the pre-assigned exit identity parameters, while the second application can obtain the entrance configuration information based on the pre-assigned entrance identity parameters, thereby ensuring the consistency of the animation effect.
[0091] In some embodiments, the process of the first application and the second application obtaining the first animation effect configuration file can be completed by the corresponding plugins of the first application and the second application. The plugins will read the corresponding animation files from the shared resource library. The process of the plugin reading the animation files will be described in subsequent embodiments.
[0092] S300: If the developer identifiers of the first application and the second application are different, then obtain the second animation effect configuration file from the default resource library of the first application or obtain the third animation effect configuration file from the default resource library of the second application; configure the exit animation of the first application according to the entrance animation configuration information of the second animation effect configuration file or the third animation effect configuration file, and configure the entrance animation of the second application according to the exit animation configuration information of the second animation effect configuration file or the third animation effect configuration file.
[0093] In some embodiments, the first and second applications, belonging to different developers, each have independent resource libraries, making it difficult for applications from different developers to directly access the resource libraries of other applications. That is, the first and second applications coordinate to unify animation effect configurations.
[0094] When the first and second applications belong to different developers, the decision-making power for animation effects needs to be delegated to the second application. That is, after obtaining the animation effect configuration file from its default resource library, the second application can actively call an interface to upload the animation effect configuration file or information to the system framework, so that the first application can read the animation effect configuration information from the system framework via an interface. This achieves a unified configuration method for animation effects with the second application as the decision-maker. The specific process of the second application uploading animation effect configuration information will be described in subsequent embodiments.
[0095] Thus, when the first and second applications belong to the same developer, the decision-making power for animation effects rests with the first application. The first application can coordinate with the second application to obtain the first animation effect configuration file from the shared resource library, ensuring consistency in animation effects. However, when they are developed by different developers, the second application becomes the decision-maker for animation effects, achieving cross-application animation effect uniformity by uploading configuration information to the system framework.
[0096] In other embodiments, the decision-making power for animation effects can be delegated to the first application, but the synchronization behavior of the first application's animation effects needs to be verified to ensure that it conforms to the animation effect configuration standards of the second application. This also ensures that the first and second applications maintain consistency in transition animations even when the developers are different.
[0097] like Figure 6 As shown, the controller is configured as follows during the configuration of the animation effects for the first application: Obtain the name of the first animation resource and the first resource query interface for the first application.
[0098] Access the shared resource table through the first resource query interface.
[0099] The first animation resource ID is retrieved from the shared resource table based on the first animation resource name. The first animation resource ID is a unique identifier for the animation resource used by the first application when it enters or exits the foreground. The shared resource table includes a mapping between resource names and resource IDs.
[0100] Retrieve the first animation effect configuration file from the shared resource library based on the first animation resource ID.
[0101] In some embodiments, the name of the first animation resource of the first application is pre-defined by the developer. For example, after the first application receives the application switching instruction and is assigned exit configuration parameters, the plugin corresponding to the first application can confirm the name of the required animation resource, such as "slide_in".
[0102] Furthermore, the host actively provides a resource query interface during application switching, allowing the plugins corresponding to the first application to access the shared resource table. The shared resource table records the first animation resource ID, which maps to the first animation resource name. In scenarios where the first and second applications belong to the same developer, the first animation resource ID serves as a globally unique ID, corresponding to a unique animation effect configuration file. This ensures that the plugins for both applications obtain the same animation effect configuration file through the first animation resource ID, thus maintaining consistency between the entrance animation of the first application and the exit animation of the second application.
[0103] It should be noted that the shared resource table and shared resource library are pre-set by the developers. Plugins belonging to the same developer can access the shared resource table and shared resource library to obtain target resources. Plugins can access the shared resource table and shared resource library through interfaces provided by the system architecture.
[0104] For example, a plugin can access the shared resource table using getHostResourceId("slide_in", "animation") to obtain the first animation resource ID corresponding to the current animation resource name.
[0105] Furthermore, the plugin can retrieve the animation effect configuration file from the shared resource library based on the first animation resource ID. For example, the plugin uploads the first animation resource ID to the system framework through the overridePendingTransition interface provided by the system framework. The system framework can receive the first animation resource ID through ActivityTaskManagerService and control the host to load the animation resource file corresponding to the first animation resource ID.
[0106] In addition, the plugin corresponding to the first application can send the first animation resource ID to the plugin of the second application. After receiving the first animation resource ID, the plugin corresponding to the second application can configure the exit animation using the same animation effect configuration method as the first application, thereby ensuring that the transition animations of the first application and the second application are consistent.
[0107] In this way, when the first application and the second application belong to the same developer, the first application is the decision-maker in the animation effect configuration stage. Based on cross-process communication, the first application can reach a consensus with the second application on the animation effect configuration, thereby ensuring the consistency of the transition animation.
[0108] like Figure 7As shown, the first application can coordinate animation effects with the second application via cross-process communication to ensure consistency of transition animations executed by the first and second applications during application switching scenarios. Specifically, the controller retrieves the first animation effect configuration file from the shared resource library based on the first animation resource ID, and is also configured as follows: Obtain the resource sharing interface.
[0109] The first animation resource ID is sent to the second application via the resource sharing interface.
[0110] The second application is controlled to retrieve the first animation effect configuration file from the shared resource library based on the first animation resource ID.
[0111] In some embodiments, the system framework can provide a resource-sharing interface, which enables cross-process communication between the first and second applications. For example, the first application can communicate with the second application using the binder cross-process communication method, thereby sending the first animation resource ID to the second application.
[0112] After receiving the ID, the second application can also trigger the system framework's ActivityTaskManagerService through the overridePendingTransition interface, and then the system framework will load the animation resource file corresponding to the ID into the second application through the host.
[0113] In this way, based on the support of cross-process communication, the first and second applications can ensure the consistency of entrance and exit animations when executing process animations, and prevent animation loading errors caused by the difficulty in unifying animation resources.
[0114] When the developer identifiers of the first and second applications are different, it is difficult for them to directly access each other's configured resource files. Therefore, it is necessary to combine the various interfaces provided by the system framework to unify the animation effect configuration of the first and second applications. When the system's API version number is different, its supported interface call capabilities also differ. Therefore, it is necessary to determine the decision-maker for animation effects based on the API version number of the system that supports the first and second applications, in order to adapt to the system's unified animation effect capabilities.
[0115] The controller 250 is configured as follows: Retrieve the API version number of the system used to support the operation of the first and second applications. The system API version is used to characterize the methods supported by the system for obtaining animation resources.
[0116] If the API version number is within the first preset range, then the second animation effect configuration file provided by the second application is retrieved.
[0117] If the API version number is in the second preset range, the second animation effect configuration file is obtained from the default resource library of the first application. The API version numbers in the second preset range are lower than those in the first preset range. The second animation effect configuration file is a pre-configured transition animation configuration file corresponding to the first application, and the third animation effect configuration file is a pre-configured transition animation configuration file corresponding to the second application. Controller 250 can determine the decision-maker for configuring animation effects based on different API version numbers, and then configure the animation effects of the first and second applications based on the animation effect configuration file corresponding to that decision-maker.
[0118] In some embodiments, the first preset range corresponds to system operating scenarios with API version numbers greater than or equal to 34, and the second preset range corresponds to system operating scenarios with API version numbers greater than or equal to 16 and less than 34. Since the API interfaces included in systems with different API version numbers differ, it is necessary to dynamically adjust the animation effect configuration strategy based on the API interface capabilities provided by the system.
[0119] In some embodiments, such as Figure 8 As shown, when the system's API version number is within the first preset range, the system can provide the overrideActivityTransition interface. Based on this interface, the second application can proactively report pre-configured animation effect configuration information, such as "swipe left to enter" and "swipe right to exit". The system framework, i.e., controller 250, can obtain the third animation effect configuration file reported by the second application and, based on the animation effect configuration information in the third animation effect configuration file...
[0120] Understandably, in Android 14+ systems (API level 34 or higher), the second application can act as the decision-maker in the animation configuration phase. The second application registers its pre-configured animation effects with the system framework, which then controls the loading of animations by both the first and second applications. Furthermore, even when the first and second applications belong to different developers, having the second application act as the decision-maker in the animation configuration phase, based on its proactive uploading of animation configuration information, can resolve resource isolation issues across task stacks, thereby ensuring consistency between the exit animation of the first application and the entrance animation of the second application.
[0121] In other embodiments, when the system's API version number is within a second preset range, the system framework can provide a `makeCustomAnimation` interface, based on which the first application can act as the decision-maker in the animation effect configuration phase. For example... Figure 9As shown, the first application, as the caller, can upload a second animation effect configuration file / configuration information to the system framework using the `makeCustomAnimation` interface. For example, `(makeCustomAnimation(enterAnim, exitAnim))`. After receiving the configuration information uploaded by the first application, the system framework can send the animation resource ID corresponding to the second animation effect configuration file to the window management service (WindowManagerService). The window management service then further configures an exit animation for the first application and an entrance animation for the second application based on the animation effect configuration information.
[0122] Thus, even if the system framework does not support the overrideActivityTransition interface, the makeCustomAnimation interface can still be used to flexibly configure animation effects. That is, even if the second application cannot act as the decision-maker for animation effects, the first application can still act as the decision-maker. By combining the resource scheduling capabilities provided by the makeCustomAnimation interface, the first and second applications can be controlled to load exit animation resources and entrance animation resources respectively.
[0123] In some embodiments, the controller 250 can configure the animation effects of the first application and the second application based on the animation effect configuration file uploaded by the first application, that is, the controller 250 is configured as follows: Configure the exit animation of the first application according to the entrance animation configuration information in the second animation effects configuration file.
[0124] Configure the entrance animation of the second application according to the exit animation configuration information in the second animation effects configuration file.
[0125] In some embodiments, the second animation effect configuration file may include parameters such as the form, duration, and gradient effect of the transition animation. The system framework can parse the second animation effect configuration file and configure the exit animation of the first application and the entrance animation of the second application according to the entrance configuration information and exit configuration information in the second animation effect configuration file.
[0126] It should be noted that, based on the animation effect configuration file uploaded by the first application, the system framework can uniformly configure the exit animation of the first application and the entrance animation of the second application to ensure the consistency and continuity of transition animations when switching applications. Furthermore, it can ensure that the consistency of transition animations between the first and second applications is maintained even when the system only provides a lower version of the API interface.
[0127] In some embodiments, the API version of some systems is lower than that in the second preset range. These systems struggle to support overly complex animation effects. Therefore, when such system versions are detected, the default animation effect configuration strategy pre-prepared in the system needs to be executed. The controller 250 is also configured as follows: If the API version number is within the third preset range, retrieve the system's default animation effect configuration file. API version numbers within the third preset range are lower than those within the second preset range.
[0128] Configure the exit animation for the first application based on the entrance animation configuration information in the default animation effects configuration file.
[0129] Configure the entrance animation of the second application based on the exit animation configuration information in the default animation effects configuration file.
[0130] In some embodiments, the system's API version number is less than 16, meaning that the system's current API interface is insufficient to support complex animation calls and unified processes. Therefore, to ensure the smoothness and continuity of application switching, the controller 250 can read the system's default animation effect configuration file.
[0131] Understandably, the default animation effect configuration file only defines basic parameters such as the entrance and exit methods of the exit and entrance animations, as well as the animation duration, to ensure that the application can maintain basic visual continuity and user experience when switching between low-version API environments.
[0132] In scenarios where the first and second applications belong to different developers, the controller 250 can determine the animation execution strategy based on the system's API version number. This ensures consistency and continuity between entrance and exit animations regardless of the system's API version. By doing so, animation effects during application switching are effectively guaranteed regardless of the system's API version, avoiding inconsistencies in animation performance caused by API version differences and improving the user's visual experience and operational smoothness when switching between different applications.
[0133] Understandably, transition animations generated during application switching also consume system resources. To ensure that these transition animations do not affect the stability of system operation, the configuration file for the transition animations needs to be validated. For example... Figure 10 As shown, controller 250 is configured as follows: Retrieve the animation effect policy token and animation effect policy verification information. The animation effect policy token includes animation effect policy metadata. The animation effect policy metadata is data provided by the first application to limit the execution policy of the animation effect. The animation effect policy verification information is used to characterize the valid operating range of the animation effect.
[0134] If the animation effect strategy metadata is within a valid operating range, obtain the API version number of the system used to support the operation of the first and second applications.
[0135] If the animation effect strategy metadata is not in a valid operating range, retrieve the system's default animation effect configuration file. Configure the entrance animation for the first application and the exit animation for the second application based on the default animation effect configuration file.
[0136] In some embodiments, before the animation effect is executed, it is necessary to verify the legality and stability of the animation effect to ensure that the animation effect runs smoothly and does not interfere with the system operation.
[0137] The controller 250 can acquire thresholds or restrictions related to the legality and stability of the current system's operation. Specifically, the controller 250 can acquire animation effect policy verification information. This verification information can exist in the form of thresholds, restrictions, etc. After acquiring the animation policy verification information, the controller 250 can compare it with the various parameters / conditions required for the animation effect to determine whether the animation effect can be executed.
[0138] The animation effect strategy token contains the execution strategy corresponding to the judgment results of various parameters / conditions. For example, based on the `setAllowOverrideSystem(true)` instruction in the animation effect strategy token, it is necessary to verify whether the current system allows custom animation effects to override system animations. Controller 250, based on the instruction of the animation effect strategy token and combined with the animation effect strategy verification information, determines whether the system allows custom animation effects. Then, if the system allows custom animations to override system animations, subsequent processing actions such as obtaining the system's API version number are executed.
[0139] If the system does not allow custom animations to override system animations, obtain the default animation effect configuration file, configure the entrance animation of the second application according to the entrance configuration information in the default animation effect configuration file, and configure the exit animation of the first application according to the exit configuration information in the animation effect configuration file.
[0140] Understandably, the animation effect policy verification information represents the valid operating range of the animation effect, while the animation effect policy token indicates the content to be verified and how to execute the corresponding policy based on the verification results. Therefore, the controller 250 can determine the feasibility of the animation effect by combining the animation effect policy token and the animation effect policy verification information, and execute subsequent actions based on the feasibility determination result. In this way, the system can flexibly adjust application animations while ensuring the legality and stability of the animation effects, thereby improving the user experience. At the same time, it avoids system operation risks caused by inappropriate animation effects, achieving a balance between animation effects and system performance.
[0141] like Figure 11 As shown, the animation effect strategy token includes animation effect strategy metadata. Based on the animation effect strategy metadata, the animation effect strategy token can have the ability to indicate the content to be checked and to indicate the execution of the corresponding strategy based on the check results.
[0142] In some embodiments, animation effect policy metadata includes system-level policy metadata, application-level policy metadata, and window-level policy metadata. For example, system-level policy metadata is used to limit the system memory required for the animation effect. Application-level policy metadata is used to limit the developer's running permissions for the animation effect. Window-level policy metadata is used to limit the display permissions of the animation effect in the window where the animation is running.
[0143] For example, if the current animation effect requires 1GB of system memory, when the controller 250 obtains the animation effect policy token and the animation effect policy verification information, it determines by comparison that the remaining memory of the current device is less than 1GB. Therefore, since the remaining memory does not meet the execution requirements of the animation effect, the controller 250 needs to forcibly start the reduction animation policy, such as using the system's default animation effect configuration file to configure the animation effects of the first and second applications.
[0144] Furthermore, controller 250 can perform multi-level verification at the application and window levels for animation effects. For example, during application-level verification, controller 250 can determine whether the developer's execution permissions for the animation effect are legitimate. If the developer's signature for the animation effect is on the system whitelist, controller 250 allows the animation effect to execute. Otherwise, controller 250 will refuse to execute the animation effect and log relevant security warnings in the system log. It can also configure animation effects for the first and second applications using the system's default animation effect configuration file.
[0145] For example, during window-level validation, controller 250 checks the permissions of the window where the animation is running, specifically whether the current window supports complex animations. If the current window supports complex animations, controller 250 allows the animation effects to execute. If the current window does not support complex animations, controller 250 uses the system's default animation effect configuration file to configure the animation effects for both the first and second applications.
[0146] During the verification process, the controller 250 checks against the verification items specified in the animation effect strategy token. These verification items include various key parameters and conditions to ensure the correct execution of the animation effect. The controller 250 checks each item one by one to ensure they are all within the valid operating range. If any of these verification items shows a result outside the valid range, i.e., exceeding a predetermined threshold or standard, the controller 250 will immediately stop the currently executing animation effect to prevent system instability or failure that may be caused by abnormal parameters.
[0147] To further ensure stable system operation, controller 250 also switches to the system's default animation effect profile, using preset standard parameters and settings. In this way, controller 250 ensures that the system maintains stable operation even under abnormal conditions, avoiding system crashes or other serious problems caused by abnormal animation effects. This mechanism not only improves system reliability but also ensures a consistent and smooth user experience.
[0148] In some embodiments, when the API version number provided by the system is within a second preset range, the decision-maker for the animation effect is the first application. That is, the first application forces the animation effect to synchronize with the second application through the `makeCustomAnimation` interface. Therefore, at this stage, the behavior of the first application needs to be verified to ensure that the current synchronized animation effect behavior is not malicious. The controller is configured as follows: Control the first application to create animation effects strategy tokens.
[0149] The first application sends an animation effect policy token to the second application. This token is used to enable the second application to call the animation policy verification interface.
[0150] When the animation strategy verification interface is called in the second reference, the animation effect strategy token and animation effect strategy verification information are obtained.
[0151] like Figure 12As shown, in some embodiments, before synchronizing the animation effects of the second application through the makeCustomAnimation interface, the first application can create an animation effect policy token to indicate verification. For example, animation effect policy metadata can be added using intent.putExtra() to form the final animation effect policy token.
[0152] In this way, controller 250 can obtain animation effect policy tokens and animation effect policy verification information based on the ActivityTaskManagerService interface, and verify the legality of the animation effect's operation. This ensures that the synchronization of animation effects between the first application and the second application complies with system security specifications, preventing malicious operations.
[0153] like Figure 13 As shown, in some embodiments, the first application performs the action of creating an animation effect strategy token during the startup phase of the second application to trigger the verification process. The first application can also send the animation effect strategy token to the second application via inter-process communication, so that the second application triggers the animation effect synchronization verification process again after startup. In this way, the system can effectively identify and prevent potential malicious behavior.
[0154] This creates a multi-layered verification mechanism, ensuring that each animation synchronization is performed under strict monitoring, further enhancing the overall security and stability of the system. Furthermore, in scenarios where the launch of a second application might impact the overall system operation, this multi-layered verification mechanism can further guarantee that the execution of animation effects will not affect the stability of system operation.
[0155] Furthermore, a multi-layered verification mechanism can enhance the security of verification. For example, in scenarios where tokens are maliciously tampered with, a multi-layered verification mechanism can promptly determine whether the animation effect synchronization behavior initiated by the first application complies with the system's security operation specifications.
[0156] In this way, the controller 250, based on a verification mechanism or a multi-layer verification mechanism, can effectively identify and block illegal animation effect synchronization requests, ensuring the security and stability of system operation and preventing malicious operations from negatively impacting the user experience. This significantly enhances the overall security capabilities of the system. Furthermore, it ensures smooth transitions of animation effects during application switching, avoiding interface stuttering or anomalies caused by animation conflicts, thereby improving user smoothness and experience.
[0157] This application also provides a method for configuring transition animations, including: In response to an application switching command, obtain the developer identifiers of the first and second applications. The first application is the one about to be switched to the foreground, and the second application is the one currently running in the foreground. The developer identifiers are used to identify the developers of the first and second applications.
[0158] If the developer identifiers of the first application and the second application are the same, then the first animation effect configuration file is obtained from the shared resource library of the first application and the second application. The exit animation configuration information of the first animation effect configuration file is configured according to the exit animation configuration information of the first animation effect configuration file, and the entrance animation of the second application is configured according to the entrance animation configuration information of the first animation effect configuration file.
[0159] If the developer identifiers of the first application and the second application are different, then the second animation effect configuration file is obtained from the default resource library of the first application or the third animation effect configuration file is obtained from the default resource library of the second application; the exit animation of the first application is configured according to the entrance animation configuration information of the second animation effect configuration file or the third animation effect configuration file, and the entrance animation of the second application is configured according to the exit animation configuration information of the second animation effect configuration file or the third animation effect configuration file.
[0160] As described above, this application provides a display device and a transition animation configuration method. When switching applications, the display device obtains the developer identifiers of the first and second applications to determine the transition animation configuration strategy based on whether the first and second applications belong to the same developer. Based on different animation configuration strategies, the decision-maker for the animation effect is determined. This ensures that in application switching scenarios, the entrance and exit animations corresponding to the first and second applications belong to the same animation resource, thereby avoiding the problem of inconsistent animation resource IDs caused by different applications, which leads to animation loading errors.
[0161] Similar parts between the embodiments provided in this application can be referred to mutually. The specific implementation methods provided above are only a few examples under the overall concept of this application and do not constitute a limitation on the scope of protection of this application. For those skilled in the art, any other implementation methods extended from the solution of this application without creative effort shall fall within the scope of protection of this application.
Claims
1. A display device, characterized in that, include: monitor; The controller is configured as follows: In response to an application switching command, obtain the developer identifiers of the first and second applications; The first application is the application currently running in the foreground, and the second application is the application that is about to be switched to the foreground. The developer identifier is used to identify the developer identity information of the first application and the second application; If the developer identifiers of the first application and the second application are the same, then the first animation effect configuration file is obtained from the shared resource library of the first application and the second application. Configure the exit animation of the first application according to the exit animation configuration information in the first animation effect configuration file, and configure the entrance animation of the second application according to the entrance animation configuration information in the first animation effect configuration file; If the developer identifiers of the first application and the second application are different, then the second animation effect configuration file is obtained from the default resource library of the first application or the third animation effect configuration file is obtained from the default resource library of the second application. Configure the exit animation of the first application according to the entrance animation configuration information of the second animation effect configuration file or the third animation effect configuration file, and configure the entrance animation of the second application according to the exit animation configuration information of the second animation effect configuration file or the third animation effect configuration file; Wherein, the controller is further configured to: when the developer identifiers of the first application and the second application are different. Obtain the API version number of the system used to support the operation of the first application and the second application; the system API version is used to characterize the animation resource synchronization method supported by the system; If the API version number is within the first preset range, then obtain the third animation effect configuration file provided by the second application; If the API version number is in the second preset range, then the second animation effect configuration file is obtained from the default resource library of the first application; the API version number in the second preset range is lower than the API version number in the first preset range.
2. The display device according to claim 1, characterized in that, The controller retrieves a first animation effect configuration file from the shared animation resource library of the first and second applications, specifically configured as follows: Obtain the first animation resource name and the first resource query interface of the first application; Access the shared resource table through the first resource query interface; Retrieve the first animation resource ID from the shared resource table based on the first animation resource name; The first animation resource ID is a unique identifier corresponding to the animation resource used by the first application when it enters or exits the foreground; the shared resource table includes a mapping relationship between resource names and resource IDs; The first animation effect configuration file is obtained from the shared resource library based on the first animation resource ID.
3. The display device according to claim 2, characterized in that, The controller is configured to retrieve the first animation effect configuration file from the shared resource library based on the first animation resource ID, and is also configured to: Obtain the resource sharing interface; The first animation resource ID is sent to the second application through the resource sharing interface; The second application is controlled to retrieve the first animation effect configuration file from the shared resource library based on the first animation resource ID.
4. The display device according to claim 1, characterized in that, After the controller retrieves the second animation effect configuration file from the default resource library of the first application, it is further configured as follows: Configure the exit animation of the first application according to the entrance animation configuration information in the second animation effect configuration file; Configure the entrance animation of the second application according to the exit animation configuration information in the second animation effect configuration file.
5. The display device according to claim 1, characterized in that, The controller is further configured to: if the developer identifiers of the first application and the second application are different. Obtain animation effect strategy token and animation effect strategy verification information; the animation effect strategy token includes animation effect strategy metadata; the animation effect strategy metadata is data provided by the first application to limit the animation effect execution strategy; the animation effect strategy verification information is used to characterize the effective operating range of the animation effect. If the animation effect strategy metadata is within the effective operating range, obtain the API version number of the system used to support the operation of the first application and the second application; If the animation effect strategy metadata is not within the effective operating range, obtain the system's default animation effect configuration file; Configure the exit animation of the first application and the entrance animation of the second application according to the default animation effect configuration file.
6. The display device according to claim 5, characterized in that, Before the controller executes the process of obtaining the animation effect policy token and animation effect policy verification information, it is also configured as follows: Control the first application to create animation effect strategy tokens; The first application is controlled to send the animation effect strategy token to the second application; the animation effect strategy token is used to enable the second application to call the animation strategy verification interface. When the second application calls the animation strategy verification interface, the animation effect strategy token and animation effect strategy verification information are obtained.
7. The display device according to claim 5, characterized in that, The animation effect strategy metadata includes system-level strategy metadata, application-level strategy metadata, and window-level strategy metadata; the system-level strategy metadata is used to limit the system memory required for the animation effect; the application-level strategy metadata is used to limit the developer's running permissions for the animation effect; and the window-level strategy metadata is used to limit the animation effect display permissions for the animation running window. The controller is configured to retrieve the animation effect policy token and animation effect policy verification information, and is also configured to: If any of the system-level policy metadata, the application-level policy metadata, and the window-level policy metadata are not within the effective operating range, obtain the system's default animation effect configuration file.
8. The display device according to claim 1, characterized in that, The controller is also configured to: If the API version number is within a third preset range, obtain the system's default animation effect configuration file; the API version number in the third preset range is lower than the API version number in the second preset range; Configure the exit animation of the first application according to the entrance animation configuration information in the default animation effect configuration file; Configure the entrance animation of the second application according to the exit animation configuration information in the default animation effect configuration file.
9. A method for configuring transition animations, characterized in that, include: In response to an application switching command, obtain the developer identifiers of the first and second applications; The first application is the application currently running in the foreground, and the second application is the application that is about to be switched to the foreground. The developer identifier is used to identify the developer identity information of the first application and the second application; If the developer identifiers of the first application and the second application are the same, then the first animation effect configuration file is obtained from the shared resource library of the first application and the second application. Configure the exit animation of the first application according to the exit animation configuration information in the first animation effect configuration file, and configure the entrance animation of the second application according to the entrance animation configuration information in the first animation effect configuration file; If the developer identifiers of the first application and the second application are different, then the second animation effect configuration file is obtained from the default resource library of the first application or the third animation effect configuration file is obtained from the default resource library of the second application. Configure the exit animation of the first application according to the entrance animation configuration information of the second animation effect configuration file or the third animation effect configuration file, and configure the entrance animation of the second application according to the exit animation configuration information of the second animation effect configuration file or the third animation effect configuration file; wherein, if the developer identifiers of the first application and the second application are different, the following is also included: Obtain the API version number of the system used to support the operation of the first application and the second application; the system API version is used to characterize the animation resource synchronization method supported by the system; If the API version number is within the first preset range, then obtain the third animation effect configuration file provided by the second application; If the API version number is in the second preset range, then the second animation effect configuration file is obtained from the default resource library of the first application; the API version number in the second preset range is lower than the API version number in the first preset range.
Citation Information
Patent Citations
Coordination of animations across multiple applications or processes
CN102736912A
Method for generating transition animation for application switching, and related device
WO2022111698A1
