CN111381728B - Touch data management and control method, device and computer readable storage medium - Google Patents
Touch data management and control method, device and computer readable storage medium Download PDFInfo
- Publication number
- CN111381728B CN111381728B CN202010167626.7A CN202010167626A CN111381728B CN 111381728 B CN111381728 B CN 111381728B CN 202010167626 A CN202010167626 A CN 202010167626A CN 111381728 B CN111381728 B CN 111381728B
- Authority
- CN
- China
- Prior art keywords
- data
- touch
- data management
- class object
- control module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000013523 data management Methods 0.000 title claims abstract description 117
- 238000000034 method Methods 0.000 title claims abstract description 104
- 238000004806 packaging method and process Methods 0.000 claims abstract description 67
- 230000006854 communication Effects 0.000 claims description 20
- 238000004891 communication Methods 0.000 claims description 19
- 230000008569 process Effects 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 15
- 238000013500 data storage Methods 0.000 claims description 15
- 238000012546 transfer Methods 0.000 claims description 14
- 230000006870 function Effects 0.000 description 19
- 238000007726 management method Methods 0.000 description 13
- 238000012986 modification Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 7
- 238000012384 transportation and delivery Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 5
- 238000010295 mobile communication Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 230000002085 persistent effect Effects 0.000 description 3
- 239000011230 binding agent Substances 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 239000006185 dispersion Substances 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000001629 suppression Effects 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
- G06F3/0416—Control or interface arrangements specially adapted for digitisers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
Abstract
The invention discloses a touch data management and control method, equipment and a computer readable storage medium, wherein the method comprises the following steps: acquiring object data of a touch signal, and generating a packaging class object of the object data; then, transmitting the packaging class object to a data management and control module through cross-process; then, generating a calling instruction for the data management and control module by a data calling module of the application program; and finally, calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file. The humanized touch data management and control scheme is realized, so that the continuous touch signals of the touch screen are stored more efficiently, the system is prevented from being additionally modified, and the stability of the system is ensured.
Description
Technical Field
The present invention relates to the field of mobile communications, and in particular, to a method and apparatus for controlling touch data, and a computer readable storage medium.
Background
In the prior art, with the rapid development of intelligent terminal devices, more and more application programs or game programs require users to perform a large number of operations or various operations to realize required functions or achieve a certain game experience. In this process, various types of touch operations bring high requirements to the reaction capability and learning capability of the user. Therefore, in the prior art, some technical solutions of continuous operation, or association operation, or shortcut operation are proposed.
However, at present, touch data of the continuous operation, or the related operation, or the shortcut operation is generated in the process of each application program, or the game program itself, and at the same time, each application program, or the game program may not obtain the storage authority of the system memory card, so even if touch data of the continuous operation, or the related operation, or the shortcut operation is obtained, the touch data may not be stored to a designated common path because the touch data is not stored in the storage authority of the system memory card, and it is also required to be stated that the touch data of the continuous operation, or the related operation, or the shortcut operation may have too large data dispersion, which may bring a large risk of data loss. Therefore, in the above application environment, a touch data storage scheme is needed to avoid the influence of the application program or the game program, and meanwhile, the data stability of the touch data needs to be ensured, so as to reduce the maintenance difficulty.
Disclosure of Invention
In order to solve the technical defects in the prior art, the invention provides a touch data management and control method, which comprises the following steps:
Acquiring object data of a touch signal, and generating a packaging class object of the object data;
transmitting the packaging class object to a data management and control module through cross-process;
generating a calling instruction for the data management and control module by a data calling module of an application program;
and calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file.
Optionally, the acquiring the object data of the touch signal and generating the packaging class object of the object data includes:
triggering the recording of the touch signal by the data management and control module;
in the recording process, acquiring object data of a touch signal in real time;
and after the recording is completed, generating a packaging class object according to the set of the object data.
Optionally, the transmitting the wrapper class object to a data management module through cross-process includes:
determining a data calling module in cross-process communication;
and receiving and carrying the packaging class object through a transfer component of the data calling module.
Optionally, the generating, by the data calling module of the application program, a calling instruction for the data management and control module includes:
Determining an application program corresponding to the touch signal;
and generating a call instruction for the data management and control module by a data call module of the application program.
Optionally, the calling the wrapper class object in the data management and control module according to the calling instruction, and storing the wrapper class object as an object file, including:
callback of the wrapper class object through the pass-through component;
the persisted or serialized wrapper class object is stored as an object oriented object file.
The invention also provides a touch data management and control device, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the computer program is realized when being executed by the processor:
acquiring object data of a touch signal, and generating a packaging class object of the object data;
transmitting the packaging class object to a data management and control module through cross-process;
generating a calling instruction for the data management and control module by a data calling module of an application program;
and calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file.
Optionally, the computer program is implemented when executed by the processor:
triggering the recording of the touch signal by the data management and control module;
in the recording process, acquiring object data of a touch signal in real time;
and after the recording is completed, generating a packaging class object according to the set of the object data.
Optionally, the computer program is implemented when executed by the processor:
determining a data calling module in cross-process communication;
and receiving and carrying the packaging class object through a transfer component of the data calling module.
Optionally, the computer program is implemented when executed by the processor:
determining an application program corresponding to the touch signal;
generating a calling instruction for the data management and control module by a data calling module of the application program;
callback of the wrapper class object through the pass-through component;
the persisted or serialized wrapper class object is stored as an object oriented object file.
The invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a touch data control program, and the touch data control program realizes the steps of the touch data control method according to any one of the above steps when being executed by a processor.
The touch data management and control method, the device and the computer readable storage medium are implemented by acquiring the object data of the touch signal and generating the packaging class object of the object data; then, transmitting the packaging class object to a data management and control module through cross-process; then, generating a calling instruction for the data management and control module by a data calling module of the application program; and finally, calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file. The humanized touch data management and control scheme is realized, so that the continuous touch signals of the touch screen are stored more efficiently, the system is prevented from being additionally modified, and the stability of the system is ensured.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
fig. 1 is a schematic diagram of a hardware structure of a mobile terminal according to the present invention;
fig. 2 is a schematic diagram of a communication network system according to an embodiment of the present invention;
FIG. 3 is a flowchart of a first embodiment of a touch data management method of the present invention;
FIG. 4 is a flow chart of a second embodiment of the touch data management method of the present invention;
FIG. 5 is a flow chart of a third embodiment of a touch data management method of the present invention;
FIG. 6 is a flow chart of a fourth embodiment of a touch data management method of the present invention;
FIG. 7 is a flowchart of a fifth embodiment of a touch data management method of the present invention.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
In the following description, suffixes such as "module", "component", or "unit" for representing elements are used only for facilitating the description of the present invention, and have no specific meaning per se. Thus, "module," "component," or "unit" may be used in combination.
The terminal may be implemented in various forms. For example, the terminals described in the present invention may include mobile terminals such as cell phones, tablet computers, notebook computers, palm computers, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices, wearable devices, smart bracelets, pedometers, and fixed terminals such as digital TVs, desktop computers, and the like.
The following description will be given taking a mobile terminal as an example, and those skilled in the art will understand that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for a moving purpose.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention, the mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an a/V (audio/video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111. Those skilled in the art will appreciate that the mobile terminal structure shown in fig. 1 is not limiting of the mobile terminal and that the mobile terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
The following describes the components of the mobile terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be used for receiving and transmitting signals during the information receiving or communication process, specifically, after receiving downlink information of the base station, processing the downlink information by the processor 110; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication, global System for Mobile communications), GPRS (General Packet Radio Service ), CDMA2000 (Code Division Multiple Access, CDMA 2000), WCDMA (Wideband Code Division Multiple Access ), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access, time Division synchronous code Division multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution, frequency Division Duplex Long term evolution), and TDD-LTE (Time Division Duplexing-Long Term Evolution, time Division Duplex Long term evolution), etc.
WiFi belongs to a short-distance wireless transmission technology, and a mobile terminal can help a user to send and receive e-mails, browse web pages, access streaming media and the like through the WiFi module 102, so that wireless broadband Internet access is provided for the user. Although fig. 1 shows a WiFi module 102, it is understood that it does not belong to the necessary constitution of a mobile terminal, and can be omitted entirely as required within a range that does not change the essence of the invention.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the mobile terminal 100. The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive an audio or video signal. The a/V input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, the graphics processor 1041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, and the like, and can process such sound into audio data. The processed audio (voice) data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting the audio signal.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and the proximity sensor can turn off the display panel 1061 and/or the backlight when the mobile terminal 100 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for applications of recognizing the gesture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; as for other sensors such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured in the mobile phone, the detailed description thereof will be omitted.
The display unit 106 is used to display information input by a user or information provided to the user. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the mobile terminal. In particular, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 1071 or thereabout by using any suitable object or accessory such as a finger, a stylus, etc.) and drive the corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends the touch point coordinates to the processor 110, and can receive and execute commands sent from the processor 110. Further, the touch panel 1071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 107 may include other input devices 1072 in addition to the touch panel 1071. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc., as specifically not limited herein.
Further, the touch panel 1071 may overlay the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or thereabout, the touch panel 1071 is transferred to the processor 110 to determine the type of touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of touch event. Although in fig. 1, the touch panel 1071 and the display panel 1061 are two independent components for implementing the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 may be integrated with the display panel 1061 to implement the input and output functions of the mobile terminal, which is not limited herein.
The interface unit 108 serves as an interface through which at least one external device can be connected with the mobile terminal 100. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.
Memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by running or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power source 111 (e.g., a battery) for supplying power to the respective components, and preferably, the power source 111 may be logically connected to the processor 110 through a power management system, so as to perform functions of managing charging, discharging, and power consumption management through the power management system.
Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described herein.
In order to facilitate understanding of the embodiments of the present invention, a communication network system on which the mobile terminal of the present invention is based will be described below.
Referring to fig. 2, fig. 2 is a schematic diagram of a communication network system according to an embodiment of the present invention, where the communication network system is an LTE system of a general mobile communication technology, and the LTE system includes a UE (User Equipment) 201, an e-UTRAN (Evolved UMTS Terrestrial Radio Access Network ) 202, an epc (Evolved Packet Core, evolved packet core) 203, and an IP service 204 of an operator that are sequentially connected in communication.
Specifically, the UE201 may be the terminal 100 described above, and will not be described herein.
The E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc. The eNodeB2021 may be connected with other eNodeB2022 by a backhaul (e.g., an X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide access from the UE201 to the EPC 203.
EPC203 may include MME (Mobility Management Entity ) 2031, hss (Home Subscriber Server, home subscriber server) 2032, other MMEs 2033, SGW (Serving Gate Way) 2034, pgw (PDN Gate Way) 2035 and PCRF (Policy and Charging Rules Function, policy and tariff function entity) 2036, and so on. The MME2031 is a control node that handles signaling between the UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location registers (not shown) and to hold user specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034 and PGW2035 may provide IP address allocation and other functions for UE201, PCRF2036 is a policy and charging control policy decision point for traffic data flows and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).
IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem ), or other IP services, etc.
Although the LTE system is described above as an example, it should be understood by those skilled in the art that the present invention is not limited to LTE systems, but may be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.
Based on the above mobile terminal hardware structure and the communication network system, various embodiments of the method of the present invention are provided.
Example 1
FIG. 3 is a flowchart of a touch data management method according to a first embodiment of the present invention. A method of touch data management, the method comprising:
s1, acquiring object data of a touch signal, and generating a packaging class object of the object data;
s2, transmitting the packaging type object to a data management and control module through cross-process;
s3, generating a calling instruction for the data management and control module by a data calling module of the application program;
s4, calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file.
In this embodiment, first, object data of a touch signal is acquired, and a package class object of the object data is generated; then, transmitting the packaging class object to a data management and control module through cross-process; then, generating a calling instruction for the data management and control module by a data calling module of the application program; and finally, calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file.
In this embodiment, the data storage scheme for the touch signal is applicable to various application program interfaces or system interfaces of the terminal device;
in this embodiment, the data storage scheme for the touch signal is suitable for the touch signal merging data storage between various application programs and the touch signal merging data storage of the application programs and the system components;
in this embodiment, optionally, during a period of time, object data of a series of touch signals is obtained according to a series of associated shortcut operations of the application program;
in this embodiment, optionally, object data of a series of touch signals is acquired according to a series of associated continuous operation of the game program over a period of time;
in this embodiment, optionally, object data of a series of touch signals is acquired according to a series of associated continuous operation of the game program over a period of time;
in this embodiment, a set of object data of a touch signal in a period of time is acquired, and a package class object of the set of object data is generated;
in this embodiment, a set of object data of one or more touch signals of a shortcut operation is obtained, and a package class object of the object data of the set is generated;
In this embodiment, a set of object data of touch signals of one or more game continuous operation is acquired, and a package class object of the object data of the set is generated;
in this embodiment, after the package class object of the object data is generated, the package class object is transmitted to a data management and control module through a cross-process, where the data management and control module is a management and control module for fast operation or a continuous call management and control module for a game program;
in this embodiment, after the package object is transmitted to the data management and control module by the cross-process, a call instruction for the data management and control module is generated by the data call module of the application program, and similarly, when the touch signal is generated in the conventional application program interface, a call instruction for the management and control module of the shortcut operation is generated by the data call module of the application program, and when the touch signal is generated in the game program interface, a call instruction for the continuous call management and control module of the game program is generated by the data call module of the game program;
in this embodiment, after generating a call instruction to the data management and control module, the wrapper class object is recalled in the data management and control module according to the call instruction, and the wrapper class object is stored as an object file. Likewise, when the touch signal is generated at the conventional application program interface, the shortcut operation is stored through the corresponding object file, and when the touch signal is generated at the game program interface, the game tie operation is stored through the corresponding object file.
The method has the advantages that the object data of the touch signal are obtained, and the packaging class object of the object data is generated; then, transmitting the packaging class object to a data management and control module through cross-process; then, generating a calling instruction for the data management and control module by a data calling module of the application program; and finally, calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file. The humanized touch data management and control scheme is realized, so that the continuous touch signals of the touch screen are stored more efficiently, the system is prevented from being additionally modified, and the stability of the system is ensured.
Example two
FIG. 4 is a flowchart of a second embodiment of the touch data management method according to the present invention, and based on the above embodiment, optionally, the method for obtaining object data of a touch signal and generating a package class object of the object data includes:
s11, triggering the recording of the touch signal by the data management and control module;
s12, acquiring object data of the touch signal in real time in the recording process;
and S13, after the recording is completed, generating a packaging class object according to the set of the object data.
Optionally, after the data management and control module triggers the recording of the touch signal, the actual touch signal is obtained by a conventional application program or a game program itself.
Optionally, when the touch signal is generated in the conventional application program interface, starting a touch operation implemented by the record shortcut operation;
optionally, when the touch signal is generated in the game program interface, starting to record the touch operation implemented by the game continuous operation;
optionally, identifying whether the function realized by the shortcut operation is completed, if so, determining the current recording ending time;
optionally, by identifying whether the game continuous operation has been successfully executed, if so, determining the end time of the current recording.
Optionally, the recorded touch signal is packaged, for example, during a game continuous operation, a one-key continuous operation is started, at this time, the user's touch operation generates a large amount of object data (for example, touching a MotionEvent object), and then the set of object data is put into a preset packaging class object (for example, an arrayist object). Since the object data itself is serializable, it is possible to support cross-process transmission, i.e., in this embodiment, it is not necessary to convert all data attributes of the object data one by one into a string-type object, and in this embodiment, the object data is transmitted through the cross-process, and thus, a set of the object data is built as one wrapper class object.
The method has the beneficial effects that the recording of the touch signal is started through the data management and control module; then, in the recording process, acquiring object data of the touch signal in real time; and finally, when the recording is completed, generating a packaging class object according to the set of the object data. The method and the device realize a more humanized touch data management and control scheme, so that the continuous touch signals of the touch screen are stored more efficiently, extra modification to the system is avoided, and the stability of the system is ensured.
Example III
FIG. 5 is a flowchart of a third embodiment of the touch data management method according to the present invention, and based on the above embodiment, optionally, the transmitting the wrapper class object to the data management module by cross-process includes:
s21, determining a data calling module in cross-process communication;
s22, receiving and carrying the packaging class object through a transfer component of the data calling module.
Optionally, in this embodiment, after the set of object data is built into a wrapper class object as described above, corresponding cross-process transmission is performed, and a pass component (e.g., bundle component) in a call component (e.g., call component) of a data calling module (e.g., contentProvider component) that communicates across processes (e.g., a Binder component) receives and carries the wrapper class object.
The method has the advantages that the data calling module in cross-process communication is determined; and then, receiving and carrying the packaging class object through a transfer component of the data calling module. The method and the device realize a more humanized touch data management and control scheme, so that the continuous touch signals of the touch screen are stored more efficiently, extra modification to the system is avoided, and the stability of the system is ensured.
Example IV
FIG. 6 is a flowchart of a fourth embodiment of the touch data management method according to the present invention, based on the above embodiment, optionally, the generating, by the data calling module of the application, a calling instruction for the data management module includes:
s31, determining an application program corresponding to the touch signal;
s32, generating a call instruction for the data management and control module by the data call module of the application program.
Optionally, in this embodiment, after the wrapper class object is received and carried by the delivery component of the data calling module, an application program (for example, a conventional application program or a game application program) corresponding to the touch signal is determined, and then, after the call of the data calling module of the conventional application program or the game application program is received, the transmitted delivery component is obtained in a related callback method, where it can be understood that the delivery component carries the wrapper class object.
The method has the advantages that the application program corresponding to the touch signal is determined; then, a calling instruction for the data management and control module is generated by a data calling module of the application program. The method and the device realize a more humanized touch data management and control scheme, so that the continuous touch signals of the touch screen are stored more efficiently, extra modification to the system is avoided, and the stability of the system is ensured.
Example five
FIG. 7 is a flowchart of a fifth embodiment of a touch data management and control method according to the present invention, based on the above embodiment, optionally, the calling the wrapper class object in the data management and control module according to the calling instruction, and storing the wrapper class object as an object file, including:
s41, callback the packaging class object through the transfer component;
s42, storing the persistent or serialized package class object as an object-oriented object file.
Optionally, in this embodiment, after the transferred delivery component is obtained in the related callback method, as described in the foregoing example, since the delivery component carries the wrapper class object, and the wrapper class object itself may be persistent or serialized, in this embodiment, a common object-oriented object file (e.g., a java file) is saved for the wrapper class object (e.g., a Parcel object) through the data management module. In this embodiment, since the data management and control module stores the file by itself, the storing operation does not need access or writing permission of the system to the memory card, and the related touch data is stored in the application directory of the data management and control module.
The beneficial effect of this embodiment is that the package class object is recalled through the transfer component; the persisted or serialized wrapper class object is then stored as an object oriented object file. The method and the device realize a more humanized touch data management and control scheme, so that the continuous touch signals of the touch screen are stored more efficiently, extra modification to the system is avoided, and the stability of the system is ensured.
Example six
Based on the above embodiment, the present invention further provides a touch data management and control device, where the device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the computer program is implemented when executed by the processor:
acquiring object data of a touch signal, and generating a packaging class object of the object data;
transmitting the packaging class object to a data management and control module through cross-process;
generating a calling instruction for the data management and control module by a data calling module of an application program;
and calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file.
In this embodiment, the data storage scheme for the touch signal is applicable to various application program interfaces or system interfaces of the terminal device;
In this embodiment, the data storage scheme for the touch signal is suitable for the touch signal merging data storage between various application programs and the touch signal merging data storage of the application programs and the system components;
in this embodiment, optionally, during a period of time, object data of a series of touch signals is obtained according to a series of associated shortcut operations of the application program;
in this embodiment, optionally, object data of a series of touch signals is acquired according to a series of associated continuous operation of the game program over a period of time;
in this embodiment, optionally, object data of a series of touch signals is acquired according to a series of associated continuous operation of the game program over a period of time;
in this embodiment, a set of object data of a touch signal in a period of time is acquired, and a package class object of the set of object data is generated;
in this embodiment, a set of object data of one or more touch signals of a shortcut operation is obtained, and a package class object of the object data of the set is generated;
in this embodiment, a set of object data of touch signals of one or more game continuous operation is acquired, and a package class object of the object data of the set is generated;
In this embodiment, after the package class object of the object data is generated, the package class object is transmitted to a data management and control module through a cross-process, where the data management and control module is a management and control module for fast operation or a continuous call management and control module for a game program;
in this embodiment, after the package object is transmitted to the data management and control module by the cross-process, a call instruction for the data management and control module is generated by the data call module of the application program, and similarly, when the touch signal is generated in the conventional application program interface, a call instruction for the management and control module of the shortcut operation is generated by the data call module of the application program, and when the touch signal is generated in the game program interface, a call instruction for the continuous call management and control module of the game program is generated by the data call module of the game program;
in this embodiment, after generating a call instruction to the data management and control module, the wrapper class object is recalled in the data management and control module according to the call instruction, and the wrapper class object is stored as an object file. Likewise, when the touch signal is generated at the conventional application program interface, the shortcut operation is stored through the corresponding object file, and when the touch signal is generated at the game program interface, the game tie operation is stored through the corresponding object file.
The method has the advantages that the object data of the touch signal are obtained, and the packaging class object of the object data is generated; then, transmitting the packaging class object to a data management and control module through cross-process; then, generating a calling instruction for the data management and control module by a data calling module of the application program; and finally, calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file. The humanized touch data management and control scheme is realized, so that the continuous touch signals of the touch screen are stored more efficiently, the system is prevented from being additionally modified, and the stability of the system is ensured.
Example seven
Based on the above embodiments, optionally, the computer program is implemented when executed by the processor:
triggering the recording of the touch signal by the data management and control module;
in the recording process, acquiring object data of a touch signal in real time;
and after the recording is completed, generating a packaging class object according to the set of the object data.
Optionally, when the touch signal is generated in the conventional application program interface, starting a touch operation implemented by the record shortcut operation;
Optionally, when the touch signal is generated in the game program interface, starting to record the touch operation implemented by the game continuous operation;
optionally, identifying whether the function realized by the shortcut operation is completed, if so, determining the current recording ending time;
optionally, by identifying whether the game continuous operation has been successfully executed, if so, determining the end time of the current recording.
Optionally, the recorded touch signal is packaged, for example, during a game continuous operation, a one-key continuous operation is started, at this time, the user's touch operation generates a large amount of object data (for example, touching a MotionEvent object), and then the set of object data is put into a preset packaging class object (for example, an arrayist object). Since the object data itself is serializable, it is possible to support cross-process transmission, i.e., in this embodiment, it is not necessary to convert all data attributes of the object data one by one into a string-type object, and in this embodiment, the object data is transmitted through the cross-process, and thus, a set of the object data is built as one wrapper class object.
The method has the beneficial effects that the recording of the touch signal is started through the data management and control module; then, in the recording process, acquiring object data of the touch signal in real time; and finally, when the recording is completed, generating a packaging class object according to the set of the object data. The method and the device realize a more humanized touch data management and control scheme, so that the continuous touch signals of the touch screen are stored more efficiently, extra modification to the system is avoided, and the stability of the system is ensured.
Example eight
Based on the above embodiments, optionally, the computer program is implemented when executed by the processor:
determining a data calling module in cross-process communication;
and receiving and carrying the packaging class object through a transfer component of the data calling module.
Optionally, in this embodiment, after the set of object data is built into a wrapper class object as described above, corresponding cross-process transmission is performed, and a pass component (e.g., bundle component) in a call component (e.g., call component) of a data calling module (e.g., contentProvider component) that communicates across processes (e.g., a Binder component) receives and carries the wrapper class object.
The method has the advantages that the data calling module in cross-process communication is determined; and then, receiving and carrying the packaging class object through a transfer component of the data calling module. The method and the device realize a more humanized touch data management and control scheme, so that the continuous touch signals of the touch screen are stored more efficiently, extra modification to the system is avoided, and the stability of the system is ensured.
Example nine
Based on the above embodiments, optionally, the computer program is implemented when executed by the processor:
Determining an application program corresponding to the touch signal;
generating a calling instruction for the data management and control module by a data calling module of the application program;
callback of the wrapper class object through the pass-through component;
the persisted or serialized wrapper class object is stored as an object oriented object file.
Optionally, in this embodiment, after receiving and carrying the wrapper class object through the transfer component of the data calling module as described above, determining an application program (for example, a conventional application program or a game application program) corresponding to the touch signal, and then, after receiving a call of the data calling module of the conventional application program or the game application program, obtaining the transferred transfer component in a related callback method, where it can be understood that the transfer component carries the wrapper class object;
optionally, in this embodiment, after the transferred delivery component is obtained in the related callback method, as described in the foregoing example, since the delivery component carries the wrapper class object, and the wrapper class object itself may be persistent or serialized, in this embodiment, a common object-oriented object file (e.g., a java file) is saved for the wrapper class object (e.g., a Parcel object) through the data management module. In this embodiment, since the data management and control module stores the file by itself, the storing operation does not need access or writing permission of the system to the memory card, and the related touch data is stored in the application directory of the data management and control module.
The beneficial effect of this embodiment is that the package class object is recalled through the transfer component; the persisted or serialized wrapper class object is then stored as an object oriented object file. The method and the device realize a more humanized touch data management and control scheme, so that the continuous touch signals of the touch screen are stored more efficiently, extra modification to the system is avoided, and the stability of the system is ensured.
Examples ten
Based on the above embodiment, the present invention further provides a computer readable storage medium, where a touch data management program is stored, where the touch data management program, when executed by a processor, implements the steps of the touch data management method according to any one of the above embodiments.
The touch data management and control method, the device and the computer readable storage medium are implemented by acquiring the object data of the touch signal and generating the packaging class object of the object data; then, transmitting the packaging class object to a data management and control module through cross-process; then, generating a calling instruction for the data management and control module by a data calling module of the application program; and finally, calling back the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file. The humanized touch data management and control scheme is realized, so that the continuous touch signals of the touch screen are stored more efficiently, the system is prevented from being additionally modified, and the stability of the system is ensured.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.
Claims (10)
1. A method for touch data management, the method comprising:
acquiring object data of a touch signal, and generating a packaging class object of the object data;
transmitting the packaging class object to a data management and control module through cross-process;
generating a calling instruction for the data management and control module by a data calling module of an application program;
callback the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file;
wherein,
the data storage scheme for the touch signals is suitable for various application program interfaces or system interfaces of terminal equipment, or suitable for the touch signal merging data storage among various application programs and suitable for the touch signal merging data storage of the application programs and system components;
Acquiring the object data of a series of the touch signals according to a series of associated shortcut operations of the application program within a period of time;
or, acquiring the object data of a series of the touch signals according to a series of associated tie operations of a game program over a period of time;
acquiring a set of the object data of the touch signal within a period of time, and generating the package class object of the object data of the set;
wherein,
acquiring a set of the object data of the touch signal of one or more shortcut operations, and generating the package class object of the object data of the set;
alternatively, a set of the object data of the touch signals of the tie operation of one or more of the game programs is acquired, and the wrapper class object of the object data of the set is generated.
2. The method for controlling touch data according to claim 1, wherein the obtaining object data of the touch signal and generating a package class object of the object data includes:
triggering the recording of the touch signal by the data management and control module;
in the recording process, acquiring object data of a touch signal in real time;
And after the recording is completed, generating a packaging class object according to the set of the object data.
3. The method of claim 2, wherein the transmitting the wrapper class object to a data management module by cross-process comprises:
determining a data calling module in cross-process communication;
and receiving and carrying the packaging class object through a transfer component of the data calling module.
4. The touch data management method according to claim 3, wherein the generating, by the data calling module of the application program, a call instruction to the data management module includes:
determining an application program corresponding to the touch signal;
and generating a call instruction for the data management and control module by a data call module of the application program.
5. The method for controlling touch data according to claim 4, wherein the calling back the wrapper class object in the data controlling module according to the calling instruction, and storing the wrapper class object as an object file, comprises:
callback of the wrapper class object through the pass-through component;
the persisted or serialized wrapper class object is stored as an object oriented object file.
6. A touch data management device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program when executed by the processor implementing:
acquiring object data of a touch signal, and generating a packaging class object of the object data;
transmitting the packaging class object to a data management and control module through cross-process;
generating a calling instruction for the data management and control module by a data calling module of an application program;
callback the packaging class object in the data management and control module according to the calling instruction, and storing the packaging class object as an object file;
wherein,
the data storage scheme for the touch signals is suitable for various application program interfaces or system interfaces of terminal equipment, or suitable for the touch signal merging data storage among various application programs and suitable for the touch signal merging data storage of the application programs and system components;
acquiring the object data of a series of the touch signals according to a series of associated shortcut operations of the application program within a period of time;
Or, acquiring the object data of a series of the touch signals according to a series of associated tie operations of a game program over a period of time;
acquiring a set of the object data of the touch signal within a period of time, and generating the package class object of the object data of the set;
wherein,
acquiring a set of the object data of the touch signal of one or more shortcut operations, and generating the package class object of the object data of the set;
alternatively, a set of the object data of the touch signals of the tie operation of one or more of the game programs is acquired, and the wrapper class object of the object data of the set is generated.
7. The touch data management device of claim 6, wherein the computer program when executed by the processor implements:
triggering the recording of the touch signal by the data management and control module;
in the recording process, acquiring object data of a touch signal in real time;
and after the recording is completed, generating a packaging class object according to the set of the object data.
8. The touch data management device of claim 7, wherein the computer program when executed by the processor implements:
Determining a data calling module in cross-process communication;
and receiving and carrying the packaging class object through a transfer component of the data calling module.
9. The touch data management device of claim 8, wherein the computer program when executed by the processor implements:
determining an application program corresponding to the touch signal;
generating a calling instruction for the data management and control module by a data calling module of the application program;
callback of the wrapper class object through the pass-through component;
the persisted or serialized wrapper class object is stored as an object oriented object file.
10. A computer readable storage medium, wherein a touch data management program is stored on the computer readable storage medium, which when executed by a processor implements the steps of the touch data management method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010167626.7A CN111381728B (en) | 2020-03-11 | 2020-03-11 | Touch data management and control method, device and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010167626.7A CN111381728B (en) | 2020-03-11 | 2020-03-11 | Touch data management and control method, device and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111381728A CN111381728A (en) | 2020-07-07 |
| CN111381728B true CN111381728B (en) | 2024-01-09 |
Family
ID=71222697
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010167626.7A Active CN111381728B (en) | 2020-03-11 | 2020-03-11 | Touch data management and control method, device and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111381728B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7069540B1 (en) * | 2001-07-02 | 2006-06-27 | Unisys Corporation | COM persistence model |
| CN109426570A (en) * | 2017-08-29 | 2019-03-05 | 阿里巴巴集团控股有限公司 | A kind of acquisition methods of data, device and equipment |
| CN110532045A (en) * | 2019-09-04 | 2019-12-03 | 深圳市迅雷网络技术有限公司 | A kind of striding course call method and relevant apparatus |
-
2020
- 2020-03-11 CN CN202010167626.7A patent/CN111381728B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7069540B1 (en) * | 2001-07-02 | 2006-06-27 | Unisys Corporation | COM persistence model |
| CN109426570A (en) * | 2017-08-29 | 2019-03-05 | 阿里巴巴集团控股有限公司 | A kind of acquisition methods of data, device and equipment |
| CN110532045A (en) * | 2019-09-04 | 2019-12-03 | 深圳市迅雷网络技术有限公司 | A kind of striding course call method and relevant apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111381728A (en) | 2020-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112799577B (en) | Method, terminal and storage medium for projecting small window | |
| CN110187925B (en) | Desktop pre-starting control method, device and computer readable storage medium | |
| CN109766119B (en) | Recovery partition upgrade method, terminal and computer readable storage medium | |
| CN111427709B (en) | Application program splitting control method, device and computer readable storage medium | |
| CN109445945B (en) | Memory allocation method of application program, mobile terminal, server and storage medium | |
| CN109545120B (en) | Screen light sensor adjusting method, mobile terminal and computer readable storage medium | |
| CN109389394B (en) | Multi-screen payment control method, equipment and computer readable storage medium | |
| CN111970738B (en) | Network switching control method, device and computer readable storage medium | |
| CN109684020B (en) | Theme switching method, device and computer readable storage medium | |
| CN112423211A (en) | Multi-audio transmission control method, equipment and computer readable storage medium | |
| CN109462829B (en) | Call transfer method, device and computer readable storage medium | |
| CN109669616B (en) | Side screen interaction control method and device and computer readable storage medium | |
| CN109388947B (en) | Background management method, device and computer readable storage medium | |
| CN110955397A (en) | Method for setting frame rate of game terminal, game terminal and storage medium | |
| CN112015508B (en) | Screen-throwing interaction control method, equipment and computer-readable storage medium | |
| CN110572518B (en) | Screen-extinguishing control method, mobile terminal and computer-readable storage medium | |
| CN111381728B (en) | Touch data management and control method, device and computer readable storage medium | |
| CN110287381B (en) | Page control node searching method, terminal and computer readable storage medium | |
| CN110262707B (en) | Application program operation recording method and device and computer readable storage medium | |
| CN110413415B (en) | Memory management control method, equipment and computer readable storage medium | |
| CN110087290B (en) | Power consumption management and control method, terminal and computer readable storage medium | |
| CN112312194B (en) | Screen recording data processing method, device and computer readable storage medium | |
| CN113852717B (en) | Wallpaper module position migration method, equipment and computer readable storage medium | |
| CN112637158B (en) | Call network regulation and control method, device and computer readable storage medium | |
| CN110110138B (en) | Preservation method, mobile terminal and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |