Touchpad mistaken touch prevention method, terminal and storage medium
By identifying and not responding to the error touch event from the touchpad when the cursor disappears on the terminal UI interface, the error operation problem caused by the error touch after the cursor disappears is solved, and the user experience is improved.
Patent Information
- Application Number
- CN202311086594.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-25
- Publication Date
- 2025-02-25
AI Technical Summary
After the cursor on the terminal UI interface disappears, the user may accidentally touch the touchpad, resulting in misoperation, such as accidentally clicking the exit button, causing inconvenience to the user.
When the cursor is not displayed on the terminal UI interface, a touch event from the touchpad is received to determine whether the touch event is a false touch event. If so, the touch event does not respond.
It effectively avoids misoperation caused by accidentally touching the touchpad, improves the user experience, and prevents unnecessary operations caused by misoperation.
Smart Images

Figure CN119512418A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of terminal technology, and in particular to a touch panel accidental touch prevention method, a terminal and a storage medium. Background Art
[0002] In order to facilitate the user to operate the terminal, a keyboard including a touchpad may be provided to the terminal, such as a notebook having an integrated keyboard with a touchpad, or an external Bluetooth keyboard may be provided to a tablet computer, etc. When the user uses the terminal, the cursor may be controlled to move to or click any desired position on the terminal UI (User Interface) by touching the surface of the touchpad with a finger.
[0003] Taking a tablet computer as an example, when a user clicks on the tablet screen or types on the keyboard, the cursor disappears on the UI interface. If the user subsequently wants to touch the touchpad to confirm the position of the cursor, it may cause an accidental click, such as accidentally clicking the exit button, which is very annoying for the user.
[0004] Therefore, how to avoid misoperation caused by accidentally touching the touchpad after the cursor disappears from the UI interface has become a problem that needs to be solved urgently. Summary of the invention
[0005] The main purpose of the embodiments of the present invention is to provide a touch panel anti-mis-touch method, terminal and storage medium, aiming to solve the technical problem of how to avoid misoperation caused by mis-touch of the touch panel after the cursor disappears from the UI interface.
[0006] In a first aspect, an embodiment of the present invention provides a touch panel accidental touch prevention method, comprising:
[0007] When it is detected that the cursor is not displayed on the terminal UI interface, a touch event from the touch pad is received;
[0008] Determining whether the touch event is a false touch event;
[0009] If it is determined that the touch event is a false touch event, the touch event is not responded to.
[0010] In a second aspect, an embodiment of the present invention further provides a terminal, comprising a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection and communication between the processor and the memory, wherein when the computer program is executed by the processor, the steps of any one of the touch panel anti-mistouch methods provided in the specification of the present invention are implemented.
[0011] In a third aspect, an embodiment of the present invention further provides a storage medium for computer-readable storage, characterized in that the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of any touch panel anti-mistouch method provided in the specification of the present invention.
[0012] The embodiment of the present invention provides a touchpad anti-mistouch method, a terminal and a storage medium. The touchpad anti-mistouch method receives a touch event from a touchpad when it is detected that a cursor is not displayed on a terminal UI interface; determines whether the touch event is a mistouch event; and does not respond to the touch event when it is determined that the touch event is a mistouch event. The embodiment of the present invention identifies the touch event when it is detected that a cursor is not displayed on a terminal UI interface, and does not respond to the touch event when it is identified that the touch event is a mistouch event, which can effectively avoid the trouble caused by misoperation caused by mis-touching the touchpad, and improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0014] Figure 1 A schematic diagram of a flow chart of a touch panel accidental touch prevention method provided by an embodiment of the present invention;
[0015] Figure 2 A schematic diagram of the architecture of an anti-mistaken-touch system for a touch panel anti-mistaken-touch method provided in an embodiment of the present invention;
[0016] Figure 3 for Figure 1 A schematic diagram of the sub-steps of the touch panel accidental touch prevention method;
[0017] Figure 4 An example diagram of the workflow of the anti-mistaken-touch system involved in the touch panel anti-mistaken-touch method provided in an embodiment of the present invention;
[0018] Figure 5 A schematic block diagram of the structure of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0019] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0020] The flowcharts shown in the accompanying drawings are only examples and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may also be decomposed, combined or partially merged, so the actual execution order may change according to actual conditions.
[0021] It should be understood that the terms used in the present specification are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the present specification and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.
[0022] The embodiment of the present invention provides a touch panel anti-mis-touch method, device and storage medium. The touch panel anti-mis-touch method identifies a touch event when it is detected that the cursor is not displayed on the terminal UI interface, and does not respond to the touch event when it is identified that the touch event is a mis-touch event, which can effectively avoid the trouble caused by mis-operation caused by mis-touch of the touch panel, and improve the user experience.
[0023] Some embodiments of the present invention are described in detail below in conjunction with the accompanying drawings. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.
[0024] Please refer to Figure 1 , Figure 1 The present invention provides a flow chart of a touch panel anti-mis-touch method according to an embodiment of the present invention. The touch panel anti-mis-touch method can be implemented by terminals such as notebook computers, tablet computers, and PCs (Personal Computers).
[0025] like Figure 1 As shown, the touch panel mis-touch prevention method includes steps S101 to S103.
[0026] Step S101: receiving a touch event from a touch panel when detecting that no cursor is displayed on a terminal UI interface.
[0027] The touchpad anti-mistouch method can be applied to a terminal with an external Bluetooth keyboard or Bluetooth mouse with a touchpad, and can also be applied to a terminal with an integrated keyboard with a touchpad. Taking the scenario of a terminal with an external Bluetooth keyboard with a touchpad as an example, the technical solution provided by the embodiment of the invention is described.
[0028] When it is detected that the cursor is not displayed on the terminal UI interface, if the user performs a touch operation such as touching or clicking the touchpad, the terminal will receive a touch event from the touchpad through the Bluetooth communication channel.
[0029] Step S102: Determine whether the touch event is an accidental touch event.
[0030] Afterwards, in order to determine whether the touch event from the touchpad is for the user to confirm the position of the cursor on the terminal UI interface or the user intentionally clicks a control on the terminal UI interface, it is necessary to determine whether the touch event from the touchpad is a false touch event.
[0031] Step S103: If it is determined that the touch event is an accidental touch event, do not respond to the touch event.
[0032] If it is determined that the touch event from the touchpad is a false touch event, the touch event will not be responded to. Specifically, not responding to the touch event includes two situations. One is that the cursor can be displayed only on the UI interface of the terminal, but the click operation is not responded to at the position indicated by the cursor, effectively avoiding false clicks. In other words, the touch event means that the user is just confirming the position of the cursor on the UI interface of the terminal, rather than the user intentionally clicking a certain control on the UI interface of the terminal. The other is not to display the cursor on the UI interface of the terminal throughout the process, completely avoiding false clicks, that is, the touch event means that the user accidentally touched the touchpad.
[0033] The touchpad anti-mis-touch method provided in the above embodiment receives a touch event from the touchpad when it is detected that the terminal UI interface does not display a cursor; determines whether the touch event is a mis-touch event; and does not respond to the touch event when it is determined that the touch event is a mis-touch event. The embodiment of the present invention identifies the touch event when it is detected that the terminal UI interface does not display a cursor, and does not respond to the touch event when it is identified that the touch event is a mis-touch event, which can effectively avoid the trouble caused by mis-operation caused by mis-touching the touchpad, and improve the user experience.
[0034] In some embodiments, in order to facilitate the control of accidental touch prevention, an accidental touch prevention system can be deployed in the terminal. Figure 2 , Figure 2 This is a schematic diagram of the architecture of the anti-accidental touch system, which mainly includes functional modules such as the framework Input module, Bluetooth protocol stack and Bluetooth driver module.
[0035] The framework Input module is used to monitor whether the terminal UI interface displays a cursor. Specifically, the framework Input module includes a specific interface, through which it can be determined whether the cursor disappears or appears on the terminal UI interface.
[0036] The framework Input module is also used to notify the Bluetooth protocol stack of the cursor monitoring result. For example, when it is detected that the terminal UI interface does not display the cursor, the Bluetooth protocol stack is notified using the cursor invisible mark; when it is detected that the terminal UI interface displays the cursor, the Bluetooth protocol stack is notified using the cursor visible mark.
[0037] The framework Input module is also used to receive the Input data reported by the Bluetooth driver module, so as to display the cursor on the terminal UI interface based on the Input data and control whether to respond to click operations.
[0038] The Bluetooth protocol stack is used to receive the cursor monitoring result, and when the cursor monitoring result is that the terminal UI interface does not display the cursor (for example, an indicator that the cursor is invisible is received), call the preset filtering algorithm to determine whether the touch event from the touchpad is a false touch event through the preset filtering algorithm. It is understandable that when the cursor monitoring result is that the terminal UI interface displays the cursor, the Bluetooth protocol stack does not call the preset filtering algorithm.
[0039] The Bluetooth protocol stack is also used to write only the first message corresponding to the touch event into the Bluetooth driver module, or discard all messages corresponding to the touch event when it is determined that the touch event from the touch pad is a false touch event; and is also used to write the specified message corresponding to the touch event into the Bluetooth driver module when it is determined that the touch event from the touch pad is not a false touch event.
[0040] The Bluetooth driver module is used to convert the messages written by the Bluetooth protocol stack into Input data and report them to the framework Input module.
[0041] The following describes in detail the specific process of the terminal implementing the technical solution provided by the embodiment of the present invention through the above-mentioned functional modules of the anti-mistouch system.
[0042] In some embodiments, a touch event corresponds to a plurality of first messages and a second message, see Figure 3 , step S102, includes sub-steps S1021 to S1023.
[0043] Sub-step S1021: when receiving the second message, determining the number or duration of receiving the first message before receiving the second message;
[0044] Sub-step S1022: when the number is less than the first preset threshold, or when the duration is less than the second preset threshold, determining that the touch event is an error touch event;
[0045] Sub-step S1023: When the number is greater than or equal to the first preset threshold, or when the duration is greater than or equal to the second preset threshold, determine that the touch event is not a false touch event.
[0046] The terminal's framework Input module monitors whether the terminal UI interface displays a cursor. If it is detected that the terminal UI interface does not display a cursor, if the user performs touch operations such as touching or clicking the touchpad, the Bluetooth keyboard will send a touch event to the terminal's Bluetooth protocol stack through the Bluetooth communication channel.
[0047] Among them, a complete touch event is composed of the HID (Human Interface Device) message of the touchpad, specifically composed of multiple Down messages and one Up message. The user's finger touches the touchpad to generate a Down message, and the user's finger is lifted from the touchpad to generate an Up message. The Down message is defined as the first message, and the Up message is defined as the second message. It should be noted that the second message is the last message corresponding to a touch event. The longer the user touches the touchpad, the more messages the Bluetooth keyboard sends to the Bluetooth protocol stack. Usually, the Bluetooth keyboard sends a message to the Bluetooth protocol stack of the terminal every 11ms.
[0048] The Bluetooth protocol stack of the terminal first continuously receives multiple first messages and finally receives the second message. When the second message is received, the Bluetooth protocol stack calls a preset filtering algorithm to determine whether the touch event from the touch panel is a false touch event based on the preset filtering algorithm and the reception of the first message.
[0049] Specifically, the Bluetooth protocol stack determines the number or duration of the first message received before receiving the second message; then compares the number of the first message received with the first preset threshold, or compares the duration of the first message received with the second preset threshold; when the number of the first message received is less than the first preset threshold, or the duration of the first message received is less than the second preset threshold, it can be determined that the touch event from the touchpad is a false touch event, and the user's intention of touch operation on the touchpad can be identified into two situations. One situation is that the user just wants to confirm the position of the cursor on the terminal UI interface, rather than the user intentionally clicking a control on the terminal UI interface, and the other situation is that the user accidentally touches the touchpad.
[0050] The first preset threshold and the second preset threshold can be flexibly set according to actual conditions. For example, taking the first preset threshold as 20 as an example, when the Bluetooth protocol stack receives an Up message, it determines the number of Down messages received before receiving the Up message. When the number of Down messages received is less than 20, it can be determined that the touch event from the touchpad is a false touch event; or taking the second preset threshold as 0.22s as an example, when the Bluetooth protocol stack receives an Up message, it determines the duration of receiving the Down message before receiving the Up message. When the duration of receiving the Down message is less than 0.22s, it can be determined that the touch event from the touchpad is a false touch event.
[0051] After the Bluetooth protocol stack of the terminal compares the number of received first messages with the first preset threshold, or compares the duration of receiving the first message with the second preset threshold, if the number of received first messages is greater than or equal to the first preset threshold, or the duration of receiving the first message is greater than or equal to the second preset threshold, that is, after the number of received first messages is greater than or equal to the first preset threshold or the duration of receiving the first message is greater than or equal to the second preset threshold, the second message is received. It can be determined that the touch event from the touchpad is not a false touch event, and the user's intention of touch operation on the touchpad can be identified as the user needs a certain amount of time to first confirm the position of the cursor on the terminal UI interface, and then intentionally move the cursor to click a desired control on the terminal UI interface.
[0052] Exemplarily, for example, if the Bluetooth protocol stack receives an Up message after receiving 25 Down messages, and the number of received Down messages is greater than the first preset threshold of 20, it can be determined that the touch event from the touchpad is not a false touch event. Or if the Up message is received after receiving a Down message of 0.4s, and the duration of receiving the Down message is greater than the second preset threshold of 0.22s, it can be determined that the touch event from the touchpad is not a false touch event. It can be understood that the effect of the first 20 Down messages can be identified as the user needing a certain amount of time to confirm the position of the cursor on the terminal UI interface, and the effect of the last 5 Down messages and Up messages received can be identified as the user intentionally moving the cursor to click on a desired control on the terminal UI interface.
[0053] In some embodiments, in order to improve convenience, a counter or a timer may be pre-set, and the number of received first messages may be counted by the counter, or the duration of receiving the first message may be monitored by the timer.
[0054] In the above manner, when the Bluetooth protocol stack of the terminal receives the second message, it can efficiently and accurately identify whether the touch event from the touch panel is a false touch event based on the reception status of the first message before receiving the second message according to the preset filtering algorithm.
[0055] In some embodiments, before determining whether the touch event is a false touch event, a displayable but invalid label is marked for the first received first message.
[0056] That is, when it is detected that the cursor is not displayed on the UI interface of the terminal, before determining whether the touch event from the touchpad is an accidental touch event, the Bluetooth protocol stack of the terminal receives the first first message, and marks the received first first message with a displayable but invalid tag. In this way, the role of the received first first message is given as displayable but invalid coordinates, and the terminal can display the cursor on the UI interface based on the first message, but will not respond to the click operation.
[0057] In some embodiments, after determining that the touch event is a false touch event, all received first messages and second messages are marked with displayable but invalid labels.
[0058] The Bluetooth protocol stack of the terminal may also mark all received first and second messages with displayable but invalid tags after determining that the touch event from the touch panel is an accidental touch event. In this way, the role of all received first and second messages is given as displayable but invalid.
[0059] In some embodiments, after determining that the touch event is an accidental touch event, the first received first message and the displayable but invalid label are reported, and the remaining first messages and second messages are discarded.
[0060] After determining that the touch event from the touchpad is an accidental touch event, the terminal's Bluetooth protocol stack can only report the first received first message and its displayable but invalid label to the framework Input module, and discard the remaining first messages, as well as the second message, to achieve the effect of filtering invalid messages based on a preset filtering algorithm. Specifically, the Bluetooth protocol stack only writes the first first message to the Bluetooth driver module, thereby converting it into Input data, and then reporting it to the framework Input module.
[0061] In some embodiments, not responding to a touch event may be displaying a cursor on a UI interface according to the first message and a displayable but invalid label, but not responding to a click operation at the position indicated by the cursor.
[0062] Thus, the framework Input module receives the Input data corresponding to the first first message, and based on the Input data and the displayable but invalid label of the first message, only displays the cursor at the position indicated by the Input data on the UI interface, but does not respond to click operations at this position.
[0063] In this way, by means of label marking, the cursor can be displayed only on the UI interface of the terminal based on the first received message and its displayable but invalid label to avoid accidental clicks, thereby effectively avoiding the troublesome problems caused by erroneous operations caused by accidentally touching the touchpad.
[0064] In some embodiments, after determining that the touch event is not a false touch event, the first message received after the number of receptions exceeds a first preset threshold or the reception duration exceeds a second preset threshold is determined from all the received first messages; the determined first message and the second message are reported.
[0065] After determining that the touch event from the touchpad is not a false touch event, the Bluetooth protocol stack of the terminal determines, from all the received first messages, the first message received after the number of receptions exceeds the first preset threshold, or the first message received after the reception duration exceeds the second preset threshold; then, the determined first message and the second message are written one by one in sequence into the Bluetooth driver module of the terminal, converted into corresponding Input data, and then reported to the framework Input module of the terminal.
[0066] It is understandable that, in order to save memory space, first messages received whose number is equal to the first preset threshold or first messages received within the second preset threshold are discarded.
[0067] For example, when the Bluetooth protocol stack receives an Up message, if it determines that the number of Down messages received before the Up message is 25, which is greater than the first preset threshold of 20, the last 5 Down messages received and the Up message are reported; or if it determines that the duration of receiving the Down message before the Up message is 0.3s, which is greater than the second preset threshold of 0.22s, the Down message and the Up message received after more than 0.22s are reported. The first 20 Down messages received or the Down message received within 0.22s are discarded.
[0068] In some embodiments, after the determined first message and the second message are reported, a touch event can be responded to according to the reported first message and the second message.
[0069] The framework Input module of the terminal receives the Input data corresponding to the first message and the second message reported by the Bluetooth protocol stack, and responds to the touch event from the touch panel based on the Input data.
[0070] In some embodiments, responding to a touch event may be displaying a cursor on a UI interface and responding to a click operation at the position indicated by the cursor.
[0071] The terminal's framework Input module displays a cursor on the UI interface and responds to click operations at the location indicated by the cursor to complete the response to touch events from the touchpad.
[0072] In this way, the framework Input module, Bluetooth protocol stack and Bluetooth driver module of the anti-mistouch system collaborate to achieve extremely efficient and reliable touchpad anti-mistouch control, solving the troublesome problems caused by misoperation caused by accidentally touching the touchpad and improving user experience.
[0073] In some embodiments, after determining that the touch event is an accidental touch event, all received first messages and second messages may be discarded so as not to display a cursor on the UI interface.
[0074] After determining that the touch event is an accidental touch event, the Bluetooth protocol stack of the terminal can discard all the received first messages and second messages, that is, do not report the message corresponding to the touch event to the framework Input module. In this way, the framework Input module does not display the cursor on the UI interface of the terminal throughout the process, thereby avoiding accidental clicks.
[0075] In some embodiments, after determining that the touch event is an accidental touch event, the Bluetooth protocol stack of the terminal may not label the multiple first messages and second messages corresponding to the touch event, but may only write the first first message received into the Bluetooth driver module, convert it into the Input data corresponding to the first first message, report it to the framework Input module, and discard the remaining first messages and second messages. In this way, the framework Input module of the terminal receives the Input data corresponding to the first first message, and based on the Input data corresponding to the first first message, only displays the cursor on the UI interface of the terminal, and does not respond to click operations at the position indicated by the cursor.
[0076] In this way, without using a label marking method, the cursor can be displayed only on the UI interface of the terminal based on the first received first message without causing an accidental click, and the troublesome problem caused by an erroneous operation caused by accidentally touching the touchpad can also be effectively avoided.
[0077] For a better understanding of the above embodiments, please refer to Figure 4 , Figure 4 To illustrate the workflow of the system to prevent accidental touches, the following is a diagram of the system workflow. Figure 4, introduces in more detail the various functional modules of the anti-accidental touch system, and the process of collaboratively realizing anti-accidental touch control.
[0078] The framework Input module monitors the cursor display status of the terminal UI interface, and if it is detected that the cursor is not displayed on the terminal UI interface, it notifies the Bluetooth protocol stack that the cursor is not displayed on the terminal UI interface.
[0079] When the cursor is not displayed on the terminal UI interface, the Bluetooth protocol stack receives a touch event from the touchpad, that is, it first continuously receives multiple Down messages from the touchpad, and finally receives an Up message from the touchpad; when the Up message is received, the preset filtering algorithm is called to determine whether the touch event is an accidental touch event based on the preset filtering algorithm and the reception of the Down message. Specifically, it can be determined whether the number of Down messages received is less than the preset number threshold when the Up message is received.
[0080] If the number of received Down messages is less than the preset number threshold, the touch event is determined to be an accidental touch event. The Bluetooth protocol stack can write the first received Down message to the Bluetooth driver module and discard the remaining Down messages and Up messages. The Bluetooth driver module writes the first received Down message to the Bluetooth driver module, and the Bluetooth driver module converts the first Down message into the corresponding Input data and reports it to the framework Input module. The framework Input module only displays the cursor on the terminal UI interface based on the Input data corresponding to the first Down message, effectively avoiding accidental clicks.
[0081] If the number of received Down messages is less than the preset threshold, the touch event is determined to be a false touch event. The Bluetooth protocol stack can also discard all received Down messages and Up messages, that is, not report the message corresponding to the touch event to the framework Input module. In this way, the framework Input module does not display the cursor on the UI interface of the terminal throughout the process, completely avoiding false clicks.
[0082] If the number of received Down messages is greater than the preset threshold, it can be determined that the touch event is not a false touch event, and the Down messages received after the number of received messages exceeds the preset threshold, as well as the Up messages, are written normally into the Bluetooth driver module, and the remaining Down messages are discarded. The Bluetooth driver module converts the written Down messages and Up messages into corresponding Input data and reports them to the framework Input module. The framework Input module displays the cursor on the terminal UI interface according to the Input data corresponding to the written Down messages and Up messages, and responds to the click operation at the position indicated by the cursor, completing the response to the touch event from the touchpad.
[0083] In this way, the Bluetooth protocol stack implements extremely efficient and reliable touchpad false touch identification based on the reception of the message corresponding to the touch event, and collaborates with the framework Input module and the Bluetooth protocol stack to achieve precise control over whether to respond to touch events from the touchpad. This can effectively avoid the troublesome problems caused by misoperation caused by mistouching the touchpad, and improve the user experience.
[0084] See also Figure 5 , Figure 5 A schematic block diagram of the structure of a terminal provided by an embodiment of the present invention.
[0085] like Figure 5 As shown, the terminal 300 includes a processor 301 and a memory 302, and the processor 301 and the memory 302 are connected via a bus 303, such as an I2C (Inter-integrated Circuit) bus.
[0086] Specifically, the processor 301 is used to provide computing and control capabilities to support the operation of the entire terminal. The processor 301 can be a central processing unit (CPU), and the processor 301 can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.
[0087] Specifically, the memory 302 may be a Flash chip, a read-only memory (ROM) disk, an optical disk, a USB flash drive, or a mobile hard disk.
[0088] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a partial structure related to the embodiment of the present invention, and does not constitute a limitation on the terminal to which the embodiment of the present invention is applied. The specific server may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0089] The processor is used to run a computer program stored in the memory, and implement any one of the touch panel mis-touch prevention methods provided by the embodiments of the present invention when executing the computer program.
[0090] In one embodiment, the processor is used to run a computer program stored in the memory, and when executing the computer, when detecting that the cursor is not displayed on the terminal UI interface, receive a touch event from the touch panel;
[0091] Determining whether the touch event is a false touch event;
[0092] If it is determined that the touch event is a false touch event, the touch event is not responded to.
[0093] In one embodiment, the touch event corresponds to a plurality of first messages and one second message; when the processor implements the step of determining whether the touch event is a false touch event, the processor is configured to implement:
[0094] When the second message is received, determine the number or duration of receiving the first message before receiving the second message;
[0095] When the number is less than a first preset threshold, or when the duration is less than a second preset threshold, determining that the touch event is a false touch event;
[0096] When the number is greater than or equal to the first preset threshold, or when the duration is greater than or equal to the second preset threshold, it is determined that the touch event is not a false touch event.
[0097] In one embodiment, before implementing the step of determining whether the touch event is a false touch event, the processor is configured to implement:
[0098] The first received message is marked with a displayable but invalid label.
[0099] In one embodiment, after determining that the touch event is a false touch event, the processor is configured to implement:
[0100] All received first messages and second messages are marked with displayable but invalid tags.
[0101] In one embodiment, after implementing the step of determining that the touch event is a false touch event, the processor is further configured to implement:
[0102] The first first message and the displayable but invalid label are reported, and the remaining first messages and the second messages are discarded.
[0103] In one embodiment, when implementing the not responding to the touch event, the processor is used to implement:
[0104] According to the first first message and the displayable but invalid label, a cursor is displayed on the UI interface, but a click operation is not responded to at the position indicated by the cursor.
[0105] In one embodiment, after implementing the step of determining that the touch event is not a false touch event, the processor is further configured to implement:
[0106] From all the first messages received, determine the first messages received after the number of received messages exceeds the first preset threshold or the reception duration exceeds the second preset threshold;
[0107] The determined first message and the second message are reported.
[0108] In one embodiment, after implementing the reporting of the determined first message and the second message, the processor is configured to implement:
[0109] Respond to the touch event according to the reported first message and the second message.
[0110] In one embodiment, when implementing the responding to the touch event, the processor is used to implement:
[0111] A cursor is displayed on the UI interface, and a click operation is responded to at the position indicated by the cursor.
[0112] In one embodiment, after implementing the step of determining that the touch event is a false touch event, the processor is configured to implement:
[0113] All received first messages and second messages are discarded so as not to display a cursor on the UI interface.
[0114] It should be noted that those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the terminal described above can refer to the corresponding process in the aforementioned touch panel anti-mistouch method embodiment, which will not be repeated here.
[0115] An embodiment of the present invention further provides a storage medium for computer-readable storage, wherein the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of any touch panel mis-touch prevention method provided in the description of the embodiment of the present invention.
[0116] The storage medium may be an internal storage unit of the terminal described in the foregoing embodiment, such as a hard disk or memory of the terminal. The storage medium may also be an external storage device of the terminal, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the terminal.
[0117] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In a hardware embodiment, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.
[0118] It should be understood that the term "and / or" used in the present specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, including these combinations. It should be noted that, in this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "including a..." does not exclude the presence of other identical elements in the process, method, article or system including the element.
[0119] The serial numbers of the embodiments of the present invention are only for description and do not represent the advantages and disadvantages of the embodiments. The above description is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.
Claims
1. A method for preventing accidental touches on a touch panel, characterized in that: include: When it is detected that the cursor is not displayed on the terminal UI interface, a touch event from the touch pad is received; Determining whether the touch event is a false touch event; If it is determined that the touch event is a false touch event, the touch event is not responded to.
2. The touch panel anti-mis-touch method according to claim 1, characterized in that: The touch event corresponds to a plurality of first messages and one second message; The determining whether the touch event is a false touch event includes: When the second message is received, determine the number or duration of receiving the first message before receiving the second message; When the number is less than a first preset threshold, or when the duration is less than a second preset threshold, determining that the touch event is a false touch event; When the number is greater than or equal to the first preset threshold, or when the duration is greater than or equal to the second preset threshold, it is determined that the touch event is not a false touch event.
3. The touch panel anti-mis-touch method according to claim 2, characterized in that: Before determining whether the touch event is a false touch event, the method includes: The first received message is marked with a displayable but invalid label.
4. The touch panel accidental touch prevention method according to claim 2, characterized in that: After determining that the touch event is a false touch event, the method includes: All received first messages and second messages are marked with displayable but invalid tags.
5. The touch panel accidental touch prevention method according to claim 3 or 4, characterized in that: After determining that the touch event is an accidental touch event, the method further includes: The first first message and the displayable but invalid label are reported, and the remaining first messages and the second messages are discarded.
6. The touch panel accidental touch prevention method according to claim 5, characterized in that: The not responding to the touch event includes: According to the first first message and the displayable but invalid label, a cursor is displayed on the UI interface, but a click operation is not responded to at the position indicated by the cursor.
7. The touch panel accidental touch prevention method according to claim 2, characterized in that: After determining that the touch event is not an accidental touch event, the method further includes: From all the first messages received, determine the first messages received after the number of received messages exceeds the first preset threshold or the reception duration exceeds the second preset threshold; The determined first message and the second message are reported.
8. The touch panel accidental touch prevention method according to claim 7, characterized in that: After reporting the determined first message and the second message, the method further comprises: Respond to the touch event according to the reported first message and the second message.
9. The touch panel accidental touch prevention method according to claim 8, characterized in that: The responding to the touch event includes: A cursor is displayed on the UI interface, and a click operation is responded to at the position indicated by the cursor.
10. The touch panel accidental touch prevention method according to claim 2, characterized in that: After determining that the touch event is a false touch event, the method further includes: All received first messages and second messages are discarded so as not to display a cursor on the UI interface.
11. A terminal, characterized in that: The terminal includes a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection and communication between the processor and the memory, wherein when the computer program is executed by the processor, the steps of the touch panel mis-touch prevention method as claimed in any one of claims 1 to 10 are realized.
12. A storage medium for computer-readable storage, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the touch panel mis-touch prevention method according to any one of claims 1 to 10.