Multi-window stacked mouse synchronization method, device, equipment and medium

Abstract

The invention provides a multi-window stacked mouse synchronization method, device, equipment and medium, and the method comprises the following steps: a Windows synchronizer arranges a master control cabinet window and slave control windows in a stacked manner, the master control window is arranged at the top layer, and the slave control windows are sequentially arranged below the master control window; monitoring a mouse event; respectively storing the monitored mouse events in event queues, and waiting for execution; setting the master control window and the slave control window to be in a penetrable window style, and executing the mouse event in the event queue; setting a window for executing the mouse event at present to be in a non-penetrable window style, and setting the window to be in a penetrable style after execution is completed; the execution of all master control windows and slave control windows is completed; after all the windows are executed, the master control window and the slave control window are set to be in a non-penetrable window style; the visual area of the main control window is enlarged, the user experience is improved, the synchronization stability is improved, and all events can be synchronized normally.

Description

Technical Field

[0001] The present invention relates to the field of information processing technology, and in particular to a multi-window stacking mouse synchronization method, device, equipment and medium. Background Art

[0002] The existing Windows synchronizer synchronizes the mouse XY axis coordinates after tiling. Under a fixed screen range, the window is cut into windows of the same proportion for synchronization. This results in a small visible range during the synchronization process, and some windows are not fully browsed.

[0003] In addition, the mouse events of the existing Windows synchronizer are synchronized 1:1 from the master window to the slave window. Because Windows scrolling events have the characteristics of many events and high frequency, and when using the touchpad, the scrolling event will instantly reach a frequency of 30 to 50 times. In the scenario of multi-window synchronization of Windows synchronizer, the frequency of 30 to 50 times will be executed in each slave window, which amplifies the performance loss caused by high-frequency execution, causing the CPU usage rate to increase rapidly in a short period of time, and then causing the user device to freeze or freeze. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a multi-window stacked mouse synchronization method, device, equipment and medium, so that the visible area of ​​the main control window is enlarged, the user experience is improved, the stability of synchronization is improved, and all events can be synchronized normally.

[0005] In a first aspect, the present invention provides a multi-window stacking mouse synchronization method, which is used for a Windows synchronizer, wherein the Windows synchronizer is used for synchronizing a master control window and at least one slave control window; the method comprises the following steps:

[0006] Step 1: Arrange the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed below the master control window in sequence;

[0007] Step 2: Use win32gui.SetWindowsHookEx to enable event monitoring and monitor mouse events;

[0008] Step 3: Store the monitored mouse events into the event queue respectively, waiting for execution;

[0009] Step 4: Set both the master window and the slave window to a transparent window style, and execute the mouse events in the event queue; set the window currently executing the mouse event to an impenetrable window style, and after the execution is completed, set the window to a transparent style; until all the master windows and slave windows are executed;

[0010] Step 5: After all windows have been executed, both the master control window and the slave control window are set to be impenetrable window styles.

[0011] In a second aspect, the present invention provides a multi-window stacking mouse synchronization device, which is used for a Windows synchronizer, wherein the Windows synchronizer is used for synchronizing a master control window and at least one slave control window; and comprises the following modules:

[0012] A stacking window module arranges the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed below the master control window in sequence;

[0013] Monitoring module, use win32gui.SetWindowsHookEx to start event monitoring and monitor mouse events;

[0014] The storage module stores the monitored mouse events into the event queue respectively, waiting for execution;

[0015] The execution module sets both the master control window and the slave control window to the transparent window style, executes the mouse events in the event queue; sets the window currently executing the mouse event to the impenetrable window style, and after the execution is completed, sets the window to the transparent style; until all the master control windows and slave control windows are executed;

[0016] The recovery module sets the master control window and the slave control window to an impenetrable window style after all windows have been executed.

[0017] In a third aspect, the present invention provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in the first aspect when executing the program.

[0018] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect.

[0019] One or more technical solutions provided by the present invention have at least the following technical effects or advantages:

[0020] The present invention arranges windows in a stacked manner, and all slave control windows are placed under the master control window; this enlarges the visible area of ​​the master control window, improves user experience, improves synchronization stability, and can synchronize all events normally.

[0021] The present invention detects the execution frequency of Windows mouse wheel events. When the execution frequency is too high, the wheel events in the same direction within a certain period of time are combined and sent, the scrolling distance is calculated, and the events are merged into a new Windows mouse wheel event for execution, thereby reducing the burden of the scrolling operation on the CPU, thereby solving the problem of freezing and blocking caused by insufficient performance of user equipment or high-frequency scrolling of a large number of slave control windows, and increasing the number of windows that can be synchronized by users.

[0022] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0024] Figure 1 is a flow chart of the method in Embodiment 1 of the present invention;

[0025] Figure 2 It is a schematic diagram of the structure of the device in the second embodiment of the present invention. DETAILED DESCRIPTION

[0026] The technical solution in the embodiment of the present application has the following general idea:

[0027] Step 1, use win32gui.ShowWindow and win32gui.SetWindowPos methods to arrange the windows in a stacked manner, with the master window on the top and the slave windows under the master window in turn;

[0028] Step 2: Use win32gui.SetWindowsHookEx to enable event monitoring, and monitor mouse click, move, and scroll events;

[0029] Step 3: Store the monitored events in the corresponding queues and wait for execution;

[0030] Step 4. Before executing mouse click, move, and scroll events, set all windows to transparent window style using win32gui.SetWindowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPARENT, and win32gui.SetLayeredWindowAttributes(hwnd,0,254,win32con.LWA_ALPHA) methods; 254 is transparency;

[0031] Step 5: Use win32gui.SendMessage with the win32con library to execute the mouse click, move, and scroll events in the corresponding queues; for example: win32con.WM_LBUTTONDOW N is a left-click; win32con.WM_MOUSEMOVE is a mouse move; win32con.WM_MOUSEWHEEL is a mouse wheel scroll;

[0032] Step 6: The executed window sets the current window back to the original state (impenetrable window style), and sets the executing window back to the penetrable window style after the mouse click, move, and scroll events are completed;

[0033] Step 7: After the execution is completed, set the window properties back to the original state (impenetrable window style) to avoid affecting user operations.

[0034] When it is a scrolling event, set a delayer, combine all Windows mouse wheel events in the same direction waiting to be executed within 20 milliseconds and mark them as cover_use, calculate the cumulative scrolling distance wParam = win32api.MAKELONG (0, int (scroll_amount * 120)), and merge them into a new mouse wheel event. Send it to the execution end. If there is a scrolling event, click event or move event in the opposite direction, combine the previous scrolling events in advance, and then set a 20 millisecond delay to combine the scrolling events, and so on.

[0035] Execute the combined wheel event on the main control window, and use win32gui.SendMesage(win32con.WM_MOUSEWHEEL,wParam,lParam) to restore the Windows mouse wheel event intercepted by the user. This allows the user to perceive that all windows are executed synchronously.

[0036] Execute the same events as the master window in the slave window in sequence, and perform a single long-distance scroll event. Reduce the number of executions and reduce the CPU burden.

[0037] Embodiment 1

[0038] like Figure 1 As shown, this embodiment provides a multi-window stacking mouse synchronization method, which is used for a Windows synchronizer, and the Windows synchronizer is used for synchronizing a master control window and at least one slave control window; it includes the following steps:

[0039] Step 1: Arrange the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed below the master control window in sequence;

[0040] Step 2: Use win32gui.SetWindowsHookEx to enable event monitoring and monitor mouse events;

[0041] Step 3: Store the monitored mouse events into the event queue respectively, waiting for execution;

[0042] Step 4: Set both the master window and the slave window to a transparent window style, and execute the mouse events in the event queue; set the window currently executing the mouse event to an impenetrable window style, and after the execution is completed, set the window to a transparent style; until all the master windows and slave windows are executed; the window is the master window or slave window that executes the mouse event;

[0043] Step 5: After all windows have been executed, both the master control window and the slave control window are set to be impenetrable window styles.

[0044] In this embodiment, preferably, the step 1 is specifically: using win32gui.ShowWindow and win32gui.SetWindowPos methods to arrange the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed under the master control window in sequence.

[0045] In this embodiment, preferably, step 4 is specifically: set the master window and the slave window to a penetrable window style using win32gui.SetWindowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPARENT and win32gui.SetLayeredWindowAttributes(hwnd, 0, 254, win32con.LWA_ALPHA) methods, and use win32gui.SendM essage with win32con.WM_LBUTTONDOWN, win32con.WM_MOUSEMO VE or win32con.WM_MOUSEWHEEL to execute mouse events in the event queue; set the window currently executing the mouse event to an impenetrable window style, and after the execution is completed, set the window to a penetrable style until all the master windows and slave windows are executed.

[0046] In this embodiment, preferably, the mouse events include: click events, move events and scroll events; the step 4 specifically includes: setting the master window and the slave window to a transparent window style by using win32gui.SetWindowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPARENT and win32gui.SetLayeredWindowAttributes(hwnd,0,254,win32con.LWA_ALPHA) methods;

[0047] If the mouse event is a click event or a move event, use win32gui.SendMessage with the win32con library to execute the mouse event in the event queue; set the window currently executing the mouse event to an impenetrable window style, and after the execution is completed, set the window to a penetrable style until all the master and slave windows are executed;

[0048] If the mouse event is a scrolling event, the device CPU usage and memory usage are obtained in real time. If the CPU usage is less than the first set threshold and the memory usage is less than the second set threshold, win32gui.SendMessage is used with win32con.WM_MOUSEWHEEL to execute the mouse event in the event queue; the window currently executing the mouse event is set to an impenetrable window style. After the execution is completed, the window is set to a penetrable style until all the master and slave windows are executed; otherwise, a delay time is set. If the scrolling events obtained within the delay time are all in the same direction and there are no click events or move events, the delay time is obtained. All scroll events in the event queues corresponding to the time are merged into a scroll merge event; if there is a scroll event, click event or move event in the opposite direction within the delay time, all scroll events in the previous event queues are combined to obtain a scroll merge event; the master window and the slave window use win32gui.SendMessage with win32con.WM_MOUSEWHEEL to execute the scroll merge event, and set the window currently executing the scroll merge event to an impenetrable window style. After the execution is completed, the window is set to a penetrable style until all the master windows and slave windows are executed. The delay time is set to 20 milliseconds to ensure that the user is not affected.

[0049] Based on the same inventive concept, the present application also provides a device corresponding to the method in Example 1, see Example 2 for details.

[0050] Embodiment 2

[0051] like Figure 2As shown, in this embodiment, a multi-window stacking mouse synchronization device is provided, which is used for a Windows synchronizer, and the Windows synchronizer is used for synchronizing a master control window and at least one slave control window; it includes the following modules:

[0052] A stacking window module arranges the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed below the master control window in sequence;

[0053] Monitoring module, use win32gui.SetWindowsHookEx to start event monitoring and monitor mouse events;

[0054] The storage module stores the monitored mouse events into the event queue respectively, waiting for execution;

[0055] The execution module sets both the master control window and the slave control window to the transparent window style, executes the mouse events in the event queue; sets the window currently executing the mouse event to the impenetrable window style, and after the execution is completed, sets the window to the transparent style; until all the master control windows and slave control windows are executed;

[0056] The recovery module sets the master control window and the slave control window to an impenetrable window style after all windows have been executed.

[0057] In this embodiment, preferably, the stacking window module specifically uses win32gui.Show Window and win32gui.SetWindowPos methods to arrange the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed at the top layer and the slave control windows being placed under the master control window in sequence.

[0058] In this embodiment, preferably, the execution module is specifically: setting the master control window and the slave control window to a penetrable window style using win32gui.SetWindowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPARENT and win32gui.SetLayeredWindowAttributes(hwnd, 0, 254, win32con.LWA_ALPHA) methods, and using win32gui.SendMessage with win32con.WM_LBUTTONDOWN, win32con.WM_MOUSE MOVE or win32con.WM_MOUSEWHEEL to execute mouse events in the event queue; setting the window currently executing the mouse event to an impenetrable window style, and after the execution is completed, setting the window to a penetrable style until all the master control windows and slave control windows are executed.

[0059] In this embodiment, preferably, the mouse event includes: a click event, a move event and a scroll event; the execution module specifically sets the master window and the slave window to a transparent window style by using win32gui.SetWi ndowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPAR ENT and win32gui.SetLayeredWindowAttributes(hwnd,0,254,win32con.LWA_ALPHA) methods;

[0060] If the mouse event is a click event or a move event, use win32gui.SendMessage with the win32con library to execute the mouse event in the event queue; set the window currently executing the mouse event to an impenetrable window style, and after the execution is completed, set the window to a penetrable style until all the master and slave windows are executed;

[0061] If the mouse event is a scrolling event, the device CPU usage and memory usage are obtained in real time. If the CPU usage is less than the first set threshold and the memory usage is less than the second set threshold, win32gui.SendMessage is used with win32con.WM_MOUSEWHEEL to execute the mouse event in the event queue; the window currently executing the mouse event is set to an impenetrable window style. After the execution is completed, the window is set to a penetrable style until all the master and slave windows are executed; otherwise, a delay time is set. If the scrolling events obtained within the delay time are all in the same direction and there is no click event or move event If there is a scroll event, all scroll events in the event queue corresponding to the delay time are obtained and merged into a scroll merge event; if there is a scroll event, click event or move event in the opposite direction within the delay time, all scroll events in the previous event queue are combined to obtain a scroll merge event; the master window and the slave window use win32gui.SendMessage with win32con.WM_MOUSEWHEEL to execute the scroll merge event, and set the window currently executing the scroll merge event to an impenetrable window style. After the execution is completed, the window is set to a penetrable style until all master windows and slave windows are executed.

[0062] Since the device introduced in the second embodiment of the present invention is a device used to implement the method of the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the device based on the method introduced in the first embodiment of the present invention, so it is not described here in detail. All devices used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.

[0063] Based on the same inventive concept, the present application provides an electronic device embodiment corresponding to the first embodiment, see the third embodiment for details.

[0064] Embodiment 3

[0065] This embodiment provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, any implementation method in the first embodiment can be implemented.

[0066] Since the electronic device introduced in this embodiment is a device used to implement the method in the first embodiment of the present application, based on the method introduced in the first embodiment of the present application, a person skilled in the art can understand the specific implementation of the electronic device of the present embodiment and its various variations, so how the electronic device implements the method in the embodiment of the present application is not described in detail here. As long as a person skilled in the art implements the device used by the method in the embodiment of the present application, it belongs to the scope of protection of the present application.

[0067] Based on the same inventive concept, the present application provides a storage medium corresponding to the first embodiment, see the fourth embodiment for details.

[0068] Embodiment 4

[0069] This embodiment provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, any implementation method in the first embodiment can be implemented.

[0070] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0071] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0072] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0073] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0074] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A multi-window stacking mouse synchronization method, used for a Windows synchronizer, wherein the Windows synchronizer is used for synchronizing a master control window and at least one slave control window; characterized in that: The steps include: Step 1: Arrange the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed below the master control window in sequence; Step 2: Use win32gui.SetWindowsHookEx to enable event monitoring and monitor mouse events; Step 3: Store the monitored mouse events into the event queue respectively, waiting for execution; Step 4: Set both the master window and the slave window to be transparent window styles, and execute the mouse events in the event queue; Set the window currently executing the mouse event to an impenetrable window style. After the execution is completed, set the window to a penetrable style; until all the master control windows and slave control windows are executed; Step 5: After all windows have been executed, both the master control window and the slave control window are set to be impenetrable window styles.

2. A multi-window stacking mouse synchronization method according to claim 1, characterized in that: The step 1 is specifically as follows: using the win32gui.ShowWindow and win32gui.SetWindowPos methods to arrange the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed under the master control window in sequence.

3. A multi-window stacking mouse synchronization method according to claim 1, characterized in that: The step 4 is specifically as follows: set the master window and the slave window to the transparent window style by using win32gui.SetWindowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPARENT and win32gui.SetLayeredWindowAttributes(hwnd,0,254,win32con.LWA_ALPHA) methods, and execute the mouse events in the event queue by using win32gui.SendMessage with win32con.W M_LBUTTONDOWN, win32con.WM_MOUSEMOVE or win32con.WM_MO USEWHEEL; set the window currently executing the mouse event to the impenetrable window style, and after the execution is completed, set the window to the transparent style until all the master windows and the slave windows are executed.

4. A multi-window stacking mouse synchronization method according to claim 1, characterized in that: The mouse events include: click events, move events and scroll events; the step 4 specifically includes: setting the master window and the slave window to a transparent window style by using win32gui.SetWindowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPARENT and win32gui.SetLayeredWindowAttributes(hwnd,0,254,win32con.LWA_ALPHA) methods; If the mouse event is a click event or a move event, use win32gui.SendMessage with the win32con library to execute the mouse event in the event queue; set the window currently executing the mouse event to an impenetrable window style, and after the execution is completed, set the window to a penetrable style until all the master and slave windows are executed; If the mouse event is a scrolling event, the device CPU usage and memory usage are obtained in real time. If the CPU usage is less than the first set threshold and the memory usage is less than the second set threshold, win32gui.SendMessage is used with win32con.WM_MOUSEWHEEL to execute the mouse event in the event queue; the window currently executing the mouse event is set to an impenetrable window style. After the execution is completed, the window is set to a penetrable style until all the master and slave windows are executed; otherwise, a delay time is set. If the scrolling events obtained within the delay time are all in the same direction and there is no click event or move event If there is a scroll event, all scroll events in the event queue corresponding to the delay time are obtained and merged into a scroll merge event; if there is a scroll event, click event or move event in the opposite direction within the delay time, all scroll events in the previous event queue are combined to obtain a scroll merge event; the master window and the slave window use win32gui.SendMessage with win32con.WM_MOUSEWHEEL to execute the scroll merge event, and set the window currently executing the scroll merge event to an impenetrable window style. After the execution is completed, the window is set to a penetrable style until all master windows and slave windows are executed.

5. A multi-window stacking mouse synchronization device, used for a Windows synchronizer, wherein the Windows synchronizer is used for synchronizing a master control window and at least one slave control window; characterized in that: Includes the following modules: A stacking window module arranges the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed below the master control window in sequence; Monitoring module, use win32gui.SetWindowsHookEx to start event monitoring and monitor mouse events; The storage module stores the monitored mouse events into the event queue respectively, waiting for execution; The execution module sets both the master control window and the slave control window to be transparent window styles, and executes the mouse events in the event queue; Set the window currently executing the mouse event to an impenetrable window style. After the execution is completed, set the window to a penetrable style; until all the master control windows and slave control windows are executed; The recovery module sets the master control window and the slave control window to an impenetrable window style after all windows have been executed.

6. A multi-window stacking mouse synchronization device according to claim 5, characterized in that: The stacking window module specifically uses win32gui.ShowWindow and win32gui.SetWindowPos methods to arrange the master control cabinet window and the slave control windows in a stacked manner, with the master control window being placed on the top layer and the slave control windows being placed under the master control window in sequence.

7. The multi-window stacking mouse synchronization device according to claim 5, characterized in that: The execution module is specifically as follows: the master control window and the slave control window are set to the penetrable window style by using win32gui.SetWindowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPARENT and win32gui.SetLayeredWindowAttributes(hwnd,0,254,win32con.LWA_ALPHA) methods; the mouse events in the execution event queue are executed by using win32gui.SendMessage with win32con.W M_LBUTTONDOWN, win32con.WM_MOUSEMOVE or win32con.WM_MO USEWHEEL; the window currently executing the mouse event is set to the impenetrable window style, and after the execution is completed, the window is set to the penetrable style until all the master control windows and the slave control windows are executed.

8. The multi-window stacking mouse synchronization device according to claim 5, characterized in that: The mouse events include: click events, move events and scroll events; the execution module specifically: set the master window and the slave window to transparent window styles using win32gui.SetWindowLong with win32con.GWL_EXSTYLE, win32con.WS_EX_TRANSPARENT and win32gui.SetLayeredWindowAttributes(hwnd,0,254,win32con.LWA_ALPHA); If the mouse event is a click event or a move event, use win32gui.SendMessage with the win32con library to execute the mouse event in the event queue; set the window currently executing the mouse event to an impenetrable window style, and after the execution is completed, set the window to a penetrable style until all the master and slave windows are executed; If the mouse event is a scrolling event, the device CPU usage and memory usage are obtained in real time. If the CPU usage is less than the first set threshold and the memory usage is less than the second set threshold, win32gui.SendMessage is used with win32con.WM_MOUSEWHEEL to execute the mouse event in the event queue; the window currently executing the mouse event is set to an impenetrable window style. After the execution is completed, the window is set to a penetrable style until all the master and slave windows are executed; otherwise, a delay time is set. If the scrolling events obtained within the delay time are all in the same direction and there is no click event or move event If there is a scroll event, all scroll events in the event queue corresponding to the delay time are obtained and merged into a scroll merge event; if there is a scroll event, click event or move event in the opposite direction within the delay time, all scroll events in the previous event queue are combined to obtain a scroll merge event; the master window and the slave window use win32gui.SendMessage with win32con.WM_MOUSEWHEEL to execute the scroll merge event, and set the window currently executing the scroll merge event to an impenetrable window style. After the execution is completed, the window is set to a penetrable style until all master windows and slave windows are executed.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 4 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images