Embedded window display method and device, electronic equipment and readable storage medium

Abstract

The invention relates to the technical field of embedded window display, and provides an embedded window display method and device, electronic equipment and a readable storage medium, the method comprises the following steps: when a preset operation instruction is detected, starting an embedded window in a currently displayed parent window according to the preset operation instruction; an embedded window application corresponding to the preset operation instruction is displayed in the embedded window, the embedded window and the parent window are located on the same level or adjacent levels, and the application displayed by the embedded window is associated with the parent window; when the operation instruction of the embedded window application is received, interactive operation is performed according to the operation instruction of the embedded window application, so that the corresponding application is opened through the embedded window, one-key operation is realized, the operation is more convenient, special adaptation is not needed, and any application can be used.

Description

Embedded window display method, device, electronic device and readable storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 29, 2022, with application number 202211203385.2 and application name “Embedded window display method, device, electronic device and readable storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the technical field of electronic devices, and in particular to an embedded window display method, device, electronic device, and readable storage medium. Background Art

[0003] Nowadays, electronic devices have more and more functions and more and more applications. When users use high-frequency quick services such as scanning and payment codes, they need to unlock the phone, open the application, and then select the corresponding service, which makes the operation cumbersome. For example, when users use applications such as screen off, lock screen, online conference or video, they also need to perform multiple operations to call up the corresponding service, which makes it inconvenient for users.

[0004] Summary of the Invention

[0005] The present application provides an embedded window display method, device, electronic device and readable storage medium, the purpose of which is to avoid users having to perform tedious operations to open applications and improve the convenience of use.

[0006] In a first aspect, the present application provides an embedded window display method, the method comprising:

[0007] When a preset operation instruction is detected, starting the embedded window in the currently displayed parent window according to the preset operation instruction;

[0008] Displaying an embedded window application corresponding to the preset operation instruction in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent levels, and the application displayed in the embedded window is associated with the parent window;

[0009] When an operation instruction of the embedded window application is received, an interactive operation is performed according to the operation instruction of the embedded window application.

[0010] The embedded window display method provided by the present application starts an embedded window in a currently displayed parent window according to the preset operation instruction when a preset operation instruction is detected; displays an embedded window application corresponding to the preset operation instruction in the embedded window, wherein the embedded window and the parent window are at the same level or an adjacent level, and the application displayed by the embedded window is associated with the parent window; when an operation instruction of the embedded window application is received, an interactive operation is performed according to the operation instruction of the embedded window application, thereby opening the corresponding application through the embedded window, realizing one-click operation, making the operation more convenient, and no special adaptation is required, and any application can be used.

[0011] In a possible implementation, starting the embedded window in the currently displayed parent window according to the preset operation instruction includes:

[0012] Drawing the parent window according to the preset operation instruction;

[0013] Starts the embedded window in the parent window after it has been drawn.

[0014] In a possible implementation, the drawing of the parent window according to the preset operation instruction includes:

[0015] Obtain the window size of the parent window to be drawn and the placeholder information of the embedded window in the parent window to be drawn;

[0016] Window drawing and layer synthesis are performed according to the window size of the parent window to be drawn and the placeholder information of the embedded window to obtain a parent window that has been drawn.

[0017] In a possible implementation, starting the embedded window in the currently displayed parent window according to the preset operation instruction includes:

[0018] Get the target window, window mode, window size of the embedded window, embedded window mark bit, stack mode of the embedded window, and touch mode of the embedded window;

[0019] The embedded window is drawn according to the target window, the window mode, the window size of the embedded window, the embedded window mark bit, the stack mode of the embedded window and the touch mode of the embedded window to obtain the embedded window.

[0020] In a possible implementation, after drawing the embedded window according to the target window, the window mode, the window size of the embedded window, the embedded window flag, the stack mode of the embedded window, and the touch mode of the embedded window, the method further includes:

[0021] When the stack mode of the embedded window is created, the stack control right is transferred to the host process corresponding to the parent window.

[0022] In a possible implementation, displaying the embedded window application corresponding to the preset operation instruction in the embedded window includes:

[0023] When drawing the embedded window, obtaining the window size of the application corresponding to the preset operation instruction and the configured window size of the embedded window; determining the display area of ​​the application corresponding to the preset operation instruction according to the window size and the configured window size of the embedded window;

[0024] The application corresponding to the preset operation instruction is displayed according to the display area.

[0025] In a possible implementation, after displaying the embedded window application corresponding to the preset operation instruction in the embedded window, the method further includes:

[0026] Get the preset synchronization event;

[0027] The display position of the embedded window is adjusted according to the preset synchronization event.

[0028] In a possible implementation, upon receiving the operation instruction of the embedded window application, performing the interactive operation according to the operation instruction of the embedded window application includes:

[0029] When an operation instruction of the embedded window application is received, an interface switching is performed according to the operation instruction of the embedded window application.

[0030] In a possible implementation, upon receiving the operation instruction of the embedded window application, after performing the interactive operation according to the operation instruction of the embedded window application, the method further includes:

[0031] Get an exit command and return to the target interface according to the exit command.

[0032] In a possible implementation, obtaining an exit instruction and returning to the target interface according to the exit instruction includes:

[0033] Remove the embedded task stack according to the exit instruction and return to the target interface.

[0034] In a second aspect, the present application provides an embedded window display device, comprising:

[0035] A starting module, configured to start the embedded window in the currently displayed parent window according to the preset operation instruction when a preset operation instruction is detected;

[0036] a display module, configured to display an embedded window application corresponding to the preset operation instruction in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent levels, and the application displayed in the embedded window is associated with the parent window;

[0037] The operation module is configured to perform interactive operations according to the operation instructions of the embedded window application when receiving the operation instructions of the embedded window application.

[0038] In a third aspect, the present application provides an electronic device, comprising:

[0039] One or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the electronic device, enable the electronic device to execute an embedded window display method as described in any one of the first aspect or possible implementations of the first aspect.

[0040] In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor executes an embedded window display method as described in any one of the above-mentioned first aspect or possible implementation methods of the first aspect.

[0041] In a fifth aspect, the present application provides a chip comprising a processor and a data interface, wherein the processor reads instructions stored in a memory through the data interface and executes the embedded window display method described in any one of the first aspect or possible implementations of the first aspect.

[0042] Optionally, as a possible implementation, the chip may further include a memory storing instructions, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the embedded window display method described in any one of the first aspect or possible implementations of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figures 1a and 1b are schematic diagrams of a scene of application process processing in the prior art;

[0044] FIG2 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

[0045] FIG3 is a block diagram of a software structure of an electronic device provided in an embodiment of the present application;

[0046] FIG4 is a flow chart of an embedded window display method according to an embodiment of the present application;

[0047] FIG5 is a schematic diagram of a scenario of starting an embedded window in an embedded window display method provided by another embodiment of the present application;

[0048] FIG6 is a schematic diagram of a display interface of an embedded window in an embedded window display method provided by another embodiment of the present application;

[0049] FIG7 is a module interaction diagram of an embedded window startup of an embedded window display method provided by another embodiment of the present application;

[0050] FIG8 is a schematic diagram of another example application covering an embedded window provided by this application;

[0051] FIG9 is a schematic diagram of an example input interface provided by this application covering an embedded window;

[0052] FIG10 is a schematic diagram of an adjusted embedded window according to an embedded window display method provided by another embodiment of the present application;

[0053] Figures 11a and 11b are schematic scene diagrams showing an example application lock interface provided by this application;

[0054] FIG12 is a functional schematic diagram of a shortcut card of an embedded window display method provided by another embodiment of the present application;

[0055] FIG13 is a flow chart of an embedded window display method according to another embodiment of the present application;

[0056] FIG14 is a schematic diagram showing loading of placeholder information in a parent window of an embedded window display method provided by another embodiment of the present application;

[0057] FIG15 is a flow chart of an embedded window display method according to another embodiment of the present application;

[0058] FIG16 is a schematic diagram of an embedded window application switching scenario of an embedded window display method provided by another embodiment of the present application;

[0059] FIG17 is a schematic diagram of an embedded window application switching scenario of an embedded window display method provided by another embodiment of the present application;

[0060] FIG18 is an interaction diagram of an embedded window exit module of an embedded window display method provided by another embodiment of the present application;

[0061] FIG19 is a schematic diagram of a scenario of an embedded window exit in an embedded window display method provided by another embodiment of the present application;

[0062] FIG20 is a schematic structural diagram of an embedded window display device provided in this application. DETAILED DESCRIPTION

[0063] The terms "first", "second" and "third" in the specification, claims and drawings of this application are used to distinguish different objects rather than to limit a specific order.

[0064] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0065] To make the description of the following embodiments clear and concise, a brief introduction to an implementation scheme of embedded window display is first given:

[0066] Currently, you can tap the back of the phone twice or three times to open a custom shortcut function on the phone, providing users with direct access to the next step in any scenario, as shown in Figure 1a, or tap the back of the phone twice or three times to open a custom shortcut function on the phone, as shown in Figure 1b, but it is impossible to interact with the user, interrupting the user's immersive experience.

[0067] Based on the problems existing in the above technical solutions, the present application provides an embedded window display method, by starting an embedded window in the currently displayed parent window according to the preset operation instruction when a preset operation instruction is detected; displaying the embedded window application corresponding to the preset operation instruction in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent level, and the application displayed by the embedded window is associated with the parent window; when receiving the operation instruction of the embedded window application, performing interactive operations according to the operation instruction of the embedded window application, thereby opening the corresponding application through the embedded window, realizing one-key operation, making the operation more convenient, and without the need for special adaptation, any application can be used. The provided embedded window display method can be applicable to electronic devices such as mobile phones, tablet computers, desktops, laptops, notebook computers, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), wearable electronic devices, smart watches, etc. Among them, the electronic device applicable to the embedded window display method can have a structure as shown in Figure 2.

[0068] As shown in Figure 2, Figure 2 is an example diagram of the composition of an electronic device provided in the present application. The electronic device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, a sensor module 280, a button 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, an air pressure sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity light sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, etc.

[0069] It should be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 200. In other embodiments, the electronic device 200 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

[0071] The controller may be the nerve center and command center of the electronic device 200. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0072] Processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 210 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 210. If processor 210 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 210 latency, and thus improves system efficiency.

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

[0074] It is understood that the interface connection relationship between the modules illustrated in this embodiment is merely a schematic illustration and does not constitute a structural limitation on the electronic device 200. In other embodiments of the present application, the electronic device 200 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0075] The wireless communication function of the electronic device 200 can be implemented through the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modem processor and the baseband processor.

[0076] The wireless communication module 260 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 200. The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210. The wireless communication module 260 can also receive the signal to be sent from the processor 210, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

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

[0078] Electronic device 200 implements display functionality through a GPU, display screen 294, and an application processor. A GPU is a microprocessor for image processing that connects display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs that execute program instructions to generate or modify display information.

[0079] A series of graphical user interfaces (GUIs) can be displayed on the display screen 294 of the electronic device 200, and these GUIs are the main screens of the electronic device 200. Generally speaking, the size of the display screen 294 of the electronic device 200 is fixed, and only limited controls can be displayed on the display screen 294 of the electronic device 200. A control is a GUI element, which is a software component included in an application that controls all data processed by the application and interactive operations on this data. Users can interact with the control through direct manipulation to read or edit relevant information of the application. Generally speaking, controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. For example, in an embodiment of the present application, the display screen 291 can display virtual buttons (one-key arrangement, start arrangement, scene arrangement).

[0080] The electronic device 200 can implement a shooting function through an ISP, a camera 293, a video codec, a GPU, a display screen 294, and an application processor.

[0081] The electronic device 200 can implement audio functions such as music playback and recording through the audio module 270, the speaker 270A, the receiver 270B, the microphone 270C, the headphone jack 270D, and the application processor.

[0082] Furthermore, operating systems run on the aforementioned components, such as Hongmeng OS, iOS OS, Android open-source OS, and Windows OS. Applications can be installed and run on these operating systems.

[0083] FIG3 is a software structure block diagram of an electronic device provided in an embodiment of the present application.

[0084] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other via software interfaces. In some embodiments of the present application, the software architecture of an electronic device includes at least three layers: from top to bottom, the application layer, the application framework layer, and the hardware abstraction layer.

[0085] The application layer may include a series of application packages. These application packages may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message. In some embodiments of the present application, the application layer also includes an embedded window service, an embedded window module, and an embedded window interface module. The embedded window service is a new module of the SystemUI module, and the embedded window module is a new module of the WM-Shell Lib module.

[0086] The embedded window module is used to implement the main functions of embedded window display interaction, including startup and exit control, window display control, state synchronization and event transmission.

[0087] The embedded window interface module is used to implement the embedded window capability interface encapsulation and provide it to the host process for calling.

[0088] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions. As shown in Figure 3, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc. The window manager is used to manage window programs. The window manager can obtain the size of the display screen, determine whether there is a status bar, lock the screen, take a screenshot, etc. In some embodiments of the present application, the application framework layer also includes an adjusted AMS module, an adjusted WMS module, and a newly added embedded window interface set.

[0089] The adjusted AMS module is used to implement embedded Activity startup and lifecycle management.

[0090] The adjusted WMS module is used to implement embedded task management, activity jump control within a task, focus and visibility management of embedded window scenes, config updates, and compatibility management.

[0091] The embedded window interface set is used to provide system applications.

[0092] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0093] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0094] The phone manager is used to provide communication functions for electronic devices, such as call status management (including answering, hanging up, etc.).

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

[0096] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0097] The hardware abstraction layer is an interface layer between the operating system kernel and the hardware circuit of the electronic device 200 , and its purpose is to abstract the hardware.

[0098] For ease of understanding, the following embodiments of the present application will take the electronic device 200 having the structure shown in Figures 2 and 3 as an example, and combine the accompanying drawings and application scenarios to specifically explain the embedded window display method provided in the embodiments of the present application.

[0099] FIG4 is a flow chart of an embedded window display method provided in one embodiment of the present application.

[0100] As shown in FIG4 , the embedded window display method may include:

[0101] Step S10: when a preset operation instruction is detected, the embedded window is started in the currently displayed parent window according to the preset operation instruction.

[0102] Under normal circumstances, when users currently use high-frequency quick services such as scanning and payment codes, the operations are cumbersome. For example, they need to unlock the phone first, then open the application, and then select the corresponding service. When users use quick services such as online meetings and videos when the screen is off or locked, the operations are not unified and inconvenient. This embodiment provides embedded window display capabilities to the application window, supports quick task cards to achieve efficient quick task window display, that is, during use, the user can open the application in the embedded window through preset operations and directly use the quick service by calling up the window. The window system provides embedded window display and interaction capabilities, supports quick task card Launcher, and facilitates users to use quick tasks efficiently.

[0103] In a specific implementation, the preset operation instruction may be a back-tap operation of the electronic device, a quick gesture operation, or other forms of operation. This embodiment does not limit this. In this embodiment, the back-tap operation of the electronic device is used as an example for explanation.

[0104] It should be noted that the number of back taps can be set, and the number of taps greater than 1 within the preset time is considered an effective tap event. Other numbers can also be set. This embodiment does not limit this and can be flexibly adjusted according to needs. Taking 2 taps as an effective back tap event as an example, in order to avoid misoperation, 2 taps are considered a valid back tap event, thereby improving the accuracy of starting the embedded window.

[0105] In order to realize opening the application through the embedded window, the scenario diagram of launching the embedded window is shown in Figure 5, where ① represents the main interface. The quick task card is launched by operating twice on the back, and the embedded window displays the WeChat payment application, as shown in Figure 6. The display interface diagram of the embedded window, where 10 represents the embedded window with the loaded application, and 20 represents the parent window.

[0106] In one possible implementation, the launched application can be launched according to a pre-set application. The pre-set launched application can be one, that is, the pre-set application is launched in the embedded window by operating the back twice. For example, as shown in Figure 6, the embedded window launches the WeChat payment application, thereby realizing quick application launch.

[0107] In one possible implementation, there can be multiple pre-set startup applications. When there are multiple applications, the priority of the applications can be set. When the embedded window is started to display the application, the application with the highest priority will be displayed first, and then other applications can be operated in sequence according to the switching operation, thereby improving the effectiveness of quick startup applications.

[0108] As shown in the module interaction diagram of the embedded window startup in Figure 7, when the startup operation of the target application is detected, the host process service is triggered, the host process sends a request to establish a connection with the embedded window service to the embedded window service, the embedded window service sends a request to obtain the embedded window cross-process communication instance to the embedded window module, the embedded window module returns the embedded window cross-process communication instance to the embedded window service, and the embedded window service returns the embedded window cross-process communication instance to the host process to realize direct communication between the host process and the embedded window module, wherein the host process can be the process corresponding to the parent window.

[0109] After the host process establishes a communication connection with the embedded window module, the host process first initializes and completes the drawing of the parent window. The specific drawing process is as follows: the host process sends a request to add a parent window to WMS, where the parent window request contains placeholder information, and sends the window size of the parent window to the Graphics drawing module for window drawing. The host process also sends layer information to SurfaceFlinger for parent window layer synthesis. After the layer synthesis is completed, the parent window is displayed. Then the host process sends a request to start the embedded window to the embedded window module. The request also includes startup parameters. The startup parameters include target window, window size, stack mode, touch mode and Back mode. Among them, the target window represents the window to start the corresponding application, the window size represents the size of the embedded window, the stack mode includes the application processing method in the embedded window, including new stack, stack demolition and reuse of main stack mode, the touch mode indicates whether the embedded window needs to have controls for touch interactive operations, and the Back mode indicates the application return processing method in the embedded window.

[0110] The embedded window module configures the target window, window mode, window size, embedded window mark bit and stack mode of the embedded window according to the received startup parameters, wherein the window mode indicates the display mode of the embedded window, including multi-window, picture-in-picture or floating frame display modes, and the embedded window mark bit indicates that the window is an embedded window identification information. The embedded window module sends the target window, window mode, window size, embedded window mark bit and stack mode to the AMS module. The AMS module sends the window mode and window size to the embedded application according to the target window to pull up the window, and then sends the embedded window mark bit and stack mode to the WMS module. The embedded application sends the window size to the WMS module to add the window, and the WMS module draws the window according to the window size and window size. The WMS module performs the drawing process of the embedded window, which includes: the embedded application sends the window size to the Graphics drawing module, the Graphics drawing module notifies the WMS module after the drawing is completed, the WMS module notifies the embedded window module that it has been created, and the stack control is transferred to the embedded window module, the embedded window module transfers the stack control to the host process, and the host process performs layer synthesis to realize the display of the window. The host process performs layer synthesis specifically as follows: the host process hangs the stack layer through SurfaceView, and sends a configuration request to set the embedded application stack layer to be visible to the SurfaceFlinger module, performs layer synthesis through the SurfaceFlinger module, and notifies the interaction module to display the interface after the synthesis is completed, thereby completing the startup of the embedded window.

[0111] Alternatively, the embedded window effect can be activated as a floating window, which then overlays the system card pack window, "digging a hole" in the card pack window to reveal the underlying application interface. This method does not require additional window capabilities and achieves the card display effect with relatively little effort, but it has three problems:

[0112] (1) Hierarchy issue. There are other types of windows between the third-party application window and the card package window. If these windows pop up, they will disrupt the card display effect. Figure 8 shows a schematic diagram of other applications covering the embedded window. In this embodiment, since application switching is performed through the embedded window, the third-party application window and the card package window are basically at the same level, thus solving the hierarchy issue.

[0113] (2) Task management issues. Directly using the main Task stack of a third-party application for card-style display, when applied in card-style and normal full-screen scenarios, the Activity interface states of the Task stack interfere with each other, resulting in a poor user experience. For example, a user is chatting on WeChat, and then calls out the card wallet to display the WeChat payment code. The system switches WeChat to card form and starts the payment code interface in the WeChat main Task stack. When the user completes the payment and returns to WeChat, they find that WeChat has returned to the home page. This is because after WeChat exits the card form, the WeChat main Task is cleaned up to avoid staying on the payment code interface, but this affects the user's ability to return to the previous chat task.

[0114] In this embodiment, after the embedded window is drawn, the control right of the embedded window is forwarded to the host process through the embedded window module, and the back mode of the embedded window is determined by the parent window, thereby ensuring the normal use of the embedded window.

[0115] When configuring the startup parameters of an embedded window, the Back mode of the embedded window can be configured as needed. The Back mode determines the return to the specified main interface or application. For example, when the embedded window displays the WeChat payment application, the user performs a Back operation. Since the embedded Task root Activity is displayed in the foreground in the new stack and unstack modes, a Back event is triggered. In the native Android process, this Back event will be consumed, and the business logic is to destroy the Activity. Ultimately, the embedded window is destroyed while its parent window is not destroyed, resulting in a display error.

[0116] In the reused main stack mode, when the embedded root activity of the embedded task is displayed in the foreground, a Back event is triggered. In the Android native process, the Back event will be consumed by it, and the business logic is: destroy the activity and display other activities under the activity; ultimately, the embedded window display area displays an embedded window that was not opened by the user.

[0117] In one possible implementation, when this embodiment determines to return to the designated main interface through the Back mode, when the embedded window is displayed as WeChat's payment application, the user performs a return operation to return to the main interface, thereby avoiding display errors or displaying an embedded window that is not pulled up by the user in the embedded window display area.

[0118] In one possible implementation, when this embodiment determines to return to the previous level application through the Back mode, when the embedded window is displayed as WeChat's payment application, the user performs a return operation to return to the previous level application interface, thereby avoiding display errors or the embedded window display area displaying an embedded window that is not pulled up by the user. It should be noted that the Back mode can also be flexibly configured according to needs, thereby improving the flexibility of interface operation display.

[0119] (3) System and application window synchronization issues. Since the system card package window and the third-party application window are "two skins", they lack the necessary association and are difficult to handle. If the adaptation is not comprehensive, some scenarios may experience state mismatch. The schematic diagram of the input interface covering the embedded window is shown in Figure 9.

[0120] In one possible implementation, in order to support the quick service card interface, the problem of hierarchical association can be solved, and embedded window interaction can be supported. In terms of Task management, the system provides a variety of embedded Task stack operation modes, including independent Task, reused main Task, and main Task stack disassembly. The appropriate operation mode is selected according to the compatibility of the embedded application. In terms of synchronization between the system and the application window, a synchronization event notification is added, and the quick service card Launcher makes necessary adjustments to the embedded application window. Specifically, it obtains a preset synchronization event and adjusts the display position of the embedded window according to the preset synchronization event. The schematic diagram of the adjusted embedded window is shown in Figure 10. The preset synchronization event can be to start other system applications. For example, when the WeChat payment application is displayed in the embedded window, if the input interface operation is required, the embedded window can be moved up to avoid the input interface covering the embedded window, thereby improving the effectiveness of the use of the embedded window.

[0121] In one possible implementation method, this embodiment forwards the control of the embedded window to the host process through the embedded window module after the window drawing is completed through the embedded window, and the window mode of the embedded window is determined by the host process to ensure the normal use of the embedded window. For example, when the corresponding application is started in the embedded window, when the application is configured with an application lock, the startup form of the application lock authentication interface can only be consistent with the startup interface. For example, when the application lock interface is loaded in a floating window, a picture-in-picture pip or a bubble, its interface form is naturally a floating window, a picture-in-picture or a bubble, such as the application lock interface in the picture-in-picture mode as shown in Figure 11a and the application lock interface in the floating window mode as shown in Figure 11b. However, if the input method needs to be called in the application lock unlocking interface, when the application lock interface window size is small, the input interface cannot be fully displayed in the application lock interface. Figures 11a and 11b are schematic scene diagrams of the application lock interface of the prior art.

[0122] However, when the startup operation of the target application is detected, the present embodiment obtains the preset display mode of the application lock interface according to the startup operation; and displays the application lock interface according to the preset display mode of the application lock interface, so that the application lock interface can be displayed according to the preset display mode of the application lock interface, that is, the window mode, without being determined according to the form of the startup interface, thereby improving the flexibility of starting the application lock authentication interface. In order to avoid incomplete display of the application lock interface, the application lock interface is set to be displayed in full screen to ensure the normal display of the application lock interface.

[0123] In the specific implementation, for this embodiment, the embedded window module obtains the display mode of the preset application lock interface, that is, the window mode, specifies the display mode according to the configuration, and starts the embedded window through the AMS module. The AMS module then sends the display mode and window size to the embedded application to pull up the embedded application window, thereby avoiding determination based on the form of the startup interface, and instead displaying the application lock interface through the preset application lock interface display mode, thereby improving the flexibility of starting the application lock authentication interface.

[0124] In another embodiment, since the embedded window startup is implemented, after the embedded window is displayed, the foreground focus is generally on the embedded window. When the pending events are obtained, the pending events are transmitted to the window corresponding to the foreground focus for processing. However, when the embedded window consumes the pending events, in the new stack and unstack modes, the embedded Task root Activity triggers a Back event when it is displayed in the foreground. Under the Android native process, the Back event will be consumed by it, and the business logic is: destroy the Activity; ultimately, the embedded window is destroyed but its parent window is not destroyed, resulting in a display error; in the reused main stack mode, the embedded root Activity of the embedded Task triggers a Back event when it is displayed in the foreground. Under the Android native process, the Back event will be consumed by it, and the business logic is: destroy the Activity and display other Activities under the Activity; ultimately, the embedded window display area displays an embedded window that is not pulled up by the user. Therefore, the pending event is transferred to the host process corresponding to the parent window for processing, thereby realizing the interaction between the embedded window and its parent window.

[0125] In order to realize the interaction between the embedded window and its parent window, it is first determined whether the foreground focus window is an embedded window. If the foreground focus window is not an embedded window, the above problem will not occur. The above problem will only occur when the foreground focus window is an embedded window, thereby improving the efficiency of system processing.

[0126] In the specific implementation, when the NativeInputManager module obtains the pending event, it sends the pending event to the PhoneWindowManager module. The PhoneWindowManager module sends an instruction to determine whether the foreground focus window is an embedded window to the WindowState module. The WindowState module determines whether the global variable mActivityRecord is empty. When the global variable mActivityRecord is empty, the judgment result is returned to the PhoneWindowManager module. The PhoneWindowManager module returns to the NativeInputManager module. When the global variable mActivityRecord is not empty, it determines whether the foreground focus window is an embedded window. If the foreground focus window is an embedded window, the foreground processing tag is canceled and a callback is made to notify the host. The process goes to the ActivityTaskManageInternal module, and the ActivityTaskManageInternal module notifies the HnEmbeddedView module, thereby notifying the host process for processing. If the foreground focus window is not an embedded window, the judgment result is returned to the PhoneWindowManager module, and the PhoneWindowManager module returns the judgment result to the NativeInputManager module. The NativeInputManager module sends the judged pending event to the InputDispatcher module. The InputDispatcher module determines whether the pending event contains the foreground processing tag. If it is determined that the pending event contains the foreground processing tag, the pending event is distributed to the foreground focus window application for processing. If it is determined that the pending event does not contain the foreground processing tag, the pending event is discarded.

[0127] Step S20: Displaying the application and interactive components corresponding to the preset operation instruction in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent levels, and the application displayed in the embedded window is associated with the parent window.

[0128] In this embodiment, when the application corresponding to the preset operation instruction is displayed in the embedded window, the interactive component can also be displayed. Continuing with the change component shown in Figure 6, the change component can be operated. In a specific implementation, when configuring the embedded window, the interactive component in the embedded window can be determined by setting the touch mode, thereby realizing user operation and improving the user interaction experience.

[0129] Step S30: upon receiving the operation instruction of the embedded window application, performing interactive operation according to the operation instruction of the embedded window application.

[0130] As shown in the functional diagram of the quick card in Figure 12, users can use quick services to call out quick cards, switch quick cards, exit quick cards, and operate quick cards, thereby expanding the functions of quick cards and improving the use of quick cards. In addition, the Android Bubble feature embeds the application interface into the Bubble window, and other applications require special adaptation. However, in this embodiment, the embedded application does not need special adaptation. The host process of the Android Bubble embedded window can only be SystemUI, while in this embodiment, any application can serve as the host process.

[0131] In this embodiment, when a preset operation instruction is detected, an embedded window is started in the currently displayed parent window according to the preset operation instruction; an embedded window application corresponding to the preset operation instruction is displayed in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent levels, and the application displayed in the embedded window is associated with the parent window; when an operation instruction of the embedded window application is received, an interactive operation is performed according to the operation instruction of the embedded window application, thereby opening the corresponding application through the embedded window, realizing one-click operation, making the operation more convenient, and no special adaptation is required, and any application can be used.

[0132] FIG13 is a flow chart of an embedded window display method provided by another embodiment of the present application. As shown in FIG13 , the embedded window display method is based on the first embodiment, and step S10 includes:

[0133] Step S101: drawing the parent window according to the preset operation instruction.

[0134] In a specific implementation, the window size of the parent window to be drawn and the placeholder information of the embedded window in the parent window to be drawn are obtained; window drawing and layer synthesis are performed according to the window size of the parent window to be drawn and the placeholder information of the embedded window to obtain a completed parent window.

[0135] As shown in Figure 14, the loading of placeholder information in the parent window, 30 represents the placeholder area of ​​the embedded window. When drawing the parent window, the placeholder information of the embedded window in the parent window to be drawn is included. The parent window is drawn according to the placeholder information of the embedded window in the parent window to be drawn. The display area of ​​the embedded window is reserved according to the placeholder information of the embedded window to facilitate the loading of the embedded window application.

[0136] In one possible implementation, an embedded window is started in the currently displayed parent window according to the preset operation instruction, including: obtaining the target window, window mode, window size of the embedded window, embedded window mark bit, stack mode of the embedded window and touch mode of the embedded window; drawing the embedded window according to the target window, window mode, window size of the embedded window, embedded window mark bit, stack mode of the embedded window and touch mode of the embedded window to obtain the embedded window.

[0137] Continuing with the module interaction diagram of the embedded window startup shown in FIG7 , when the embedded window is started, the embedded window is configured through startup parameters to complete the drawing of the embedded window. The startup parameters include the target window, window mode, window size of the embedded window, embedded window mark bit, stack mode of the embedded window, touch mode of the embedded window, and Back mode, etc.

[0138] In one possible implementation, after drawing the embedded window according to the target window, window mode, window size of the embedded window, embedded window mark bit, stack mode of the embedded window and touch mode of the embedded window, it also includes: when the stack mode of the embedded window is created, the stack control is transferred to the host process corresponding to the parent window.

[0139] It should be noted that the stack mode of the embedded window in this embodiment can be adjusted according to actual needs. Since this embodiment realizes the startup of the embedded window, after the embedded window is started and the foreground focus is on the embedded window, under normal circumstances, when an operation event is obtained, the operation event will be processed by the embedded window corresponding to the foreground focus. However, in the event of a problem with the embedded window, such as an application error, the operation event cannot be processed. This embodiment transfers the stack control to the host process corresponding to the parent window instead of processing it through the embedded window. The stack control is transferred to the host process corresponding to the parent window. When an operation event is obtained, the operation event is processed through the host process corresponding to the parent window to ensure a normal response to the event.

[0140] Step S102: Start the embedded window in the parent window that has been drawn.

[0141] In one possible implementation, when drawing an embedded window, the window size of the application corresponding to the preset operation instruction and the configured window size of the embedded window are obtained; the display area of ​​the application corresponding to the preset operation instruction is determined based on the window size and the configured window size of the embedded window, and the application corresponding to the preset operation instruction is displayed based on the display area.

[0142] It should be noted that since the embedded window module has been configured with a window size, the window size configured for the embedded window module may be inconsistent with the window size of the pulled-up embedded application. In order to ensure the normal display of the application corresponding to the preset operation instruction in the embedded window, appropriate adjustments can be made based on the window size and the configured window size of the embedded window.

[0143] FIG15 is a flowchart of an embedded window display method provided by another embodiment of the present application. As shown in FIG15 , the embedded window display method is based on the first embodiment, and step S30 includes:

[0144] Step S301: upon receiving an operation instruction of the embedded window application, performing interface switching according to the operation instruction of the embedded window application.

[0145] It should be noted that the embedded window application is provided with an interactive component. For example, the embedded window application shown in Figure 6 includes a change component, through which interactive operations can be performed. The operation instructions of the embedded window application can also be left or right swipe operations, or other forms of operations.

[0146] When the embedded window application is swiped left or right, the embedded window application can be switched, for example, the embedded window application WeChat payment can be switched to the Alipay payment application, as shown in the embedded window application switching scenario in Figure 16. An interactive component can also be provided in the embedded window to switch applications and thus switch interfaces. The interactive component can be a switch button or other forms of switching methods, which are not limited in this embodiment.

[0147] In one possible implementation, an interactive component may be provided in the quick task card. The quick task card is a launcher started by a preset operation. The quick task card includes an embedded window and an interactive component. Application switching is performed through the interactive component provided in the quick task card. As shown in FIG17 , in the embedded window application switching scenario of another embodiment, the interactive component in the quick task card, such as payment, can be used to switch the WeChat payment application in the embedded window application to the Alipay payment application, thereby improving the flexibility of the embedded window display.

[0148] In a possible implementation, after step S20, the method further includes: obtaining an exit instruction, and returning to the target interface according to the exit instruction, specifically removing the embedded task stack according to the exit instruction, and returning to the target interface.

[0149] It should be noted that the interactive component provided on the embedded window application can also be a close control. The exit command can be obtained by clicking the close control, and the exit command can also be executed by sliding operation. This embodiment does not limit this. The target interface can be the main interface, or it can be the upper-level application interface running in the system. This embodiment does not limit this. When configuring the embedded window, you can set the Back mode. The Back mode can be used to return to the specified target interface when exiting. For example, if the Back mode is configured as the main interface, when the embedded window detects an exit event, the embedded window will be exited. As shown in the embedded window exit module interaction diagram in Figure 18, when the trigger operation of the close control is detected, the embedded window will be exited. According to the triggering operation, the host process business is closed. The host process sends a request to close the embedded window to the embedded window module. The embedded window module sends a request to remove the embedded task to the AMS module. The AMS module sends a request to close the embedded application to the embedded application. The AMS module also sends a request to destroy the embedded task to the WMS module. The WMS module destroys the embedded task and notifies the embedded window module that the embedded task has been destroyed. The embedded window module notifies the host process that the embedded task has been destroyed. The interface of the embedded window presented in the interaction module disappears and returns to the specified target interface, as shown in the scenario diagram of the embedded window exit in Figure 19.

[0150] In this embodiment, the exit function of the embedded window is implemented in the embedded window, and the embedded task stack is removed according to the exit instruction and returned to the target interface, thereby returning to the specified target interface and improving the accuracy of the interface display.

[0151] FIG20 shows a schematic diagram of the structure of an embedded window display device provided by the present application. The embedded window display device 900 provided by the present application includes:

[0152] The starting module 901 is configured to start the embedded window in the currently displayed parent window according to the preset operation instruction when a preset operation instruction is detected.

[0153] The display module 902 is used to display the embedded window application corresponding to the preset operation instruction in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent levels, and the application displayed in the embedded window is associated with the parent window.

[0154] The operation module 903 is configured to perform an interactive operation according to the operation instruction of the embedded window application when receiving the operation instruction of the embedded window application.

[0155] The embedded window display method provided by the present application, in this embodiment, when a preset operation instruction is detected, the embedded window is started in the currently displayed parent window according to the preset operation instruction; the embedded window application corresponding to the preset operation instruction is displayed in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent levels, and the application displayed by the embedded window is associated with the parent window; when the operation instruction of the embedded window application is received, the interactive operation is performed according to the operation instruction of the embedded window application, thereby opening the corresponding application through the embedded window, realizing one-click operation, and the operation is more convenient. No special adaptation is required, and any application can use it.

[0156] In a possible implementation, the starting module 901 is further configured to start the embedded window in the currently displayed parent window according to the preset operation instruction, including:

[0157] Drawing the parent window according to the preset operation instruction;

[0158] Starts the embedded window in the parent window after it has been drawn.

[0159] In a possible implementation, the starting module 901 is further configured to obtain the window size of the parent window to be drawn and the placeholder information of the embedded window in the parent window to be drawn;

[0160] Window drawing and layer synthesis are performed according to the window size of the parent window to be drawn and the placeholder information of the embedded window to obtain a parent window that has been drawn.

[0161] In a possible implementation, the starting module 901 is further configured to obtain a target window, a window mode, a window size of an embedded window, an embedded window flag, a stack mode of the embedded window, and a touch mode of the embedded window;

[0162] The embedded window is drawn according to the target window, the window mode, the window size of the embedded window, the embedded window mark bit, the stack mode of the embedded window and the touch mode of the embedded window to obtain the embedded window.

[0163] In a possible implementation, the startup module 901 is further configured to transfer the stack control right to the host process corresponding to the parent window when the stack mode of the embedded window is created.

[0164] In one possible implementation, the display module 902 is further configured to, when drawing the embedded window, obtain the window size of the application corresponding to the preset operation instruction and the configured window size of the embedded window; and determine the display area of ​​the application corresponding to the preset operation instruction according to the window size and the configured window size of the embedded window;

[0165] The application corresponding to the preset operation instruction is displayed according to the display area.

[0166] In a possible implementation, the display module 902 is further configured to obtain a preset synchronization event;

[0167] The display position of the embedded window is adjusted according to the preset synchronization event.

[0168] In a possible implementation, the operating module 903 is further configured to, upon receiving an operating instruction from the embedded window application, perform interface switching according to the operating instruction from the embedded window application.

[0169] In a possible implementation, the operation module 903 is further configured to obtain an exit instruction and return to the target interface according to the exit instruction.

[0170] In a possible implementation, the operation module 903 is further configured to remove the embedded task stack according to the exit instruction and return to the target interface.

[0171] It should be understood that the electronic devices here are embodied in the form of functional modules. The term "module" here can be implemented in the form of software and / or hardware, without specific limitation. For example, a "module" can be a software program, a hardware circuit, or a combination of the two that implements the above functions. The hardware circuit may include an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, a combined logic circuit, and / or other suitable components that support the described functions.

[0172] The present application also provides an electronic device comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, which, when executed by the electronic device, enable the electronic device to perform an embedded window display method as described in any one of the first aspect or possible implementations of the first aspect.

[0173] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor executes the embedded window display method as described in any one of the first aspect or possible implementations of the first aspect.

[0174] The present application also provides a chip, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface and executes the embedded window display method described in any one of the first aspect or possible implementations of the first aspect.

[0175] Optionally, the chip may further include a memory storing instructions, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the embedded window display method described in any one of the first aspect or possible implementations of the first aspect.

[0176] The memory may be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0177] In the embodiments of the present application, "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent the existence of A alone, the existence of A and B at the same time, and the existence of B alone. A and B may be singular or plural. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can be represented by: a, b, c, a□b, a□c, b□c, or a□b□c, where a, b, c can be single or multiple.

[0178] Those skilled in the art will appreciate that the various units and algorithm steps described in the embodiments disclosed herein can be implemented using a combination of electronic hardware, computer software, and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0179] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0180] In the several embodiments provided in this application, if any function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of this application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0181] The above description is merely a specific embodiment of the present application. Any person skilled in the art may easily conceive of variations or substitutions within the technical scope disclosed in this application, and such variations or substitutions shall be within the scope of protection of this application. The scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A method for displaying an embedded window, characterized in that: The embedded window display method includes: When a preset operation instruction is detected, starting the embedded window in the currently displayed parent window according to the preset operation instruction; Displaying an embedded window application corresponding to the preset operation instruction in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent levels, and the application displayed in the embedded window is associated with the parent window; When an operation instruction of the embedded window application is received, an interactive operation is performed according to the operation instruction of the embedded window application.

2. The embedded window display method according to claim 1, wherein: The starting of the embedded window in the currently displayed parent window according to the preset operation instruction includes: Drawing the parent window according to the preset operation instruction; Starts the embedded window in the parent window after it has been drawn.

3. The embedded window display method according to claim 1, wherein: Drawing the parent window according to the preset operation instruction includes: Obtain the window size of the parent window to be drawn and the placeholder information of the embedded window in the parent window to be drawn; Window drawing and layer synthesis are performed according to the window size of the parent window to be drawn and the placeholder information of the embedded window to obtain a parent window that has been drawn.

4. The embedded window display method according to claim 1, wherein: The starting of the embedded window in the currently displayed parent window according to the preset operation instruction includes: Get the target window, window mode, window size of the embedded window, embedded window mark bit, stack mode of the embedded window, and touch mode of the embedded window; The embedded window is drawn according to the target window, the window mode, the window size of the embedded window, the embedded window mark bit, the stack mode of the embedded window and the touch mode of the embedded window to obtain the embedded window.

5. The embedded window display method according to claim 4, wherein: After drawing the embedded window according to the target window, the window mode, the window size of the embedded window, the embedded window flag, the stack mode of the embedded window, and the touch mode of the embedded window, the method further includes: When the stack mode of the embedded window is created, the stack control right is transferred to the host process corresponding to the parent window.

6. The embedded window display method according to claim 1, wherein: The displaying of the embedded window application corresponding to the preset operation instruction in the embedded window includes: When drawing the embedded window, obtaining the window size of the application corresponding to the preset operation instruction and the configured window size of the embedded window; Determine the preset operation instruction according to the window size and the configured window size of the embedded window The display area of ​​the corresponding application; The application corresponding to the preset operation instruction is displayed according to the display area.

7. The embedded window display method according to claim 1, wherein: After displaying the embedded window application corresponding to the preset operation instruction in the embedded window, the method further includes: Get the preset synchronization event; The display position of the embedded window is adjusted according to the preset synchronization event.

8. The embedded window display method according to claim 1, wherein: The step of performing an interactive operation according to the operation instruction of the embedded window application upon receiving the operation instruction of the embedded window application includes: When an operation instruction of the embedded window application is received, an interface switching is performed according to the operation instruction of the embedded window application.

9. The embedded window display method according to claim 1, wherein: After receiving the operation instruction of the embedded window application and performing the interactive operation according to the operation instruction of the embedded window application, the method further includes: Get an exit command and return to the target interface according to the exit command.

10. The embedded window display method according to claim 9, wherein: The obtaining of the exit instruction and returning to the target interface according to the exit instruction includes: Remove the embedded task stack according to the exit instruction and return to the target interface.

11. An embedded window display device, characterized in that: The embedded window display device includes: A starting module, configured to start the embedded window in the currently displayed parent window according to the preset operation instruction when a preset operation instruction is detected; a display module, configured to display an embedded window application corresponding to the preset operation instruction in the embedded window, wherein the embedded window and the parent window are at the same level or adjacent levels, and the application displayed in the embedded window is associated with the parent window; The operation module is configured to perform interactive operations according to the operation instructions of the embedded window application when receiving the operation instructions of the embedded window application.

12. An electronic device, characterized in that: include: one or more processors; Memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the electronic device, cause the electronic device to execute the embedded window display method as described in any one of claims 1 to 10.

13. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor executes the embedded window display method according to any one of claims 1 to 10.

Images