Display equipment and split screen control method

By creating a primary stack and a secondary stack on the display device and processing application task stack information that does not support split screen, the problem of split screen failure caused by the application not supporting split screen after starting split screen mode is solved, and split screen display for split screen applications that do not support split screen.

CN120151573APending Publication Date: 2025-06-13HISENSE VISUAL TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311714709.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-12-13
Publication Date
2025-06-13

AI Technical Summary

Technical Problem

After the existing display device starts split screen mode, split screen failure occurs because some applications do not support split screen.

Method used

By responding to the user's split-screen instructions when displaying the interface of the first application on the display, a primary stack and a secondary stack are created, and the display parameters of each display area are calculated. If the second application participating in split screen does not support split screen, look up its task stack information and store it in the database, and create a mapping relationship between the database and the secondary stack to achieve split screen display.

Benefits of technology

Even if the second application does not support split screen, this method can still display the interfaces of the first application and the second application in the split screen mode to avoid split screen failure.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120151573A_ABST
    Figure CN120151573A_ABST
Patent Text Reader

Abstract

The invention provides a display device and a split screen control method, when an interface of a first application is displayed on a display, in response to a split screen instruction input by a user, a first task stack to which the first application belongs is created as a prime stack, and meanwhile, a secondary stack is created. And calculating a first display parameter of the first display area and a second display parameter of the second display area. The stack information of the second task stack is stored in the first database, and a first mapping relation between the first database and the session stack is created. Displaying the interface of the first application in the first display area according to the first display parameter, and displaying the interface of the second application in the second display area according to the second display parameter based on the first mapping relation. Thus, when the first application and the second application need to be displayed in a split-screen mode, even if the second application does not support split-screen, the first application and the second application can be displayed according to the split-screen mode, and screen splitting failure is avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of display devices, and in particular, to a display device and a split-screen control method. Background Art

[0002] Compared with traditional display devices that provide live TV programs for users through digital broadcasting, current display devices can be configured with various different applications, such as network video, network games, network social networking, etc. These applications provide users with richer content and services. However, as the number of applications configured on the display device increases, users' requirements for the presentation method of applications on the display device are also getting higher and higher. For example, users hope to conduct social activities and watch videos on the display device at the same time, that is, to operate on the network social application and the network video application simultaneously in the foreground of the display device.

[0003] To achieve simultaneous operation on at least two applications in the foreground of the display device, Android provides a variety of multi-window technologies: split-screen mode, picture-in-picture mode, and Freeform (free window) mode. Among them, after the display device starts the split-screen mode, the system divides the screen into two parts. The currently opened application moves to the upper part of the screen (moves to the left side of the screen if it is in landscape mode), and all other opened applications are listed in the lower part (moves to the right side of the screen if it is in landscape mode) in the form of multitasking.

[0004] However, in actual applications, after the display device starts the split-screen mode, the split-screen may fail due to some applications not supporting the split-screen mode. For example, if the application is set not to support split-screen, or the application's own properties do not support split-screen, the split-screen will fail. Summary of the Invention

[0005] The present application provides a display device and a split-screen control method to solve the problem that the split-screen fails after the split-screen mode is started because some applications do not support split-screen.

[0006] In a first aspect, some embodiments of the present application provide a display device, including:

[0007] A display;

[0008] A controller, configured to:

[0009] When displaying the interface of a first application on the display, in response to a split-screen instruction input by the user, create the first task stack to which the first application belongs as the primary stack, and simultaneously create a secondary stack, where the primary stack corresponds to a first display area, the secondary stack corresponds to a second display area, and the first application supports split-screen;

[0010] Calculate the first display parameter of the first display area and the second display parameter of the second display area;

[0011] If the second application participating in split - screen does not support split - screen, find the second task stack to which the second application belongs;

[0012] Store the stack information of the second task stack into the first database, and create a first mapping relationship between the first database and the secondary stack;

[0013] Display the interface of the first application in the first display area according to the first display parameter, and at the same time, based on the first mapping relationship, display the interface of the second application in the second display area according to the second display parameter.

[0014] In a second aspect, some embodiments of the present application provide a split - screen control method, including:

[0015] When the interface of the first application is displayed on the display, in response to a split - screen instruction input by the user, create the first task stack to which the first application belongs as the primary stack, and at the same time create a secondary stack, where the primary stack corresponds to the first display area, the secondary stack corresponds to the second display area, and the first application supports split - screen;

[0016] Calculate the first display parameter of the first display area and the second display parameter of the second display area;

[0017] If the second application participating in split - screen does not support split - screen, find the second task stack to which the second application belongs;

[0018] Store the stack information of the second task stack into the first database, and create a first mapping relationship between the first database and the secondary stack;

[0019] Display the interface of the first application in the first display area according to the first display parameter, and at the same time, based on the first mapping relationship, display the interface of the second application in the second display area according to the second display parameter.

[0020] As can be seen from the above technical solutions, for the display device and the split-screen control method provided in the above embodiments, when the interface of the first application is displayed on the display, in response to the split-screen instruction input by the user, the first task stack to which the first application belongs is created as the primary stack, and at the same time, a secondary stack is created. The primary stack corresponds to a first display area, the secondary stack corresponds to a second display area, and the first application supports split-screen. Calculate the first display parameters of the first display area and the second display parameters of the second display area. If the second application participating in the split-screen does not support split-screen, find the second task stack to which the second application belongs. Then store the stack information of the second task stack in the first database, and create a first mapping relationship between the first database and the secondary stack. Display the interface of the first application in the first display area according to the first display parameters, and at the same time, display the interface of the second application in the second display area based on the first mapping relationship according to the second display parameters. In this way, when it is necessary to display the first application and the second application in split-screen, even if the second application does not support split-screen, the first application and the second application can still be displayed in split-screen mode, avoiding split-screen failure. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0022] Figure 1 Schematic diagram of the operation scenario between the display device and the control device provided in the embodiments of the present application;

[0023] Figure 2 Hardware configuration block diagram of the control device 100 provided in the embodiments of the present application;

[0024] Figure 3 Hardware configuration block diagram of the display device 200 provided in the embodiments of the present application;

[0025] Figure 4 Software configuration diagram of the display device 200 provided in the embodiments of the present application;

[0026] Figure 5 Schematic diagram of the user interface of the display device 200 provided in some embodiments of the present application;

[0027] Figure 6 Schematic diagram of the flow of the split-screen control method provided in some embodiments of the present application;

[0028] Figure 7 Schematic diagram of the split-screen display principle provided in some embodiments of the present application;

[0029] Figure 8 Another schematic diagram of the split - screen display principle provided for some embodiments of the present application;

[0030] Figure 9 Another schematic diagram of the split - screen display principle provided for some embodiments of the present application;

[0031] Figure 10 Another schematic diagram of the split - screen display principle provided for some embodiments of the present application;

[0032] Figure 11 Another schematic diagram of the split - screen display principle provided for some embodiments of the present application;

[0033] Figure 12 Schematic diagram of the calculation method flow of the first display parameter and the second display parameter provided for some embodiments of the present application;

[0034] Figure 13 Schematic diagram of the display area scaling principle provided for some embodiments of the present application;

[0035] Figure 14 Another schematic diagram of the display area scaling principle provided for some embodiments of the present application;

[0036] Figure 15 Another schematic diagram of the user interface of the display device 200 provided for some embodiments of the present application;

[0037] Figure 16 Another schematic diagram of the user interface of the display device 200 provided for some embodiments of the present application;

[0038] Figure 17 Another schematic diagram of the user interface of the display device 200 provided for some embodiments of the present application;

[0039] Figure 18 Another schematic diagram of the user interface of the display device 200 provided for some embodiments of the present application;

[0040] Figure 19 Another schematic diagram of the user interface of the display device 200 provided for some embodiments of the present application;

[0041] Figure 20 Schematic diagram of the specific application process of the split - screen control method provided for some embodiments of the present application;

[0042] Figure 21 Schematic diagram of the method flow for adjusting the Activity interface provided for some embodiments of the present application. Detailed implementation manners

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the following will clearly and completely describe the exemplary embodiments of this application and the corresponding drawings. Obviously, the described exemplary embodiments are only a part of the embodiments of this application, rather than all of the embodiments.

[0044] It should be noted that the brief description of the terms in this application is only for the convenience of understanding the following described embodiments, rather than intending to limit the embodiments of some embodiments of this application. Unless otherwise specified, these terms should be understood in their ordinary and common meanings.

[0045] The terms "first", "second", "third", etc. in the description, claims, and the above-mentioned drawings of this application are used to distinguish similar or homogeneous objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that such terms can be interchanged under appropriate circumstances.

[0046] The terms "comprising" and "having" and any variations thereof are intended to cover but not exclude inclusion. For example, a product or device comprising a series of components does not necessarily have to be limited to all the components clearly listed, but may include other components not clearly listed or inherent to these products or devices.

[0047] The display device provided by the embodiments of this application can have various implementation forms. For example, it can be a television, a smart TV, a laser projection device, a monitor, an electronic bulletin board, an electronic table, etc.

[0048] Figure 1 and Figure 3 is a specific implementation manner of the display device of this application.

[0049] Figure 1 is a schematic diagram of the operation scenario between the display device and the control device in the exemplary embodiments of this application. As Figure 1 shown, the user can operate the display device 200 through the mobile terminal 300 and the control device 100.

[0050] In some embodiments, the control device 100 can be a remote control. The communication between the remote control and the display device includes infrared protocol communication or Bluetooth protocol communication, and other short-distance communication methods, and controls the display device 200 wirelessly or wiredly. The user can input user instructions through the buttons on the remote control, voice input, control panel input, etc. to control the display device 200.

[0051] In some embodiments, a smart device 300 (such as a mobile terminal, a tablet computer, a computer, a laptop, etc.) may also be used to control the display device 200. For example, an application running on the smart device is used to control the display device 200.

[0052] In some embodiments, the display device may receive instructions not by using the above-mentioned smart device or control device, but by receiving user control through touch, gestures, etc.

[0053] In some embodiments, the display device 200 may also be controlled in a manner other than the control device 100 and the smart device 300. For example, it may directly receive a user's voice instruction for control through a module for obtaining voice instructions configured inside the display device 200, or receive a user's voice instruction for control through a voice control device provided outside the display device 200.

[0054] In some embodiments, the display device 200 also communicates with the server 400. The display device 200 is allowed to communicate and connect through a local area network (LAN), a wireless local area network (WLAN), and other networks. The server 400 may provide various contents and interactions to the display device 200. The server 400 may be a cluster or multiple clusters, and may include one or more types of servers.

[0055] Figure 2 An exemplary hardware configuration block diagram of the control device 100 according to an exemplary embodiment is shown. As Figure 2 shown, the control device 100 includes a controller 110, a communication interface 130, a user input / output interface 140, a memory, and a power supply. The control device 100 can receive a user's input operation instruction, and convert the operation instruction into an instruction recognizable and responsive by the display device 200, acting as an interaction intermediary between the user and the display device 200. As Figure 3 , the display device 200 includes at least one of a tuner demodulator 210, a communicator 220, a detector 230, an external device interface 240, a processor 250, a display 260, an audio output interface 270, a memory, a power supply, and a user interface.

[0056] In some embodiments, the processor includes a video processor, an audio processor, a graphics processor, RAM, ROM, and first to n interfaces for input / output. The display 260 includes a display screen component for presenting a picture, and a driving component for driving image display, which is used to receive an image signal output from the processor and display video content, image content, and a menu control interface component, as well as a user control UI interface. The display 260 may be a liquid crystal display, an OLED display, and a projection display, and may also be a projection device and a projection screen.

[0057] The communicator 220 is a component for communicating with external devices or servers according to various communication protocol types. For example, the communicator may include at least one of a Wifi module, a Bluetooth module, a wired Ethernet module, other network communication protocol chips such as a near-field communication protocol chip, and an infrared receiver. The display device 200 can establish the sending and receiving of control signals and data signals with the external control device 100 or the server 400 through the communicator 220.

[0058] The user interface can be used to receive control signals from the control device 100 (such as an infrared remote control, etc.).

[0059] The detector 230 is used to collect signals from the external environment or for external interactions. For example, the detector 230 includes a light receiver, a sensor for collecting the intensity of environmental light; or, the detector 230 includes an image collector, such as a camera, which can be used to collect external environmental scenes, user attributes, or user interaction gestures. Or, the detector 230 includes a sound collector, such as a microphone, etc., for receiving external sounds.

[0060] The external device interface 240 may include, but is not limited to, the following: any one or more of a high-definition multimedia interface (HDMI), an analog or data high-definition component input interface (component), a composite video input interface (CVBS), a USB input interface (USB), an RGB port, etc. It can also be a composite input / output interface formed by the above multiple interfaces.

[0061] The tuner demodulator 210 receives broadcast television signals through wired or wireless reception, and demodulates audio and video signals, such as EPG data signals, from multiple wireless or wired broadcast television signals.

[0062] In some embodiments, the processor 250 and the tuner demodulator 210 may be located in different split devices, that is, the tuner demodulator 210 may also be in an external device of the main device where the processor 250 is located, such as an external set-top box, etc.

[0063] The processor 250 controls the operation of the display device and responds to user operations through various software control programs stored in the memory. The processor 250 controls the overall operation of the display device 200. For example: in response to receiving a user command for selecting a UI object to be displayed on the display 260, the processor 250 can perform operations related to the object selected by the user command.

[0064] In some embodiments, the processor includes at least one of a Central Processing Unit (CPU), a video processor, an audio processor, a Graphics Processing Unit (GPU), a Random Access Memory (RAM), a Read-Only Memory (ROM), a first interface to an nth interface for input / output, a communication bus (Bus), etc.

[0065] The user can input a user command through the graphical user interface (GUI) displayed on the display 260, and then the user input interface receives the user input command through the graphical user interface (GUI). Alternatively, the user can input a user command by inputting a specific sound or gesture, and then the user input interface recognizes the sound or gesture through the sensor to receive the user input command.

[0066] The "user interface" is a media interface for interaction and information exchange between an application or an operating system and a user, and it realizes the conversion between the internal form of information and the form acceptable to the user. The common manifestation form of the user interface is the graphical user interface (GUI), which refers to the user interface related to computer operation displayed in a graphical manner. It can be an icon, a window, a control, etc. interface element displayed on the display screen of an electronic device, where the control can include visible interface elements such as an icon, a button, a menu, a tab, a text box, a dialog box, a status bar, a navigation bar, a Widget, etc.

[0067] As Figure 4 shown, the system of the display device is divided into three layers, namely the application layer, the middleware layer, and the hardware layer from top to bottom.

[0068] The application layer mainly includes common applications on the TV and an application framework. Among them, the common applications are mainly applications developed based on the browser, such as HTML5 APPs; and native applications (Native APPs).

[0069] The application framework is a complete program model that has all the basic functions required for a standard application software, such as file access, data exchange..., and the usage interfaces of these functions (toolbars, status bars, menus, dialog boxes).

[0070] Native applications (Native APPs) can support online or offline, message push, or local resource access.

[0071] The middleware layer includes various middleware such as TV protocols, multimedia protocols, and system components. The middleware can use the basic services (functions) provided by the system software to connect various parts of the application system on the network or different applications, and can achieve the purpose of resource sharing and function sharing.

[0072] The hardware layer mainly includes the HAL interface, hardware, and drivers. Among them, the HAL interface is the unified interface for all TV chips to dock, and the specific logic is implemented by each chip. The drivers mainly include: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor drivers (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver, etc.

[0073] The display device 200 can be configured with various different applications, such as network video, online games, network social applications, etc. These applications provide users with richer content and services. However, as the number of applications configured on the display device increases, users' requirements for the presentation method of applications on the display device 200 are also getting higher and higher. For example, users hope to conduct social activities and watch videos on the display device 200 at the same time, that is, operate on the network social application and the network video application simultaneously in the foreground of the display device 200.

[0074] To achieve simultaneous operation of at least two applications in the foreground of the display device 200, Android provides a variety of multi-window technologies: split-screen mode, picture-in-picture mode, and Freeform (free window) mode. Among them, as Figure 5 shown in the user interface, after the display device 200 starts the split-screen mode, the system will divide the screen into two parts. The currently opened application will move to the upper part of the screen (if it is in landscape mode, it will move to the left side of the screen), and all other opened applications will be listed in the lower part (if it is in landscape mode, it will move to the right side of the screen) in the form of multitasking. Figure 5 In the user interface shown, the application on the left is the media asset playback application, and the application on the right is the video chat application. In Figure 5 the shown user interface, the user can operate on the media asset playback application and the video chat application simultaneously. For example, perform fast forward / rewind operations in the media asset playback application, or perform operations such as closing / opening the microphone in the video chat application, etc. However, Figure 5 the basis of the split screen shown is that both the media asset playback application and the video chat application support the split-screen mode. In actual applications, after the display device 200 starts the split-screen mode, it may cause the split screen to fail due to some applications not supporting the split-screen mode.

[0075] In view of the above problems, some embodiments of the present application provide a split-screen control method applied to a display device 200. To facilitate the understanding of the technical solutions in some embodiments of the present application, the following describes each step in detail in combination with some specific embodiments and drawings. Figure 6 It is a schematic flowchart of a split-screen control method executed by a display device 200 provided in some embodiments of the present application.

[0076] As Figure 6 shown, the controller 250 in some embodiments of the present application is configured to execute the following steps:

[0077] Step S601, when the interface of the first application is displayed on the display, in response to a split-screen instruction input by the user, create the first task stack to which the first application belongs as the primary stack, and at the same time create a secondary stack, where the primary stack corresponds to the first display area, the secondary stack corresponds to the second display area, and the first application supports split-screen.

[0078] Before implementing the split-screen control method of the present application, it is necessary to first start the first application on the display device 200. Specifically, it may be in response to a start instruction for the first application received through the user input interface. At this time, the interface of the first application can be drawn according to the full-screen window size during full-screen display, and the interface of the first application can be controlled to be full-screen displayed on the display. It can also draw the interface of the first application according to the window size during non-full-screen display, and control the interface of the first application to be non-full-screen displayed on the display. That is to say, the present application does not limit the initial display mode of the first application.

[0079] It should be noted that since the first task stack to which the first application belongs needs to be created as the primary stack, the first application supports split-screen display. Here, for the first application to support split-screen display, the first application needs to meet the following conditions: the first application is not Launcher; the resizeable parameter of the first application is set to true. This is because Launcher (HomeScreen) is the first application to run after the display device 200 is powered on. Therefore, Launcher is actually also an application program, and its function is to display and manage other applications on the display device 200. The Launcher application also has an interface and needs to configure an Activity as the container of the application page.

[0080] Here, the Activity component is one of the four major components provided by the Android system. The Activity component is the carrier of an interface in an application, that is, the Activity component is the container of the application page of the application, and the application pages are all composed of the Activity component. When the user clicks an application icon on the desktop, the application will be launched and the application page carried by the main Activity component will be displayed. When operating the application, multiple application pages can be displayed by calling multiple Activity components. In the Android system, the Activity window is implemented and scheduled by different task stacks.

[0081] For the Launcher application, it has a special Activity stack type, which is marked as home. That is to say, the stack type of the task stack to which the Launcher application belongs is the home stack. When the display device 200 starts the split-screen mode, the home-type stack will be automatically filtered. This is because in the process of the control logic for managing split screens in related technologies, only the management of the primary type of the split-screen main stack and the secondary type of the secondary stack is included. That is to say, in the process of adjusting the size and position of the Activity stack of the application in the split-screen process in related technologies, the control and compatibility of the home-type stack are lacking. Therefore, if the first application is the Launcher application, it will cause the first application not to support split screens. Therefore, this application restricts the first application from being the Launcher application.

[0082] In addition, whether an application supports split screens also depends on the interface configuration of the application. If the application adds the attribute android:resizeableActivity="false" to the AndroidManifest.xml in the interface configuration, it will cause the interface of the application not to support split screens. This situation is also defaulted to unable to enable split screens in the Android system. The solution in related technologies for the inability to split screens caused by the interface configuration of the application itself is to forcibly ignore the function of the application's resizeable configuration. After this function is enabled, ordinary applications that do not support split screens can also enable split screens. However, the solution in related technologies cannot solve the problem that special applications such as the Launcher application cannot enable split screens. The embodiment of this application can not only solve the problem of the inability to split screens caused by the interface configuration of ordinary applications, but also solve the problem of the inability to split screens caused by the inherent attributes of the Launcher application.

[0083] After receiving the split-screen instruction input by the user, in response to the split-screen instruction, in the embodiments of the present application, it is equivalent to the split screen initiated by the first application. Therefore, the first task stack to which the first application belongs can be started to the split-screen stack, and then the first task stack to which the first application belongs is created as the primary stack, that is, the stack type of the first task stack to which the first application belongs is changed from the fullscreen type to the primary type, and at the same time, a secondary stack is created.

[0084] It should be noted that the key to split screen lies in the primary stack. That is to say, only by creating the primary stack first can the split-screen state be carried out. If the primary stack is not created, the display device 200 cannot enter the split-screen mode, and if the primary stack disappears, the split-screen state will also automatically exit.

[0085] In the multi-window framework, the display area of different stacks can be controlled by setting the boundaries of the task stacks. The stack boundary is represented by Rect(left, top, right, bottom), and the four stored values respectively represent the positions of the four sides of the rectangle from the coordinate axes. The size of the window finally displayed on the screen is determined according to the size of the task stack boundary. As Figure 7 shown in the schematic diagram, it is the state of the Activity in the split-screen mode. The entire screen includes two areas: the first display area and the second display area. The first display area is the display area corresponding to the primary stack, and the second display area is the display area corresponding to the secondary stack. Figure 7 In the shown schematic diagram, the first display area and the second display area are in the left-right split-screen mode, and the present application does not make a display for the specific split-screen form. The first display area and the second display area can also be in the up-down split-screen form as Figure 8 shown. At the same time, the relative positions of the first display area and the second display area are not limited either.

[0086] For example, in the left-right split-screen mode, the first display area corresponding to the primary stack can be located on the left side of the second display area corresponding to the secondary stack (as Figure 7 shown); the first display area corresponding to the primary stack can be located on the right side of the second display area corresponding to the secondary stack (as Figure 9as shown). The specific display orientation here can be set according to user needs. If the user needs to display the interface of the currently displayed application (the first application) on the left, it can be set that the first display area corresponding to the primary stack can be located on the left of the second display area corresponding to the secondary stack. If the user needs to display the interface of the currently displayed application on the right, it can be set that the first display area corresponding to the primary stack can be located on the right of the second display area corresponding to the secondary stack.

[0087] Step S602, calculate the first display parameter of the first display area and the second display parameter of the second display area.

[0088] After creating the primary stack and the secondary stack and determining the first display area corresponding to the primary stack and the second display area corresponding to the secondary stack, it is also necessary to calculate the first display parameter of the first display area and the second display parameter of the second display area.

[0089] In some embodiments, the first display parameter of the first display area and the second display parameter of the second display area can be calculated according to the position of the split-screen middle bar. Among them, there is a second mapping relationship between the position of the split-screen middle bar and the split-screen ratio, and the split-screen ratio is based on the ratio of the first display area corresponding to the primary stack and the second display area corresponding to the secondary stack set by the user. That is to say, the split-screen ratio of the first display area and the second display area can be determined according to the user position, and then the position of the split-screen middle bar can be determined according to the split-screen ratio.

[0090] For example, in response to the split-screen ratio set by the user being 1:1, that is, the user needs to display the first display area and the second display area on the display in a 1:1 ratio, the position of the split-screen middle bar is in the middle of the display, as Figure 7 shown in the user interface, the first display area and the second display area are presented on the display in a 1:1 split-screen ratio. In response to the split-screen ratio set by the user being 2:1, that is, the user needs to display the first display area and the second display area on the display in a 2:1 ratio, the position of the split-screen middle bar is at the 2 / 3 position of the display, as Figure 10 shown in the user interface, the first display area and the second display area are displayed on the display in a 2:1 ratio for the first display area and the second display area. In response to the split-screen ratio set by the user being 1:2, that is, the user needs to display the first display area and the second display area on the display in a 1:2 ratio, the position of the split-screen middle bar is at the 1 / 3 position of the display, as Figure 11 shown in the user interface, the first display area and the second display area are displayed on the display in a 1:2 ratio for the first display area and the second display area.

[0091] In practical applications, if the first display area and the second display area are configured in the Figures 7 to 11 way, it may cause the layout of the application interface to be squeezed. Therefore, the Figures 7 to 11 shown first display area and second display area can be scaled. For example, the Figure 12 scaling method shown includes the following processes:

[0092] Step S1301, obtain the first size of the first basic area, where the first basic area is the display area of the application in the full-screen state;

[0093] Step S1302, determine the second size of the second basic area according to the split-screen ratio, where the second basic area is the display area of the application in the split-screen state;

[0094] Step S1303, calculate the first display parameter of the first display area and the second display parameter of the second display area according to the first size and the second size.

[0095] As shown in Figure 13 the scaling principle diagram, the range marked with # is called resolvedBound, and this range is the range in the full-screen state of the application, that is, the first basic area. When the first application starts, the system side sends the first size of the first basic area to the controller, and the controller controls the first application to be displayed on the screen in the first size first.

[0096] The range marked with @ is called parentBound, and this range is the size of the task stack that limits the Activity size in the split-screen state, that is, the second basic area. When the split-screen mode starts, the system vehicle sends the second size of the second basic area to the controller. In the related art, the second size is directly used as the final split-screen display size, which will cause the interface of the application to be compressed and displayed. In the embodiments of the present application, the second size of the second basic area can be determined according to the frequency division ratio. Then finally, the first display parameter of the first display area and the second display parameter of the second display area are calculated according to the first size and the second size. Here, the first display parameter and the second display parameter are both size parameters of the display area and do not include specific coordinate parameters.

[0097] Figure 13The example of the scaling principle is based on a split-screen ratio of 1:1, that is, the position of the split-screen middle bar is in the exact middle of the display screen. The first basic area is the entire screen range of the machine, so the first size is 1920×1080. Then, according to the 1:1 split-screen ratio, the second size of the second basic area is determined to be 960×1080 (in fact, only the width of the second basic area needs to be confirmed, that is, dividing the width of the first basic area by 2 to get the width of the second basic area as 960). Then, based on the first size and the second size, the sizes of the first display area and the second display area are determined (in fact, the height of the first display area is calculated), and the calculation formula is as follows:

[0098]

[0099] Among them, H1 is the height of the first display area, D1 is the width of the first display area (in fact, it is the width of the second basic area, with a value of 960), H2 is the height of the first basic area, with a value of 1080, and D2 is the width of the first basic area, with a value of 1920. Therefore, the finally calculated value of H1 is 540. The size of the first display area is 960×540. Since the display ratio is 1:1, the size of the second display area is also 960×540. The display ranges of the first display area and the second display area (the width of the second display area is D3 and the height is H3, and the calculation process is the same as that of the first display area) are as shown in Figure 13 the range marked by * (this range is called compatBound). Figure 13 The scaling ratios (equal ratio scaling ratios) of the first display area and the second display area shown are both 0.5, and this scaling ratio is recorded in the mScale parameter.

[0100] Figure 14 The example of the scaling principle is based on a split-screen ratio of 2:1, that is, the position of the split-screen middle bar is at the 2 / 3 position of the display screen. The first basic area is the entire screen range of the machine, so the first size is 1920×1080. Then, according to the 2:3 split-screen ratio, the second size of the second basic area is determined to be 1280×1080 (in fact, only the width of the second basic area needs to be confirmed, that is, multiplying the width of the first basic area by 2 / 3 to get the width of the second basic area as 1280). Then, based on the first size and the second size, the size of the first display area is determined (in fact, the height of the first display area is calculated), and the calculation formula is as follows:

[0101]

[0102] Among them, H1 is the height of the first display area, D1 is the width of the first display area (actually the width of the second basic area, with a value of 1280), H2 is the height of the first basic area, with a value of 1080, and D2 is the width of the first basic area, with a value of 1920. Therefore, the finally calculated value of H1 is 720. The size of the first display area is 1280×720.

[0103] The size calculation formula of the second display area is as follows:

[0104]

[0105] Among them, H3 is the height of the second display area, D3 is the width of the second display area (actually 1 / 3 of the width of the first basic area, with a value of 640), H2 is the height of the first basic area, with a value of 1080, and D2 is the width of the first basic area, with a value of 1920. Therefore, the finally calculated value of H1 is 360. The size of the second display area is 640×360. The display ranges of the first display area and the second display area are as Figure 15 the range of * in (this range is called compatBound). Figure 15 As shown, the scaling ratio of the first display area is 2 / 3, and this scaling ratio is recorded in the mscale parameter corresponding to the first display area. The scaling ratio of the second display area is 1 / 3, and this scaling ratio is recorded in the mscale parameter corresponding to the second display area.

[0106] In the related art, only parentBound and resolvedBound are used, and the ranges of the two are equal. Since a task stack may contain multiple Activities, parentBound is originally used to limit that all Activities in the stack have the same size, that is, they cannot exceed the range defined by parentBound. In the embodiments of the present application, the above adjustments are also made to the display process of the Activity, so that parentBound and resolvedBound are no longer exactly equal, so that the actual display area of the application can exceed the range defined by parentBound. Then when the Activity display elements are drawn and ready to be refreshed on the Surface of WindowState, this resolvedBound is scaled according to the mscale parameter corresponding to each area, and finally the scaled content is sent to the surface for display.

[0107] For example, Figure 13 In the shown scaling principle diagram, the mscale parameters of the first display area and the second display area are both 0.5. Therefore, after scaling resolvedBound according to this scaling ratio, we getFigure 13 The interface of the compatBound range size shown. And in Figure 14 the shown scaling principle diagram, the mscale parameter of the first display area is 2 / 3. Therefore, after scaling the resolvedBound according to this scaling ratio, we get Figure 14 the interface of the compatBound range size on the left. The mscale parameter of the second display area is 1 / 3. Therefore, after scaling the resolvedBound according to this scaling ratio, we get Figure 14 the interface of the compatBound range size on the right.

[0108] Step S603, if the second application participating in split - screen does not support split - screen, search for the second task stack to which the second application belongs;

[0109] Step S604, store the stack information of the second task stack into the first database, and create a first mapping relationship between the first database and the secondary stack;

[0110] Step S605, based on the first mapping relationship, while displaying the interface of the first application in the first display area according to the first display parameter, display the interface of the second application in the second display area according to the second display parameter.

[0111] When the process of Step S601 - Step S602 is completed to create the primary stack and the secondary stack and determine the first display parameter of the first display area corresponding to the primary stack and the second display parameter of the second display area corresponding to the secondary stack, then based on the determined display size, the Activity carrying the application interface can be split - screen displayed. Since the first application supports split - screen, the interface of the first application can be drawn in the first display area corresponding to the primary stack based on the first display parameter. If the second application participating in split - screen also supports split - screen, the second task stack to which the second application belongs can be created as the secondary stack, and then based on the second display parameter, the interface of the second application can be drawn in the second display area corresponding to the secondary stack, thus realizing the split - screen display of the interface of the first application and the interface of the second application.

[0112] Specifically, if the first application supports split-screen, the first task stack to which the first application belongs can be launched into the split-screen stack, and then the fullscreen type of the first task stack can be modified to the primary type, so as to create the first task stack to which the first application belongs as the primary stack. Similarly, if the second application also supports split-screen, the second task stack to which the second application belongs can be launched into the split-screen stack, and then the fullscreen type of the second task stack can be modified to the secondary type, so as to create the second task stack to which the second application belongs as the secondary stack.

[0113] However, if the second application does not support split-screen, the second task stack to which the second application belongs cannot be directly created as the secondary stack, and the split-screen display of the interface of the first application and the interface of the second application cannot be achieved. To solve the above problems, in the embodiments of the present application, the second task stack to which the second application belongs can be searched, and then the stack information of the second task stack can be stored in the first database. After being stored in the first database, the ID of the second task stack is updated to split_home_id. The stack information of the second task stack may be the stack ID. Then, a first mapping relationship between the first database and the secondary stack is created, that is, the task stack corresponding to the stack ID stored in the first database can be designed as the secondary stack and displayed in the type of the secondary stack.

[0114] The Android native multi-window is a multi-task stack solution, that is, there are multiple ActivityStacks. The task stack is an abstract stack, and each task stack has its own screen area (Bound) and ID. Activities are organized in a task manner and placed in a certain task stack. For example, Launcher belongs to the stack with id = HOME_STACK, and the id of the task stack where the ordinary Activity is located is FULLSCREEN_WORKSPACE_STACK_ID.

[0115] The task stack exists in the AMS (ActivityManagerService) service of the system process. The task stack is a collection of a series of ActivityRecords (a class in AMS that records the launched Activity components). Multiple task stacks can be created simultaneously in the AMS service, and different task stacks manage different Activity components respectively. A task stack can include all the Activity components corresponding to the same application, or it can also include Activity components corresponding to different applications. That is to say, different Activity components of an application can be scattered in different task stacks. For example, if the payment software can be called in the chat software, then the Activity components of the payment software and the chat software can be located in the same task stack in order to complete the same project.

[0116] The ActivityRecord can be mapped to the "truly launched Activity component" in the application process through the Token. The Token is a static inner class of the Activity component and is created by the AMS for the newly launched Activity component. It is a Binder (communication mechanism) with a token representing the Activity, that is to say, the Token is a unique identifier created by the AMS for the Activity component, and the Token of the Activity component can be used to identify the Activity component. The Activity component is displayed through a window, and the WMS (WindowManagerService) is responsible for managing all the windows in the current system. The Activity component is managed in the AMS in the form of a task stack. The data structure in the WMS corresponds one-to-one with the data structure in the AMS, and the Token, as the unique identifier of the Activity component, can be used as the basis for window grouping. Therefore, the corresponding window information can be found using the Token, and the window information here includes the task stack where the Activity component is located.

[0117] Therefore, in the embodiments of the present application, the task stack to which the Activity component corresponding to the second application belongs can be found according to the Token of the Activity component, that is, the second task stack to which the second application belongs can be found based on the Token of the Activity component. For example, if the second application is the Launcher application, the second task stack to which the second application belongs, that is, the Home stack, can be found based on the Token of the Activity component corresponding to the second application, and the ID of the Home stack is "HOME_STACK". If the second application is a common application, the second task stack to which the second application belongs, that is, the common stack, can also be found based on the Token of the Activity component corresponding to the second application, and the stack information of the common stack can be "current stack id: 26, current number of activities in the stack: 2". This stack information indicates that the stack id is 26 and this task stack includes two activities.

[0118] After the stack information (stack ID) of the second task stack to which the second application belongs is found, the stack information (stack ID) is then stored in the first database, and a first mapping relationship between the first database and the secondary stack is created. After the mapping relationship between the first database and the secondary stack is established, when splitting the screen, the task stacks in the first database can be displayed in the form of the secondary stack.

[0119] For example, if the second application is the Launcher application, the second task stack to which the second application belongs, that is, the Home stack, can be found based on the Token of the Activity component corresponding to the second application, and the ID of the Home stack is "HOME_STACK". Then the stack ID "HOME_STACK" is written into the first database. Then when splitting the screen, the stack ID "HOME_STACK" can be retrieved from the first database, and then the task stack with the stack ID "HOME_STACK" is displayed in the form of the secondary stack. If the second application is a common application and the found stack ID is 26, when splitting the screen, the stack ID 26 can be retrieved from the first database, and then the task stack with the stack ID 26 is displayed in the form of the secondary stack.

[0120] In the embodiments of the present application, the second task stack to which the second application belongs is not directly created as the secondary stack, but a first database having a first mapping relationship with the secondary stack is created, and then when splitting the screen, according to the stack ID stored in the first database, the task stack corresponding to the stack ID is displayed in the form of the secondary stack. That is to say, finally, the task stack corresponding to the stack ID stored in the first database is not created as a real secondary stack, but is displayed in the form of the secondary stack.

[0121] In step S602, the first display parameter corresponding to the primary stack for the first display area and the second display parameter corresponding to the secondary stack for the second display area have been calculated. Therefore, when performing split-screen display, the interface of the first application can be displayed in the first display area according to the first display parameter. Then, based on the first mapping relationship, after looking up the stack ID from the first database, the second task stack corresponding to the stack ID is displayed in the second display area according to the second display parameter, that is, the interface of the second application is displayed in the second display area according to the second display parameter. If it is a left-right split-screen display, the final display effect is as Figure 15 shown (the split-screen ratio is 1:1, corresponding to Figure 13 ) or as Figure 16 shown (the split-screen ratio is 2:1, corresponding to Figure 14 ).

[0122] As can be seen from the above technical solutions, for the display device and split-screen control method provided in the above embodiments, when the interface of the first application is displayed on the display, in response to the split-screen instruction input by the user, the first task stack to which the first application belongs is created as the primary stack, and at the same time, a secondary stack is created. The primary stack corresponds to having a first display area, the secondary stack corresponds to having a second display area, and the first application supports split-screen. Calculate the first display parameter for the first display area and the second display parameter for the second display area. If the second application participating in the split-screen does not support split-screen, look up the second task stack to which the second application belongs. Then store the stack information of the second task stack in the first database, and create a first mapping relationship between the first database and the secondary stack. Display the interface of the first application in the first display area according to the first display parameter, and at the same time display the interface of the second application in the second display area according to the second display parameter based on the first mapping relationship. In this way, when it is necessary to perform split-screen display for the first application and the second application, even if the second application does not support split-screen, the first application and the second application can still be displayed in split-screen mode, avoiding split-screen failure.

[0123] When splitting the screen, it is necessary to display the interface of the first application on the display, and then drag the icon corresponding to the second application participating in the split screen onto the screen to complete the split-screen operation. However, this process requires first finding the icon corresponding to the second application and then dragging the icon corresponding to the second application onto the screen, and the operation is relatively cumbersome. Also, if the user accidentally releases the hand before dragging the icon corresponding to the second application onto the screen, it will also cause split-screen failure.

[0124] To solve the above problems, in some embodiments, the operation of selecting the second application can be performed in the following manner: After responding to the split-screen instruction input by the user, a list of the first application combinations can be displayed on the display (such asFigure 17 As shown, the first application combination list corresponds to the first application, and the first application combination list at least includes the first application combination of the first application and the second application. Then, in response to the selection instruction for the first application combination input by the user, it is determined whether the second application participating in the split screen supports split screen, and then the split screen process of the first application and the second application is performed. In this way, if split screen needs to be implemented, the user only needs to click the split screen button control and then click the first application combination in the first application combination list, so as to complete the split screen operation with two clicks, and avoid the situation that the user accidentally releases the hand before dragging the icon corresponding to the second application onto the screen, resulting in the failure of the split screen operation.

[0125] In some embodiments, for the application combination related to the first application, a third mapping relationship between the position of the split screen middle bar and the split screen ratio can also be set, so as to achieve the effect of different split screen displays between the first application and different applications. For example, if the split screen ratio between the display area corresponding to the first application and the display area corresponding to the second application is set to 1:1, when the first application and the second application are split screen displayed, the position of the split screen middle bar is in the middle of the display screen. Calculate the display parameters of the primary stack and the secondary stack according to the position of the split screen middle bar. Finally, the display area sizes of the first application and the second application are the same. If the split screen ratio between the display area corresponding to the first application and the display area corresponding to the second application is set to 2:1, when the first application and the third application are split screen displayed, the position of the split screen middle bar is at the 2 / 3 position of the display screen. Calculate the display parameters of the primary stack and the secondary stack according to the position of the split screen middle bar. Finally, the display area of the first application is twice that of the display area of the third application.

[0126] In some embodiments, after storing the stack information of the second task stack to which the second application belongs in the first database through the above steps and completing the split screen, the stack information of the second task stack can be retained in the first database and the first database can be retained after exiting the split screen. Then, when the first application is displayed on the display, in response to the split screen instruction input by the user again, the first task stack to which the first application belongs is created as the primary stack, and the secondary stack is created at the same time. Similarly, calculate the first display parameters of the first display area corresponding to the primary stack and the second display parameters of the second display area corresponding to the secondary stack.

[0127] When it is determined that the second application is the application participating in split-screen, at this time, it is not necessary to store the stack information of the second task stack to which the second application belongs in the first database (the stack information of the second task stack has already been stored in the first database). The stack information of the second task stack can be directly read from the first database, and then the second task stack is displayed on the display according to the second display parameter of the secondary stack, that is, while the interface of the first application is displayed in the first display area according to the first display parameter, the interface of the second application is displayed in the second display area according to the second display parameter.

[0128] However, when split-screen is required again, if it is determined that the third application is the application participating in split-screen and the third application does not support split-screen, at this time, the stack information of the third task stack to which the third application belongs cannot be directly read from the first database. Therefore, it is necessary to find the third task stack to which the third application belongs, and then store the stack information of the third task stack in the first database. Then, the third task stack can be displayed on the display according to the third display parameter of the secondary stack, that is, while the interface of the first application is displayed in the first display area according to the first display parameter, the interface of the third application is displayed in the second display area according to the second display parameter.

[0129] Figure 15 and Figure 16 In the user interface shown in, although the application interface is scaled proportionally so that the interface content is not squeezed, they are all displayed at the top, which is not conducive to the user's viewing. Therefore, the embodiment of the present application can also further center the display area of the specified display based on the split-screen method in the above embodiment, that is, Figure 15 and Figure 16 the content of the first application interface and the content of the second application interface displayed at the top in the user interface are centered. The specific process of centering is as follows:

[0130] Figure 15 and Figure 16The starting origin of the displayed Activity is (0, 0). The vertical starting position of the Activity can be adjusted by calculating the coordinates of the windows of all interfaces in the WMS. Specifically, when calculating the size of the split-screen stack in SystemUI (the Divider in the SystemUI module manages all objects related to split-screen), the actual screen size, the size of the left application stack (display parameters of the primary stack), the size of the right application stack (display parameters of the secondary stack), the package name of the left application, and the package name of the right application are recorded in the database. The corresponding parameters can be obtained from the database in the computeFrame of the Window. Then, according to the height (H1) of the compatBound after splitting, the offset coordinates of the upper left corner (0, 0) are calculated if the window needs to be centered, and the first display area and the second display area are re-determined according to the offset coordinates.

[0131] For example, when the splitting ratio is 1:1, both H1 and H3 are 540. Therefore, based on Figure 15 To center the content of the first application interface and the second application interface, the upper left corner of the Activity of both needs to be moved down by 270, and finally the display effect as shown in Figure 18 is obtained. When the split-screen ratio is 2:1, H1 is 720 and H3 is 360. Therefore, based on Figure 15 To center the content of the first application interface, the upper left corner of the Activity corresponding to the first application needs to be moved down by 180, and the upper left corner of the Activity corresponding to the second application needs to be moved down by 360. Finally, the display effect as shown in Figure 19 is obtained.

[0132] Based on the split-screen control method described in the above embodiments, in the flowchart as shown in Figure 20 the following is the specific application process of the split-screen control method provided by the embodiments of the present application. In this example, the Launcher application participates in the split-screen. The process specifically includes the following steps:

[0133] Step S1801, the recent task initiates split-screen. When the user enables split-screen, the main screen generally has existing tasks and does not need to be restarted. The corresponding task can be found through mRootWindowContainer.anyTaskForId().

[0134] Step S1802, the specified task stack in the recent task is started into the split-screen stack, so that the type of the task stack is changed from the fullscreen type to the primary type. The specified task stack in the recent task refers to the task stack to which the task (Activity corresponding to the application) belongs.

[0135] Step S1803: Query the stack information of the home stack to which the Launcher application belongs, and then write the home stack ID to the database split_home_id.

[0136] Step S1804: Initiate a stack status change callback.

[0137] Step S1805: After SystemUI receives the primary stack creation or stack status change callback, calculate the display parameters of the primary stack and the secondary stack according to the position of the split screen middle bar (the position of the split screen middle bar is determined according to the split ratio).

[0138] Step S1806: Reconfigure and adjust the display parameters of the primary stack and the secondary stack.

[0139] Step S1807: Query the information in the database split_home_id. If the database value is empty, directly end the split screen. If the database value is not empty, proceed to Step S1808.

[0140] Step S1808: Query the stack with the ID split_home_id through AMS, and then readjust the home stack according to the display parameters (size and position) of the secondary stack, so that the home stack is displayed in the form of the secondary stack.

[0141] Among them, the process of calculating the display parameters of the primary stack and the secondary stack and adjusting the Activity interface according to the display parameters is as Figure 21 shown, and this process specifically includes the following steps:

[0142] Step S2101: Detect that the Activity interface needs to be adjusted.

[0143] Step S2102: Determine whether the current Activity stack is a split screen stack (primary stack). If the current Activity stack is not a split screen stack, proceed to Step S2103. If the current Activity stack is a split screen stack, proceed to Step S2105.

[0144] Step S2103: Query the split_home_id information.

[0145] Step S2104: Determine whether the current stack is a split screen home stack. If it is not a split screen home stack, proceed to Step S2107. If it is a split screen home stack, proceed to Step S2105.

[0146] Step S2105, calculate the size of compatBound and the ratio of mscale according to the size of the stack type parentBound.

[0147] Step S2106, adjust resolvedBound to the full screen size.

[0148] Step S2107, continue the interface refresh process of the related technology.

[0149] Step S2018, enter the WindowState drawing process and prepare to send it to the surface for display.

[0150] Step S2019, determine whether mscale is not equal to 1. If mscale is not equal to 1, then perform Step S2110. If mscale is equal to 1, then perform Step S2111.

[0151] Step S2010, perform scale scaling on the current Window display content.

[0152] Step S2011, send the scaled Window display content to the surface for display or send the unscaled Window display content to the surface for display.

[0153] For the same and similar parts among the various embodiments in this specification, reference can be made to each other, and details will not be repeated here.

[0154] Those skilled in the art can clearly understand that the technologies in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solutions in the embodiments of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disc, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of the various embodiments or some parts of the embodiments of the present invention.

[0155] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the various embodiments of the present application.

[0156] For ease of explanation, the above description has been presented in connection with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Many modifications and variations are possible in light of the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and the practical applications, so that those skilled in the art can better use the embodiments and various different modified embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that, comprising: a display; a controller configured to: when displaying the interface of a first application on the display, in response to a split-screen instruction input by a user, create the first task stack to which the first application belongs as a primary stack, and simultaneously create a secondary stack, wherein the primary stack corresponds to a first display area, the secondary stack corresponds to a second display area, and the first application supports split-screen; calculate a first display parameter of the first display area and a second display parameter of the second display area; if a second application participating in split-screen does not support split-screen, find the second task stack to which the second application belongs; store the stack information of the second task stack in a first database, and create a first mapping relationship between the first database and the secondary stack; display the interface of the first application in the first display area according to the first display parameter, and simultaneously display the interface of the second application in the second display area according to the second display parameter based on the first mapping relationship.

2. The display device according to claim 1, characterized in that, the controller is further configured to: if a second application participating in split-screen supports split-screen, create the second task stack to which the second application belongs as a secondary stack, and display the interface of the first application in the first display area according to the first display parameter, and display the interface of the second application in the second display area according to the second display parameter.

3. The display device according to claim 1, characterized in that, when the controller executes to determine that a second application participating in split-screen does not support split-screen, it is configured to: determine that the second task stack to which the second application belongs is the home stack, or determine that the second application does not support split-screen when the resizeableActivity of the second application is set to false.

4. The display device according to claim 1, characterized in that, when the controller executes to calculate a first display parameter of the first display area and a second display parameter of the second display area, it is configured to: calculate a first display parameter of the first display area and a second display parameter of the second display area according to the position of the split-screen middle bar, wherein there is a second mapping relationship between the position of the split-screen middle bar and the split-screen ratio, and the split-screen ratio is the ratio of the first display area corresponding to the primary stack and the second display area corresponding to the secondary stack based on user settings.

5. The display device according to claim 4, characterized in that, when the controller executes to calculate a first display parameter of the first display area and a second display parameter of the second display area, it is configured to: obtain a first size of a first basic area, wherein the first basic area is the display area of an application in full-screen state; determine a second size of a second basic area according to the split-screen ratio, wherein the second basic area is the display area of an application in split-screen state; Calculate a scaling ratio based on the first dimension and the second dimension, and determine a first display parameter of the first display area and a second display parameter of the second display area according to the scaling ratio, where the scaling ratio is an equal-proportion scaling ratio.

6. The display device according to claim 1, wherein, in response to a split-screen instruction input by a user, the controller is further configured to: display a first application combination list on the display, where the first application combination list corresponds to the first application, and the first application combination list at least includes a first application combination of the first application and the second application; in response to a selection instruction input by a user, determine whether the second application participating in the split screen supports split screen, where the selection instruction is used to indicate selection of the first application combination.

7. The display device according to claim 6, wherein, there is a third mapping relationship between the position of the split-screen middle bar and the split-screen ratio, and the split-screen ratio is a ratio of a display area corresponding to a first application and a display area corresponding to a second application set by a user.

8. The display device according to claim 1, wherein, the controller is further configured to: when displaying the interface of the first application on the display, in response to a split-screen instruction input by a user again, create the first task stack to which the first application belongs as the primary stack, and create a secondary stack at the same time; calculate a first display parameter of a first display area corresponding to the primary stack and a second display parameter of a second display area corresponding to the secondary stack; if the application participating in the split screen is the second application, look up the stack information of the second task stack from the first database based on the first mapping relationship, so that while displaying the interface of the first application in the first display area according to the first display parameter, display the interface of the second application in the second display area according to the second display parameter.

9. The display device according to claim 8, wherein, the controller is further configured to: if the application participating in the split screen is a third application and the third application does not support split screen, look up the third task stack to which the third application belongs; store the stack information of the third task stack in the first database; display the interface of the first application in the first display area according to the first display parameter, and at the same time, based on the first mapping relationship, display the interface of the third application in the second display area according to the second display parameter.

10. A split-screen control method, wherein, applied to a display device, the split-screen control method includes: when displaying the interface of a first application on the display, in response to a split-screen instruction input by a user, create the first task stack to which the first application belongs as the primary stack, and create a secondary stack at the same time, where the primary stack corresponds to a first display area, the secondary stack corresponds to a second display area, and the first application supports split screen; Calculate the first display parameter of the first display area and the second display parameter of the second display area; If the second application participating in split-screen does not support split-screen, find the second task stack to which the second application belongs; Store the stack information of the second task stack in the first database, and create a first mapping relationship between the first database and the secondary stack; According to the first display parameter, display the interface of the first application in the first display area, and at the same time, based on the first mapping relationship, display the interface of the second application in the second display area according to the second display parameter.