Display method and related device

Abstract

The application provides a display method and related device. The method comprises: a display screen displays a recent task interface, the recent task interface comprising at least two application pairs of thumbnails, each application pair comprising at least two applications; receiving a first operation on a thumbnail of a first application pair, the first application pair being one of the at least two application pairs; at the beginning of initiating a dynamic effect, in the case that the first application pair comprises a target application, in response to the first operation, modifying a semi-transparent attribute of the target application to be opaque; wherein the target application is an application in the first application pair with a semi-transparent attribute of semi-transparent; at the end of the dynamic effect, re-modifying the semi-transparent attribute of the target application from opaque to semi-transparent; and displaying interfaces of each application in the first application pair respectively on the display screen in a split-screen display function. Implementing the method can avoid errors in the application pairs.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to display methods and related devices. Background Technology

[0002] Currently, when users use electronic devices with large displays (such as foldable screen devices, tablets, or large-screen phones), these devices typically support split-screen functionality. Furthermore, split-screen pairing solutions already exist. This means that applications can be paired up; for example, the recent tasks list might display split-screen pair A and split-screen pair B. Clicking on split-screen pair A in the recent tasks list will display the content of applications a and b corresponding to split-screen pair A on the screen. Clicking on split-screen pair B in the recent tasks list will display the content of applications c and d corresponding to split-screen pair B on the screen. However, in current split-screen pairing solutions, when users click on split-screen pair A in the recent tasks list and then return to the recent tasks list, split-screen pair B might no longer be present. Instead, the recent tasks list might display the full-screen content of applications c and d separately, or it might display the split-screen pair consisting of applications a and c, along with the full-screen content of applications b and d. In other words, current split-screen pairing solutions still have the problem of potential errors in the split-screen pairings. Summary of the Invention

[0003] This application provides a display method and related apparatus that can prevent errors from occurring in split-screen pairs.

[0004] In a first aspect, this application provides a display method applied to an electronic device including a display screen having a split-screen display function; the method includes: displaying a recent tasks interface on the display screen, the recent tasks interface including thumbnails of at least two application pairs, each application pair including at least two applications; receiving a first operation applied to the thumbnails of a first application pair, the first application pair being one of the at least two application pairs; at the start of initiating an animation effect, if the first application pair includes a target application, in response to the first operation, modifying the semi-transparency attribute of the target application to opaque; wherein the target application is the application in the first application pair whose semi-transparency attribute is semi-transparent; at the end of the animation effect, modifying the semi-transparency attribute of the target application from opaque back to semi-transparent; and displaying the interfaces of each application in the first application pair separately on the display screen using the split-screen display function.

[0005] In current solutions, due to the asynchronous execution of programs within electronic devices, the presence of applications with semi-transparent attributes may cause the electronic device to modify the visibility of other applications (or the visibility of other applications' interfaces), leading to the electronic device obtaining incorrect visibility information and causing errors in the application pair. In this embodiment, by modifying the semi-transparent attribute of the target application to opaque at the beginning of the animation (i.e., the process of updating the interface displayed on the screen from the recent tasks interface to displaying the interfaces of each application in the first application pair using the split-screen display function), the electronic device will not modify the visibility of other applications due to the presence of applications with semi-transparent attributes. This allows the electronic device to correctly obtain the visibility of each application pair (or each application), thus preventing errors in the application pair (or split-screen pair).

[0006] In conjunction with the first aspect, in one possible implementation, the electronic device includes a shell module and a core module. Modifying the semi-transparent attribute of the target application to opaque includes: sending a first window container transaction to the core module through the shell module; the first window container transaction looking for the operation that includes modifying the semi-transparent attribute of the target application to opaque; and the core module parsing the first window container transaction to modify the semi-transparent attribute of the target application to opaque.

[0007] In this embodiment of the application, by setting the semi-transparent attribute of the target application to opaque, the core module can be prevented from setting the visibility of applications included in other application pairs to visible, thereby preventing the shell module from obtaining error information and thus preventing errors from occurring in the application pair.

[0008] In conjunction with the first aspect, in one possible implementation, modifying the semi-transparent attribute of the target application from opaque to semi-transparent includes: sending a second window container transaction to the core module via the shell module, the second window container transaction including the operation of modifying the opaque attribute of the target application to semi-transparent, the second window container transaction being a callback window container transaction of the first window container transaction; and parsing the second window container transaction via the core module to modify the semi-transparent attribute of the target application back to semi-transparent.

[0009] In this embodiment of the application, by modifying the semi-transparent attribute of the target application back to semi-transparent, the initial state (e.g., semi-transparent) of the target application's attribute (e.g., semi-transparent attribute) can be restored without causing errors in the application.

[0010] In conjunction with the first aspect, in one possible implementation, the electronic device further includes a launcher module, which, before modifying the semi-transparent attribute of the target application from opaque back to semi-transparent at the end of the animation, further includes: determining the visibility of at least two application pairs (or, determining the visibility of each application in at least two application pairs) via the core module; and updating the visibility of at least two application pairs to the launcher module via the shell module.

[0011] In conjunction with the first aspect, in one possible implementation, the visibility of each application in the first application pair is visible, and the visibility of each application in at least two other application pairs other than the first application is invisible.

[0012] In conjunction with the first aspect, in one possible implementation, the display screen includes a first screen and a second screen; the first application pair includes a target application and other applications; the interfaces of each application in the first application pair are displayed on the display screen using a split-screen display function, including: displaying the interface of the target application on the first screen with a semi-transparent attribute, and displaying the interfaces of other applications on the second screen with a semi-transparent attribute and an opaque attribute.

[0013] In conjunction with the first aspect, in one possible implementation, the first operation is a click, double-click, long-press, or swipe operation on the thumbnail of the first application pair.

[0014] In a second aspect, embodiments of this application provide an electronic device, the electronic device comprising: one or more processors and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the electronic device to perform the method in the first aspect or any possible implementation of the first aspect.

[0015] Thirdly, a chip system is provided, the chip system being applied to an electronic device, the chip system including one or more processors, the processors being configured to invoke computer instructions to cause the electronic device to perform a method as described in the first aspect or any possible implementation thereof.

[0016] Fourthly, a computer-readable storage medium is provided, including instructions that, when executed on an electronic device, cause the electronic device to perform a method as described in the first aspect or any possible implementation thereof.

[0017] The beneficial effects of the technical solutions provided in the second to fourth aspects of this application can be referred to the beneficial effects of the technical solutions provided in the first aspect, and will not be repeated here. Attached Figure Description

[0018] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly described below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0019] Figure 1A This is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application;

[0020] Figure 1B A software structure block diagram of an electronic device 100 provided in this application embodiment;

[0021] Figure 1C A schematic diagram of a software system framework provided in an embodiment of this application;

[0022] Figure 2 A user interface diagram provided for an embodiment of this application;

[0023] Figure 3 A schematic flowchart illustrating a display method provided in an embodiment of this application;

[0024] Figure 4 Another user interface diagram provided for the application embodiment;

[0025] Figure 5 This is an interactive schematic diagram of a display method provided in an embodiment of this application. Detailed Implementation

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

[0027] The following describes an electronic device, a user interface for such an electronic device, and embodiments for using such an electronic device. In some embodiments, the electronic device may be a portable electronic device that also includes other functions such as a personal digital assistant and / or music player, such as a mobile phone, tablet computer, wearable electronic device with wireless communication capabilities (such as a smartwatch), etc. Exemplary embodiments of the portable electronic device include, but are not limited to, carrying... Alternatively, it could be a portable electronic device with another operating system. The aforementioned portable electronic device could also be other portable electronic devices, such as a laptop computer with a touch-sensitive surface or touch panel. It should also be understood that in some other embodiments, the aforementioned electronic device may not be a portable electronic device, but rather a desktop computer with a touch-sensitive surface or touch panel.

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

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

[0030] First, we introduce the exemplary electronic device 100 provided in the following embodiments of this application.

[0031] Figure 1A A schematic diagram of the structure of the electronic device 100 is shown.

[0032] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180G, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0033] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0034] Processor 110 may include one or more processing units, such as application processors (APs), central processing units (CPUs), graphics processing units (GPUs), neural network processing units (NPUs), modem processors, image signal processors (ISPs), controllers, memory, video codecs, digital signal processors (DSPs), baseband processors, etc. Different processing units may be independent devices or integrated into one or more processors. In some embodiments, electronic device 100 may also include one or more processors 110.

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

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

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

[0038] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180K, charger, flash, camera 193, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180K through the I2C interface, enabling the processor 110 and the touch sensor 180K to communicate through the I2C bus interface, thereby realizing the touch function of the electronic device 100.

[0039] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to enable the function of answering phone calls through a Bluetooth headset.

[0040] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering phone calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0041] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to enable music playback through Bluetooth headphones.

[0042] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to enable the camera function of the electronic device 100. The processor 110 and the display screen 194 communicate via the DSI interface to enable the display function of the electronic device 100.

[0043] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to a camera 193, a display screen 194, a wireless communication module 160, an audio module 170, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0044] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0045] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0046] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0047] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

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

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

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

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

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

[0053] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via 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 technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

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

[0055] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0056] Electronic device 100 can realize camera function through camera 193, ISP, video codec, GPU, display screen 194, application processor AP, neural network processor NPU, etc.

[0057] Camera 193 can be used to acquire color image data and depth data of the subject. An ISP can be used to process the color image data acquired by camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, converting it into a visible image. The ISP can also perform algorithmic optimization on image noise, brightness, etc. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be integrated into camera 193.

[0058] In some embodiments, the camera 193 may consist of a color camera module and a 3D sensing module.

[0059] In some embodiments, the photosensitive element of the camera in the color camera module can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then transmitted to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats.

[0060] In some embodiments, the 3D sensing module can be a time-of-flight (TOF) 3D sensing module or a structured light 3D sensing module. Structured light 3D sensing is an active depth sensing technology. The basic components of a structured light 3D sensing module may include an infrared emitter, an IR camera module, etc. The working principle of a structured light 3D sensing module is to first emit a specific pattern of light onto the object being photographed, then receive the light coding on the object's surface, compare it with the original projected light pattern, and calculate the object's three-dimensional coordinates using triangulation principles. These three-dimensional coordinates include the distance between the electronic device 100 and the object being photographed. Similarly, TOF 3D sensing is also an active depth sensing technology. The basic components of a TOF 3D sensing module may include an infrared emitter, an IR camera module, etc. The working principle of a TOF 3D sensing module is to calculate the distance (i.e., depth) between the TOF 3D sensing module and the object being photographed by measuring the infrared reflection time to obtain a 3D depth map.

[0061] Structured light 3D sensing modules can also be applied to facial recognition, motion-sensing game consoles, and industrial machine vision inspection. Time-of-flight (TOF) 3D sensing modules can also be applied to game consoles, augmented reality (AR) / virtual reality (VR) and other fields.

[0062] In other embodiments, camera 193 may also consist of two or more cameras. These two or more cameras may include a color camera, which can be used to acquire color image data of the object being photographed. These two or more cameras may employ stereo vision technology to acquire depth data of the object being photographed. Stereo vision technology is based on the principle of human parallax. Under natural light, two or more cameras capture images of the same object from different angles, and then triangulation and other calculations are performed to obtain the distance information, i.e., depth information, between the electronic device 100 and the object being photographed.

[0063] In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1. Specifically, the electronic device 100 may include one front-facing camera 193 and one rear-facing camera 193. The front-facing camera 193 is typically used to capture color image data and depth data of the photographer facing the display screen 194, while the rear-facing camera 193 is used to capture color image data and depth data of the subject (such as a person, landscape, etc.) in front of the photographer.

[0064] In some embodiments, the CPU, GPU, or NPU in the processor 110 can process the color image data and depth data acquired by the camera 193. In some embodiments, the NPU can identify the skeletal points of the subject by using neural network algorithms based on skeletal point recognition technology, such as convolutional neural network algorithms (CNN). The CPU or GPU can also run neural network algorithms to determine the skeletal points of the subject based on the color image data. In some embodiments, the CPU, GPU, or NPU can also be used to determine the body shape of the subject (such as body proportions and the degree of fatness or thinness of body parts between skeletal points) based on the depth data acquired by the camera 193 (specifically, the 3D sensing module) and the identified skeletal points, and can further determine body beautification parameters for the subject. Finally, the captured image of the subject is processed according to the body beautification parameters to beautify the body shape of the subject in the captured image. Subsequent embodiments will detail how to perform body shaping processing on the image of the photographed person based on the color image data and depth data collected by the camera 193, which will not be elaborated here.

[0065] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0066] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG)-1, MPEG-2, MPEG-3, MPEG-4, etc.

[0067] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0068] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, photos, videos, and other data can be stored on the external memory card.

[0069] The internal memory 121 can be used to store one or more computer programs, which include instructions. The processor 110 can execute the instructions stored in the internal memory 121, thereby causing the electronic device 100 to perform the photographic preview method, various functional applications, and data processing provided in some embodiments of this application. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system; it may also store one or more application programs (such as a gallery, contacts, etc.). The data storage area may store data created during the use of the electronic device 100 (such as photos, contacts, etc.). Furthermore, the internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0070] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0071] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0072] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or make hands-free calls through the speaker 170A.

[0073] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a telephone call or voice message, the receiver 170B can be brought close to the ear to listen to the voice.

[0074] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic device 100 may have at least one microphone 170C. In some embodiments, electronic device 100 may have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 100 may also have three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0075] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0076] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the intensity of the touch operation based on pressure sensor 180A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0077] The gyroscope sensor 180B can be used to determine the motion attitude of the electronic device 100. In some embodiments, the gyroscope sensor 180B can determine the angular velocity of the electronic device 100 about three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the shake of the electronic device 100, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the electronic device 100 by moving in the opposite direction, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing game scenarios.

[0078] The barometric pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates altitude using the air pressure value measured by the barometric pressure sensor 180C to assist in positioning and navigation.

[0079] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip cover. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover using the magnetic sensor 180D. Then, based on the detected opening and closing state of the cover or the flip cover, features such as automatic flip unlocking can be set.

[0080] The 180E accelerometer can detect the magnitude of acceleration of electronic device 100 in various directions (typically three axes). When electronic device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of electronic devices and applied to applications such as screen orientation switching and pedometers.

[0081] A distance sensor 180F is used to measure distance. Electronic device 100 can measure distance via infrared or laser. In some embodiments, during a shooting scene, electronic device 100 can utilize the distance sensor 180F to measure distance for rapid focusing.

[0082] The proximity sensor 180G may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The electronic device 100 emits infrared light outward through the LED. The electronic device 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 may use the proximity sensor 180G to detect when a user holds the electronic device 100 close to their ear for a call, so as to automatically turn off the screen to save power. The proximity sensor 180G can also be used in holster mode and pocket mode for automatic unlocking and locking of the screen.

[0083] The ambient light sensor 180L is used to sense the brightness of ambient light. The electronic device 100 can adaptively adjust the brightness of the display screen 194 based on the sensed ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also work with the proximity sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

[0084] The fingerprint sensor 180G is used to collect fingerprints. The electronic device 100 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering calls with fingerprints, etc.

[0085] Temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 uses the temperature detected by temperature sensor 180J to execute a temperature handling strategy. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs thermal protection by reducing the performance of a processor located near temperature sensor 180J to reduce power consumption. In other embodiments, when the temperature is below another threshold, electronic device 100 heats battery 142 to prevent abnormal shutdown of electronic device 100 due to low temperature. In still other embodiments, when the temperature is below yet another threshold, electronic device 100 boosts the output voltage of battery 142 to prevent abnormal shutdown due to low temperature.

[0086] Touch sensor 180K, also known as a touch panel or touch-sensitive surface, can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also called a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0087] The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire vibration signals from the vibrating bone segments of the human vocal cords. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure signals. In some embodiments, the bone conduction sensor 180M can also be incorporated into headphones to form bone conduction headphones. The audio module 170 can parse the voice signals from the vibrating bone segments of the vocal cords acquired by the bone conduction sensor 180M to realize voice functionality. The application processor can parse heart rate information from the blood pressure signals acquired by the bone conduction sensor 180M to realize heart rate detection functionality.

[0088] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0089] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0090] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0091] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0092] Figure 1A The exemplary electronic device 100 can display various user interfaces described in the following embodiments via a display screen 194. The electronic device 100 can detect touch operations in each user interface via a touch sensor 180K, such as click operations (e.g., touch on an icon, double-click operation), swipe up or down, or perform a circle gesture, etc. In some embodiments, the electronic device 100 can detect motion gestures performed by a user holding the electronic device 100, such as shaking the electronic device, via a gyroscope sensor 180B, an accelerometer 180E, etc. In some embodiments, the electronic device 100 can detect non-touch gesture operations via a camera 193 (e.g., a 3D camera, a depth camera).

[0093] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses the layered architecture Android system as an example to exemplify the software structure of electronic device 100.

[0094] Figure 1B This is a software structure block diagram of the electronic device 100 according to an embodiment of this application.

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

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

[0097] like Figure 1B As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and SMS.

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

[0099] like Figure 1B As shown, the application framework layer may include a window manager, content provider, view system, event manager, phone manager, resource manager, notification manager, etc.

[0100] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0101] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

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

[0103] The phone manager is used to provide communication functions for electronic device 100. For example, it manages call status (including connection and disconnection).

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

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

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

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

[0108] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

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

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

[0111] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, G.264, MP3, AAC, AMR, JPG, and PNG.

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

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

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

[0115] Figure 1B The software system shown involves application presentations that utilize sharing capabilities (such as a library and file manager), an instant sharing module that provides sharing capabilities, a print service and a print spooler that provide printing capabilities, an application framework layer that provides a printing framework, WLAN service, and Bluetooth service, and a kernel and underlying layer that provide WLAN and Bluetooth capabilities and basic communication protocols.

[0116] The following example, using a display scenario, illustrates the workflow of the software and hardware of electronic device 100.

[0117] When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the application layer to invoke the window manager of the application framework layer. The window manager allows modification of the application's semi-transparent properties, thereby preventing application errors.

[0118] For details, please see Figure 1C , Figure 1C This application provides a schematic diagram of a software system framework, which may include a launcher module, a shell module, and a core module. The core module and the shell module belong to... Figure 1B The window manager in the application framework layer. The launcher module belongs to... Figure 1B The application layer is comprised of several modules. The `core` module handles the most basic tasks, such as hardware management, memory management, and process scheduling. It forms the foundation of the software system framework, providing the fundamental services and interfaces for all higher-level components. The `shell` module provides the interface for user interaction with the system; this can be a command-line interface, a graphical user interface, or other forms of interactive interface. The `shell` module receives user input, translates it into instructions that the `core` module can understand, and presents the `core` module's output to the user. The `launcher` module is a component in the user interface used to launch applications or perform specific tasks. The `launcher` module can be a desktop shortcut, a start menu item, an application drawer, a game launcher, etc. It provides users with a quick entry point to access and launch other programs or services. In other words, the `core` module provides basic services, and the `shell` module builds upon these services, providing a user-friendly interactive experience. The `shell` module receives user commands or operations and executes them through the interface provided by the `core` module. The `launcher` module provides the ability to quickly launch applications, allowing users to easily access the programs or services they need.

[0119] Currently, when users use electronic devices with large displays (such as foldable screen devices, tablets, or large-screen phones), these devices typically support split-screen functionality. Furthermore, split-screen pair solutions already exist. This means that applications can be paired up; for example, the recent tasks list might display split-screen pair A and split-screen pair B. Clicking on split-screen pair A in the recent tasks list will display the content of applications a and b corresponding to split-screen pair A on the screen. Clicking on split-screen pair B in the recent tasks list will display the content of applications c and d corresponding to split-screen pair B on the screen. However, in current split-screen pair solutions, when clicking on split-screen pair A in the recent tasks list and then returning to the recent tasks list, split-screen pair B might no longer be present. Instead, the recent tasks list might display the full-screen content of applications c and d, or it might display the split-screen pair consisting of applications a and c, along with the full-screen content of applications b and d. In other words, current split-screen pair solutions still have the problem of potential errors in the split-screen pair configuration. A split-screen pair can also be referred to as an application pair.

[0120] For example, see Figure 2 , Figure 2 This application provides a schematic diagram of a user interface. When a user creates two application pairs and one full-screen application and enters the recent tasks interface, the user interface can display as follows: Figure 2 The recent tasks interface shown in (A) includes thumbnails of two application pairs and a thumbnail of a full-screen application c. The two application pairs are application pair A (comprising applications a1 and a2) and application pair B (comprising applications b1 and b2). In application pair A, application a1 has a semi-transparent attribute, while applications a2, b1, and b2 in application pair B have an opaque attribute. When clicked... Figure 2 After applying the thumbnail of A to the application of (A), the user interface can display as follows: Figure 2 As shown in (B), applications a1 and a2 are displayed separately using the split-screen display function. When switching from... Figure 2 When the user interface shown in (B) returns to the recent tasks screen, it should display as follows: Figure 2 The recent tasks interface shown in (A) is shown in the image. However, what may actually be displayed is as shown in the image below. Figure 2 The recent tasks interface is shown in (C). Figure 2 The recent tasks interface shown in (C) includes three full-screen applications (application a1, application b1, and application c) and an application pair D consisting of application a2 and application b2. This is because, in such... Figure 2 The recent tasks interface shown in (A) receives the first operation on A from application a1, which has a semi-transparent attribute. Then, it displays as shown in (A). Figure 2 Before application a1 and application a2 are displayed separately using the split-screen display function as shown in (B), there will be other application groups (or applications) M (for example, when entering such a window). Figure 2 Before the recent tasks shown in (A), the applications displayed on the screen are located behind the interfaces of applications a1 and a2. This can be understood as application group M still being displayed on the screen, but being covered by applications a1 and a2, thus not visible to the user. However, when the core module ensures the visibility of each application in the task group, the presence of application a1 (which has a semi-transparent attribute) causes applications in other application pairs (e.g., application b2) that should be invisible but are located behind application a1 to be modified (or set) to be visible. This causes an error in the shell module when retrieving visible applications, resulting in an error in the application pair. The first operation updates the display from showing the recent tasks interface to displaying the interfaces of each application in a specific application pair (e.g., application pair A) using a split-screen display function.

[0121] It should be noted that, Figure 2 The application pair error shown in (C) is one possible type of error; other types are also possible. For example, another possible type of error is an application pair consisting of application a1 and application b2, where any one of application a2, application b1, and application c is capable of full-screen display and is not part of an application pair with other applications. It should be noted that when in situations such as... Figure 2 After the interface shown in (A) receives the first operation on A for the application, that is, when the display changes from displaying as shown in (A), Figure 2 The recent tasks interface shown in (A) has been updated to display as follows: Figure 2 As shown in (B), before the split-screen display function is used to show applications a1 and a2 in A, the information obtained by the shell module has already been corrupted, instead of being obtained upon re-entering the application. Figure 2 The error occurred after the recent tasks screen shown in (C), but you can see if the error occurred by re-entering the recent tasks screen.

[0122] To address the aforementioned problems, this application provides a display method. This method, by modifying the application's semi-transparency attribute at a specific time, can prevent application errors. Please refer to the following sections for details. Figures 3-5 Related explanations.

[0123] Please see Figure 3 This is a flowchart illustrating a display method provided in an embodiment of this application.

[0124] like Figure 3 As shown, the display method may include the following steps S301-S305.

[0125] Step S301: The display screen shows the recent tasks interface.

[0126] The recent tasks interface includes thumbnails of at least two application pairs, with each application pair containing at least two applications.

[0127] For example, the display can show a recent tasks interface in landscape or portrait mode, which includes thumbnails of at least two app pairs. Thumbnails can also be referred to as cards.

[0128] The Recent Tasks screen can include thumbnails of at least two app pairs, or thumbnails of at least two apps. An app pair can consist of two or more apps that can be displayed separately on the screen using split-screen functionality. For example... Figure 2 The recent tasks interface shown in (A) includes thumbnails of two application pairs (application pair A and application pair B) and a thumbnail of one application (application c). It is understood that the thumbnails of the application pairs and / or the application displayed on the recent tasks interface represent applications that the user has opened and used on the electronic device, or applications that have been recently used. The thumbnails corresponding to the application pairs and / or the application can clearly display the content of one interface of the application corresponding to the thumbnail, or they can vaguely display the content of one interface of the application corresponding to the thumbnail. Furthermore, the thumbnail of any application pair can clearly display the content of one interface of one or more applications in the application pair, and vaguely display the content of one interface of another one or more applications in the application pair; this embodiment of the application does not limit this. For example, in Figure 2 On the recent tasks screen shown in (A), in the thumbnail of application A, the content of application a1's interface is clearly displayed, while the content of application a2's interface is blurred. Alternatively, the content of application a2's interface is clearly displayed, while the content of application a1's interface is blurred. Alternatively, the content of both application a1's and application a2's interfaces is clearly displayed. Alternatively, the content of both application a1's and application a2's interfaces is blurred.

[0129] Step S302: Receive a first operation applied to the thumbnail of the first application pair.

[0130] The first application pair is one of at least two application pairs. That is, the recent tasks interface can include thumbnails of at least two application pairs, with the application pair corresponding to one of these thumbnails being the first application pair. Alternatively, it can be understood as the application pair on which the first operation operates being called the first application pair in order to distinguish it from other application pairs.

[0131] The first operation is used to update the display screen from showing the recent tasks interface to displaying the interfaces of each application in the first application pair using the split-screen display function.

[0132] In one possible implementation, the first operation unit can be a click operation, double-click operation, long-press operation, or swipe operation on the thumbnail of the first application pair.

[0133] In one possible implementation, the electronic device may also include a launcher module.

[0134] Specifically, the launcher module may receive a first operation applied to the thumbnail of the first application pair.

[0135] Step S303: At the start of initiating the motion effect, if the target application is included in the first application pair, in response to the first operation, the semi-transparent property of the target application is modified to opaque.

[0136] The target application is the application in the first application pair where the semi-transparent attribute is semi-transparent.

[0137] In the embodiments of this application, unless otherwise specified, the animation effect can refer to the dynamic effect of the content displayed on the screen being updated from the recent task interface to displaying the interfaces of each application in the first application pair using the split-screen display function.

[0138] For example, whether the semi-transparent attribute of the target application in the first application pair is semi-transparent can be determined by the boolean value of the semi-transparent attribute. For instance, if the boolean value of the semi-transparent attribute of the application in the first application pair is true, then that application is the target application; if the boolean value of the semi-transparent attribute of the application in the first application pair is false, then that application is not the target application. For example, in... Figure 2 In (A), application a1 in A is the target application, meaning that the boolean value of the semi-transparent property of application a1 is true; application a2 in A is not the target application, meaning that the boolean value of the semi-transparent property of application a2 is false.

[0139] In other words, if the first application pair contains an application with a semi-transparent attribute, then that application is the target application. It is understood that the number of target applications in an application pair can be N, where N is an integer greater than or equal to 0. That is, in an application pair, the number of target applications can be 0, 1, 2, etc., and this application embodiment does not limit this.

[0140] When the first application pair includes a target application, that is, when the number of target applications in the first application pair is greater than or equal to one, in response to the first operation, the electronic device modifies the semi-transparent attribute of the target application in the first application pair to opaque, and displays the interface of each application in the first application pair on the display screen using the split-screen display function.

[0141] For example, one way to change the semi-transparent property of a target application to opaque is to set the boolean value of the semi-transparent property to false.

[0142] In one possible implementation, the electronic device may include a shell module and a core module. Modifying the semi-transparent attribute of the target application to opaque may specifically include: sending a first window container transaction to the core module via the shell module; the first window container transaction including an operation (or instruction, command, or directive) to modify the semi-transparent attribute of the target application to opaque; then, upon receiving the first window container transaction, the core module parses the first window container transaction and modifies the semi-transparent attribute of the target application to opaque.

[0143] For example, after receiving a first operation for a first application pair, if the first application pair includes a target application, the shell module includes an operation to modify the target application's semi-transparent attribute to opaque in the first window container transaction sent to the core module. In other words, if the first application pair includes the target application, the shell module, in the first window container transaction sent to the core module, notifies or instructs the core module to modify the target application's semi-transparent attribute to opaque. It can be understood that the shell module itself does not modify the target application's semi-transparent attribute; instead, the core module, after receiving the first window container transaction from the shell module, parses the transaction to obtain the command or instruction to modify the target application's semi-transparent attribute. The core module then modifies the target application's semi-transparent attribute to opaque based on the parsed first window container transaction. The first window container transaction can be sent to the core module when initiating an animation. That is, the first window container transaction for initiating an animation can include a command or instruction to modify the target application's semi-transparent attribute from semi-transparent to opaque.

[0144] Step S304: When the animation ends, change the semi-transparent property of the target application from opaque back to semi-transparent.

[0145] Since the target application's original semi-transparent attribute was semi-transparent, after the shell module correctly obtains the visibility of each application and / or each application in the application pair, the electronic device needs to change the target application's semi-transparent attribute from opaque back to semi-transparent.

[0146] For example, one way to change the semi-transparent property of a target application from opaque to semi-transparent is to change the boolean value of the semi-transparent property from false to true.

[0147] When the animation ends, it can refer to the display screen showing something like... Figure 2 The image in (B) shows the interface of application a1 and application a2 in A using the split-screen display function. Alternatively, the semi-transparent property of the target application can be changed from opaque back to transparent just before the animation ends.

[0148] In one possible implementation, the semi-transparent property of the target application is modified from opaque to semi-transparent again, including: at the end of the animation, a second window container transaction is sent to the core module through the shell module. The second window container transaction includes the operation of modifying the opaque property of the target application to semi-transparent. The second window container transaction is a callback window container transaction of the first window container transaction. The core module parses the second window container transaction and modifies the semi-transparent property of the target application back to semi-transparent.

[0149] For example, when the animation ends, it indicates that the shell module has correctly obtained the visibility of each application and / or each application in the application pair, and has not been affected by the target application. At this time, the shell module can send a second window container transaction (i.e., a callback window container transaction of the first window container transaction) to the core module. The second window container transaction can carry a command or instruction to change the semi-transparent attribute of the target application from opaque to semi-transparent. Thus, after the core module receives and parses the second window container transaction, it can change the semi-transparent attribute of the target application from opaque to semi-transparent according to the instruction or command in the second window container transaction. Therefore, without ultimately changing the attribute of the target application (e.g., the semi-transparent attribute), errors in the application pair are avoided. In other words, after adopting the display method provided in this application, in situations such as... Figure 2 After clicking on application pair A, which includes the target application a1, in the recent tasks interface shown in (A), when the recent tasks interface is displayed again, it will still display as shown in (A). Figure 2 The recent tasks interface shown in (A) is shown in the middle.

[0150] In one possible implementation, the electronic device also includes a launcher module that, before the semi-transparent property of the target application is changed from opaque back to semi-transparent at the end of the animation, includes: determining the visibility of at least two application pairs via the core module; and updating the visibility of at least two application pairs to the launcher module via the shell module.

[0151] In other words, after initiating the animation and before changing the target's semi-transparency attribute from opaque back to semi-transparent, the core module can determine the visibility of at least two application pairs in the recent tasks interface. After changing the target application's semi-transparency attribute from semi-transparent to opaque using the core module, when determining the visibility of each application and / or each application pair, the core module will not change the visibility of applications in other application pairs from invisible to visible due to the target application. Therefore, the core module can obtain the correct visibility of each application and / or each application pair. That is, after initiating the animation, when determining the visibility of at least two application pairs in the recent tasks interface using the core module, it can be found that the visibility of each application in the first application pair is visible, and the visibility of each application in at least two other application pairs (i.e., other application pairs in the recent tasks interface excluding the first application) is invisible. Then, based on the visibility information (the visibility of the at least two application pairs) obtained by the core module, the shell module updates the visibility of the at least two applications to the launcher module, thereby avoiding errors in application pairs.

[0152] Step S305: Display the interfaces of each application in the first application pair on the display screen using the split-screen display function.

[0153] In one possible implementation, the display screen includes a first screen and a second screen. The first application pair includes a target application and other applications. A split-screen display function on the display screen displays the interfaces of each application in the first application pair respectively, including: displaying the interface of the target application with a semi-transparent attribute on the first screen, and displaying the interfaces of other applications with a semi-transparent attribute on the second screen.

[0154] For example, such as Figure 2 As shown in (B), the display screen includes a first screen on the left and a second screen on the right. The first screen displays the interface of application a1 (the target application), and the second screen displays the interface of application a2 (another application). Since application a1 is the target application, after changing the semi-transparent attribute of application a1 from opaque back to semi-transparent, the interface of application a1 is still displayed with the semi-transparent attribute set to semi-transparent, while the interface of application a2 is displayed with the semi-transparent attribute set to opaque. It should be noted that having the first screen on the left and the second screen on the right is one example; the display screen could also have the second screen on the left and the first screen on the right; or it could be as follows... Figure 4 The user interface shown has a first screen (displaying application a1) at the top and a second screen (displaying application a2) at the bottom; alternatively, the second screen can be at the top and the first screen at the bottom. Further, when the number of applications in an application pair is greater than two, the number of first and / or second screens on the display screen can be greater than one. This application embodiment does not limit this. It is understood that an application pair consisting of two applications can include applications split horizontally or vertically; an application pair consisting of more than two applications can include applications split horizontally or vertically; furthermore, it can include both horizontally and vertically split applications. It is understood that the recent tasks interface can simultaneously display application pairs with different split-screen formats, such as vertically split application pairs and horizontally split application pairs; this application embodiment does not limit this. If a vertically split application pair (or other split-screen application pairs) includes an application with a semi-transparent attribute, the display method provided in this application embodiment can also be applied.

[0155] Please see Figure 5 This is an interactive schematic diagram of a display method provided in an embodiment of this application.

[0156] like Figure 5 As shown, it may include the following steps S501-S509.

[0157] In step S501, the launcher module receives the first operation.

[0158] Displayed on the screen as follows Figure 2 On the recent tasks interface shown in (A), the first operation applied to the thumbnail of the first application pair can be received by the launcher module.

[0159] In step S502, the launcher module sends the first notification to the shell module.

[0160] Accordingly, the shell module receives the first notification.

[0161] The first notification is used to instruct the shell module to construct the first window container transaction and initiate the animation.

[0162] In step S503, the shell module initiates the animation and constructs the first window container transaction.

[0163] Here, "building" can also be called "creation." After receiving the first notification from the launcher module, the shell module can initiate animations and build the first window container transaction based on the first notification.

[0164] In the case where the first application pair includes the target application, the first window container transaction constructed by the shell module includes an operation to modify the semi-transparent attribute of the target application to opaque.

[0165] In step S504, the shell module sends the first window container transaction to the core module.

[0166] Correspondingly, the core module receives the transaction from the first window container.

[0167] Step S505: The core module parses the transaction of the first window container.

[0168] After receiving the first window container transaction, the core module can parse the first window container transaction and modify the visibility of the semi-transparent attribute of the target application based on the first window container transaction.

[0169] In step S506, the core module determines the visibility of at least two application pairs.

[0170] Determining the visibility of at least two application pairs can be understood as determining the visibility of each application within those pairs. It is understandable that if the core module does not modify the target application's semi-transparent attribute to opaque in step S505, then in step S506, when the core module determines the visibility of at least two application pairs, because the target application's semi-transparent attribute is semi-transparent, the core module might change the visibility of other applications in the pair from invisible to visible, thus causing an error in the visibility determination of the at least two application pairs by the core module.

[0171] By modifying the target application's semi-transparent attribute from opaque to transparent using the core module, the core module can obtain the correct information when determining the visibility of at least two applications. This ensures the correct application pair is obtained and avoids errors in application pairing.

[0172] In step S507, the shell module obtains the visibility of at least two application pairs from the core module.

[0173] Understandably, when at least two application pairs identified by the core module have errors, the visibility of at least two application pairs obtained by the shell module from the core module will also be incorrect.

[0174] In step S508, the shell module sends the second window container transaction to the core module.

[0175] Correspondingly, the core module receives transactions from the second window container.

[0176] At the end of the animation, or more specifically, just before the animation ends, the shell module sends a second window container transaction to the core module. This second window container transaction is a callback to the first window container transaction. The second window container transaction includes the operation of restoring the target application's semi-transparent property to semi-transparent.

[0177] After the core module receives the transaction of the second window container, it parses the transaction of the second window container and changes the semi-transparent property of the target application from opaque back to semi-transparent.

[0178] Steps S503 to S508 can be executed during the animation process from initiation to completion.

[0179] In step S509, the shell module sends the visibility of at least two application pairs to the launcher module.

[0180] Accordingly, the launcher module receives visibility from at least two applications.

[0181] Step S509 can be executed during the animation process or after the animation ends; this application embodiment does not limit this.

[0182] After the animation ends, the screen can display something like this. Figure 2 The image in (B) shows application a1 and application a2 displayed using the split-screen display function.

[0183] In this embodiment of the application, by modifying the semi-transparent attribute of the target application to opaque during the animation process, the core module can be prevented from obtaining incorrect application pair information (application pair visibility), thereby preventing application pair errors.

[0184] This application also provides an electronic device, which includes: one or more processors and a memory;

[0185] The memory is coupled to one or more processors and is used to store computer program code, which includes computer instructions. The one or more processors call the computer instructions to cause the electronic device to perform the methods shown in the foregoing embodiments.

[0186] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if..." or "after..." or "in response to determining..." or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is detected" can be interpreted as meaning "if determining..." or "in response to determining..." or "when (the stated condition or event) is detected" or "in response to detecting (the stated condition or event)".

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

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

Claims

1. A display method, characterized in that, An electronic device including a display screen with split-screen display capability; the method includes: The display screen shows a recent tasks interface, which includes thumbnails of at least two application pairs, each application pair including at least two applications; Receive a first operation applied to a thumbnail of a first application pair, wherein the first application pair is one of the at least two application pairs; At the start of initiating the animation, if the first application pair includes the target application, in response to the first operation, the semi-transparent attribute of the target application is modified to opaque; wherein, the target application is the application in the first application pair whose semi-transparent attribute is semi-transparent; When the animation ends, the semi-transparent property of the target application is changed back from opaque to semi-transparent; The interface of each application in the first application pair is displayed on the display screen using the split-screen display function.

2. The method according to claim 1, characterized in that, The electronic device includes a shell module and a core module. Modifying the semi-transparent attribute of the target application to opaque includes: The shell module sends a first window container transaction to the core module, and the first window container transaction includes an operation to change the semi-transparent attribute of the target application to opaque. The core module parses the transaction of the first window container and modifies the semi-transparent attribute of the target application to opaque.

3. The method according to claim 2, characterized in that, The step of modifying the semi-transparent property of the target application from opaque back to semi-transparent includes: The shell module sends a second window container transaction to the core module. The second window container transaction includes an operation to modify the opacity attribute of the target application to semi-transparent. The second window container transaction is a callback window container transaction of the first window container transaction. The core module parses the transaction of the second window container and modifies the semi-transparent attribute of the target application back to semi-transparent.

4. The method according to claim 2 or 3, characterized in that, The electronic device also includes a launcher module, and the method further includes, before modifying the semi-transparent property of the target application from opaque back to semi-transparent at the end of the animation, the method further includes: The visibility of the at least two application pairs is determined by the core module; The shell module updates the visibility of the at least two application pairs to the launcher module.

5. The method according to claim 4, characterized in that, The visibility of each application in the first application pair is visible, while the visibility of each application in the at least two application pairs other than the first application to the outside is invisible.

6. The method according to claim 4 or 5, characterized in that, The display screen includes a first screen and a second screen, and the first application pair includes the target application and other applications; the step of displaying the interface of each application in the first application pair on the display screen using a split-screen display function includes: The target application's interface is displayed semi-transparently on the first screen, and the other application's interface is displayed opaquely on the second screen.

7. The method according to any one of claims 1-6, characterized in that, The first operation is a click, double-click, long press, or swipe operation on the thumbnail of the first application pair.

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

9. A chip system, characterized in that, The chip system is applied to an electronic device, the chip system including one or more processors, the processors being used to invoke computer instructions to cause the electronic device to perform the method as described in any one of claims 1-7.

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

Images