CN104035714A - Event processing method, device and equipment based on Android system - Google Patents
Event processing method, device and equipment based on Android system Download PDFInfo
- Publication number
- CN104035714A CN104035714A CN201410288685.4A CN201410288685A CN104035714A CN 104035714 A CN104035714 A CN 104035714A CN 201410288685 A CN201410288685 A CN 201410288685A CN 104035714 A CN104035714 A CN 104035714A
- Authority
- CN
- China
- Prior art keywords
- event
- touch event
- touch
- prediction
- 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.)
- Granted
Links
Abstract
The invention provides event processing method, device and equipment based on the Android system. The method includes acquiring a currently-triggered touch event; judging whether the current touch event is a press event or not; if so, triggering a touch event predicting process including judging whether the time difference between the occurring time of the last triggered event and the current time is larger than a preset touch time interval or not, if so, predicting the next touch event according to a preset predicting event model; determining the predicted next touch event as a touch event to be processed. According to an embodiment, the problem that in the prior art, the large delay exists in user's touch operation can be solved, the finger of a user sliding on a touch screen can be locked to react to the touch event of the user rapidly, the response speed of the Android system can be increased, and using experience of the user can be improved.
Description
Technical field
The application relates to the Android Android system field of smart machine, particularly touch event disposal route, device and the equipment based on Android system.
Background technology
Along with scientific and technical progress, on the mobile device of Android (Android) system, generally all adopt touch-screen to realize display interface.Therefore, the fluency that user controls mobile device on touch-screen just seems particularly important, and this is also to affect the very key factor that user experiences.This seems particularly outstanding when user triggers drag operation in touch screen, as: slip screen, drag list etc.
Inventor finds in research process, smart machine of the prior art, such as smart mobile phone or panel computer etc., the touch operation that user produces generally has larger time delay, can not cling the finger that user slides in touch screen, can not make a response fast to user's touch event.
Summary of the invention
The application's technical matters to be solved is to provide a kind of touch event disposal route based on Android system, in order to solve the problem that has larger time delay in prior art for user's touch operation, thereby can cling the finger that user slides in touch screen, make a response fast with the touch time to user, not only improve the response speed of Android system, can also promote user's experience.
The application also provides a kind of touch event treating apparatus and equipment based on Android system, in order to guarantee said method implementation and application in practice.
In order to address the above problem, the application discloses a kind of touch event disposal route based on Android system, comprising:
Obtain the touch event of current triggering;
Judge that whether current touch event is for pressing event, if press event, trigger touch event prediction flow process, described touch event prediction flow process comprises: judge whether the time of last touch event generation and the mistiming of current time are greater than the default touch time interval, if be greater than, according to default predicted events model prediction touch event next time;
The touch event next time of described prediction is responded as pending touch event.
Optionally, at described current touch event, be not, the in the situation that of pressing event, also to comprise:
Judge whether described current touch event is the event of unclamping, if, stop described touch event prediction flow process, if not, determine that described current touch event is moving event, and judge whether described moving event exists corresponding prediction touch event, if existed, obtain the pixel value difference between the occurrence positions of described prediction touch event and the occurrence positions of described moving event.
Optionally, also comprise:
Judge whether described pixel value difference is greater than default error threshold, if so, described prediction touch event is recorded as to anomalous event.
Optionally, described event prediction model comprises higher-order function model and linear function model, also comprises:
Whether the frequency that judges described anomalous event is greater than predeterminated frequency threshold value, if, the event prediction model using while default higher-order function model being defined as to the flow process of trigger event prediction next time, the event prediction model using during if not, using default linear function model as the flow process of trigger event prediction next time.
Optionally, described current touch event is stored in event queue,, after stopping described touch event prediction flow process, also comprises:
Remove all touch events in described event queue.
Optionally, also comprise:
Cpu load situation according to described Android system was adjusted the described default touch time interval.
The application also provides a kind of touch event treating apparatus based on Android system, comprising:
Obtain event module, for obtaining the touch event of current triggering;
The first judge module, for judging that whether current touch event is for pressing event;
Trigger module, when being, triggers touch event prediction module for the result at described the first judge module;
Touch event prediction module comprises: judgement submodule and predictor module, described judgement submodule, for judging whether the time of last touch event generation and the mistiming of current time are greater than the default touch time interval, described predictor module is in the situation that the result of described judgement submodule is to be, according to default predicted events model prediction touch event next time;
Determination module, for responding the touch event next time of described prediction as pending touch event.
Optionally, at described current touch event, be not, the in the situation that of pressing event, also to comprise:
The second judge module, for judging whether described current touch event is the event of unclamping;
Stopping modular, in the situation that the result of described the second judge module is to be to stop trigger module;
Determination module, in the situation that the result of described the second judge module is no, determines that described current touch event is moving event;
The 3rd judge module, for judging whether described moving event exists corresponding prediction touch event;
Obtain pixel value difference module, in the situation that the result of described the 3rd judge module is to be, obtain the pixel value difference between the occurrence positions of described prediction touch event and the occurrence positions of described moving event.
Optionally, also comprise:
The 4th judge module, for judging whether described pixel value difference is greater than default error threshold;
Logging modle, in the situation that the result of described the 4th judge module is to be, is recorded as anomalous event by described prediction touch event.
Optionally, also comprise:
The 5th judge module, for judging whether the frequency of described anomalous event is greater than predeterminated frequency threshold value;
The first determination module, in the situation that the result of described the 5th judge module is no, is defined as default higher-order function model on the event prediction model using when trigger event is predicted flow process next time;
The second determination module, in the situation that the result of described the 5th judge module is to be, the event prediction model using during using default linear function model as the flow process of trigger event prediction next time.
Optionally, described current touch event is stored in event queue, also comprises:
Remove module, for removing all touch events of described event queue.
Optionally, also comprise:
Adjusting module, adjusts the described default touch time interval for the cpu load situation according to described Android system.
Compared with prior art, the application comprises following advantage:
In this application, due to when mistiming of the time occurring at upper once touch event and current time surpasses the touch time interval, will predict touch event next time, thereby system can respond the touch event of this prediction, rather than the touch event of waiting for the actual generation of user responds again, so just can solve the problem that has larger time delay in prior art for user's touch operation, thereby can cling the finger that user slides in touch screen, make a response fast with the touch time to user, not only improve the response speed of Android system, can also promote user's experience.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme in the embodiment of the present application, below the accompanying drawing of required use during embodiment is described is briefly described, apparently, accompanying drawing in the following describes is only some embodiment of the application, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the process flow diagram of a kind of touch event disposal route embodiment 1 based on Android system of the application;
Fig. 2 is the process flow diagram of a kind of touch event disposal route embodiment 2 based on Android system of the application;
Fig. 3 is the structured flowchart of a kind of touch event treating apparatus embodiment based on Android system of the application.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present application, the technical scheme in the embodiment of the present application is clearly and completely described, obviously, described embodiment is only the application's part embodiment, rather than whole embodiment.Embodiment based in the application, those of ordinary skills are not making the every other embodiment obtaining under creative work prerequisite, all belong to the scope of the application's protection.
The application can be used in numerous general or special purpose calculation element environment or configuration.For example: personal computer, server computer, handheld device or portable set, plate equipment, multi-processor device, comprise distributed computing environment of above any device or equipment etc.
The application can describe in the general context of the computer executable instructions of being carried out by computing machine, for example program module.Usually, program module comprises the routine carrying out particular task or realize particular abstract data type, program, object, assembly, data structure etc.Also can in distributed computing environment, put into practice the application, in these distributed computing environment, by the teleprocessing equipment being connected by communication network, be executed the task.In distributed computing environment, program module can be arranged in the local and remote computer-readable storage medium that comprises memory device.
With reference to figure 1, show the process flow diagram of a kind of touch event disposal route embodiment 1 based on Android system of the application, can comprise the following steps:
Step 101: the touch event that obtains current triggering.
In the embodiment of the present application, while having triggered touch event on the touch-screen of user at smart machine, first get the touch event of the current triggering of user.Wherein, touch event refers to, the touch event producing in the current interface showing on touch-screen.For example, active user has opened micro-letter, just need to catch so in the present embodiment slip (move) event of user on micro-letter interface of front opening.And if user has been switched to the interface of Taobao from micro-letter, the touch event capturing is in this case exactly the slip event that user triggers on the interface of Taobao.Also for example, slip event when user is switched between the multi-screen of the desktop application of smart machine, etc.
Step 102: judge that current touch event, whether for pressing event, if press event, enters step 103.
Whether the current touch event getting in step 101 is judged for pressing event, if press event, the follow-up touch event prediction flow process that just triggers.In the present embodiment, touch event is divided into three kinds: press, unclamp and move, can trigger touch event prediction flow process when event is pressed in generation.
Step 103: trigger touch event prediction flow process, described touch event prediction flow process can comprise: judge whether the time of last touch event generation and the mistiming of current time are greater than the default touch time interval, if be greater than, according to default predicted events model prediction touch event next time.
In the present embodiment, when having produced while pressing event, first the touch event prediction flow process triggering can judge whether the time of last touch event generation and the mistiming of current time are greater than a default touch time interval, 10ms for example, if this mistiming is also larger than the default touch time interval, illustrate that the touch event that user produces has had time delay, the situation that just there will be in this case the discontinuous or time delay of the drafting at interface on touch-screen, for fear of this situation, just can predict touch event next time according to default predicted events model.For example, the position that prediction touch event next time occurs, predicts which position on current touch interface may produce touch event.
Be understandable that, the numerical value that touches the time interval can independently be arranged according to actual demand or application scenarios by those skilled in the art, for example, according to the cpu load situation of described Android system, the described default touch time interval is adjusted.Wherein, if cpu load is larger, can be accordingly will touch a little bit smaller a little that the time interval arranges, and if cpu load is less, can will touch the larger a little of time interval setting accordingly.For example, when cpu load surpasses 70%, the speed of illustrative system response user's touch event can be slow, so now the default touch time interval is adjusted into 10ms, so just can dope faster touch event next time, and if cpu load is less than or equal to 70%, the Performance Ratio of illustrative system is better, just corresponding very fast to user's touch event itself, now just the touch time interval can be adjusted into 20ms, so frequently touch event not predicted.Certainly, above-mentioned numerical value is concrete example, should not be understood as the restriction to the application.
Step 104: the touch event next time of described prediction is defined as to pending touch event.
Then system is just defined as pending touch event by the touch event of prediction in step 103.
Adopt the embodiment of the present invention, when user carries out finger sliding on touch apparatus, once there is not touch operation within the default touch time interval, will dope the position of contingent touch event next time, then by system, the touch event of this prediction be responded.Thereby the operation of response user that can be faster on touch-screen, so not only promoted the response speed of system, the touch time to user makes a response fast, thereby there is the problem of larger time delay in the touch operation that has solved user, also can produce the effect of clinging the finger that user slides in touch screen, thereby promote user's experience.
With reference to figure 2, show the process flow diagram of a kind of touch event disposal route embodiment 2 based on Android system of the application, the present embodiment is the concrete example of embodiment 1, this concrete example can comprise the following steps:
Step 201: the touch event that obtains current triggering.
Step 202: judge that current touch event, whether for pressing event, if press event, enters step 203, if not pressing event, enter step 204.
Step 201～step 202 is consistent with embodiment 1, does not repeat them here.
Step 203: trigger event prediction flow process, and enter step 213.
In the present embodiment, event prediction flow process can adopt one independently to predict thread realization.In the time of needs trigger event prediction flow process, just trigger this and independently predict thread.Be understandable that, this independently predicts that thread is after triggering, can judge whether Set For Current and exit sign, for example whether user has triggered the event of unclamping, if so, this prediction thread can stop, and if user does not trigger the event of unclamping, predict that thread can get the default touch time interval, thereby and get the time that last time, touch event occurred and subtract each other and obtain the mistiming with current time.If being greater than, this mistiming touches the time interval, can call default predicted events model and generate touch event next time, if being greater than, the mistiming do not touch the time interval, this independently predicts that thread can enter dormancy, the length of dormant event can be the length at default touch event interval, thereby waits for that user is waken up when event is pressed in generation next time.
Step 204: judge whether described current touch event is the event of unclamping, and if so, enters step 205, if not, enters step 206.
In the present embodiment, if current touch event is not the event of pressing, continues the current touch event of judgement and whether unclamp event.
Step 205: stop touch event prediction flow process, and remove all touch events in described event queue, finish current flow process.
If current touch event is the event of unclamping, the current operation having completed touch-screen of user is described, now can stop touch event prediction flow process.
In the present embodiment, can set up the event queue of a first-in first-out, and touch event is saved in this event queue successively, so after stopping touch event prediction flow process, can be by the touch event zero clearing in this event queue, thereby when conveniently triggering touch event prediction flow process, then store touch event in this event queue next time.
Step 206: determine that described current touch event is moving event, and judge whether described moving event exists corresponding prediction touch event, if existed, enter step 207, if there is no, finish current flow process.
At current touch event neither the event of pressing neither unclamp event in the situation that, determine that current touch event is mobile (move) event, so, judging whether this moving event exists corresponding prediction touch event, is to judge whether that predicted events matches with this moving event in addition.When specific implementation, predicted events can be put into prediction queue, when user has triggered touch event, from the head of prediction queue, takes out predicted events, can put into event queue together with touch event.If there is no touch event in prediction queue, illustrate that this moving event does not have corresponding predicted events.
Step 207: obtain the pixel value difference between the occurrence positions of described prediction touch event and the occurrence positions of described moving event.
When there is corresponding prediction touch event in moving event, get the occurrence positions of prediction touch event, be horizontal ordinate X and the ordinate Y value of prediction touch event on touch-screen display interface, and the same occurrence positions that gets moving event, be horizontal ordinate X and the ordinate Y value of moving event on touch-screen display interface, both coordinate figures are subtracted each other and obtain pixel value difference.
Step 208: judge whether described pixel value difference is greater than default error threshold, if so, enter step 209, if not, finish current flow process.
Whether the pixel value difference that determining step 207 obtains is greater than default error threshold.This error threshold can value be 5～8, and generally, user's finger can cover 5～8 pixels while pressing on the interface of touch-screen.If be not more than, finish current flow process.
Step 209: described prediction touch event is recorded as to anomalous event.
When pixel value difference is greater than default error threshold, the pixel region for example, having covered when being greater than user and on average touching, the prediction touch event that this is described is so relatively not accurate enough, in this case, this prediction touch event is recorded as to anomalous event.
Step 210: whether the frequency that judges described anomalous event is greater than predeterminated frequency threshold value, if so, enters step 211, if not, enters step 212.
In actual applications, if all there is several times continuously anomalous event, be that the frequency of anomalous event is greater than predeterminated frequency threshold value, for example, in nearest continuous 8 prediction touch events, there are 3 to be all anomalous event, possible predicted events Model Selection not accurate enough.
Step 211: the event prediction model using when default higher-order function model is defined as to the flow process of trigger event prediction next time, finishes current flow process.
When the number of times that occurs when anomalous event is more, just adopt default higher-order function model as predicted events model, when upper once trigger event prediction flow process, will adopt default higher-order function model to predict the occurrence positions of touch event.
Step 212: the event prediction model using during using default linear function model as the flow process of trigger event prediction next time, finishes current flow process.
When the number of times that occurs when anomalous event is less, just adopt default linear function model as predicted events model, when next trigger event prediction flow process, will adopt default linear function model to predict the occurrence positions of touch event.
Step 213: the touch event next time of described prediction is defined as to pending touch event.
When having predicted touch event, just using the touch event next time of prediction as pending touch event.Follow-up when the real touch event of user is not delivered to input window processor, just directly respond the touch event of this prediction.
Adopt the embodiment of the present invention, the operation of response user that not only can be faster on touch-screen, promoted the response speed of system, the touch time to user makes a response fast, thereby there is the problem of larger time delay in the touch operation that has solved user, also can produce the effect of clinging the finger that user slides in touch screen, thereby promote user's experience.
For aforesaid each embodiment of the method, for simple description, therefore it is all expressed as to a series of combination of actions, but those skilled in the art should know, the application is not subject to the restriction of described sequence of movement, because according to the application, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in instructions all belongs to preferred embodiment, and related action and module might not be that the application is necessary.
Corresponding with the method that a kind of touch event disposal route embodiment 1 based on Android system of above-mentioned the application provides, referring to Fig. 3, the application also provides a kind of touch event treating apparatus embodiment 1 based on Android system, in the present embodiment, can comprise:
Obtain event module 301, for obtaining the touch event of current triggering;
The first judge module 302, for judging that whether current touch event is for pressing event;
Trigger module 303, when being, triggers touch event prediction module 304 for the result at described the first judge module;
Touch event prediction module 304 comprises: judgement submodule 3041 and predictor module 3042, described judgement submodule, for judging whether the time of last touch event generation and the mistiming of current time are greater than the default touch time interval, described predictor module is in the situation that the result of described judgement submodule is to be, according to default predicted events model prediction touch event next time;
Determination module 305, for being defined as pending touch event by the touch event next time of described prediction.
Adopt the embodiment of the present invention, when user carries out finger sliding on touch apparatus, once there is not touch operation within the default touch time interval, will dope the position of contingent touch event next time, then by system, the touch event of this prediction be responded.Because system responses also can take the regular hour, therefore, when the real touch event of user does not also transmit in time with regard to the touch event of response prediction, thereby the operation of response user that can be faster on touch-screen, so not only promoted the response speed of system, the touch time to user makes a response fast, thereby there is the problem of larger time delay in the touch operation that has solved user, also can produce the effect of clinging the finger that user slides in touch screen, thereby promote user's experience.
In different embodiment, except the modules shown in Fig. 3, the touch event treating apparatus embodiment 2 based on Android system specifically can also comprise:
The second judge module, for judging whether described current touch event is the event of unclamping.
Stopping modular, in the situation that the result of described the second judge module is to be to stop trigger module.
Determination module, in the situation that the result of described the second judge module is no, determines that described current touch event is moving event.
The 3rd judge module, for judging whether described moving event exists corresponding prediction touch event.
Obtain pixel value difference module, in the situation that the result of described the 3rd judge module is to be, obtain the pixel value difference between the occurrence positions of described prediction touch event and the occurrence positions of described moving event.
The 4th judge module, for judging whether described pixel value difference is greater than default error threshold.
Logging modle, in the situation that the result of described the 4th judge module is to be, is recorded as anomalous event by described prediction touch event.
The 5th judge module, for judging whether the frequency of described anomalous event is greater than predeterminated frequency threshold value;
The first determination module, in the situation that the result of described the 5th judge module is no, is defined as default higher-order function model on the event prediction model using when trigger event is predicted flow process next time.
The second determination module, in the situation that the result of described the 5th judge module is to be, the event prediction model using during using default linear function model as the flow process of trigger event prediction next time.
Remove module, for removing all touch events of described event queue.
Adjusting module, adjusts the described default touch time interval for the cpu load situation according to described Android system.
The application also provides a kind of equipment, the smart machine of concrete touch-screen such as this equipment such as smart mobile phone or panel computer etc., the upper integrated aforesaid any one device of its CPU.
It should be noted that, each embodiment in this instructions all adopts the mode of going forward one by one to describe, and each embodiment stresses is the difference with other embodiment, between each embodiment identical similar part mutually referring to.For device class embodiment, because it is substantially similar to embodiment of the method, so description is fairly simple, relevant part is referring to the part explanation of embodiment of the method.
Finally, also it should be noted that, in this article, relational terms such as the first and second grades is only used for an entity or operation to separate with another entity or operational zone, and not necessarily requires or imply and between these entities or operation, have the relation of any this reality or sequentially.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thereby the process, method, article or the equipment that make to comprise a series of key elements not only comprise those key elements, but also comprise other key elements of clearly not listing, or be also included as the intrinsic key element of this process, method, article or equipment.The in the situation that of more restrictions not, the key element being limited by statement " comprising ... ", and be not precluded within process, method, article or the equipment that comprises described key element and also have other identical element.
The safety access method of a kind of ECU above the application being provided, ECU and host computer are described in detail, applied specific case herein the application's principle and embodiment are set forth, the explanation of above embodiment is just for helping to understand the application's method and core concept thereof; Meanwhile, for one of ordinary skill in the art, the thought according to the application, all will change in specific embodiments and applications, and in sum, this description should not be construed as the restriction to the application.
Claims (12)
1. the touch event disposal route based on Android system, is characterized in that, comprising:
Obtain the touch event of current triggering;
Judge that whether current touch event is for pressing event, if press event, trigger touch event prediction flow process, described touch event prediction flow process comprises: judge whether the time of last touch event generation and the mistiming of current time are greater than the default touch time interval, if be greater than, according to default predicted events model prediction touch event next time;
The touch event next time of described prediction is defined as to pending touch event.
2. method according to claim 1, is characterized in that, at described current touch event, is not, the in the situation that of pressing event, also to comprise:
Judge whether described current touch event is the event of unclamping, if, stop described touch event prediction flow process, if not, determine that described current touch event is moving event, and judge whether described moving event exists corresponding prediction touch event, if existed, obtain the pixel value difference between the occurrence positions of described prediction touch event and the occurrence positions of described moving event.
3. method according to claim 2, is characterized in that, also comprises:
Judge whether described pixel value difference is greater than default error threshold, if so, described prediction touch event is recorded as to anomalous event.
4. method according to claim 3, is characterized in that, described event prediction model comprises higher-order function model and linear function model, also comprises:
Whether the frequency that judges described anomalous event is greater than predeterminated frequency threshold value, if, the event prediction model using while default higher-order function model being defined as to the flow process of trigger event prediction next time, the event prediction model using during if not, using default linear function model as the flow process of trigger event prediction next time.
5. method according to claim 2, is characterized in that, described current touch event is stored in event queue,, after stopping described touch event prediction flow process, also comprises:
Remove all touch events in described event queue.
6. according to the method described in claim 1～5 any one, it is characterized in that, also comprise:
Cpu load situation according to described Android system was adjusted the described default touch time interval.
7. the touch event disposal route based on Android system, is characterized in that, comprising:
Obtain event module, for obtaining the touch event of current triggering;
The first judge module, for judging that whether current touch event is for pressing event;
Trigger module, when being, triggers touch event prediction module for the result at described the first judge module;
Touch event prediction module comprises: judgement submodule and predictor module, described judgement submodule, for judging whether the time of last touch event generation and the mistiming of current time are greater than the default touch time interval, described predictor module is in the situation that the result of described judgement submodule is to be, according to default predicted events model prediction touch event next time;
Determination module, for being defined as pending touch event by the touch event next time of described prediction.
8. device according to claim 7, is characterized in that, at described current touch event, is not, the in the situation that of pressing event, also to comprise:
The second judge module, for judging whether described current touch event is the event of unclamping;
Stopping modular, in the situation that the result of described the second judge module is to be to stop trigger module;
Determination module, in the situation that the result of described the second judge module is no, determines that described current touch event is moving event;
The 3rd judge module, for judging whether described moving event exists corresponding prediction touch event;
Obtain pixel value difference module, in the situation that the result of described the 3rd judge module is to be, obtain the pixel value difference between the occurrence positions of described prediction touch event and the occurrence positions of described moving event.
9. device according to claim 8, is characterized in that, also comprises:
The 4th judge module, for judging whether described pixel value difference is greater than default error threshold;
Logging modle, in the situation that the result of described the 4th judge module is to be, is recorded as anomalous event by described prediction touch event.
10. device according to claim 9, is characterized in that, also comprises:
The 5th judge module, for judging whether the frequency of described anomalous event is greater than predeterminated frequency threshold value;
The first determination module, in the situation that the result of described the 5th judge module is no, is defined as default higher-order function model on the event prediction model using when trigger event is predicted flow process next time;
The second determination module, in the situation that the result of described the 5th judge module is to be, the event prediction model using during using default linear function model as the flow process of trigger event prediction next time.
11. devices according to claim 8, is characterized in that, described current touch event is stored in event queue, also comprises:
Remove module, for removing all touch events of described event queue.
12. according to the device described in claim 7～11 any one, it is characterized in that, also comprises:
Adjusting module, adjusts the described default touch time interval for the cpu load situation according to described Android system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410288685.4A CN104035714B (en) | 2014-06-24 | 2014-06-24 | Event processing method, device and equipment based on Android system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410288685.4A CN104035714B (en) | 2014-06-24 | 2014-06-24 | Event processing method, device and equipment based on Android system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104035714A true CN104035714A (en) | 2014-09-10 |
| CN104035714B CN104035714B (en) | 2017-05-03 |
Family
ID=51466497
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410288685.4A Active CN104035714B (en) | 2014-06-24 | 2014-06-24 | Event processing method, device and equipment based on Android system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104035714B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105912319A (en) * | 2016-03-31 | 2016-08-31 | 百度在线网络技术（北京）有限公司 | Method and device for reverse control over pages of mobile terminals |
| CN108055405A (en) * | 2017-12-26 | 2018-05-18 | 北京传嘉科技有限公司 | Wake up the method and terminal of terminal |
| CN112748845A (en) * | 2019-10-31 | 2021-05-04 | 屈国栋 | Control method and device, electronic equipment and display system |
| WO2021190314A1 (en) * | 2020-03-25 | 2021-09-30 | 华为技术有限公司 | Sliding response control method and apparatus of touch screen, and electronic device |
| CN114103845A (en) * | 2022-01-25 | 2022-03-01 | 星河智联汽车科技有限公司 | Vehicle central control screen operator identity recognition method and device and vehicle |
| CN116909433A (en) * | 2023-09-12 | 2023-10-20 | 宁波普瑞均胜汽车电子有限公司 | Touch event detection method, device and system and computer equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080041639A1 (en) * | 1998-01-26 | 2008-02-21 | Apple Inc. | Contact tracking and identification module for touch sensing |
| CN102609130A (en) * | 2010-12-29 | 2012-07-25 | 微软公司 | Touch event anticipation in a computing device |
| CN102622127A (en) * | 2011-02-12 | 2012-08-01 | 微软公司 | Prediction-based touch contact tracking |
| CN103403665A (en) * | 2012-08-29 | 2013-11-20 | 华为终端有限公司 | Instruction-obtaining method for a terminal device and terminal device |
-
2014
- 2014-06-24 CN CN201410288685.4A patent/CN104035714B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080041639A1 (en) * | 1998-01-26 | 2008-02-21 | Apple Inc. | Contact tracking and identification module for touch sensing |
| CN102609130A (en) * | 2010-12-29 | 2012-07-25 | 微软公司 | Touch event anticipation in a computing device |
| CN102622127A (en) * | 2011-02-12 | 2012-08-01 | 微软公司 | Prediction-based touch contact tracking |
| CN103403665A (en) * | 2012-08-29 | 2013-11-20 | 华为终端有限公司 | Instruction-obtaining method for a terminal device and terminal device |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105912319A (en) * | 2016-03-31 | 2016-08-31 | 百度在线网络技术（北京）有限公司 | Method and device for reverse control over pages of mobile terminals |
| CN108055405A (en) * | 2017-12-26 | 2018-05-18 | 北京传嘉科技有限公司 | Wake up the method and terminal of terminal |
| CN112748845A (en) * | 2019-10-31 | 2021-05-04 | 屈国栋 | Control method and device, electronic equipment and display system |
| WO2021190314A1 (en) * | 2020-03-25 | 2021-09-30 | 华为技术有限公司 | Sliding response control method and apparatus of touch screen, and electronic device |
| CN114103845A (en) * | 2022-01-25 | 2022-03-01 | 星河智联汽车科技有限公司 | Vehicle central control screen operator identity recognition method and device and vehicle |
| CN114103845B (en) * | 2022-01-25 | 2022-04-15 | 星河智联汽车科技有限公司 | Vehicle central control screen operator identity recognition method and device and vehicle |
| CN116909433A (en) * | 2023-09-12 | 2023-10-20 | 宁波普瑞均胜汽车电子有限公司 | Touch event detection method, device and system and computer equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104035714B (en) | 2017-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104035714A (en) | Event processing method, device and equipment based on Android system | |
| US20140359538A1 (en) | Systems and methods for moving display objects based on user gestures | |
| CN109857303B (en) | Interaction control method and device | |
| US20100315439A1 (en) | Using motion detection to process pan and zoom functions on mobile computing devices | |
| EP3133481B1 (en) | Terminal device display method and terminal device | |
| CN111831182B (en) | Application icon control method and device and electronic equipment | |
| TW201543342A (en) | Electronic apparatus and drawing method and computer products thereof | |
| CN109144309B (en) | Touch control method and device, storage medium and terminal equipment | |
| CN109144370A (en) | A kind of screenshotss method, apparatus, terminal and computer-readable medium | |
| CN105824491A (en) | Split screen processing method and device in mobile equipment | |
| CN104461312A (en) | Display control method and electronic equipment | |
| CN104267812B (en) | A kind of information processing method and electronic equipment | |
| US11069019B2 (en) | Multi-threaded asynchronous frame processing | |
| CN112433693A (en) | Split screen display method and device and electronic equipment | |
| CN113176841A (en) | Floating window display method and device, electronic equipment and readable storage medium | |
| CN104699535B (en) | A kind of information processing method and electronic equipment | |
| CN112764611A (en) | Application program control method and device and electronic equipment | |
| CN105892895A (en) | Multi-finger sliding gesture recognition method and device as well as terminal equipment | |
| US20140331238A1 (en) | Electronic device and method for controlling application to execute input command | |
| CN112269501A (en) | Icon moving method and device and electronic equipment | |
| CN104049867A (en) | Information processing method and electronic device | |
| CN105511772B (en) | The method, device and mobile terminal for touching on-screen button are triggered by gesture operation | |
| CN103226440A (en) | System and method for unlocking electronic equipment | |
| CN108021313B (en) | Picture browsing method and terminal | |
| CN114416264A (en) | Message display method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20190822 Address after: 401120, Chongqing, Yubei District, Xiantao street, No. 19 East Valley Road Patentee after: Zhongke Chuang Da (Chongqing) Automotive Technology Co., Ltd. Address before: 100191 Beijing Haidian District Lung Cheung Road No. 1 Tai Xiang business building 4 layer 401-409 Patentee before: Thunder Software Technology Co., Ltd. |
|
| TR01 | Transfer of patent right |