Display device and application window control methods

Abstract

This application provides a display device and an application window control method, relating to the field of computer technology. The display device includes: a display; and a controller connected to the display, wherein the controller is configured to: detect an application window display request; obtain the current task identifier of the current application window; compare the current task identifier with a target task identifier in the WMS window manager; wherein the target task identifier identifies the task corresponding to the application window currently receiving focus control; if the current task identifier and the target task identifier are the same, control the window area of ​​the current application window to be drawn according to the focus acquisition; and replace the window interface of the application window currently receiving focus control with the window interface of the current application window on the display. This application addresses the problem of flickering in toolbar and other window areas when launching a new application window interface in Freeform mode.

Description

Technical Field

[0001] This application relates to the field of computer technology. More specifically, it relates to a display device and an application window control method. Background Technology

[0002] With the continuous development of terminal devices and computing technology, the multi-window technology of Android devices is being used more and more widely in various industry scenarios. Among them, the Freeform mechanism of computer-aided design system is a typical example of multi-window application technology.

[0003] However, due to the inherent defects of the Freeform pattern implementation framework, there are many problems. For example, in a very important user experience scenario, when launching a new application interface in a floating window state, the top toolbar will flicker. Summary of the Invention

[0004] An exemplary embodiment of this application provides a display device and an application window control method to solve the problem of flickering in toolbar and other window areas when launching a new application window interface in Freeform mode.

[0005] The technical solutions provided in this application are as follows:

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

[0007] monitor;

[0008] A controller connected to the display, wherein the controller is configured to:

[0009] Obtain the application window display request and determine the current task identifier of the current application window;

[0010] The current task identifier is compared with the target task identifier in the WMS window manager; wherein, the target task identifier is used to identify the task corresponding to the application window that is currently receiving focus control.

[0011] If the current task identifier and the target task identifier are the same, control the window area of ​​the current application window to be drawn according to the focus acquisition;

[0012] The window interface of the currently focused application window is displayed on the monitor, replacing the window interface of the current application window.

[0013] In some embodiments, the controller is further configured to:

[0014] If the current task identifier and the target task identifier are different, control the window area of ​​the current application window to be drawn as if it has lost focus;

[0015] The display shows the window interface of the current application window and the window interface of the application window that currently has focus; wherein the window interface of the application window that currently has focus is displayed on top of the window interface of the current application window.

[0016] In some embodiments, the controller is further configured to:

[0017] The application window display request is obtained through a pre-set callback interface.

[0018] Secondly, embodiments of this application provide another display device, including:

[0019] monitor;

[0020] A controller connected to the display, wherein the controller is configured to:

[0021] Upon detecting a change in focus application information, determine whether there is an application window that has gained focus control.

[0022] If an application window has been given focus control, query the task to which the application window with focus control belongs.

[0023] In the WMS window manager, mark the task identifier corresponding to the task so that the window interface is displayed on the monitor by comparing the task identifier.

[0024] In some embodiments, the controller is further configured to:

[0025] Set the preferred focus control parameters in the WMS window manager;

[0026] Assign a parameter value corresponding to the preferred focus control parameter to mark the task identifier corresponding to the task, and store the task identifier corresponding to the task in the WMS window manager.

[0027] Thirdly, embodiments of this application provide an application window control method applied to a display device, the method comprising:

[0028] Obtain the application window display request and determine the current task identifier of the current application window;

[0029] The current task identifier is compared with the target task identifier in the WMS window manager; wherein, the target task identifier is used to identify the task corresponding to the application window that is currently receiving focus control.

[0030] If the current task identifier and the target task identifier are the same, control the window area of ​​the current application window to be drawn according to the focus acquisition;

[0031] The window interface of the currently focused application window is displayed on the monitor, replacing the window interface of the current application window.

[0032] In some embodiments, the method further includes:

[0033] If the current task identifier and the target task identifier are different, control the window area of ​​the current application window to be drawn as if it has lost focus;

[0034] The display shows the window interface of the application window that currently has focus control.

[0035] In some embodiments, the method further includes:

[0036] The application window display request is obtained through a pre-set callback interface.

[0037] Fourthly, embodiments of this application provide another application window control method applied to a display device, the method comprising:

[0038] Obtain the application window display request and determine the current task identifier of the current application window;

[0039] The current task identifier is compared with the target task identifier in the WMS window manager; wherein, the target task identifier is used to identify the task corresponding to the application window that is currently receiving focus control.

[0040] If the current task identifier and the target task identifier are the same, control the window area of ​​the current application window to be drawn according to the focus acquisition;

[0041] The window interface of the currently focused application window is displayed on the monitor, replacing the window interface of the current application window.

[0042] In some embodiments, the method further includes:

[0043] The method further includes:

[0044] Set the preferred focus control parameters in the WMS window manager;

[0045] Assign a parameter value corresponding to the preferred focus control parameter to mark the task identifier corresponding to the task, and store the task identifier corresponding to the task in the WMS window manager.

[0046] Fifthly, embodiments of this application provide an electronic device, including: a memory and a processor, wherein the memory is used to store a computer program; and the processor is used to, when executing the computer program, cause the electronic device to implement the application window control method described in the third or fourth aspect or any embodiment of the third or fourth aspect.

[0047] Sixthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a computing device, causes the computing device to implement the application window control method described in the third or fourth aspect or any of the third or fourth aspect embodiments.

[0048] In a seventh aspect, embodiments of this application provide a computer program product that, when run on a computer, enables the computer to implement the application window control method described in the third or fourth aspect or any of the third or fourth aspect embodiments.

[0049] As can be seen from the above technical solutions, the display device and application window control method provided in this application embodiment detects an application window display request and obtains the current task identifier of the current application window; compares the current task identifier with the target task identifier in the WMS window manager; wherein, the target task identifier is used to identify the task corresponding to the application window that is currently focused; when the current task identifier and the target task identifier are the same, controls the window area of ​​the current application window to be drawn according to the focus acquisition; and replaces the window interface of the current application window with the window interface of the application window that is currently focused on and displays it on the display. Because the display device and application window control method provided in this application embodiment can compare the current task identifier of the current application window with the target task identifier of the application window that has gained focus when the current application window loses focus, and if the current task identifier and the target task identifier are the same, it means that the newly launched application window and the current application window are the same floating window, and the floating window with focus has not changed, by controlling the window area of ​​the current application window to be drawn according to the focus, that is, the display state of the toolbar and other window areas of the current application window remains unchanged, and finally replacing the window interface of the current application window with the window interface of the application window that has gained focus and displaying it on the display, this application embodiment can solve the problem of the toolbar and other window areas flickering when launching a new application window interface in Freeform mode, thereby avoiding the flickering of the toolbar and other window areas when launching a new application window interface and improving the user experience. Attached Figure Description

[0050] To more clearly illustrate the implementation methods in the embodiments of this application or related technologies, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0051] Figure 1 A scenario architecture diagram of the application window control method in some embodiments is shown;

[0052] Figure 2 Hardware configuration block diagrams of the control device are shown in some embodiments;

[0053] Figure 3 A hardware configuration block diagram of a display device is shown in some embodiments;

[0054] Figure 4 A software configuration diagram of a display device in some embodiments is shown;

[0055] Figure 5 An example diagram showing an application window in a first display device according to some embodiments is shown;

[0056] Figure 6 An example diagram showing an application window in a second display device according to some embodiments is shown;

[0057] Figure 7 An example diagram showing an application window in a third display device according to some embodiments is shown;

[0058] Figure 8 A flowchart of an application window control method according to some embodiments is shown;

[0059] Figure 9 An example diagram showing an application window in a fourth display device according to some embodiments is shown;

[0060] Figure 10 An example diagram showing an application window in a fifth display device according to some embodiments is shown;

[0061] Figure 11 An example diagram of displaying an application window in a sixth type of display device according to some embodiments is shown;

[0062] Figure 12 A flowchart of another application window control method according to some embodiments is shown;

[0063] Figure 13 An example diagram showing an application window in a seventh display device according to some embodiments is shown;

[0064] Figure 14 A flowchart of yet another application window control method according to some embodiments is shown;

[0065] Figure 15 An example diagram showing an application window in an eighth display device according to some embodiments is shown;

[0066] Figure 16 A flowchart of another application window control method according to some embodiments is shown;

[0067] Figure 17 A flowchart of another application window control method according to some embodiments is shown. Detailed Implementation

[0068] To make the objectives and implementation methods of this application clearer, the exemplary implementation methods of this application will be clearly and completely described below with reference to the accompanying drawings of the exemplary embodiments of this application. Obviously, the exemplary embodiments described are only some embodiments of this application, and not all embodiments.

[0069] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0070] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0071] The display device provided in this application can have various implementation forms, such as a television, a smart television, a laser projection device, a monitor, an electronic bulletin board, an electronic table, etc. Figure 1 and Figure 2 This is one specific embodiment of the display device of this application.

[0072] Figure 1 This is a schematic diagram illustrating the operational scenario between the display device and the control unit according to the embodiment. Figure 1 As shown, the user can operate the display device 200 through the smart device 300 or the control device 100.

[0073] In some embodiments, the control device 100 may be a remote control. Communication between the remote control and the display device includes infrared protocol communication, Bluetooth protocol communication, and other short-range communication methods, controlling the display device 200 wirelessly or via wired means. Users can control the display device 200 by inputting user commands through buttons on the remote control, voice input, control panel input, etc.

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

[0075] In some embodiments, the display device may receive instructions not through the aforementioned smart devices or control devices, but through touch or gestures.

[0076] In some embodiments, the display device 200 can also be controlled in ways other than the control device 100 and the smart device 300. For example, it can be controlled by directly receiving the user's voice commands through a module configured inside the display device 200 for acquiring voice commands, or it can be controlled by receiving the user's voice commands through a voice control device set outside the display device 200.

[0077] In some embodiments, the display device 200 also communicates with the server 400. The display device 200 may communicate via a local area network (LAN), wireless local area network (WLAN), and other networks. The server 400 may provide various content and interactive features to the display device 200. The server 400 may be a cluster or multiple clusters, and may include one or more types of servers.

[0078] Figure 2 An exemplary block diagram of the configuration of the control device 100 according to an exemplary embodiment is shown. Figure 2 As shown, the control device 100 includes a controller 110, a communication interface 130, a user input / output interface 140, a memory, and a power supply. The control device 100 can receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to, thus acting as an intermediary for interaction between the user and the display device 200.

[0079] In some embodiments, the display device 200 includes at least one of a tuner 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface 270, a memory, a power supply, and a user interface.

[0080] In some embodiments, the controller includes a processor, a video processor, an audio processor, a graphics processor, RAM, ROM, and a first interface to an nth interface for input / output.

[0081] In some embodiments, the display 260 includes a display screen component for presenting an image, a driving component for driving image display, a component for receiving image signals from the controller output, and a user control UI interface for displaying video content, image content, menu control interface, and user control UI interface.

[0082] In some embodiments, the display 260 may be a liquid crystal display, an OLED display, or a projection display, and may also be a projection device and a projection screen.

[0083] In some embodiments, the communicator 220 is a component used to communicate with external devices or servers according to various communication protocol types. For example, the communicator may include at least one of a Wi-Fi module, a Bluetooth module, a wired Ethernet module, other network communication protocol chips or near-field communication protocol chips, and an infrared receiver. The display device 200 can establish the transmission and reception of control signals and data signals with the external control device 100 or the server 400 through the communicator 220.

[0084] In some embodiments, the user interface can be used to receive control signals from the control device 100 (e.g., an infrared remote control).

[0085] In some embodiments, detector 230 is used to acquire signals from the external environment or to interact with the outside world. For example, detector 230 includes a light receiver, a sensor for acquiring ambient light intensity; or, detector 230 includes an image acquisition device, such as a camera, which can be used to acquire external environmental scenes, user attributes, or user interaction gestures; or, detector 230 includes a sound acquisition device, such as a microphone, for receiving external sounds.

[0086] In some embodiments, the external device interface 240 may include, but is not limited to, one or more interfaces such as: High Definition Multimedia Interface (HDMI), analog or data high-definition component input interface (component), composite video input interface (CVBS), USB input interface (USB), RGB port, etc. It may also be a composite input / output interface formed by multiple interfaces mentioned above.

[0087] In some embodiments, the tuner 210 receives broadcast television signals via wired or wireless reception and demodulates audio and video signals, such as EPG data signals, from multiple wireless or wired broadcast television signals.

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

[0089] In some embodiments, the controller 250 controls the operation of the display device and responds to user operations via various software control programs stored in memory. The controller 250 controls the overall operation of the display device 200. For example, in response to receiving a user command to select a UI object to display on the display 260, the controller 250 can perform operations related to the object selected by the user command.

[0090] In some embodiments, the object can be any of the optional objects, such as a hyperlink, an icon, or other operable controls. Operations related to the selected object include: displaying links to hyperlinked pages, documents, images, etc., or performing operations corresponding to the program associated with the icon.

[0091] In some embodiments, the controller includes at least one of a central processing unit (CPU), a video processor, an audio processor, a graphics processing unit (GPU), RAM (random access memory), ROM (read-only memory), a first to an nth interface for input / output, a communication bus, etc.

[0092] Users can input commands through a graphical user interface (GUI) displayed on the monitor 260, and the user input interface receives the user input commands through the GUI. Alternatively, users can input commands by entering specific sounds or gestures, and the user input interface receives the user input commands by recognizing the sounds or gestures through sensors.

[0093] In some embodiments, a "user interface" is the medium through which an application or operating system interacts and exchanges information with a user, converting information between its internal form and a form acceptable to the user. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an icon, window, control, or other interface element displayed on the screen of an electronic device. Controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0094] See Figure 4 In some embodiments, the system is divided into four layers, from top to bottom: the Applications layer (referred to as the "Application Layer"), the Application Framework layer (referred to as the "Framework Layer"), the Android runtime and system library layer (referred to as the "System Runtime Layer"), and the kernel layer.

[0095] In some embodiments, at least one application runs in the application layer. These applications may be Windows programs, system settings programs, or clock programs that come with the operating system; they may also be applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the examples above.

[0096] The framework layer provides application programming interfaces (APIs) and a programming framework for applications. The application framework layer includes predefined functions. It acts as a central processing unit, determining the actions taken by applications within the application layer. Through the API, applications can access system resources and obtain system services during execution.

[0097] like Figure 4 As shown, the application framework layer in this embodiment includes managers, content providers, etc., wherein the managers include at least one of the following modules: ActivityManager, which interacts with all activities running in the system; LocationManager, which provides access to system location services for system services or applications; PackageManager, which retrieves various information related to application packages currently installed on the device; NotificationManager, which controls the display and clearing of notification messages; and WindowManager, which manages icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0098] In some embodiments, the Activity Manager manages the lifecycle of individual applications and common navigation and back functions, such as controlling application exit, opening, and back actions. The Window Manager manages all window programs, such as obtaining the screen size, determining if a status bar is present, locking the screen, capturing the screen, and controlling display window changes (e.g., shrinking the display window, shaking the display, distorting the display, etc.).

[0099] In some embodiments, the system runtime library layer provides support for the upper layer, namely the framework layer. When the framework layer is used, the Android operating system runs the C / C++ libraries contained in the system runtime library layer to implement the functions that the framework layer needs to perform.

[0100] In some embodiments, the kernel layer is a layer between hardware and software. For example... Figure 4 As shown, the kernel layer includes at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver.

[0101] In some embodiments, with Figure 4 Taking a document application as an example, when the remote control receiver receives input from the remote control or from the user via touch or gesture, and confirms that the control corresponding to the input operation is the control corresponding to the document application icon, the document application calls the interface of the application framework layer to start the document application and display the application window interface corresponding to the document. Figure 5 The window interface shown is the window interface of the current application window A displayed on the display device 200.

[0102] Furthermore, when the remote control receiver receives input from the remote control or user input via touch or gesture, it confirms the launch of a new application window interface. During the launch of the new application window interface, Figure 5 The changes in the window interface of the current application window A shown are as follows: Figure 6 As shown, after the new application window interface is launched, the window interface of the new application window is displayed, which is the window interface of the current application window B. Figure 7 As shown. From Figures 5 to 7 It is quite obvious that during the switching process, the window area ( Figures 5 to 7 The toolbar in the browser is exhibiting a "gray-black-gray" flickering problem.

[0103] Understandable Figure 5 and Figure 7 The gray color displayed in the toolbar is the color that appears when the toolbar has focus. Figure 6The black color in the toolbar is the color displayed when the toolbar loses focus. In other words, changes in window focus can cause flickering. This is because the focus control logic in Freeform mode involves a necessary emptying process for window focus control; that is, a window recorded as having focus in the Android system must first become empty before becoming a new window. Taking the example above: from the time application window A loses focus until no application window has focus until application window B gains focus, the time when application window A receives the focus change callback is much earlier than the time application window B is displayed. During this time difference, the toolbar of application window A turns black, causing the flickering problem.

[0104] The process of applying window control in this embodiment will be described in detail below.

[0105] Figure 8 A flowchart of an application window control method according to some embodiments is shown. An embodiment of this application provides a display device in which a controller is configured to perform... Figure 8 The application window control method includes:

[0106] Step 801: Obtain the application window display request and determine the current task identifier of the current application window.

[0107] An application window display request refers to a request to display a new application window interface on the monitor. This can be understood as a user triggering the application window display request using input devices such as a remote control, keyboard, and mouse, or through touch or gestures. For example, ... Figure 5 As shown, the user can access the device by touching... Figure 5 The "W" icon for creating a new document in the application triggers a request to display the application window.

[0108] In some embodiments of this application, the current task identifier of the current application window displayed on the display is determined after obtaining the application window display request; wherein, the current application window refers to the application window displayed at the top layer of the display interface, which can be understood as the application window that has obtained focus control before obtaining the application window display request.

[0109] In some embodiments of this application, each application window (floating window) displayed on the display is actually a task. A task can be uniquely identified by a task identifier, thereby uniquely identifying an application window. Each task corresponds to one application window, and multiple tasks will result in multiple application windows.

[0110] In some embodiments of this application, a callback interface can be set between the WMS window manager and the window area (toolbar) of the application window, so that the window area of ​​the application window can obtain the application window display request through the callback interface, and query the current task identifier of the current application window in the WMS window manager through the callback interface.

[0111] Step 802: Compare the current task identifier with the target task identifier in the WMS window manager; wherein the target task identifier is used to identify the task corresponding to the application window that is currently receiving focus control.

[0112] In some embodiments of this application, when there is a focus control application window, the task identifier corresponding to the task to which the focus control application window belongs can be stored in the WMS window manager. That is to say, the WMS window manager stores the task identifier corresponding to the currently focus control application window and the task identifier corresponding to the previously focus control application windows.

[0113] In some embodiments of this application, the target task identifier represents the task identifier corresponding to the application window that currently has focus control. It may be the same as the current task identifier of the current application window or it may be different from the current task identifier of the current application window.

[0114] For example, with Figure 9 The current application window C shown is... Figure 10 Taking the currently focused application window D as an example, the toolbars of the currently displayed application window C and the currently focused application window D are exactly the same. However, the toolbars of the currently displayed application window C and the currently focused application window D exist independently. Therefore, the toolbars of the currently displayed application window C and the currently focused application window D do not share the same control logic. It can be understood that, from the perspective of the toolbar of the currently displayed application window C, the currently displayed application window C only knows that it has lost focus, and thus changes the toolbar controlling the currently displayed application window C accordingly. The currently displayed application window C is unaware of whether other application windows have gained focus. Similarly, the currently focused application window D only knows that it has gained focus, and is unaware of whether other application windows have lost focus.

[0115] Therefore, it is necessary to compare the current task identifier of the current application window C with the target task identifier of the application window D that is currently in focus control, in order to determine whether the current application window C and the application window D that is currently in focus control belong to the same task. That is, based on the current task identifier and the target task identifier, it is necessary to determine how the toolbar of the current application window C is drawn and how the window interface is displayed subsequently.

[0116] It should be noted that only one application window can have focus control at any given time. The reason why application window D, currently having focus control, receives focus later is because the window interface must be completely drawn before it can acquire focus.

[0117] Step 803: If the current task identifier and the target task identifier are the same, control the window area of ​​the current application window to be drawn according to the focus acquisition.

[0118] It's understandable that the current application window and the application window currently receiving focus can belong to the same application or different applications. Therefore, continuing with... Figure 9 and Figure 10 For example, the currently active application window C and the currently focused application window D can belong to the same task group or different task groups. Each displayed application window (floating window) is actually a task, meaning each task corresponds to one application window; multiple tasks will result in multiple application windows.

[0119] In some embodiments of this application, the same current task identifier and target task identifier indicate that the current application window and the application window currently receiving focus control belong to the same group of tasks, and the process continues... Figure 9 and Figure 10 For example, if the current application window C and the currently focused application window D belong to the same task group, the newly appearing window of the currently focused application window D will cover the window of the previous current application window C. This means that application windows in the same task group share the same window area on the interface. The window area of ​​the current application window can be controlled to be drawn according to the focus state; that is, the color and other states of the window area remain unchanged when the application window has focus. In other words, since the current application window C and the currently focused application window D belong to the same task group, when the current application window C starts the currently focused application window D, the current application window C disappears, and the currently focused application window D appears.

[0120] Step 804: Replace the current application window's window interface on the display with the window interface of the application window that currently has focus control.

[0121] In some embodiments of this application, after the window area of ​​the current application window is drawn according to the focus acquisition, the window interface of the currently focused control application window is replaced by the window interface of the current application window and displayed on the display.

[0122] For example, continue with Figure 9 and Figure 10 For example, Figure 11As shown, the window interface D of the application window currently receiving focus is displayed on the monitor, replacing the window interface of the current application window C. Figure 11 The window interface of the currently applied window C disappears, and the window interface of the currently focused applied window D appears.

[0123] In the example above, when the current application window loses focus, it checks whether the task identifier corresponding to the current task and the currently focused application window belong to the same task. If they are the same task, it means that the newly launched application window is the same floating window as itself, and the window area with focus has not changed. The window area of ​​the current application window is then drawn according to the focus, further improving the user experience.

[0124] Figure 12 A flowchart of another application window control method according to some embodiments is shown. This embodiment further optimizes the above application window control method based on the embodiments described above. Figure 12 As shown, the method also includes:

[0125] In some embodiments of this application, when the current task identifier and the target task identifier are different, the window area of ​​the current application window is controlled to be drawn as if it has lost focus, and the window interface of the current application window and the window interface of the currently focused control application window are displayed on the display; wherein, the window interface of the currently focused control application window is placed on top of the window interface of the current application window.

[0126] In some embodiments of this application, if the current task identifier and the target task identifier are different, it indicates that the current application window and the application window currently receiving focus control do not belong to the same group of tasks, and the process continues... Figure 9 and Figure 10 For example, if the current application window C and the currently focused application window D do not belong to the same task group, the newly appearing window interface of the currently focused application window D will not cover the window interface of the previous current application window C. That is, application windows that do not belong to the same task group do not share the same window area on the interface. The window area of ​​the current application window can be controlled to be drawn according to the gain and loss of focus. In other words, the current application window C and the currently focused application window D do not belong to the same task group; they each have their own window area and are displayed independently, without affecting each other.

[0127] In some embodiments of this application, after the window area of ​​the current application window is drawn according to the loss of focus, the window interface of the currently focused control application window is placed on top of the window interface of the current application window.

[0128] For example, continue with Figure 9 and Figure 10 For example, Figure 13 As shown, the window interface of the application window D, which currently has focus control, is placed on top of the window interface of the current application window C and displayed on the screen. Figure 13 The window interface of the currently applied window C does not disappear, while the window interface of the currently focused applied window D appears. The window interfaces of the currently applied window C and the window interface of the currently focused applied window D can be seen simultaneously, and two window interfaces are displayed on the monitor.

[0129] In the example above, when the current application window loses focus, it checks whether the task identifier corresponding to the current task and the currently focused application window belong to the same task. If they are not the same task, it means that the newly launched application window is not the same floating window as the current one, and the window area with focus changes. The current application window's window area is then drawn according to the loss of focus, further improving the user experience.

[0130] Figure 14 A flowchart of another application window control method according to some embodiments is shown. An embodiment of this application provides a display device in which the controller is configured to perform... Figure 14 The application window control method includes:

[0131] Step 1401: Detect focus application change information and determine whether there is an application window that has gained focus control.

[0132] In some embodiments of this application, when the remote control receiving device receives input operations from the remote control or receives user input operations through touch or gestures, and confirms the launch of a new application window interface, it can detect the focus application change information, thereby determining whether there is an application window that has gained focus control.

[0133] Step 1402: If a focus-controlled application window exists, query the task to which the focus-controlled application window belongs.

[0134] Step 1403: Mark the task identifier corresponding to the task in the WMS window manager so that the window interface is displayed on the monitor by comparing the task identifier.

[0135] In some embodiments of this application, when there is an application window that obtains focus control, the task to which the application window belongs can be queried, that is, it can be determined which task the application window belongs to, and the task identifier corresponding to the task is marked in the WMS window manager. That is, the task is uniquely identified by the task identifier, and application windows (floating windows) belonging to the same task can share the same task identifier.

[0136] In some embodiments of this application, a task identifier corresponding to the task is marked in the WMS window manager so that the window interface is displayed on the display based on the comparison of the task identifier. For example, when the current task identifier of the current application window is the same as the target task identifier in the WMS window manager, the window area of ​​the current application window is controlled to be drawn according to gaining focus; or when the current task identifier of the current application window is different from the target task identifier in the WMS window manager, the window area of ​​the current application window is controlled to be drawn according to losing focus.

[0137] For example, such as Figure 15 The current application window X shown is accompanied by application icons K and M on the monitor. By clicking application icon K, the focus application change information can be detected, and it can be determined that there is an application window that has gained focus control corresponding to application icon K. The task to which the focus control application window belongs can be retrieved, and the task identifier corresponding to the task is marked in the WMS window manager, for example, "task-K", so that the window interface can be determined to be displayed on the monitor based on the comparison of the task identifier.

[0138] In the example above, by marking the task identifier corresponding to the task in the WMS window manager, the window interface is determined by comparing the task identifier and displayed on the monitor. This avoids the problem of flickering in the toolbar and other window areas when launching a new application window interface, thus improving the user experience.

[0139] Figure 16 A flowchart of another application window control method according to some embodiments is shown. This embodiment further optimizes the above application window control method based on the above embodiments. Figure 16 As shown, the method includes:

[0140] In some embodiments of this application, a preferred focus control parameter is set in the WMS window manager, a parameter value corresponding to the preferred focus control parameter is assigned to mark the task identifier corresponding to the task, and the task identifier corresponding to the task is stored in the WMS window manager.

[0141] The preferred focus control parameter can be one or more combinations of letters, symbols, and numbers. By setting different parameter values ​​for the preferred focus control parameter, different task identifiers corresponding to the assigned task are marked and stored in the WMS window manager. Thus, the task identifiers in the WMS window manager can be obtained through the callback interface for comparison, quickly determining how the window area should be drawn, ensuring the application window control effect, and meeting user needs.

[0142] As an example of a scenario, such as Figure 17 As shown, the WMS window manager detects changes in the focus application and sets a new focus application. It can determine whether the focus-controlled application window is empty. If the focus-controlled application window is not empty, it queries the task to which the focus-controlled application window belongs and records the corresponding task identifier. When it detects a change in focus application information (such as triggering a displayed interface to lose focus or triggering a new interface to gain focus), it triggers a callback through a callback interface, thereby prompting the toolbar to request the display of the application window. It then determines whether the toolbar's application window has gained focus. If the toolbar's application window has not gained focus, it checks whether the task identifiers of the toolbar's application window and the application window that has gained focus are the same. If the task identifiers of the toolbar's application window and the application window that has gained focus are the same, the toolbar is drawn as if it has gained focus. If the task identifiers of the toolbar's application window and the application window that has gained focus are different, the toolbar is drawn as if it has lost focus.

[0143] Specifically, a new control parameter is added to the WMS window manager, namely the preferred focus control parameter, for example, defined as "Prefered Focus Task Id". This preferred focus control parameter records the task identifier selected by the embodiments of this application (each task has a unique task identifier).

[0144] It is understandable that when a new application window is launched, the focus of the currently displayed application window changes first, and the toolbar of the currently displayed application window changes after losing focus. That is, the new focus application is first set through the WMS window manager, and then the focus of the corresponding application window of the new focus application is found, triggering the focus change of the application window. Therefore, when setting a new focus application in the WMS window manager, the task to which the new focus application belongs can be queried, and the task identifier of the task can be obtained. During the processing of the root node view DécorView toolbar, when the application window receives a callback request (application window display request), it usually changes the window interface display as soon as it gains focus, resulting in a flickering problem. In this embodiment, when the current application window loses focus, it is compared with the task identifier (target task identifier) ​​recorded in "Preferred Focus Task Id" to determine whether the current application window and the application window that currently gains focus belong to the same task. If they are the same task, it means that the launched new application window is the same floating window as itself, and the floating window with focus has not changed, so there is no need to change the window area of ​​the current application window.

[0145] In scenarios where application window 1 and application window 2 belong to the same task, when application window 1 launches application window 2, application window 1 will maintain a focused state, such as gray, without flickering. In scenarios where application window 1 and application window 2 do not belong to the same task, when application window 1 launches application window 2, application window 1 will still lose focus because it does not belong to the same task as application window 2. This is consistent with the user interaction experience of multi-window mode in Freeform. For example, the floating window of application window 1 turns black, and the floating window of application window 2 appears and is gray with focus.

[0146] The toolbar can determine whether the task identifier of the application window is in the same task as the "Prefered Focus Task Id" recorded. It can query the callback interface path of "Prefered Focus Task Id" from WMS through DecorCaptionView (toolbar object) and realize the comparison query of task identifier through the application window.

[0147] Therefore, when the current application window loses focus, it checks whether the task identifier of the current task and the task identifier of the application window that currently has focus belong to the same task. If they are the same task, it means that the newly launched application window is the same floating window as the current one, and the window area with focus has not changed. The current application window's window area is then drawn according to the focus-gaining behavior. When the current application window loses focus, it checks whether the task identifier of the current task and the task identifier of the application window that currently has focus belong to the same task. If they are not the same task, it means that the newly launched application window is not the same floating window as the current one, and the window area with focus has changed. The current application window's window area is then drawn according to the focus-loss behavior. This solves the problem of flickering toolbars and other window areas when launching a new application window in Freeform mode, further improving the user experience.

[0148] In some embodiments, this application also provides an electronic device, including: a memory and a processor, wherein the memory is used to store a computer program; and the processor is used to cause the electronic device to implement the application window control method described in any of the above embodiments when executing the computer program.

[0149] In some embodiments, this application provides a computer-readable storage medium storing a computer program that, when executed by a computing device, causes the computing device to implement the application window control method described in any of the above embodiments.

[0150] In some embodiments, this application provides a computer program product that, when run on a computer, enables the computer to implement the application window control method described in the second aspect or any embodiment of the second aspect.

[0151] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0152] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Various modifications and variations can be obtained based on the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, thereby enabling those skilled in the art to better utilize the described embodiments and various different variations of embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that, include: monitor; A controller connected to the display, wherein the controller is configured to: Obtain the application window display request and determine the current task identifier of the current application window; The current task identifier is compared with the target task identifier in the WMS window manager; wherein, the target task identifier is used to identify the task corresponding to the application window that is currently receiving focus control. If the current task identifier and the target task identifier are the same, control the window area of ​​the current application window to be drawn according to the focus acquisition; The window interface of the currently focused application window is displayed on the monitor, replacing the window interface of the current application window. If the current task identifier and the target task identifier are different, control the window area of ​​the current application window to be drawn as if it has lost focus; The display shows the window interface of the current application window and the window interface of the application window that currently has focus; wherein the window interface of the application window that currently has focus is displayed on top of the window interface of the current application window.

2. The display device according to claim 1, characterized in that, The controller is also configured to: The application window display request is obtained through a pre-set callback interface.

3. A display device, characterized in that, include: monitor; A controller connected to the display, wherein the controller is configured to: Upon detecting a change in focus application information, determine whether there is an application window that has gained focus control. If an application window has been given focus control, query the task to which the application window with focus control belongs. In the WMS window manager, mark the task identifier corresponding to the task so that the window interface is displayed on the monitor by comparing the task identifier; Set the preferred focus control parameters in the WMS window manager; Assign a parameter value corresponding to the preferred focus control parameter to mark the task identifier corresponding to the task, and store the task identifier corresponding to the task in the WMS window manager.

4. An application window control method, characterized in that, include: Obtain the application window display request and determine the current task identifier of the current application window; The current task identifier is compared with the target task identifier in the WMS window manager; wherein, the target task identifier is used to identify the task corresponding to the application window that is currently receiving focus control. If the current task identifier and the target task identifier are the same, control the window area of ​​the current application window to be drawn according to the focus acquisition; Replace the current application window's window interface on the monitor with the window interface of the application window that currently has focus control; If the current task identifier and the target task identifier are different, control the window area of ​​the current application window to be drawn as if it has lost focus; The display shows the window interface of the application window that currently has focus control.

5. The application window control method according to claim 4, characterized in that, The method further includes: The application window display request is obtained through a pre-set callback interface.

6. An application window control method, characterized in that, include: Upon detecting a change in focus application information, determine whether there is an application window that has gained focus control. If an application window has been given focus control, query the task to which the application window with focus control belongs. In the WMS window manager, mark the task identifier corresponding to the task so that the window interface is displayed on the monitor by comparing the task identifier; Set the preferred focus control parameters in the WMS window manager; Assign a parameter value corresponding to the preferred focus control parameter to mark the task identifier corresponding to the task, and store the task identifier corresponding to the task in the WMS window manager.

Images