A method and system for collaborative display and control of multiple application windows across screens

Abstract

The present invention discloses a method and system for cross-screen collaborative display and control of multiple application windows, belonging to the field of computer application technology. The method includes registering a private task organizer and a view container, starting an application through the container and configuring key parameters; monitoring new task events, updating or creating a container based on the task registration status, and implementing multi-window layout management using the setBounds function; implementing independent volume control of a single application by packaging audio tracks; supporting cross-screen movement of windows, implementing cross-screen display through mirror image reuse and display containers, and triggering resolution refresh to adapt to the target screen; the system includes a task organizer registration module, a task view container packaging module, a layout management module, an audio management module, and a cross-screen display / movement module, etc., to achieve cross-device dynamic layout of multiple windows, input event penetration management, focus switching, and a closed-loop cross-screen operation. The present invention supports multi-split screen and cross-device display, improving multi-tasking efficiency and interactive flexibility.

Description

Technical Field

[0001] The present invention relates to the field of computer application technology, and in particular to a method and system for collaborative display and control of multiple application windows across screens. Background Art

[0002] With the diversified development of Android devices, users' demand for multitasking and cross-screen collaboration is increasing.

[0003] Currently, the Android system provides basic multi-window management functions, such as split-screen mode and free-form windows, allowing users to display two or more applications on the same screen at the same time;

[0004] However, existing technologies still have limitations in the following aspects:

[0005] First, dynamic multi-window layout is limited: Traditional solutions cannot dynamically adjust window layouts based on new screen sizes or user needs (such as fixed-ratio adaptation, cross-screen task migration, and screen refresh).

[0006] Second, the issue of multi-screen sharing of application window images: Currently, an application window image can only be displayed on one screen;

[0007] Third, cross-screen input coordination is insufficient: multi-window input events are limited to single-screen responses, lacking a global focus management mechanism, leading to cross-screen operation conflicts or response delays.

[0008] Fourth, weak integration between audio and display: The audio control and display operations of multiple application windows are not deeply integrated, and cannot support independent muting or volume adjustment.

[0009] Based on this, the present invention designs a method and system for cross-screen collaborative display and control of multiple application windows to solve the above problems. Summary of the Invention

[0010] In view of the above-mentioned shortcomings of the prior art, the present invention provides a method and system for cross-screen collaborative display and control of multiple application windows.

[0011] To achieve the above objectives, the present invention is implemented through the following technical solutions:

[0012] A method for collaboratively displaying and controlling multiple application windows across screens, comprising the following steps:

[0013] Step S1: register a private task organizer;

[0014] Step S2: Packaging a private task view container with window focus switching and window return functions;

[0015] Step S3: Start the application through the private task view container, configure the start scope, start flag, and active options for starting the window mode, and configure the start flag to the private task organizer;

[0016] Step S4: monitor whether a new task appears;

[0017] If a new task appears, obtain the window information and proceed to step S5;

[0018] If no new task appears, wait for the new task event to appear;

[0019] Step S5: Determine whether the new task has been registered;

[0020] If it has been registered, update the corresponding private task view container status and display the window information in the private task view container;

[0021] If not registered, create a new private task view container and repeat step S3 to display the window information in the new private task view container;

[0022] Step S6: Use the setBounds function to manage the layout of the screen and position of the multi-application multi-window event;

[0023] Step S7: Determine whether volume control is required;

[0024] If volume control is required, package the audio track and associate it with the actual application package name to perform single application volume control;

[0025] If volume control is not required, proceed to step S8;

[0026] Step S8: Determine whether the window needs to be moved across screens;

[0027] If it needs to be moved, remove the original application's private task view container from the main screen and add it to the display container of another screen. Call the function that moves the root task and all its existing contents to the specified display, triggering a screen resolution refresh of the task window.

[0028] If no movement is required, the current screen display will be maintained.

[0029] Furthermore, the method for the private task view container to switch window focus is:

[0030] Get the activity manager and call the function that moves the target window to the front, move the target window to the foreground, and switch the window focus.

[0031] Furthermore, the method for the private task view container to return the window is:

[0032] By actively requesting window focus switching, the current window gets the focus, and the input event manager is used to inject a return key to control the specified application window rollback.

[0033] Furthermore, the window information includes the window position and size.

[0034] Furthermore, in step S6, there are two ways to manage multi-application multi-window events:

[0035] One is to create a virtual display to manage multi-application and multi-window events;

[0036] The second is to manage multi-application and multi-window events without a virtual display.

[0037] Furthermore, creating a virtual display to manage multi-application multi-window events includes the following steps:

[0038] Step A1: Create a local virtual display and add the private task view container to the virtual display view layout;

[0039] Step A2: Overlay a receiving event view on the virtual display;

[0040] Step A3: When the event receiving view receives an event, the coordinate conversion is performed directly, and the screen coordinates are converted into virtual display coordinates;

[0041] Step A4: determine whether the layout position application window is in a controlled state;

[0042] If the controlled state is turned on, it is injected into the virtual display through the input event manager, and finally distributed to the window view of the current area by the input event manager in the virtual display;

[0043] If the controlled state is not enabled, the event is discarded.

[0044] Furthermore, managing multi-application multi-window events without a virtual display includes the following steps:

[0045] Step B1: Directly overlay a top-level window on each private task view container;

[0046] Step B2: The top-level window receives the event and determines whether the application window is in the controlled state;

[0047] If the controlled state is enabled, this layer of window is removed so that the event directly penetrates the application window;

[0048] If the controlled state is not enabled, this window layer is maintained and events are intercepted.

[0049] Furthermore, in step S7, the method for controlling the volume of a single application is:

[0050] Step C1, packaging the audio tracks in the system;

[0051] Step C2: registering into a private audio management module;

[0052] Step C3: Associating the audio track with the application package name;

[0053] Step C4: Obtain the actual package name of the window application through the actual window information;

[0054] Step C5: The audio management module searches for all audio tracks corresponding to the current application according to the package name and performs volume control.

[0055] Furthermore, in step S8, the cross-screen display method of the application includes the following steps:

[0056] Step D1, obtaining the actual screen controller handle of the application;

[0057] Step D2: calling the control function of the actual screen controller handle to create a surface mirror image to reuse the window layer screen and generate a mirror image view;

[0058] Step D3: Display the image on a mirrored image view through the image controller transaction;

[0059] Step D4: Add the mirrored image view to the display container of another screen for display.

[0060] In order to better achieve the purpose of the present invention, the present invention also provides a multi-application window cross-screen collaborative display and control system, including a task organizer registration module, a task view container packaging module, an application startup configuration module, a task callback processing module, a screen display module, a window startup management module, a layout management module, an event management module, a focus and return event processing module, an audio management module, a cross-screen display module and a cross-screen movement module;

[0061] The task organizer registration module, application startup configuration module, task callback processing module, and window startup management module are all connected to the task view container packaging module; the application startup configuration module, cross-screen mobile module, screen display module, and window startup management module are all connected to the task callback processing module; the screen display module is connected to the layout management module and the cross-screen display module; the layout management module is connected to the event management module, the cross-screen mobile module, the window startup management module, and the focus and return event processing module; the event management module is connected to the focus and return event processing module and the screen display module; the focus and return event processing module is connected to the application startup configuration module; the audio management module is connected to the event management module; the cross-screen display module is connected to the event management module and the cross-screen mobile module.

[0062] Compared with the existing technology, the present invention has the following advantages: 1. It supports flexible layout of multiple application windows on a single screen, such as four-division and six-division (such as split screen and floating window), and accurately controls the window position and size through the setBounds function to adapt to different screen sizes and user operating habits;

[0063] 2. By uniquely identifying the task with the startup identifier, independent management of multiple instances of the same application is achieved; if the task has been registered, the container status is directly updated to avoid duplicate resource creation and improve system response speed;

[0064] 3. Support seamless movement of application windows between heterogeneous devices such as the main screen and extended screens. Trigger resolution refresh through the moveRootTaskToDisplay function, so that the window automatically adapts to the target screen size to avoid screen stretching or black edge issues;

[0065] 4. Generate window mirroring views, supporting the simultaneous display of the same application window on multiple screens (such as same-screen presentation + remote screen projection); realize mirroring of multiple window applications on different screens or smooth movement to different screens, realizing the same or different display of application windows across screens;

[0066] 5. After the present invention binds the audio track to the application package name, the audio volume of a separate application can be managed. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. Those skilled in the art can also derive other drawings based on these drawings without inventive effort.

[0068] Figure 1 This is a flow chart of a method for collaborative display and control of multiple application windows across screens according to the present invention;

[0069] Figure 2 A flow chart of a method for converting the focus of a task view container window according to the present invention;

[0070] Figure 3 This is a flow chart of the window return method of the present invention;

[0071] Figure 4 A flowchart of a method for managing window event management according to the present invention;

[0072] Figure 5 is a flow chart of the volume control method of the present invention;

[0073] Figure 6A flowchart of a method for implementing cross-screen display of an application of the present invention;

[0074] Figure 7 This is a connection block diagram of a system for cross-screen collaborative display and control of multiple application windows according to the present invention. DETAILED DESCRIPTION

[0075] To make the purpose, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0076] Example 1: In some embodiments, please refer to the accompanying drawings of the specification. Figures 1-6 A method for collaboratively displaying and controlling multiple application windows across screens includes the following steps:

[0077] Step 1: Register a private task organizer with the Android system's task organizer controller to monitor events such as the appearance, disappearance, and information changes of application tasks;

[0078] Step 2: Package a private task view container with window focus switching and window return functions to associate the specified application task screen display and hiding logic, as well as handle application lifecycle events (such as start and pause);

[0079] Preferably, the method for the private task view container to switch the window focus is: obtaining the ActivityManager (activity manager) of the Android system and calling a function to move the target window to the front to achieve the target window focus switching.

[0080] Preferably, the method for the private task view container to return the window is: by actively requesting the window focus switch to make the current window get the focus, and using the InputManager (input event manager) to inject a KEYCODE_BACK (return key) event to control the specified application window to fall back.

[0081] Step 3. Launch the app through a private task view container, configure the launch bounds, launch cookie, and launch windowing mode, and assign the launch cookie to a private task organizer as a unique identifier for the app to listen for launch events.

[0082] Step 4: When the private task organizer detects a new task (such as when a user opens an app or clicks a button), it triggers a callback signal to the private task view container. The private task view container processes the callback signal and receives the actual window information and the handle of the actual screen controller of the remote application.

[0083] Preferably, the window information includes window position, size and playback progress.

[0084] A private task view container is like a "virtual display window" specifically opened for a certain application. It receives various operation feedbacks of the application (such as what you clicked) through the private task organizer, and correctly displays the interface and content of the application on the screen according to the actual window state (such as window size and position) and control instructions of the remote application.

[0085] When the private task organizer completes some tasks, such as successfully loading the user's chat history, it will trigger a callback. This callback is like sending a notification to the private task view container, telling it: "The chat history has been loaded, you can display it." Then the private task view container will display the chat history to the user on the interface based on this notification.

[0086] For example, your mobile phone order page (private task view container) is like a "takeout monitoring screen", which specifically monitors the milk tea you ordered; when the kitchen of the milk tea shop prints out your order (the task organizer triggers a callback), your phone will receive a notification and obtain the real-time progress of the order (window information) from the kitchen system (remote application), and update it on the screen through the "communication channel" (handle). In this way, you can see the status of the milk tea production on your mobile phone without having to go to the kitchen to check it in person.

[0087] Step 5. Use the screen controller transaction (the "pipeline" for transmitting signals) to point the parent of the remote application screen controller (the remote original screen) to the screen controller of the private task view container, so that the remote application window screen is displayed in the private task view container.

[0088] For example, when you make a video call with a friend, the screen controller transaction transmits the "original picture" captured by the friend's mobile phone camera to the "video window" on your phone, so that you can only see your friend in the video window of your phone, and not anywhere else;

[0089] For example, you use a signal cable to connect the live broadcast signal of a TV station to the set-top box screen in your home. Originally, the TV station signal can be transmitted to anywhere (TV, projector and mobile phone), but through this operation, you can only display the signal on the set-top box screen, so that you can watch the live broadcast on the set-top box screen.

[0090] Step 6: While monitoring the task occurrence event of the task organizer controller, it is necessary to confirm whether the current application task information has been registered in the private task organizer. If not, create a private task view container in the private task organizer and repeat step 3 to achieve local management of window startup and display of different applications;

[0091] For example, a restaurant's kitchen management system constantly monitors new orders from the front desk. Whenever a new order comes in, the system first checks to see if it's already on the "pending orders board." If not, a new record is created and a dedicated lunch box is assigned to the order, facilitating subsequent preparation and serving.

[0092] For example, when an application (such as WeChat) requests to open a new window, the mobile phone system will first check whether "WeChat" is already in the task list. If not, it will create a dedicated window container for WeChat to ensure that the application interface can be displayed and managed independently.

[0093] Step 7: Arrange and layout multiple local private task view containers on the same display and use the setBounds function of the window container transaction to manage the layout and position of multiple application windows on the same screen.

[0094] Preferably, the setBounds function can accurately control the position (x, y coordinates) and size (width, height) of a window or component;

[0095] For example, open WeChat (left half of the screen) and the browser (right half of the screen) on your phone at the same time; use the setBounds function to set WeChat to the size of the left half of the screen (x=0, y=0, width=50%, height=100%), and the browser box to the right half of the screen (x=50%, y=0, width=50%, height=100%).

[0096] Preferably, the step seven includes two management methods for multi-application window event management:

[0097] One is to create a virtual display to manage multi-application and multi-window events;

[0098] Specifically, a local virtual display is created, a private task view container is added to the virtual display view layout, and a view that receives events is placed on top of the virtual display. When the event view receives an event, it directly converts the screen coordinates into virtual display coordinates. It also determines whether the application window in the layout position is in the controlled state. If so, the event is injected into the virtual display through the input event manager, and finally distributed to the window view in the current area by the input event manager in the virtual display.

[0099] The second is to manage multi-application and multi-window events without a virtual display.

[0100] Specifically, a top-level window is directly covered on each private task view container. This top-level window receives events to determine whether the application window is in the controlled state. If the controlled state is turned on, this top-level window is removed so that the event directly penetrates the application window; if the controlled state is not turned on, this top-level window is kept and the event is intercepted.

[0101] Step 8. Package the Audio Track in the Android system and register it in the private audio management module, and associate the Audio Track with the package name of its actual application;

[0102] This step associates an Audio Track with a specific application (identified by package name), enabling independent control of each application's audio; this is particularly important in a multi-window environment as it allows the audio of a specific application to be adjusted or muted individually, rather than globally controlling all sounds.

[0103] Preferably, the private task view container provides a single application volume control method: the actual package name of the window application is obtained through the actual window information, and then all audio tracks corresponding to the current application are found according to the package name through the private audio management module and volume control is performed (such as adjusting the volume, muting, etc.);

[0104] Step 9. Call the control function of the actual screen controller handle (Surface Control, screen surface control handle) to create a surface mirror (mirrorSurface) to reuse the window layer (layer) to generate a mirror screen view, and then display the screen on a mirror screen view through the screen controller transaction. Then, add this mirror screen view to the Presentation (multi-screen content display view designed for independent display of content) container of other screens to realize cross-screen display of the application;

[0105] The cross-screen display events are received by the mirror image view of this screen and forwarded to the actual corresponding application window through the data channel of the private task view container, thereby realizing cross-screen display event processing;

[0106] Step 10. When a user cross-screen movement instruction is received (such as dragging a window to the boundary of another screen) or the Android system automatically allocates a demand, the original application's private task view container is removed from the main screen and then added to the Presentation (display container) of the other screen. Finally, the Android system active task manager is obtained and the function (move Root Task To Display) that moves the root task and all its existing contents to the specified display is called to notify the current task that the screen has changed, triggering a screen resolution refresh of the task window view.

[0107] Realize the mirroring display of multiple window applications on different screens or smoothly move them to different screens, and realize the same or different display of application windows across screens.

[0108] Embodiment 2: In some embodiments, as Figure 7 As shown, as a preferred embodiment of the present invention, a system for cross-screen collaborative display and control of multiple application windows includes:

[0109] The task organizer registration module is used to register a private task organizer with the task organizer controller of the Android system;

[0110] Task view container packaging module, used to package private task view container;

[0111] Application launch configuration module, used to launch the application through the private task view container and configure activity options;

[0112] The task callback processing module is used to process task callbacks and receive remote application window information and handles;

[0113] The screen display module is used to display the remote application window screen in the private task view container;

[0114] Window startup management module, used to manage the startup and display of windows of different applications;

[0115] A layout management module, used to arrange multiple local private task view containers on the same display;

[0116] Event management module, used for multi-application window event management;

[0117] Focus and return event processing module, used to specify window focus switching and return event processing;

[0118] Audio management module, used to modify and mute the volume of a specified window;

[0119] Cross-screen display module, used for cross-screen display of multiple application windows and event processing;

[0120] Cross-screen mobile module, used for cross-screen mobile application windows.

[0121] The task organizer registration module is connected to the task view container packaging module and is used to provide the task view container packaging module with a successfully registered private task organizer instance;

[0122] The task view container packaging module is connected to the application startup configuration module and the task callback processing module, and is used to provide a private task view container instance to the application startup configuration module and transmit task status change notifications to the task callback processing module;

[0123] The application startup configuration module is connected to the task callback processing module to trigger the task callback processing module to monitor the application startup event;

[0124] The task callback processing module is connected to the screen display module and the window startup management module, and is used to provide the remote application window information and screen controller handle to the screen display module, and send a new task occurrence notification to the window startup management module;

[0125] The screen display module is connected to the layout management module and the cross-screen display module, and is used to provide the rendered window screen to the layout management module and provide the mirrored window screen data to the cross-screen display module;

[0126] The window startup management module is connected to the task view container packaging module and the layout management module, and is used to request the task view container packaging module to create a new container when a new task is detected, and to notify the layout management module to perform window layout;

[0127] The layout management module is connected to the event management module and the cross-screen movement module, and is used to provide window layout coordinate information to the event management module and provide current window layout data to the cross-screen movement module;

[0128] The event management module is connected to the focus and return event processing module and the screen display module, and is used to forward user input events to the focus and return event processing module, and distribute the events to the window corresponding to the screen display module according to the layout information;

[0129] The focus and return event processing module is connected to the layout management module and the application startup configuration module, and is used to adjust the focus window position through the layout management module and trigger the window return operation through the application startup configuration module;

[0130] The audio management module is connected to the event management module and is used to receive the volume adjustment request transmitted by the event management module and operate the audio track;

[0131] The cross-screen display module is connected to the event management module and the cross-screen movement module, and is used to forward the cross-screen display window events to the event management module and provide the cross-screen movement module with mirrored window data;

[0132] The cross-screen mobile module is connected to the layout management module and the task callback processing module, and is used to update the window layout of the source screen and the target screen through the layout management module, and notify the task screen changes through the task callback processing module.

[0133] The system of the present invention includes a task organizer registration module, a task view container packaging module, a layout management module, an audio management module and a cross-screen display / mobile module, etc., to realize multi-window cross-device dynamic layout, input event penetration management, focus switching and cross-screen operation closed loop.

[0134] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements will not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A method for collaborative display and control of multiple application windows across screens, characterized by: The following steps are included: Step S1: register a private task organizer; Step S2: Packaging a private task view container with window focus switching and window return functions; Step S3: Start the application through the private task view container, configure the start scope, start flag, and active options for starting the window mode, and configure the start flag to the private task organizer; Step S4: monitor whether a new task appears; If a new task appears, obtain the window information and proceed to step S5; If no new task appears, wait for the new task event to appear; Step S5: Determine whether the new task has been registered; If it has been registered, update the corresponding private task view container status and display the window information in the private task view container; If not registered, create a new private task view container and repeat step S3 to display the window information in the new private task view container; Step S6: Use the setBounds function to manage the layout of the screen and position of the multi-application multi-window event; Step S7: Determine whether volume control is required; If volume control is required, package the audio track and associate it with the actual application package name to perform single application volume control; If volume control is not required, proceed to step S8; Step S8: Determine whether the window needs to be moved across screens; If it needs to be moved, remove the original application's private task view container from the main screen and add it to the display container of another screen. Call the function that moves the root task and all its existing contents to the specified display, triggering a screen resolution refresh of the task window. If no movement is required, the current screen display will be maintained.

2. The method for cross-screen collaborative display and control of multiple application windows according to claim 1, characterized in that: The method for the private task view container to switch window focus is: Get the activity manager and call the function that moves the target window to the front, move the target window to the foreground, and switch the window focus.

3. The method for cross-screen collaborative display and control of multiple application windows according to claim 2, characterized in that: The method for the private task view container to return the window is: By actively requesting window focus switching, the current window gets the focus, and the input event manager is used to inject a return key to control the specified application window rollback.

4. The method for cross-screen collaborative display and control of multiple application windows according to claim 3, characterized in that: The window information includes the window position and size.

5. The method for cross-screen collaborative display and control of multiple application windows according to claim 4, characterized in that: In step S6, there are two ways to manage multi-application multi-window events: One is to create a virtual display to manage multi-application and multi-window events; The second is to manage multi-application and multi-window events without a virtual display.

6. The method for cross-screen collaborative display and control of multiple application windows according to claim 5, characterized in that: Creating a virtual display to manage multi-application multi-window events includes the following steps: Step A1: Create a local virtual display and add the private task view container to the virtual display view layout; Step A2: Overlay a receiving event view on the virtual display; Step A3: When the event receiving view receives an event, the coordinate conversion is performed directly, and the screen coordinates are converted into virtual display coordinates; Step A4: determine whether the layout position application window is in a controlled state; If the controlled state is turned on, it is injected into the virtual display through the input event manager, and finally distributed to the window view of the current area by the input event manager in the virtual display; If the controlled state is not enabled, the event is discarded.

7. The method for cross-screen collaborative display and control of multiple application windows according to claim 6, characterized in that: Managing multi-application multi-window events without a virtual display includes the following steps: Step B1: Directly overlay a top-level window on each private task view container; Step B2: The top-level window receives the event and determines whether the application window is in the controlled state; If the controlled state is enabled, this layer of window is removed so that the event directly penetrates the application window; If the controlled state is not enabled, this window layer is maintained and the event is intercepted.

8. The method for cross-screen collaborative display and control of multiple application windows according to claim 7, characterized in that: In step S7, the method for controlling the volume of a single application is as follows: Step C1, packaging the audio tracks in the system; Step C2: registering into a private audio management module; Step C3: Associating the audio track with the application package name; Step C4: Obtain the actual package name of the window application through the actual window information; Step C5: The audio management module searches for all audio tracks corresponding to the current application according to the package name and performs volume control.

9. The method for cross-screen collaborative display and control of multiple application windows according to claim 8, characterized in that: In step S8, the cross-screen display method of the application includes the following steps: Step D1, obtaining the actual screen controller handle of the application; Step D2: calling the control function of the actual screen controller handle to create a surface mirror image to reuse the window layer screen and generate a mirror image view; Step D3: Display the image on a mirrored image view through the image controller transaction; Step D4: Add the mirrored image view to the display container of another screen for display.

10. A multi-application window cross-screen collaborative display and control system, used in the multi-application window cross-screen collaborative display and control method according to claim 9, characterized in that: It includes task organizer registration module, task view container packaging module, application startup configuration module, task callback processing module, screen display module, window startup management module, layout management module, event management module, focus and return event processing module, audio management module, cross-screen display module and cross-screen mobile module; The task organizer registration module, application startup configuration module, task callback processing module, and window startup management module are all connected to the task view container packaging module; the application startup configuration module, cross-screen mobile module, screen display module, and window startup management module are all connected to the task callback processing module; the screen display module is connected to the layout management module and the cross-screen display module; the layout management module is connected to the event management module, the cross-screen mobile module, the window startup management module, and the focus and return event processing module; the event management module is connected to the focus and return event processing module and the screen display module; the focus and return event processing module is connected to the application startup configuration module; the audio management module is connected to the event management module; the cross-screen display module is connected to the event management module and the cross-screen mobile module.

Images