Touch data processing method, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses a touch data processing method, electronic equipment and a storage medium. On the basis of the touch data processing method in the embodiment of the invention, under the condition that the existing native touch drive realizes corresponding quick start and input, the first touch drive is set corresponding to the annotation application, the annotation application sends the interception instruction to the first touch drive according to the application running state, and the annotation application is triggered to possibly trigger other applications from the aspect of configuration. However, the interception and judgment of the touch data required by corresponding triggering are not available at present; under the condition that the current touch data obtained through interception meets the triggering condition for quickly starting the annotation application, the first touch drive stops interception, and the touch data can be directly sent to the annotation application to be processed and responded; under the condition that the intercepted current touch data does not meet the triggering condition, packaging and forwarding can be carried out according to the first equipment identifier, a system layer can carry out accurate processing according to a basic processing flow, and meanwhile it is guaranteed that the whole interaction process is accurately completed.

Description

Technical Field

[0001] This application relates to the field of touch technology, and more particularly to touch data processing methods, electronic devices, and storage media. Background Technology

[0002] With the rapid development of intelligent technology, people are encountering a wider variety of electronic products in their daily lives, and they are increasingly inclined to have a better human-computer interaction experience, leading to a proliferation of interactive electronic products.

[0003] To improve interaction response speed and enhance the user experience, a new interaction method has emerged in interactive electronic products. This method can directly determine the user's operational needs based on their actions even before the user has opened the corresponding application, and then quickly respond accordingly. For example, a user can simply pick up a pen and write a few strokes on the interactive tablet to launch the corresponding writing application and draw the handwriting.

[0004] The inventors' research into existing fast-response solutions revealed that when an electronic device has multiple fast-response interaction methods, it is impossible to accurately launch the application that requires the response. Summary of the Invention

[0005] This invention provides a touch data processing method, an electronic device, and a storage medium to solve the technical problem that when an electronic device has multiple fast-response interaction methods, it is impossible to accurately launch the application that needs to respond.

[0006] In a first aspect, embodiments of this application provide a touch data processing method for an electronic device. The electronic device includes a touch module, and the driving layer of the electronic device is equipped with a native touch driver and a first touch driver corresponding to the touch module. The touch data processing method includes:

[0007] Upon receiving an interception command from the annotation application, the first touch driver intercepts touch data in the driver layer according to a preset device identifier list. The device identifier list records at least the touch device identifier, which is the device identifier presented by the touch module through the native touch driver.

[0008] The first touch driver determines the trigger conditions based on the intercepted current touch data according to the preset annotation trigger rules;

[0009] When the current touch data meets the triggering conditions, the first touch driver wakes up the annotation window corresponding to the annotation application, sends the current touch data to the annotation application for response, and stops intercepting the touch data, allowing the operating system to distribute the touch data.

[0010] If the current touch data does not meet the triggering conditions, the first touch driver encapsulates and forwards the current touch data based on the first device identifier, which is the simulated device identifier corresponding to the first touch driver.

[0011] As described above, with the existing native touch driver enabling quick launch and input, a first touch driver is set up for the corresponding annotation application. The annotation application sends an interception command to the first touch driver based on its running status, triggering the interception and judgment of touch data that may trigger other applications according to the configuration, but for which there is currently no corresponding trigger. If the intercepted current touch data meets the triggering conditions for quickly launching the annotation application, it indicates that the current touch data itself is an operation on the annotation application, and the first touch driver can stop intercepting. The touch data output by the native touch driver will be directly sent to the annotation application for processing and response. If the intercepted current touch data does not meet the triggering conditions, the current touch data can be encapsulated according to the corresponding first device identifier and forwarded. The system layer can process it accurately according to the basic processing flow, while also preventing the first touch driver from repeatedly intercepting touch data, ensuring the accurate completion of the entire interaction process.

[0012] The touch data processing method also includes:

[0013] If the first touch driver does not receive an interception command from the annotation application, it notifies the native touch driver to encapsulate and forward the touch data detected by the touch module based on the native device identifier, so that the document presentation application can implement the annotation function when it receives the touch data of writing operation encapsulated based on the native device identifier in the document presentation state.

[0014] As described above, when the first touch driver does not receive the interception command sent by the annotation application, the native touch driver encapsulates the touch data according to the native device identifier and forwards it. The document presentation application can obtain the touch data generated by the writing operation encapsulated by the native touch driver in the document presentation state, and can also realize pen writing in the document presentation state, ensuring that various applications with annotation needs can accurately trigger pen writing in their respective application scenarios.

[0015] The equipment identifiers recorded in the equipment identifier list are confirmed through the following steps:

[0016] The first touch driver reads the list of human-computer interaction devices and identifies the device identifier corresponding to the touch peripheral from the list.

[0017] As described above, the first touch driver reads the list of human-computer interaction devices and directly identifies the device identifier corresponding to the touch peripheral. It can adapt to the operating needs of the specific installed electronic device, be flexibly configured, and avoid unnecessary blocking settings.

[0018] The first touch driver reads the list of human-computer interaction devices and identifies the device identifier corresponding to the touch peripheral from the list, including:

[0019] The first touch driver runs when the device is powered on and reads the list of human-computer interaction devices, identifying the device identifier corresponding to the touch peripheral from the list.

[0020] As mentioned above, the first touch driver runs every time the device is powered on and reads the list of human-computer interaction devices to confirm the device identification list, enabling targeted adjustments when the software installation or interaction settings of the electronic device change.

[0021] The annotation application includes an initial state and a display state. The annotation application runs and enters the initial state when the computer starts up, and the annotation window is not visible in the initial state; the elements in the annotation window are visible in the display state.

[0022] The above describes how, for interactive flat panels and other electronic devices with high demand for handwriting input, commonly used annotation applications for handwriting input will run when the device is powered on, and the interactive flat panel will monitor the operation of applications so as to accurately and flexibly launch other applications or annotation applications quickly based on touch data according to actual operating needs.

[0023] The interception command is sent to the first touch driver when the annotation application detects in its initial state that the currently displayed application window is not the document presentation application window in the document presentation state.

[0024] As mentioned above, considering that document presentation applications typically display the document pages in full-screen mode, page by page, based on an existing edited document page, and that there is a need to annotate and supplement the full-screen document page by hand during document presentation mode, if the currently displayed application window is not the document presentation application window in document presentation mode, then for possible writing operations, it can be assumed that no other application besides the annotation application has an interactive design that implements handwriting. In this case, the first touch driver should be activated to intercept touch data so as to quickly display the annotation window and input handwriting according to the user's operation.

[0025] Among them, the first touch driver, after encapsulating and forwarding the current touch data based on the first device identifier when the current touch data does not meet the triggering conditions, also includes:

[0026] When the annotation application detects that the currently displayed application window is the document presentation application window in document presentation mode, it sends a stop interception command to the first touch driver so that the native touch driver encapsulates and forwards the touch data detected by the touch module based on the native device identifier, so that the document presentation application can implement the annotation function when it receives the touch data of writing operation encapsulated based on the native device identifier in document presentation mode.

[0027] As mentioned above, during the operation of the annotation application, it is detected that the currently displayed application window is the document presentation application window in document presentation mode. That is, when the document presentation application is launched and enters document presentation mode, the user's current operation is usually centered on the content displayed by the document presentation application. The user adds annotations and supplementary explanations to the full-screen document page displayed by the document presentation application in a handwritten manner. The annotation function of the document presentation application itself responds accordingly. Moreover, the annotation function of the document presentation application usually has the ability to quickly launch and add handwriting based on touch data. At this time, the first touch driver is instructed to stop intercepting touch data so that the native touch driver can only be responded to by the document presentation application for touch data encapsulated based on the native device identifier. The first touch driver stopping the interception can avoid interfering with the response of the document presentation application.

[0028] Among them, after the annotation application detects that the currently displayed application window is the document presentation application window in document presentation mode, it sends a stop interception command to the first touch driver, and then includes:

[0029] The annotation application enters its initial state.

[0030] As described above, the annotation application returns to its initial state, ensuring the normal display of the document presentation application window. At the same time, it begins to monitor changes in the corresponding window during application operation, responding to user writing operations by intercepting and displaying the annotation window as needed.

[0031] The annotation triggering rules include the movement trajectory corresponding to the touch data, the touch size, and / or the judgment conditions corresponding to the touch medium.

[0032] As described above, by using various operation information confirmed by touch data, the touch data generated by the writing operation can be quickly confirmed, and the annotation operation can be triggered accordingly.

[0033] Secondly, embodiments of this application provide an electronic device, which includes:

[0034] One or more processors;

[0035] Memory, used to store one or more computer programs;

[0036] When one or more computer programs are executed by one or more processors, an electronic device enables the touch data processing method as described in the first aspect.

[0037] Thirdly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the touch data processing method as described in the first aspect.

[0038] The electronic devices and computer-readable storage media of the second and third aspects can be used to perform the touch data processing method provided in any of the above embodiments, and have corresponding functions and beneficial effects. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 A flowchart of a touch data processing method provided in this application embodiment;

[0041] Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings. It is to be understood that the specific embodiments described herein are for illustrative purposes only and not for limiting the invention. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the drawings, not all of the structures.

[0043] It should be noted that, due to space limitations, this application specification does not exhaustively list all possible implementation methods. Those skilled in the art should be able to conceive after reading this application specification that, as long as the technical features do not contradict each other, any combination of technical features can constitute an optional implementation method.

[0044] The embodiments are described in detail below.

[0045] In electronic devices, rapid application launch can be achieved by intercepting and judging touch data at the driver layer. For example, an annotation application sends interception information to the corresponding touch driver in the driver layer. The touch driver, based on the interception information, intercepts the touch data and responds or distributes it based on the writing operation. Distribution refers to the process where, when the touch data does not meet the general requirements of the writing operation, the intercepted touch data is encapsulated according to a simulated device identifier and forwarded, ensuring that the touch data can be provided to other applications to achieve other user operation goals.

[0046] The inventors, through comprehensive research on existing fast-launch and response designs, discovered that when multiple applications implement fast-launch and response interactions, each application intercepts and encapsulates and forwards touch data at the driver layer using a corresponding simulated device identifier, specifically according to the priority relationships between applications. This mechanism leads to a situation where, for a given touch data, the highest-priority application on the device receives the data but does not need to launch or respond; conversely, the second application, with a lower priority, needs to launch and respond. However, because touch data is distributed according to application priority during actual processing, the touch driver encapsulates the touch data and forwards it to the first application. This results in touch data failing to reach the second application, thus preventing the second application from launching. This presents a technical problem where, when an electronic device has multiple fast-response interaction designs, the application requiring a response cannot be accurately launched.

[0047] To address the aforementioned technical issues, this application proposes a touch data processing method. In the case of existing native touch drivers enabling quick launch and input, a first touch driver is set up for the corresponding annotation application. The annotation application sends an interception command to the first touch driver based on its running state, triggering the interception and judgment of touch data that may trigger other applications according to its configuration, but for which there is currently no corresponding trigger. If the intercepted current touch data meets the triggering conditions for quickly launching the annotation application, it indicates that the current touch data itself is an operation on the annotation application, and the first touch driver can stop intercepting. The touch data output by the native touch driver will be directly sent to the annotation application for processing and response. If the intercepted current touch data does not meet the triggering conditions, the current touch data can be encapsulated and forwarded according to the corresponding first device identifier. The system layer can then process it accurately according to the basic processing flow, without causing the first touch driver to repeatedly intercept touch data, ensuring the accurate completion of the entire interaction process.

[0048] Figure 1 This is a flowchart of a touch data processing method provided in an embodiment of this application, such as... Figure 1As shown, the touch data processing method includes, but is not limited to, steps S110-S140. The touch data processing method provided in this application embodiment is used in an electronic device. The electronic device includes a touch module, and the driving layer of the electronic device is equipped with a native touch driver and a first touch driver corresponding to the touch module. Specifically, the touch module can be a capacitive touch module, a resistive touch module, an inductive touch module, an infrared touch frame, etc.

[0049] like Figure 1 As shown, the touch data processing method includes:

[0050] Step S110: When the first touch driver receives the interception instruction sent by the annotation application, it intercepts the touch data of the driver layer according to the preset device identifier list. The device identifier list records at least the touch device identifier, which is the device identifier presented by the touch module through the native touch driver.

[0051] In this embodiment, a hardware device may correspond to different applications with different drivers, and each driver has its own underlying processing logic designed for the application. Each driver ultimately presents itself as a different piece of hardware to the system layer, which may include one or more simulated hardware devices with different device identifiers. Specifically, in this embodiment, the device identifier presented by the touch module through the basic system driver (i.e., the native touch driver) is defined as the native device identifier.

[0052] This application targets electronic devices, such as the annotation applications commonly found on interactive whiteboards, by setting up a first touch driver and configuring a device identifier list to achieve comprehensive interception of touch data provided by each driver.

[0053] The annotation application includes an initial state and a display state. The annotation application runs and enters the initial state upon startup, during which the annotation window is invisible. Elements within the annotation window are visible in the display state. For interactive whiteboards and other electronic devices with high handwriting input requirements, commonly used annotation applications will run upon startup. The system will also monitor application operation on the interactive whiteboard to accurately and flexibly launch other applications or annotation applications quickly based on touch data as needed.

[0054] For the annotation application, the user is unaware of the interaction in the initial state. Only the underlying layer detects the currently running application. If no other application needs to intercept touch data, an interception command is generated. Specifically, the interception command is sent by the annotation application to the first touch driver when it detects that the currently displayed application window is not the document presentation application window in the document presentation state. Considering that the document presentation application typically displays the document pages in full-screen format, page by page, based on an existing edited document page, and that the need for handwritten annotations and supplementary explanations on the full-screen document page only arises in document presentation state, if the currently displayed application window is not the document presentation application window, any potential writing operations can be considered as if no other application besides the annotation application has implemented handwriting interaction design. In this case, the first touch driver initiates touch data interception to quickly display the annotation window and allow handwriting input based on user actions.

[0055] In the specific implementation, if the first touch driver does not receive the interception instruction sent by the annotation application, it notifies the native touch driver to encapsulate and forward the touch data detected by the touch module based on the native device identifier, so that the document presentation application can implement the annotation function when it receives the touch data of the writing operation encapsulated based on the native device identifier in the document presentation state.

[0056] The first touch driver did not receive any interception instructions from the annotation application. Specifically, based on the description of the first touch driver's operating state, it means that the first touch driver currently does not need to process the touch data; the native touch driver directly sends the touch data to the upper layer. The first touch driver does not need to process the touch data; this could mean that the electronic device quickly launches the presentation application and enters presentation mode after powering on. The annotation application has not yet sent any interception instructions to the first touch driver, and because the currently displayed application window is the presentation application window in presentation mode, the annotation application will not send any interception instructions to the first touch driver until the presentation mode ends. Consequently, the native touch driver will continue to directly send touch data to the upper layer. The first touch driver does not need to process the touch data. Alternatively, after receiving the interception command sent by the annotation application, the window changes due to user operation. The window on top switches from other windows to the document presentation application window in the document presentation state. At this time, the annotation application sends a stop interception command to the first touch driver. The previously received interception command becomes invalid, and the first touch is equivalent to not receiving the interception command sent by the annotation application. After receiving the stop interception command, the first touch driver maintains the native touch driver method of directly sending touch data to the upper layer.

[0057] For touch data sent to the upper layer by the native touch driver, the system layer can receive the touch data and distribute it to the corresponding application for response based on the current application window's display state; alternatively, the current application window can be a full-screen presentation application window in presentation mode. In this case, the actual content of the currently displayed presentation cannot be edited, but annotations can be added using the presentation application's annotation function, displaying handwriting on a different layer than the presentation content. The presentation application can directly intercept touch data encapsulated with a specified device identifier, directly triggering the annotation function's response. In existing technologies, presentation applications typically intercept touch data based on standard-based device identifiers, i.e., native device identifiers.

[0058] In the absence of an interception command from the annotation application, the native touch driver encapsulates and forwards the touch data according to the native device identifier. The document presentation application, in document presentation mode, can obtain the touch data generated by the writing operation encapsulated by the native touch driver and also enables pen writing in document presentation mode. The document presentation application and annotation application mentioned in this embodiment are equivalent to respectively implementing internal annotations on the application's own display page and independent annotations on the content displayed by other applications (excluding the document page in document presentation mode). When both the document presentation application and the annotation application obtain touch data to quickly implement internal or independent annotations, to avoid conflicts and disorder caused by the same touch data simultaneously triggering internal and independent annotations, the annotation application implementing independent annotations actively detects the running status of the document presentation application. Only when there is no internal annotation requirement from the document presentation application will the touch data be intercepted and judged, ensuring that the same touch data triggers at most one of internal or independent annotations, guaranteeing that various applications with annotation requirements accurately trigger pen writing in their respective application scenarios.

[0059] In the specific implementation process, considering that some electronic devices may not be designed with other fast startup and response interaction methods, to simplify the actual operation logic after the first touch driver is installed, the device identifiers to be intercepted can be set according to the actual situation after installation. That is, the device identifiers recorded in the device identifier list are confirmed through the following steps: The first touch driver reads the human-computer interaction device list and identifies the device identifier corresponding to the touch peripheral from the list. Here, touch data is generally encapsulated into a standard interface format before being connected to the electronic device, and is recognized by the electronic device as a peripheral device providing touch data. Therefore, the electronic device can identify the existence of the touch peripheral by reading the human-computer interaction device list. The first touch driver reads the human-computer interaction device list and directly identifies the device identifier corresponding to the touch peripheral, which can adapt to the operating needs of the specific installed electronic device, allowing for flexible configuration and avoiding unnecessary interception settings.

[0060] In another alternative implementation, the electronic device itself may also experience state changes, allowing for corresponding detailed design. Specifically, the first touch driver reads the list of human-computer interaction devices and identifies the device identifier corresponding to the touch peripheral from this list. This includes: the first touch driver running upon power-on and reading the list of human-computer interaction devices to identify the device identifier corresponding to the touch peripheral. The first touch driver runs every time the device is powered on and reads the list of human-computer interaction devices to confirm the device identifier list, enabling targeted adjustments when the electronic device's software installation or interaction settings change.

[0061] Step S120: The first touch driver performs a trigger condition judgment on the intercepted current touch data according to the preset annotation trigger rules.

[0062] The annotation triggering rules include the movement trajectory corresponding to the touch data, the touch point size, and / or the judgment conditions corresponding to the touch point medium. Through various operation information confirmed by the touch data, the touch data generated by the writing operation can be quickly identified, and the annotation operation can be triggered accordingly. It should be noted that confirming whether a writing operation is performed through the movement trajectory, touch point size, and / or touch point medium is merely an example; other methods of confirming writing operations in related technologies can also implement this solution.

[0063] Step S130: When the current touch data meets the triggering conditions, the first touch driver wakes up the annotation window corresponding to the annotation application, sends the current touch data to the annotation application for response, and stops intercepting the touch data, allowing the operating system to distribute the touch data.

[0064] If the current touch data meets the triggering conditions, it can be processed according to the wake-up method and subsequent response annotated in the relevant technology, which will not be elaborated here.

[0065] Step S140: If the current touch data does not meet the triggering conditions, the first touch driver encapsulates the current touch data based on the first device identifier and forwards it. The first device identifier is the simulated device identifier corresponding to the first touch driver.

[0066] If the current touch data does not meet the triggering conditions, it indicates that the current touch data will not trigger any automatic startup and response interaction design. In this case, it is only necessary to forward the data according to the general touch data forwarding strategy. One detail is that the current touch data needs to be encapsulated according to the first device identifier corresponding to the first touch driver to avoid the device identifier used for encapsulation being the same as the device identifier recorded in the device identifier list (such as the native device identifier), thereby avoiding the situation of being blocked in a loop.

[0067] Users might launch the annotation application first, then launch the presentation application and enter the presentation state to display the document page in full screen. In this case, it is necessary to prioritize the quick launch of the annotation function of the presentation application and the generation of handwriting. Therefore, it is necessary to stop the annotation application from intercepting touch data to avoid conflicts between the interception and response of touch data by multiple applications. Accordingly, after the first touch driver encapsulates and forwards the current touch data based on the first device identifier when the current touch data does not meet the trigger conditions, it also includes: when the annotation application detects that the currently displayed application window is the presentation application window in the presentation state, it sends a stop interception command to the first touch driver, so that the native touch driver encapsulates and forwards the touch data detected by the touch module based on the native device identifier, so that the presentation application can implement the annotation function when it receives the touch data of the writing operation encapsulated based on the native device identifier in the presentation state. During the operation of the annotation application, it is detected that the currently displayed application window is the document presentation application window in document presentation mode. That is, when the document presentation application is launched and enters document presentation mode, the user's current operation is usually centered on the content displayed by the document presentation application. The user adds annotations and supplementary explanations to the full-screen document page displayed by the document presentation application in a handwritten manner. The document presentation application responds accordingly with its own annotation function. The annotation function of the document presentation application usually also has the ability to quickly launch and add handwriting based on touch data. At this time, the first touch driver is instructed to stop intercepting touch data so that the native touch driver can only be responded to by the document presentation application for touch data encapsulated based on the native device identifier. The first touch driver stops interception to avoid interfering with the response of the document presentation application.

[0068] In another optional implementation, when the annotation application detects that the currently displayed application window is the document presentation application window in document presentation mode, after sending a stop interception command to the first touch driver, the annotation application also includes: the annotation application entering the initial state. The annotation application re-entering the initial state ensures the normal display of the document presentation application window, and simultaneously begins listening for changes in the corresponding window during application operation, responding to user writing operations to intercept and display the annotation window as needed.

[0069] Overall, with the existing native touch driver enabling quick launch and input, a first touch driver is set up for the corresponding annotation application. The annotation application sends an interception command to the first touch driver based on its running status, triggering the interception and judgment of touch data that may trigger other applications according to the configuration, but for which there is currently no corresponding trigger. If the intercepted current touch data meets the triggering conditions for quickly launching the annotation application, it indicates that the current touch data itself is an operation on the annotation application, and the first touch driver can stop intercepting. The touch data output by the native touch driver will be directly sent to the annotation application for processing and response. If the intercepted current touch data does not meet the triggering conditions, the current touch data can be encapsulated according to the corresponding first device identifier and forwarded. The system layer can process it accurately according to the basic processing flow, while preventing the first touch driver from repeatedly intercepting touch data, ensuring the accurate completion of the entire interaction process.

[0070] Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 2 As shown, the electronic device includes a processor 310 and a memory 320. In one possible form of the electronic device, it may also include an input device 330, an output device 340, and a communication device 350. The number of processors 310 in the electronic device can be one or more. Figure 2 Taking a processor 310 as an example; the processor 310, memory 320, input device 330, output device 340, and communication device 350 in the electronic device can be connected via a bus or other means. Figure 2 Taking the example of a connection between China and Israel via a bus.

[0071] The memory 320, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the touch data processing method in the embodiments of this application. The processor 310 executes various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the memory 320, thereby implementing the aforementioned touch data processing method.

[0072] The memory 320 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on the use of the electronic device. Furthermore, the memory 320 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 320 may further include memory remotely located relative to the processor 310, which can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0073] Input device 330 can be used to receive network configuration information. Output device 340 may include a display device such as a screen.

[0074] The aforementioned electronic device can be used to execute any touch data processing method and has corresponding functions and beneficial effects.

[0075] This application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform relevant operations in the touch data processing method provided in any embodiment of this application, and have corresponding functions and beneficial effects.

[0076] Those skilled in the art will understand that embodiments of this application may be provided as methods, systems, or computer program products.

[0077] Therefore, this application may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application 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. This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, produce implementations of the flowchart... Figure 1 One or more processes and / or boxes Figure 1The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0078] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0079] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0080] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0081] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A touch data processing method for electronic devices, characterized in that, The electronic device includes a touch module, and the driving layer of the electronic device is equipped with a native touch driver and a first touch driver corresponding to the touch module. The touch data processing method includes: When the first touch driver receives an interception command sent by the annotation application, it intercepts touch data of the driver layer according to a preset device identifier list. The device identifier list records at least touch device identifiers, which are device identifiers presented by the touch module through the native touch driver. The first touch driver performs a trigger condition judgment on the intercepted current touch data according to the preset annotation trigger rules; When the current touch data meets the triggering condition, the first touch driver wakes up the annotation window corresponding to the annotation application, sends the current touch data to the annotation application for response, and stops intercepting the touch data, allowing the operating system to distribute the touch data. If the current touch data does not meet the triggering condition, the first touch driver encapsulates and forwards the current touch data based on a first device identifier, where the first device identifier is the simulated device identifier corresponding to the first touch driver.

2. The touch data processing method according to claim 1, characterized in that, Also includes: If the first touch driver does not receive an interception command from the annotation application, it notifies the native touch driver to encapsulate and forward the touch data detected by the touch module based on the native device identifier, so that the document presentation application can implement the annotation function when it receives the touch data of the writing operation encapsulated based on the native device identifier in the document presentation state.

3. The touch data processing method according to claim 1, characterized in that, The device identifiers recorded in the device identifier list are confirmed through the following steps: The first touch driver reads the list of human-computer interaction devices and identifies the device identifier corresponding to the touch peripheral from the list of human-computer interaction devices.

4. The touch data processing method according to claim 3, characterized in that, The first touch driver reads a list of human-computer interaction devices and identifies a device identifier corresponding to a touch peripheral from the list, including: The first touch driver runs when the device is powered on and reads the list of human-computer interaction devices, and identifies the device identifier corresponding to the touch peripheral from the list of human-computer interaction devices.

5. The touch data processing method according to claim 1, characterized in that, The annotation application includes an initial state and a display state. The annotation application runs and enters the initial state when the computer is powered on, and the annotation window is not visible in the initial state; the elements in the annotation window are visible in the display state.

6. The touch data processing method according to claim 5, characterized in that, The interception command is sent to the first touch driver when the annotation application detects in its initial state that the currently displayed application window is not the document presentation application window in the document presentation state.

7. The touch data processing method according to claim 6, characterized in that, When the current touch data does not meet the triggering condition, the first touch driver, after encapsulating and forwarding the current touch data based on the first device identifier, further includes: When the annotation application detects that the currently displayed application window is the document presentation application window in document presentation mode, it sends a stop interception command to the first touch driver, so that the native touch driver encapsulates and forwards the touch data detected by the touch module based on the native device identifier, so that the document presentation application can implement the annotation function when it receives the touch data of the writing operation encapsulated based on the native device identifier in document presentation mode.

8. The touch data processing method according to claim 6, characterized in that, When the annotation application detects that the currently displayed application window is a document presentation application window in document presentation mode, after sending a stop interception command to the first touch driver, it further includes: The annotation application enters the initial state.

9. The touch data processing method according to any one of claims 1-8, characterized in that, The annotation triggering rules include the movement trajectory corresponding to the touch data, the touch size, and / or the judgment conditions corresponding to the touch medium.

10. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more computer programs; When the one or more computer programs are executed by the one or more processors, the electronic device implements the touch data processing method as described in any one of claims 1-9.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the touch data processing method as described in any one of claims 1-9.

Images