Processing method and electronic equipment

Abstract

The invention provides a processing method and electronic equipment, and is applied to the technical field of terminals. The processing method comprises the steps that a first window and a second window are displayed on a display interface in a multi-window mode, the display level of the second window is larger than that of the first window, and a second area of the second window is at least overlapped with a first area of the first window; a first input event for the second window is responded to act on the second area, if the second window has a first identifier, the first input event is sent to a first application corresponding to the first window so that the first application can respond to the first input event, and the first identifier is used for unvarnished transmission of the first input event of the second window.

Description

Technical Field

[0001] This disclosure relates to the field of terminal technology, and in particular to a processing method and an electronic device. Background Technology

[0002] Currently, most electronic devices support multi-window display, allowing users to open multiple applications. These applications can be displayed in split-screen or overlay formats. However, if multiple windows overlap, the applications may not be able to respond to user input events in the overlapping area of ​​the underlying window, negatively impacting the user experience. Summary of the Invention

[0003] In view of this, the present disclosure provides a processing method and an electronic device.

[0004] According to a first aspect of this disclosure, a processing method is provided, comprising: displaying a first window and a second window in a multi-window mode on a display interface, wherein the display layer of the second window is greater than that of the first window, and a second region of the second window overlaps at least with a first region of the first window; in response to a first input event acting on the second region of the second window, if the second window has a first identifier, sending the first input event to a first application corresponding to the first window so that the first application responds to the first input event, wherein the first identifier is used to transmit the first input event of the second window.

[0005] According to an embodiment of this disclosure, sending a first input event to a first application corresponding to a first window to cause the first application to respond to the first input event includes: if the input event acts on a first operation item area, generating a sub-window corresponding to the first operation item, wherein the display layer of the second window is greater than the display layer of the sub-window, and the second area of ​​the second window overlaps at least with the third area of ​​the sub-window; and controlling a first identifier to act on the sub-window.

[0006] According to an embodiment of this disclosure, controlling the first identifier to act on a child window includes: in response to a second input event acting on a second area for a second window, based on the second window having a first identifier, sending the second input event to a first application corresponding to the child window so that the child window of the first application responds to the second input event.

[0007] According to embodiments of this disclosure, the method further includes: responding to an input event acting on a target area in a second region of the second window, if the second window has a first identifier, sending the input event to a second application corresponding to the second window so that the second application responds to the input event; responding to an input event acting on a non-target area in a second region of the second window, if the second window has a first identifier, sending the input event to a first application corresponding to the first window so that the first application responds to the input event, wherein the second region includes a target area and a non-target area.

[0008] According to embodiments of this disclosure, sending an input event to a second application corresponding to a second window to cause the second application to respond to the input event includes: displaying a menu window corresponding to the second window, and creating a second identifier for the menu window, the second identifier being used to allow the second application to receive input events outside the menu window area to close the menu window.

[0009] According to embodiments of this disclosure, the method further includes: a menu window covering a fourth area of ​​a first window, the fourth area being different from the first area; responding to a third input event acting on a fifth area outside the fourth and first areas, sending the third input event to a second application so that the second application closes the menu window in response to the third input event.

[0010] According to embodiments of this disclosure, the method further includes: a menu window covering a fourth area of ​​a first window, the fourth area being different from the first area; responding to a fourth input event acting on a non-target area of ​​a second area of ​​a second window and acting on a first operation item area of ​​the first window, and closing the menu window;

[0011] The input event is then sent to the first application so that the first application performs the function corresponding to the first operation item.

[0012] According to an embodiment of this disclosure, closing the menu window includes: generating a virtual event with non-zero event coordinates, sending the virtual event to a second application, the second application identifying the virtual event as an event outside the menu area based on a second identifier, closing the menu window, and destroying the second identifier.

[0013] According to embodiments of this disclosure, the first window is an application window, the second window is a control bar window corresponding to the system application, and the target area is the menu extension options of the control bar.

[0014] A second aspect of this disclosure provides an electronic device, comprising: a display screen having a display interface for displaying a window corresponding to an application; a processor for displaying a first window and a second window in a multi-window mode on the display interface, wherein the display layer of the second window is greater than the display layer of the first window, and a second area of ​​the second window overlaps at least with a first area of ​​the first window; and in response to an input event acting on the second area of ​​the second window, if the second window has a first identifier, sending the input event to a first application corresponding to the first window to cause the first application to respond to the input event, wherein the first identifier is used to transmit the input event of the second window.

[0015] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0016] The above and other objects, features and advantages of this disclosure will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0017] Figure 1 This schematic diagram illustrates a multi-window display used in various applications within the relevant technology.

[0018] Figure 2 A flowchart illustrating a processing method according to an embodiment of the present disclosure is shown schematically.

[0019] Figure 3 One of the schematic diagrams of a processing method according to an embodiment of the present disclosure is shown;

[0020] Figure 4 A second schematic diagram illustrating a processing method according to an embodiment of the present disclosure is shown.

[0021] Figure 5 A schematic diagram of a processing method according to an embodiment of the present disclosure is shown in Figure 3.

[0022] Figure 6 A schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure is shown;

[0023] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing a processing method according to an embodiment of the present disclosure. Detailed Implementation

[0024] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0026] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0027] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0028] This disclosure provides a processing method and an electronic device. Before introducing the technical solutions provided by this disclosure, the relevant technologies involved in this disclosure will be described first.

[0029] Currently, most electronic devices support multi-window display, allowing users to open multiple applications. These applications can be displayed in split-screen or overlay formats. However, if multiple windows overlap, the applications may not be able to respond to user input events in the overlapping area of ​​the underlying window, negatively impacting the user experience.

[0030] For example, taking a tablet computer as an example, such as Figure 1As shown, the tablet displays a first window (gray area) of a first application and a second window (green area) of a second application. The second window overlaps with the first window (green area), and the second window is on a higher level than the first window. The second window is usually transparent so that the user can see the content in the overlapping first window through it. User input events in the overlapping area of ​​the first and second windows are intercepted by the second application in the second window, preventing the first application from receiving user input events in that area. For example, if the user clicks the login option in the first window, there will be no response because the area where the login option is located overlaps with the second window.

[0031] The following will be through Figures 2-5 The processing method of the embodiments of this disclosure will be described in detail.

[0032] Figure 2 A flowchart illustrating a processing method according to an embodiment of the present disclosure is shown schematically. Figure 3 One of the schematic diagrams of a processing method according to an embodiment of the present disclosure is shown.

[0033] like Figure 2 As shown, the processing method of this embodiment includes operations S210 to S220.

[0034] In operation S210, a first window and a second window are displayed in a multi-window mode on the display interface. The display layer of the second window is greater than that of the first window, and the second area of ​​the second window overlaps with the first area of ​​the first window at least once.

[0035] In operation S220, in response to a first input event acting on a second area for a second window, if the second window has a first identifier, the first input event is sent to a first application corresponding to the first window so that the first application responds to the first input event, wherein the first identifier is used to pass through the first input event of the second window.

[0036] For example, multi-window mode can be a mode in which the display interface of an electronic device can display multiple application windows simultaneously. For instance, in multi-window mode, the multiple windows can adopt various layout methods such as split-screen mode, floating window mode, and picture-in-picture mode.

[0037] The first window can be one of the windows in a multi-window interface, used to display the interface content of the first application. For example, the first window can be a window of a map application, a window of a browser application, a window of a video player, etc. This disclosure does not specifically limit the type of the first application.

[0038] The second window can be another window within a multi-window interface, used to display the interface content of a second application. The first and second windows can be interfaces of different applications, or interfaces of different functional modules of the same application. For example, the second window can be a control bar, a system floating window, a floating control window, a notification bar, a sidebar, an instant message bubble, etc.

[0039] For example, refer to Figure 3 On a tablet, the browser serves as the first window, and the control bar as the second. On the in-vehicle terminal, the map serves as the first window, and the incoming call notification pop-up is the second. On a computer, the game serves as the first window, and the calculator application pop-up is the second.

[0040] In a window management system, each window has a Z-order value, or layer value, used to determine the stacking relationship of windows. Windows with higher layer levels visually overlay windows with lower layer levels. A second window has a higher display layer than the first window, meaning the second window visually appears above the first. For example, a floating calculator window (the second window) has a higher layer than a full-screen game window (the first window). (Continue to...) Figure 3 The title bar window (second window) is at a higher level than the browser application window (first window).

[0041] The second region of the second window overlaps at least with the first region of the first window. Specifically, at least a portion of the second window (referred to as the second region) overlaps with a portion of the first window (referred to as the first region) in screen coordinates. Overlap means that the two regions intersect in a two-dimensional plane. The second region and the first region can completely overlap, partially overlap, or the second region can be completely contained within the first region. For example, continue referring to... Figure 3 The lower half (second area) of the title bar window (white) overlaps with the upper half (first area) of the browser application window (gray), meaning the title bar window and the browser application window partially overlap.

[0042] Input events include, but are not limited to, touch events, mouse click events, and gesture events. When a user's input operation (the first input event) occurs within the second area of ​​the second window, it means that the coordinates of the first input event fall within the range of the second area. That is, according to the normal window event dispatch logic, this event should be received by the second window first, because it has a higher hierarchy and is located at the input position.

[0043] The first identifier can be a window configuration attribute. If a window has a first identifier, it indicates that the window supports input event pass-through functionality. For example, when a second window has a first identifier, when a first input event is applied to a second area of ​​the second window (overlapping with the first area of ​​the first window), the first input event will be passed to the first application of the first window. For instance, if the second window is a semi-transparent overlay panel, after setting the first identifier for the second window, when the user swipes left or right in the overlay's covered area, the event is passed through to the video player in the first window, and the player performs fast forward / rewind or toggle.

[0044] In one example, continue to refer to Figure 3 When a user opens a browser application, forming the first window, the system configures a semi-transparent control bar for the browser application, forming the second window. The control bar visually appears above the browser window, and its lower half (the second area) overlaps with the upper half (the first area) of the browser window. A first identifier is configured for the second window. For example, the window decorator (WM Shell Window Decoration) of the window manager creates a caption bar window and adds an INPUT_SPY flag (the first identifier) ​​to inform the input flinger. When the user performs an input operation (the first input event) on the second area of ​​the control bar, the first input event is sent to the first application to which the first window corresponding to the first area belongs.

[0045] Understandably, by setting an input passthrough flag for a window, the upper window can selectively pass input events through to the lower window for processing. Thus, in multi-window display scenarios, users can directly operate the content of the obscured lower window without closing or moving the upper window. This effectively solves the problem of the upper window blocking the interaction of the lower window in the traditional multi-window mode, improving the convenience of multitasking and the smoothness of the user experience.

[0046] Figure 4 A second schematic diagram of a processing method according to an embodiment of the present disclosure is shown.

[0047] As described above, in operation S220, a first input event is sent to a first application corresponding to the first window so that the first application responds to the first input event. In one possible implementation, the operation may further include the operation that, if the input event acts on a first operation item area, a child window corresponding to the first operation item is generated, the display layer of the second window is greater than the display layer of the child window, and the second area of ​​the second window overlaps at least with the third area of ​​the child window.

[0048] For example, the first action item area can be an interactive area in the first window used to trigger a specific function. For instance, the first action item area can be a button area, toolbar icon area, etc., in the application interface. When the user performs an input operation on the first action item area, the first application will generate corresponding interface elements based on the function of that action item.

[0049] A child window can be a subordinate window created by the first application, used to display the functional interface corresponding to the first operation item. For example, a child window can be a settings panel window, a file selector window, etc. The child window belongs to the same application as the first window.

[0050] The second window's display layer is higher than the child window's display layer, meaning the second window visually sits above the child window. In the window hierarchy, the second window's Z-axis order value is higher than the child window, forming a top-to-bottom stacking order: the second window is on top, the child window is in the middle layer, and the first window is at the bottom. For example, the control bar window (the second window) is on a higher layer than the application's pop-up settings panel window (the child window), and the settings panel window is on a higher layer than the application's main interface window (the first window).

[0051] The second region of the second window overlaps with at least the third region of the child window. This overlap can occur in screen coordinates between the second region of the second window and a portion of the child window (referred to as the third region). For example, the second region of the control bar window (the second window) overlaps with the top region (the third region) of the file selector window (the child window) that pops up with the application.

[0052] In one example, continue to refer to Figure 4The user opens a browser application on the tablet's display, forming the first window. The system configures a control bar for the browser application, forming a second window. The second area of ​​the control bar overlaps with the first area of ​​the browser application. The insert option (the first operation item area) in the browser window is located in the first area, meaning the insert option is visually covered by the second area of ​​the control bar. A first identifier is configured for the second window, enabling the control bar to support input event pass-through. When the user clicks the position in the second window corresponding to the insert option in the first window, the click event is passed through to the corresponding insert option in the first window because the second window has the first identifier. The browser application responds to this click event, generating a child window (blue area) corresponding to the first window. This child window is a file selector window, allowing the user to insert images, links, etc. The control bar window (second window) is on top, the file selector window (child window) is in the middle layer, and the browser application's main interface (first window) is at the bottom layer. If the second area of ​​the control bar overlaps with the third area of ​​the child window, the first identifier continues to apply to the file selector window. This allows the click event to be passed through to the file selector application when the user clicks an option in the file selector within the third area (the overlapping area between the file selector window and the control bar window). The file selector application can then process the user's actions on the file selector normally.

[0053] Understandably, by applying the first identifier to the child window, the child window generated by the first application can still receive user input events normally when it overlaps with the second window. This effectively solves the problem of blocked child window interaction in multi-window mode, ensuring the integrity of application functions and the continuity of user operations.

[0054] As described above, in the operation: control the first identifier to act on the child window. In one possible implementation, the operation may further include the operation: in response to a second input event acting on a second region for a second window, based on the second window having a first identifier, sending the second input event to a first application corresponding to the child window so that the child window of the first application responds to the second input event.

[0055] For example, the second input event can be another input operation performed by the user within a second area of ​​the second window. The second input event may be the same as or different from the first input event in type, but both belong to input operations targeting the second window. For instance, the first input event may be a click operation that triggers the generation of a child window; the second input event may be a swipe operation, a click operation, a long press operation, etc., used to interact with the already generated child window.

[0056] In one example, continuing with the previous example, a user wants to select an image file for insertion in the file selector window. They click on the image file's thumbnail within the overlapping area, generating a second input event. Because the coordinates of this click operation fall within the second area of ​​the second window, and the second window is located above the child window, the second input event is first captured by the second window's event handling system.

[0057] The system detects that the second window has the first identifier and determines that the second input event needs to be passed through. The system sends the second input event to the browser application. The browser application determines that the event applies to the file list area (third area) of the file selector window (child window) based on the event coordinates, and then dispatches the event to the file selector window. The file selector window responds to the click event and performs an image insertion operation.

[0058] Figure 5 The diagram illustrates a third schematic of a processing method according to an embodiment of the present disclosure.

[0059] As described above, in some embodiments, the processing method of this embodiment may further include the following operations: in response to an input event acting on a target area in a second region of the second window, if the second window has a first identifier, sending the input event to a second application corresponding to the second window so that the second application responds to the input event; in response to an input event acting on a non-target area in a second region of the second window, if the second window has a first identifier, sending the input event to a first application corresponding to the first window so that the first application responds to the input event, wherein the second region includes a target area and a non-target area.

[0060] For example, the target area can be an interactive area in the second area of ​​the second window used to trigger the functions of the second application itself. That is, the target area overlaps with the first area of ​​the first window. For example, the target area can be a menu button area, a function icon area, an operation control area, etc. on the control bar.

[0061] The non-target area can be any area in the second area of ​​the second window other than the target area.

[0062] The second region includes a target region and a non-target region, meaning that the area where the second window overlaps with the first window is functionally divided into two parts. The target region needs to respond to the functions of the second application, while the non-target region does not need to respond to the functions of the second application.

[0063] In one example, refer to Figure 5The user opens a browser application on the tablet's display, forming the first window. The system then configures a control bar for the browser application, forming the second window. The control bar window visually appears above the browser window, and its second area overlaps with the first area of ​​the browser window. The second area includes a target area and a non-target area. The target area is the "three-dot menu" button area in the middle of the control bar, while the non-target area comprises the rest of the control bar, including its background area and title display area.

[0064] Configure a first identifier for the second window to enable differentiated input event handling in the control bar. When the user clicks the target area, i.e., the three-dot menu button in the middle of the control bar, the system sends the click event to the second application corresponding to the second window, which then responds to the click event and executes the function of opening the menu. When the user clicks a non-target area, i.e., a location other than the three-dot menu button in the overlapping area of ​​the control bar and the browser application, the system forwards the click event to the first application corresponding to the first window, since that area is not the target area.

[0065] Understandably, by dividing the overlapping area of ​​the second window into target and non-target areas and differentiating them according to the specific location of the user input event, the second window can retain its core interactive functions while passing input events from non-functional areas to the first window. In multi-window display scenarios, this ensures the normal use of the second window's functions while avoiding the problem of the second window blocking the interaction of the first window, effectively improving the interaction flexibility and user-friendliness in window overlap scenarios.

[0066] As described above, the operation involves sending an input event to a second application corresponding to the second window so that the second application responds to the input event. In one possible implementation, this operation may further include the operation of displaying a menu window corresponding to the second window and creating a second identifier for the menu window, the second identifier being used to allow the second application to receive input events outside the menu window area to close the menu window.

[0067] For example, the menu window can be an interactive window that pops up when the second application responds to the user's input on the target area. For instance, the menu window can be a drop-down menu window, a pop-up option window, a context menu window, etc. The menu window is used to carry the functional options of the second application, allowing the user to select and perform a specific operation.

[0068] The second identifier can be a window configuration attribute used to enable the menu window to receive special input events. If the menu window has a second identifier, it means that a second application can receive input events outside the menu window's display area. This capability allows the second application to capture and process events when the user clicks or performs other input operations outside the menu window, such as closing the menu window.

[0069] In one example, continue to refer to Figure 5 The user opens a browser application on the tablet's display, forming the first window. The system configures a control bar for the browser application, forming the second window. The second area of ​​the control bar window overlaps with the first area of ​​the browser window. The second area includes a target area and a non-target area, where the target area is the "three-dot menu" button area in the middle of the control bar (i.e., the area surrounded by the red box).

[0070] When a user clicks on a target area, the click event is sent to the second application corresponding to the second window. The second application responds to the click event by displaying a menu window corresponding to the second window on the display interface. The menu window is displayed above both the second and first windows, visually positioned above the control bar window and the browser window.

[0071] Create a second identifier for the menu window so that a second application can receive input events outside the menu window's display area. For example, the window manager adds OUTSIDE and NOT ZERO OUTSIDE COORDS tags to the menu window. These tags tell the input dispatcher that when an input event occurs outside the menu window's display area, the input event should be sent to the second application.

[0072] When a user clicks a menu item within the menu window area, the second application responds to the click event and executes the corresponding function. When the user clicks outside the menu window area (i.e., clicks anywhere else on the display interface besides the menu window), because the second window has a first identifier for pass-through, if this were received by the first application window, the menu would not be able to close. Therefore, in this embodiment, by configuring the menu window with a second identifier, even if the user clicks an area outside the menu window after it has been expanded, the second application can still receive the click event. That is, the second application responds to click events outside the menu window area, closes the menu window, and restores the display interface to its state before the menu window was displayed.

[0073] Understandably, by creating a second identifier for the menu window, the second application can receive input events outside the menu window area, thus realizing the function of automatically closing the menu when the user clicks outside the menu window. In multi-window display scenarios, this not only meets the user's habitual expectations for menu interaction and avoids being responded to by the first window, but also avoids the problem of the menu window continuously occupying interface space, effectively improving the convenience of menu interaction and the smoothness of interface operation.

[0074] As described above, in some embodiments, the processing method of this embodiment may further include the following operations: the menu window is overlaid on a fourth area of ​​the first window, the fourth area being different from the first area; in response to a third input event acting on a fifth area outside the fourth area and the first area, the third input event is sent to a second application so that the second application closes the menu window in response to the third input event.

[0075] For example, the fourth region can be another region in the first window that is different from the first region. It should be noted that the first and fourth regions may partially overlap or not overlap. For instance, the first region may be the top region of the first window, while the fourth region may be the middle or bottom region of the first window.

[0076] The fifth region can be any region in the first window other than the first and fourth regions. The fifth region is spatially separate from the first and fourth regions and does not overlap with them.

[0077] In one example, continue to refer to Figure 5 The user opens a browser application on the tablet's display, creating the first window. The system then configures a control bar for the browser application, creating a second window. The control bar window is located at the top of the browser window, and its second area overlaps with the first area of ​​the browser window.

[0078] When a user clicks the three-dot menu button in the second area of ​​the control bar, the second application responds to the click event and displays the menu window. The menu window overlays the fourth area of ​​the browser window.

[0079] A second identifier is created for the menu window, enabling the second application to receive input events outside the menu window area. When the user performs a click operation outside the menu window area, this click operation constitutes a third input event. The third input event can be applied to a fifth area outside the first and fourth areas of the first window. The third input event is sent to the second application. The second application responds to the third input event, closes the menu window, causing the menu window to disappear from the display interface, and the fourth area of ​​the browser window is fully displayed again.

[0080] As described above, in some embodiments, the processing method of this embodiment may further include the following operations: the menu window is overlaid on a fourth area of ​​the first window, the fourth area being different from the first area; in response to a fourth input event acting on a non-target area of ​​the second area of ​​the second window and acting on a first operation item area of ​​the first window, the menu window is closed; and the input event is sent to a first application so that the first application performs the function corresponding to the first operation item.

[0081] In one example, continue to refer to Figure 5 The user opens a browser application on the tablet's display, creating the first window. A control bar is then configured for the browser application, creating the second window. The second area of ​​the control bar window overlaps with the first area of ​​the browser window. The second area includes a target area and a non-target area. The target area is the "three-dot menu" button area in the middle of the control bar, and the non-target area is the rest of the second control bar area excluding the "three-dot menu" button.

[0082] When a user clicks on a non-target area of ​​the control bar while the menu window is displayed, and the click location corresponds to the insertion box position in the browser window, the user's click action triggers the fourth input event. The fourth input event applies to the non-target area of ​​the second window, and also to the area where the search box is located in the first window.

[0083] Upon responding to the fourth input event, the system first closes the menu window. The menu window disappears from the display interface, and the fourth area of ​​the browser window is fully displayed again. After the menu window closes, the system sends the fourth input event to the first application. Upon receiving the fourth input event, the first application determines that the input event occurred in the area where the insertion box is located and executes the function corresponding to the insertion box, i.e., activating the file selection window.

[0084] As described above, the operation is to close the menu window. In one possible implementation, this operation may further include the following steps: generating a virtual event with non-zero event coordinates, sending the virtual event to a second application, the second application identifying the virtual event as an event outside the menu area based on a second identifier, closing the menu window, and destroying the second identifier.

[0085] For example, a virtual event can be a simulated input event generated by the system or application to trigger corresponding processing logic under specific conditions. Virtual events differ from real input events directly generated by the user; they are actively created at the software level. For instance, virtual events can be simulated click events, simulated touch events, simulated key press events, etc.

[0086] Non-zero event coordinates can be location information carried by a virtual event, where the coordinate values ​​are not zero. Event coordinates are typically represented by X and Y coordinates in the screen coordinate system. Non-zero event coordinates mean that the event occurred in a physical spatial location. For example, when a user clicks on a location with coordinates (100, 200) on the screen, the event coordinates are non-zero. Virtual events with non-zero event coordinates can transmit location information to the application that receives the event, allowing the application to determine the specific area where the event occurred based on this location information.

[0087] The second identifier can be an attribute marker configured on the menu window to indicate that the window supports receiving input events outside the window's display area. For example, the second identifier can include a combination of the OUTSIDE marker and the NOT_ZERO_OUTSIDE_COORDS marker. The OUTSIDE marker indicates that the window can receive events occurring outside the window's boundaries, and the NOT_ZERO_OUTSIDE_COORDS marker indicates that external events passed to the window should contain non-zero coordinate information. When the menu window has this second identifier, even if the user's input operation occurs outside the menu window's display area, the system will still send the input event to the menu window as a virtual event, and this virtual event carries the actual coordinates of the input operation.

[0088] In one example, let's continue with the example above. When creating a menu window, the system configures a second identifier for the menu window, which includes the OUTSIDE flag and the NOT_ZERO_OUTSIDE_COORDS flag.

[0089] After the menu window pops up, the user continues browsing the webpage and clicks the "Insert" button in the browser window. Since the settings button is located in the overlapping area (second area) of the control bar window and the browser window, and this location is also outside the display area of ​​the menu window, the user's click triggers two processing flows simultaneously. First, because the control bar window has a first identifier, the click event is propagated to the browser application, which responds to the user's click of the "Insert" button. Second, detecting that the click location is outside the boundary of the menu window, and that the menu window has a second identifier, a virtual event with non-zero event coordinates is generated. The coordinates of this virtual event are the actual coordinates of the user's click on the settings button.

[0090] The virtual event is sent to the second application corresponding to the menu window. Upon receiving the virtual event, the second application identifies the coordinate information carried by the virtual event based on the second identifier configured in the menu window. By comparing the coordinates of the virtual event with the boundary range of the menu window, the second application determines that the virtual event occurs outside the display area of ​​the menu window, i.e., it identifies the virtual event as an external event. In response to this external event, the second application closes the menu window, destroys the second identifier of the menu window, and clears the OUTSIDE and NOT_ZERO_OUTSIDE_COORDS flags. After the menu window is closed, the interface reverts to a state where only the control bar window and browser window are displayed, and the browser application has synchronously completed the response to the insert button, opening the file selector window.

[0091] As described above, in some embodiments, the first window is an application window, the second window is a control bar window corresponding to the system application, and the target area is the menu extension options of the control bar.

[0092] For example, an application window can be the window corresponding to an application actively opened by the user, used to carry the main functional interface of the application. An application window can be a window of a third-party application or a window of a system-pre-installed application. For instance, an application window can be a browser application window, a map application window, a video player window, a document editor window, a game application window, etc. Application windows typically occupy the main display area of ​​the interface, used to present the application's content and interactive controls. A control bar window can be a window created by a system application, used to provide window control functionality for application windows in multi-window mode.

[0093] Control bar windows are typically located at the edge or in a specific position within an application window, and are used to display window operation controls. For example, a control bar window can be a title bar window, a toolbar window, or a floating control bar window. The control bar window's display hierarchy is usually higher than the application window to ensure that users can access window controls at any time. Control bar windows can contain various control buttons, such as minimize, maximize, close, split-screen, and menu expansion buttons.

[0094] Menu extension options can be the area in the control bar window used to trigger a pop-up menu. These options are typically presented as icons or buttons; clicking on this area opens a menu window containing more options for window operations. For example, menu extension options might be a three-dot icon button, a three-line icon button, a "More" text button, or a drop-down arrow icon. The corresponding menu window can contain extended functionality options such as adjusting window transparency, locking window position, screenshotting, sharing, and application information.

[0095] Based on the above processing method, this disclosure also provides an electronic device. The following will be combined with... Figure 6 Provide a detailed description of the electronic device.

[0096] Figure 6 A schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure is shown.

[0097] like Figure 6 As shown, the electronic device 300 of this embodiment includes a display screen 310 and a processor 320.

[0098] The display screen 310 has a display interface and is used to display windows corresponding to the application.

[0099] The processor 320 is configured to display a first window and a second window in a multi-window mode on a display interface, wherein the display layer of the second window is greater than that of the first window, and a second area of ​​the second window overlaps at least with a first area of ​​the first window; in response to an input event applied to the second area of ​​the second window, if the second window has a first identifier, the processor sends the input event to a first application corresponding to the first window so that the first application responds to the input event, wherein the first identifier is used to pass through the input event of the second window.

[0100] The description of the technical solution in this embodiment can be referred to the description of the processing method above, and will not be repeated here.

[0101] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing a processing method according to an embodiment of the present disclosure.

[0102] like Figure 7 As shown, an electronic device 400 according to an embodiment of the present disclosure includes a processor 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage portion 408 into a random access memory (RAM) 403. The processor 401 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 401 may also include onboard memory for caching purposes. The processor 401 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0103] RAM 403 stores various programs and data required for the operation of electronic device 400. Processor 401, ROM 402, and RAM 403 are interconnected via bus 404. Processor 401 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 402 and / or RAM 403. It should be noted that programs may also be stored in one or more memories other than ROM 402 and RAM 403. Processor 401 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in one or more memories.

[0104] According to embodiments of this disclosure, the electronic device 400 may further include an input / output (I / O) interface 405, which is also connected to a bus 404. The electronic device 400 may also include one or more of the following components connected to the I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 410 as needed so that computer programs read from it can be installed into the storage section 408 as needed.

[0105] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0106] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 402 and / or RAM 403 and / or one or more memories other than ROM 402 and RAM 403 described above.

[0107] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the display methods provided in the embodiments of this disclosure.

[0108] When the computer program is executed by the processor 401, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0109] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via communication section 409, and / or installed from removable medium 411. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0110] In such an embodiment, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by processor 401, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0111] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0112] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0113] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0114] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A processing method, comprising: The first window and the second window are displayed in a multi-window mode on the display interface. The display layer of the second window is greater than that of the first window, and the second area of ​​the second window overlaps with the first area of ​​the first window at least. In response to a first input event acting on the second area for the second window, if the second window has a first identifier, the first input event is sent to a first application corresponding to the first window so that the first application responds to the first input event, wherein the first identifier is used to pass through the first input event of the second window.

2. The method according to claim 1, wherein sending the first input event to a first application corresponding to the first window so that the first application responds to the first input event, comprises: If the input event is applied to the first operation item area, a sub-window corresponding to the first operation item is generated. The display level of the second window is greater than the display level of the sub-window, and the second area of ​​the second window overlaps with at least the third area of ​​the sub-window. Control the first identifier to act on the child window.

3. The method according to claim 2, wherein controlling the first identifier to act on the sub-window includes: In response to a second input event acting on the second area for the second window, based on the second window having a first identifier, the second input event is sent to a first application corresponding to the child window so that the child window of the first application responds to the second input event.

4. The method according to claim 1, further comprising: In response to an input event applied to a target area in the second region of the second window, if the second window has a first identifier, the input event is sent to a second application corresponding to the second window so that the second application responds to the input event; In response to an input event applied to a non-target area within the second region of the second window, if the second window has a first identifier, the input event is sent to a first application corresponding to the first window so that the first application responds to the input event, wherein the second region includes the target region and the non-target region.

5. The method according to claim 4, wherein sending the input event to a second application corresponding to the second window so that the second application responds to the input event, comprises: Display a menu window corresponding to the second window, and create a second identifier for the menu window. The second identifier is used to allow the second application to receive input events outside the menu window area to close the menu window.

6. The method according to claim 5, further comprising: The menu window is overlaid on a fourth area of ​​the first window, and the fourth area is different from the first area; In response to a third input event acting on the four regions and a fifth region outside the first region, the third input event is sent to the second application so that the second application closes the menu window in response to the third input event.

7. The method according to claim 5, further comprising: The menu window is overlaid on a fourth area of ​​the first window, and the fourth area is different from the first area; In response to the fourth input event, the non-target area in the second region of the second window and the first operation item area of ​​the first window are applied, and the menu window is closed. The input event is then sent to the first application so that the first application performs the function corresponding to the first operation item.

8. The method according to claim 6 or 7, closing the menu window, comprising: A virtual event with non-zero event coordinates is generated and sent to the second application. The second application identifies the virtual event as an external event of the menu area based on the second identifier, closes the menu window, and destroys the second identifier.

9. The method according to claim 1, wherein the first window is an application window, the second window is a control bar window corresponding to the system application, and the target area is the menu extension options of the control bar.

10. An electronic device, comprising: A display screen has a display interface, and the display screen is used to display a window corresponding to the application; A processor is configured to display a first window and a second window in a multi-window mode on a display interface, wherein the display layer of the second window is greater than the display layer of the first window, and a second region of the second window overlaps at least with a first region of the first window. In response to an input event applied to the second area for the second window, if the second window has a first identifier, the input event is sent to a first application corresponding to the first window so that the first application responds to the input event, wherein the first identifier is used to pass through the input event of the second window.

Images