CN111367456A

CN111367456A - Communication terminal and display method in multi-window mode

Info

Publication number: CN111367456A
Application number: CN202010128710.8A
Authority: CN
Inventors: 荆楠楠; 孙哲
Original assignee: Hisense Mobile Communications Technology Co Ltd
Current assignee: Hisense Mobile Communications Technology Co Ltd
Priority date: 2020-02-28
Filing date: 2020-02-28
Publication date: 2020-07-03

Abstract

The application discloses a communication terminal and a display method in a multi-window mode. The communication terminal includes: a touch screen configured to receive a touch operation from a user; a display screen configured to display a user interface; a processor coupled to the touch screen and the display screen, respectively; the display displays at least two windows, wherein a first window of the at least two windows is a non-full screen window; the processor is configured to: in response to a user operation of launching an application in the first window or launching a background running application into the first window, displaying a user interface of the application in the first window, and enabling the layout of interface elements of the user interface to be matched with the size of the first window.

Description

Communication terminal and display method in multi-window mode

Technical Field

The present application relates to the field of communications, and in particular, to a communication terminal and a display method in a multi-window mode.

Background

With the popularization of intelligent communication terminals, more and more functions are supported by the communication terminals, and in order to enable users to obtain better use experience, more and more communication terminals support a multi-window mode. In the multi-window mode, two or more windows can be displayed on the screen of the communication terminal, and user interfaces of different applications can be displayed in different windows.

One typical type of multi-window mode is a picture-in-picture mode, where picture-in-picture refers to displaying one or more sub-windows in a main window, and the main window and the sub-windows may display different contents so that a user can view the contents in the main window and the contents in the sub-windows simultaneously. The sub-window may also be located outside the main window. Another typical type of multi-window mode is a split-screen mode, which means that two or more non-overlapping windows are displayed simultaneously on the same screen. In addition, the multi-window mode may also include other types, such as a full-screen window and one or more small windows (a small window is a non-full-screen window, whose window size is smaller than the full-screen window) displayed on the screen.

How to correctly display the user interface of the application program in the multi-window mode is a problem to be solved at present.

Disclosure of Invention

An exemplary embodiment of the present application provides a communication terminal and a display method in a multi-window mode, so as to correctly display a user interface of an application program in the multi-window mode.

According to an aspect of the exemplary embodiments, there is provided a communication terminal including:

a touch screen configured to receive a touch operation from a user;

a display screen configured to display a user interface;

a processor coupled to the touch screen and the display screen, respectively;

the display displays at least two windows, wherein a first window of the at least two windows is a non-full screen window;

the processor is configured to:

in response to a user operation of launching an application in the first window or launching a background running application into the first window, displaying a user interface of the application in the first window, and enabling the layout of interface elements of the user interface to be matched with the size of the first window.

Based on the embodiment, when the application is started to the non-full screen window, the size of the non-full screen window can be obtained, so that when the application performs layout design on the interface elements of the user interface, the layout design can be performed according to the size of the non-full screen window, and the layout of the interface elements of the user interface is matched with the size of the non-full screen window.

In the above embodiment, the processor is further configured to: when the application running in the background is started to the user operation in the first window, the application is informed to perform horizontal and vertical screen switching, so that the application obtains the size of the first window, and layout setting is performed on interface elements of a user interface according to the size of the first window.

Based on the embodiment, when the application running in the background is started to the non-full-screen window, the application is notified to perform horizontal and vertical screen switching, so that the application obtains the size of the non-full-screen window, and the application can perform layout design according to the size of the non-full-screen window when performing layout design of interface elements of a user interface. By adopting the embodiment, when the application is started to the full screen window and then enters the background operation, and then is called to the foreground and needs to be displayed on the non-full screen window, the layout of the interface elements of the user interface can be matched with the size of the non-full screen window.

In the above embodiment, the processor is further configured to: after the user interface of the application is displayed in the first window, responding to the user operation of horizontal and vertical screen switching, adjusting the layout of the at least two windows, redrawing the user interface in the first window, and enabling the interface element layout of the user interface in the first window to be matched with the size of the first window.

Based on the above embodiment, when the horizontal and vertical screens are switched, the application currently displayed in the non-full screen window can obtain the size of the non-full screen window, so that when the application performs the layout design of the interface elements of the user interface, the application can perform the layout design according to the size of the non-full screen window, and the layout of the interface elements of the user interface is adapted to the size of the non-full screen window.

In the above embodiment, the processor is further configured to: judging whether the application needs to be displayed in a non-full screen window or not according to the request of the application for acquiring the size of a default display window; if the application needs to be displayed in a non-full screen window, acquiring the size of the first window, wherein the first window is a target window for displaying the application, otherwise, acquiring the size of a default display window; and informing the application of the acquired size of the window.

Based on the above embodiment, when the application requests the application framework layer to acquire the default display window size, the application framework layer needs to determine whether the application needs to be displayed in the non-full-screen window, and if so, returns the size of the non-full-screen window instead of the size of the full-screen window (the default display window size is usually the size of the full-screen window), so that when the application performs the interface element layout design of the user interface, the application can perform the layout design according to the size of the non-full-screen window, so that the interface element layout of the user interface is adapted to the size of the non-full-screen window.

In the above embodiment, the processor is further configured to: according to the request of the application for acquiring the size of the default display window, judging whether the application needs to be displayed in a non-full-screen window or not, and according to first attribute information, judging whether the application needs to be displayed in the non-full-screen window or not; wherein the first attribute information is used to indicate a name of an application package launched into the first window, and the first attribute information is created when the first window is created.

In the above embodiment, the processor is further configured to: when the size of the first window is obtained, obtaining the size of the first window according to second attribute information; wherein the second attribute information is used to indicate a size of the first window, and the second attribute information is created when the memory window is created.

According to an aspect of an exemplary embodiment, there is provided a display method in a multi-window mode, including: in response to a user operation of launching an application in the first window or launching a background running application into the first window, displaying a user interface of the application in the first window, and enabling the layout of interface elements of the user interface to be matched with the size of the first window.

In the above embodiment, the method further includes: when the application running in the background is started to the user operation in the first window, the application is informed to perform horizontal and vertical screen switching, so that the application obtains the size of the first window, and layout setting is performed on interface elements of a user interface according to the size of the first window.

In the above embodiment, before displaying the user interface of the application in the first window, the method further includes: judging whether the application needs to be displayed in a non-full screen window or not according to the request of the application for acquiring the size of a default display window; if the application needs to be displayed in a non-full screen window, acquiring the size of the first window, wherein the first window is a target window for displaying the application, otherwise, acquiring the size of a default display window; and informing the application of the acquired size of the window.

According to an aspect of the exemplary embodiments, there is provided a computer storage medium having stored therein computer program instructions which, when run on a computer, cause the computer to perform the above-described method.

On the basis of the common knowledge in the field, the above preferred conditions can be combined randomly to obtain the preferred embodiments of the application.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.

Fig. 1 schematically illustrates a structural diagram of a communication terminal provided in an embodiment of the present application;

fig. 2 is a schematic diagram illustrating a software architecture of a communication terminal according to an embodiment of the present application;

fig. 3 is a schematic diagram illustrating a user interface of a communication terminal provided by an embodiment of the present application;

FIGS. 4a and 4b are diagrams illustrating a comparison of a full screen window and a multi-window mode user interface in a scene;

5a, 5b illustrate a comparison of a full screen window and a multi-window mode displaying a user interface in another scenario;

FIG. 6 is a schematic flow chart illustrating the application starting in the widget in the embodiment of the present application;

fig. 7, fig. 8, and fig. 9 respectively illustrate schematic diagrams of a user interface in a multi-window mode in an embodiment of the present application.

Detailed Description

The technical solution in the embodiments of the present application will be described in detail and removed with reference to the accompanying drawings. Wherein in the description of the embodiments of the present application, "/" means or, unless otherwise stated, for example, a/B may mean a or B; "and/or" in the text is only an association relationship describing an associated object, and means that three relationships may exist, for example, a and/or B may mean: three cases of a alone, a and B both, and B alone exist, and in addition, "a plurality" means two or more than two in the description of the embodiments of the present application.

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

Fig. 1 shows a schematic configuration of a communication terminal 100.

The communication terminal 100 in the embodiment of the present application supports a multi-window mode, for example, the communication terminal may be a smartphone, a wearable device, a tablet computer, and the like, which support the multi-window mode.

The following describes an embodiment specifically taking the communication terminal 100 as an example. It should be understood that the communication terminal 100 shown in fig. 1 is only an example, and the communication terminal 100 may have more or less components than those shown in fig. 1, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

A block diagram of a hardware configuration of a communication terminal 100 according to an exemplary embodiment is exemplarily shown in fig. 1. As shown in fig. 1, the communication terminal 100 includes: a Radio Frequency (RF) circuit 110, a memory 120, a display unit 130, a camera 140, a sensor 150, an audio circuit 160, a Wireless Fidelity (Wi-Fi) module 170, a processor 180, a bluetooth module 181, and a power supply 190.

The RF circuit 110 may be used for receiving and transmitting signals during information transmission and reception or during a call, and may receive downlink data of a base station and then send the downlink data to the processor 180 for processing; the uplink data may be transmitted to the base station. Typically, the RF circuitry includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 120 may be used to store software programs and data. The processor 180 executes various functions of the communication terminal 100 and data processing by executing software programs or data stored in the memory 120. The memory 120 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. The memory 120 stores an operating system that enables the communication terminal 100 to operate. The memory 120 in the embodiment of the present application may store an operating system and various application programs, and may also store codes for performing the methods described in the embodiment of the present application.

The display unit 130 may be used to receive input numeric or character information and generate signal input related to user settings and function control of the communication terminal 100, and particularly, the display unit 130 may include a touch screen 131 disposed on the front surface of the communication terminal 100 and may collect touch operations of a user thereon or nearby, such as clicking a button, dragging a scroll box, and the like.

The display unit 130 may also be used to display a Graphical User Interface (GUI) of information input by or provided to the user and various menus of the terminal 100. Specifically, the display unit 130 may include a display screen 132 disposed on the front surface of the communication terminal 100. The display screen 132 may be configured in the form of a liquid crystal display, a light emitting diode, or the like. The display unit 130 may be used to display various graphical user interfaces described in embodiments of the present application.

The touch screen 131 may cover the display screen 132, or the touch screen 131 and the display screen 132 may be integrated to implement the input and output functions of the communication terminal 100, and after the integration, the touch screen may be referred to as a touch display screen for short. In the embodiment of the present application, the display unit 130 may display the application program and the corresponding operation steps.

The camera 140 may be used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing elements convert the light signals into electrical signals which are then passed to the processor 180 for conversion into digital image signals.

The communication terminal 100 may further comprise at least one sensor 150, such as an acceleration sensor 151, a distance sensor 152, a fingerprint sensor 153, a temperature sensor 154. The communication terminal 100 may also be configured with other sensors such as a gyroscope, barometer, hygrometer, thermometer, infrared sensor, optical sensor, motion sensor, and the like.

The audio circuitry 160, speaker 161, microphone 162 may provide an audio interface between a user and the communication terminal 100. The audio circuit 160 may transmit the electrical signal converted from the received audio data to the speaker 161, and convert the electrical signal into a sound signal for output by the speaker 161. The communication terminal 100 may also be provided with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 162 converts the collected sound signal into an electrical signal, converts the electrical signal into audio data after being received by the audio circuit 160, and outputs the audio data to the RF circuit 110 to be transmitted to, for example, another terminal or outputs the audio data to the memory 120 for further processing. In the embodiment of the present application, the microphone 162 may acquire the voice of the user.

Wi-Fi belongs to a short-distance wireless transmission technology, and the communication terminal 100 may help a user to send and receive e-mails, browse webpages, access streaming media, and the like through the Wi-Fi module 170, which provides a wireless broadband internet access for the user.

The processor 180 is a control center of the communication terminal 100, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the communication terminal 100 and processes data by running or executing software programs stored in the memory 120 and calling data stored in the memory 120. In some embodiments, processor 180 may include one or more processing units; the processor 180 may also integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a baseband processor, which mainly handles wireless communications. It will be appreciated that the baseband processor described above may not be integrated into the processor 180. The processor 180 in the embodiment of the present application may run an operating system, an application program, a user interface display, and a touch response, and the processing method in the embodiment of the present application. In addition, the processor 180 is coupled with the display unit 130 and the camera 140.

And the bluetooth module 181 is configured to perform information interaction with other bluetooth devices having a bluetooth module through a bluetooth protocol. For example, the communication terminal 100 may establish a bluetooth connection with a wearable electronic device (e.g., a smart watch) having a bluetooth module via the bluetooth module 181, so as to perform data interaction.

The communication terminal 100 also includes a power supply 190 (such as a battery) to power the various components. The power supply may be logically connected to the processor 180 through a power management system to manage charging, discharging, power consumption, etc. through the power management system. The communication terminal 100 may also be configured with power buttons for powering the terminal on and off, and for locking the screen.

Fig. 2 is a block diagram of a software configuration of the communication terminal 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include applications such as camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide a communication function of the communication terminal 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the communication terminal vibrates, and an indicator light flashes.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The following exemplifies the workflow of the software and hardware of the communication terminal 100 in connection with capturing a photographing scene.

When the touch screen 131 receives a touch operation, a corresponding hardware interrupt is issued to the kernel layer. The kernel layer processes the touch operation into an original input event (including touch coordinates, a time stamp of the touch operation, and other information). The raw input events are stored at the kernel layer. And the application program framework layer acquires the original input event from the kernel layer and identifies the control corresponding to the input event. Taking the touch operation as a touch click operation, and taking a control corresponding to the click operation as a control of a camera application icon as an example, the camera application calls an interface of an application framework layer, starts the camera application, further starts a camera drive by calling a kernel layer, and captures a still image or a video through the camera 140.

Fig. 3 is a schematic diagram for illustrating a user interface on a communication terminal (e.g., communication terminal 100 of fig. 1). In some implementations, a user can open a corresponding application by touching an application icon on the user interface, or can open a corresponding folder by touching a folder icon on the user interface.

The communication terminal in the embodiment of the application supports a multi-window mode. The user may enable or disable the multi-window mode as desired. Taking picture-in-picture mode as an example, a user may enable or exit picture-in-picture mode by setting a picture-in-picture mode setting option in the interface.

In the multi-window mode, an application displayed in a small window may not be displayed normally. In the embodiment of the application, a small window is distinguished from a full-screen window, and the small window is a non-full-screen window, and the size of the small window is smaller than that of the full-screen window. For example, a "widget" may be a split screen window in a split screen mode, or may be a sub-window in a picture-in-picture mode.

The "application" described in the embodiment of the present application may be a third-party application or a system application, or may be another type of application, and this is not limited in the embodiment of the present application.

Fig. 4a and 4b illustrate a comparison graph of user interface display in full-screen window mode and multi-window mode when processing by the existing scheme in a scenario.

As shown in fig. 4a, in this scenario, the first application is a shopping application, and when the application is started in a full-screen window and a user requests registration, the application displays a popup window 400 in a popup manner, and user usage statement content is displayed in the popup window 400.

As shown in fig. 4b, also taking the first application as an example, in this scenario, the communication terminal enables a picture-in-picture mode, and a first window 410 and a second window 420 are displayed on the screen of the communication terminal. The first window 410 is a small window and the second window 420 is a full screen window. The first application is a shopping application and is started into the first window 410, the second application is a game application and is started into the second window 420, the interface of the game is displayed in a full screen mode, a user use statement is displayed in a popup mode in the user interface of the shopping application, the width of the popup box 411 exceeds the width of the first window 410, the content of the user use statement cannot be completely displayed in the first window 410, and user use and user experience are affected.

Fig. 5a and 5b illustrate another scenario in which a contrast graph of user interface display in full-screen window and multi-window mode is processed by the existing scheme.

As shown in fig. 5a, in this scenario, the first application is a social application, and when the application is started in a full screen window and uses a video call, a video call window 500 of the application is as shown in fig. 5 a.

When the user starts the split screen mode, as shown in fig. 5b, a first split screen window 510 and a second split screen window 520 are displayed on the screen of the communication terminal. A first application (the social-type application) is displayed in a first split screen window 510. The second split screen window 520 displays a desktop (home screen interface) of the communication terminal. The length and width of the video call window in the user interface of the social application exceed the range of the first screen window 510, so that the video pictures in the video call window cannot be completely displayed in the first screen window 510, and the use and the experience of the user are influenced.

The embodiment of the application provides a display method in a multi-window mode, and when an application is started in a small window or an application running in a background is started in the small window, the layout of interface elements of a user interface can be matched with the size of the small window, so that the user experience is improved.

The following describes in detail a display process in a multi-window mode according to an embodiment of the present application with reference to the drawings.

Fig. 6 is a schematic flow chart illustrating the application starting in the widget in the embodiment of the present application.

In this embodiment, the communication terminal is currently in a multi-window mode, and the display displays at least two windows, including a first window, which is a small window. The following flow describes the starting process of the application a by taking the example of starting the application a in the widget, and as shown in the figure, the flow may include:

in S601, when the application a is started, a window size (window size) is requested from the application framework layer.

In this step, in some scenarios, the user may launch application a into the first window by clicking on application a's icon in the home page displayed in the first window.

The application A can call an interface for acquiring the window size, so that the application framework layer acquires the window size and returns the window size to the application A. For example, application a may obtain the window size by calling the following interface:

interface for obtaining a default display window width:

getWindowManager().getDefaultDisplay().getWidth()；

interface for obtaining default display window height:

getWindowManager().getDefaultDisplay().getHeigh()

an interface for acquiring an area that can be actually displayed by an application in a default display window (for example, if an icon (icon) area is included in the default display window, the icon area needs to be deducted by the application):

WindowManager().getDefaultDisplay().getRealMetrics()

in S602, after receiving the request of the application a for obtaining the window size, the application framework layer determines whether the target window of the application a is a widget, and preferentially records the widget by using the attribute container, so as to distinguish the drawing during the subsequent switching of the full-screen application interface from the non-full-screen application interface. If the window is small, go to S603, otherwise go to S604.

At S603, the application framework layer acquires the size of a small window (i.e., a first window) for displaying the application a, and returns the size of the first window to the application a.

For example, the size of the first window (portlet) is 1080 × 1170 (1080 full size 1080 × 2340).

At S604, the application framework layer obtains the size of the default display window and returns the size of the default display window to application a.

The default display window, i.e. the default main screen, is usually the full screen size, such as 1080 × 2340. the screen sizes of different models of communication terminals may be different according to the model differences of the communication terminals.

In S605 to S606, the application a performs layout design on interface elements in the user interface according to the size of the window returned by the application framework layer to obtain display parameters of the user interface, and provides the display parameters of the user interface to the application framework layer, and the application framework layer performs rendering and display of the user interface according to the display parameters of the user interface.

In this step, if the window size obtained by the application a is a small window size, the interface elements in the user interface are designed in a layout manner according to the small window size, so as to prevent the display range of the interface elements in the user interface from exceeding the range of the small window, for example, prevent a pop-up window or a video window in the user interface from exceeding the range of the small window. And if the window size obtained by the step A is the full-screen window size, layout design is carried out on interface elements in the user interface according to the full-screen window size.

And then, under the condition of not switching horizontal and vertical screens or switching window modes, the application A performs layout setting on interface elements in the user interface of the application according to the window size acquired during starting.

For an application, the layout display of each user interface of the application can include the following two modes:

the first method comprises the following steps: an interface display designed according to a relative layout, including but not limited to: top end alignment, both end alignment, full screen centering, left alignment, right alignment, and the like;

and the second method comprises the following steps: interface displays designed according to a fixed layout, including but not limited to: the width of the fixed interface display element, the height of the fixed interface display element, the distance from the fixed display interface element to the edge of the display window, the distance from the fixed display interface element to the Liu Hai area, and the like.

In the above flow, after receiving a request sent by the application a by calling an interface for obtaining a default display window size, the application framework layer does not directly return to the default display window size (the default display window size is the default home screen size, and is usually a full screen size), but returns the size of the small window to the application a when determining that the application a is started in the small window (i.e., the application a needs to be displayed in the small window). That is, when the application a is launched in the first window (widget), the window size returned by the application framework layer to the application a is the size of the first window (widget), but not the default size of the main screen window (such as the size of a full screen window), so that the application a performs layout design on the interface elements in the user interface according to the size of the widget, so that the layout of the interface elements in the user interface matches the size of the widget, so as to avoid that the display of the interface elements exceeds the range of the widget due to the fact that the layout of the interface elements does not match the size of the widget.

Fig. 7 is a schematic diagram illustrating a user interface in a multi-window mode in an embodiment of the present application. The scenario shown in this schematic is the same as the scenario of fig. 4 b. As shown in fig. 7, also taking the first application as an example, in this scenario, the communication terminal enables a picture-in-picture mode, and a first window 710 and a second window 720 are displayed on the screen of the communication terminal. The first window 710 is a full widget and the second window 720 is a full screen window. The first application is a shopping application and is started into the first window 710, the second application is a game application and is started into the second window 720, the interface of the game is displayed in a full screen mode, and a user use statement is displayed in a popup frame mode in the user interface of the shopping application. Due to the adoption of the method provided by the embodiment of the application, the width of the pop-up window 711 is matched with the width of the first window 710, so that the content of the user usage statement can be normally displayed in the first window 710 after being reduced in an equal proportion, a complete user operation button is provided, and the user experience is improved.

Fig. 8 is a schematic diagram illustrating a user interface in a multi-window mode in an embodiment of the present application. The scenario shown in this schematic is the same as the scenario of fig. 5 b. As shown in fig. 8, when the user starts the split screen mode, a first split screen window 810 and a second split screen window 820 are displayed on the screen of the communication terminal. A first application (the social-type application) is displayed in the first split screen window 810. The second split screen window 820 displays a desktop (home screen interface) of the communication terminal. By adopting the method provided by the embodiment of the application, the length and the width of the video call window in the user interface of the social application are matched with the range of the first split screen window 510, so that the video picture in the video call window can be normally displayed in the first split screen window 810 after being scaled down in equal proportion, and the user experience is improved.

Optionally, in some embodiments of the present application, when the communication terminal enables the multi-window mode, the application framework layer may obtain and record a package name of an application that needs to be launched into the widget and a display size of the widget, so that when launching the application, the application framework layer may determine whether the currently launched application needs to be launched into the widget according to the recorded package name of the application that needs to be launched into the widget, and return a window size to the application that needs to be launched into the widget according to the recorded size of the widget.

In particular, in some embodiments, when the communication terminal enters a multi-window mode, the application framework layer may obtain the package name of the application that needs to be launched into the widget. In the embodiment of the application, the related control of opening and closing of multiple windows and the like is realized by an application framework layer, and a menu of a small window starting mode can be provided to support a user to select which applications are started in a small window form or a full screen window form. Taking split screen as an example, the application may be split screen displayed by providing a certain starting mode, for example, a long press of a recent task key may perform split screen display on the currently started application, or a UI (user interface) menu may be provided on a desktop to directly start a certain application in a form of a small window, so that the application framework layer may obtain a package name of the application that needs to be started to the small window.

Alternatively, the package name of the application that needs to be launched into the widget may be recorded in the form of an attribute, which may be defined as: property _ AppNme. When the application is started, the application framework layer can judge whether the application needs to be started into the small window or not through the recorded property _ AppNme property.

In some further embodiments, when the communication terminal enters a multi-window mode (e.g., a split screen mode or a picture-in-picture mode), the application framework layer may record the size of the widget for the widget. Alternatively, the display size of the small window may be recorded in the form of an attribute, for example, the attribute may be defined as: property _ display. When an application requests an application framework layer to acquire a window size by calling a corresponding interface, the application framework layer obtains the size of a widget through the recorded property _ display attribute of the widget and returns the size to the application under the condition that the application is judged to need to be started to the widget.

In some embodiments of the present application, when the communication terminal performs horizontal and vertical screen switching in the multi-window mode, interface elements in the user interface in the small window may still be adapted to the size of the small window after the horizontal and vertical screen switching.

Specifically, when the communication terminal starts the multi-window mode, the user interface of the application a is displayed in the small window (the process of launching the application a to the small window can refer to the above embodiment). At this time, a horizontal-vertical screen switching occurs, and in response, the communication terminal adjusts the window layout (for example, when the vertical screen is switched to the horizontal screen, the layout in which the two windows are vertically arranged is adjusted to the layout in which the two windows are horizontally arranged, and vice versa), the application a requests the application framework layer to acquire the window size, and after receiving the request of the application a to acquire the window size, the application framework layer determines that the target window of the application a is a small window, therefore, the size of the small window used for displaying the application A is obtained, the size of the small window is returned to the application A, the application A carries out layout design on interface elements in the user interface according to the size of the window returned by the application framework layer to obtain display parameters of the user interface, and providing the display parameters of the user interface to an application framework layer, and rendering and displaying the user interface by the application framework layer according to the display parameters of the user interface. The processing procedure is similar to the flow shown in fig. 6 and will not be repeated here.

For example, taking the user interface shown in fig. 8 as an example, when the horizontal and vertical screens are switched, as shown in fig. 9, a first split screen window 910 and a second split screen window 920 are displayed on the screen of the communication terminal, and the vertical arrangement of the two windows before the horizontal and vertical screens are switched is adjusted to the horizontal arrangement after the switching. A first application (the social-type application) is displayed in the first split screen window 910. A desktop (home screen interface) of the communication terminal is displayed in the second split screen window 920. By adopting the method provided by the embodiment of the application, the length and the width of the video call window in the user interface of the social application are matched with the range of the first split screen window 910, so that the video picture in the video call window can be normally displayed in the first split screen window 910, and the user experience is improved.

In some scenarios, an application is already started and displayed as a full screen, and when the application is started again in a small window of a foreground after entering a background operation, the application does not acquire a window size any more according to a conventional flow, but performs layout setting of interface elements in a user interface according to the size of the full screen window acquired in the previous starting, so that a situation that the interface elements of the user interface are not matched with the size of the small window may occur.

Therefore, in some embodiments of the application, when the application currently running in the background and started in full screen is launched into a widget, the application framework layer may send a notification of switching between horizontal and vertical screens to the application after detecting the event, the application may request the application framework layer to obtain a window size after receiving the notification, the application framework layer may send the size of the target widget of the application to the application, so that the application performs layout design on interface elements in the user interface according to the size of the window returned by the application framework layer, obtains display parameters of the user interface, provides the display parameters of the user interface to the application framework layer, and the application framework layer performs user interface rendering and display according to the display parameters of the user interface. The processing procedure is similar to the flow shown in fig. 6 and will not be repeated here.

Optionally, when the application currently running in the background and being started in a full screen window is started, processing may be performed in a conventional manner, that is, the application framework layer does not need to send a notification of switching between horizontal and vertical screens to the application, and then does not trigger the application to send a request for obtaining a window size, where the application uses a default window size (that is, a default full screen window size) obtained when the application is started to design an interface element layout in the user interface.

In the above flow, taking the Android system as an example, the third-party application running in the background may be started by calling the startActivity interface, that is, when the application framework layer receives a relevant event or message of the startActivity interface, it is determined that the application running in the background needs to be called to the foreground currently. For example, an application currently running in the background can be started in a first window (widget) through UI menus, gestures, voice control and the like, and these starting operations need to call a starting interface of the widget provided by a system window module of an application framework layer, so that the window display of the application is directly changed into a widget form.

In the above flow, taking the Android system as an example, the application framework layer may trigger the application to call an interface for acquiring the window size by sending a configchange notification that triggers the horizontal-vertical screen switching, so that the application framework layer acquires the window size and returns the window size to the application.

According to a further aspect of the exemplary embodiments, there is provided a computer storage medium having stored therein computer program instructions which, when run on a computer, cause the computer to perform a processing method as described above.

Since the communication terminal and the computer storage medium in the embodiment of the present application may be applied to the processing method, reference may also be made to the above method embodiment for obtaining technical effects, and details of the embodiment of the present application are not described herein again.

Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

While specific embodiments of the present application have been described above, it will be appreciated by those skilled in the art that these are by way of example only, and that the scope of the present application is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the spirit and principles of this application, and these changes and modifications are intended to be included within the scope of this application.

Claims

1. A communication terminal, comprising:

a touch screen configured to receive a touch operation from a user;

a display screen configured to display a user interface;

a processor coupled to the touch screen and the display screen, respectively;

the processor is configured to:

2. The communication terminal of claim 1, wherein the processor is further configured to:

when the application running in the background is started to the user operation in the first window, the application is informed to perform horizontal and vertical screen switching, so that the application obtains the size of the first window, and layout setting is performed on interface elements of a user interface according to the size of the first window.

3. The communication terminal of claim 1, wherein the processor is further configured to:

after the user interface of the application is displayed in the first window, responding to the user operation of horizontal and vertical screen switching, adjusting the layout of the at least two windows, redrawing the user interface in the first window, and enabling the interface element layout of the user interface in the first window to be matched with the size of the first window.

4. The communication terminal of any of claims 1-3, wherein the processor is further configured to:

judging whether the application needs to be displayed in a non-full screen window or not according to the request of the application for acquiring the size of a default display window;

if the application needs to be displayed in a non-full screen window, acquiring the size of the first window, wherein the first window is a target window for displaying the application, otherwise, acquiring the size of a default display window;

and informing the application of the acquired size of the window.

5. The communication terminal of claim 4, wherein the processor is further configured to:

according to the request of the application for acquiring the size of the default display window, judging whether the application needs to be displayed in a non-full-screen window or not, and according to first attribute information, judging whether the application needs to be displayed in the non-full-screen window or not; wherein the first attribute information is used to indicate a name of an application package launched into the first window, and the first attribute information is created when the first window is created.

6. The communication terminal of claim 5, wherein the processor is further configured to:

when the size of the first window is obtained, obtaining the size of the first window according to second attribute information; wherein the second attribute information is used to indicate a size of the first window, and the second attribute information is created when the memory window is created.

7. A display method in a multi-window mode, comprising:

8. The method of claim 7, further comprising:

9. The method of claim 7 or 8, prior to displaying the user interface of the application in the first window, further comprising:

and informing the application of the acquired size of the window.

10. A computer storage medium having computer program instructions stored therein, which when run on a computer, cause the computer to perform the method of any one of claims 7-9.