CN108021456A - touch event processing method, device and operating system - Google Patents

touch event processing method, device and operating system Download PDF

Info

Publication number
CN108021456A
CN108021456A CN201610974784.7A CN201610974784A CN108021456A CN 108021456 A CN108021456 A CN 108021456A CN 201610974784 A CN201610974784 A CN 201610974784A CN 108021456 A CN108021456 A CN 108021456A
Authority
CN
China
Prior art keywords
touch event
notification message
auxiliary system
auxiliary
window
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.)
Pending
Application number
CN201610974784.7A
Other languages
Chinese (zh)
Inventor
金卓军
朱林法
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Banma Zhixing Network Hongkong Co Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201610974784.7A priority Critical patent/CN108021456A/en
Publication of CN108021456A publication Critical patent/CN108021456A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • 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)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Digital Computer Display Output (AREA)

Abstract

This application discloses a kind of touch event processing method, device and operating system, applied to the operating system comprising main system and auxiliary system.In the application, after main system in operating system obtains touch event, send a notification message, the touch event is responded for determining whether auxiliary system, so as to so that auxiliary system after touch event is obtained, determines whether to respond the touch event according to corresponding notification message.As it can be seen that message channel is opened between main system and auxiliary system, so that main system notifies auxiliary system to respond the touch event, it is achieved thereby that the fusion treatment of the touch event of different system.

Description

Touch event processing method, device and operating system
Technical field
This application involves field of computer technology, more particularly to a kind of touch event processing method, device and operating system.
Background technology
Cloud operating system is also known as cloud OS, is to be used as the operating system supported using cloud computing, cloud storage technology.Cloud operating system Because it can integrate the computing capability of magnanimity and be capable of providing powerful resource allocation ability, future will obtain widely should With.
Cloud operating system not only can be used for traditional desktop system equipment (such as PC) but also suitable for mobile equipment.Based on cloud The application or service of operating system, and application or service based on legacy operating system, it will in cloud operating system frame Operation, this requires cloud operating system frame can be merged the application based on different operating system or service.
At present, in a kind of operating system frame, how to merge the touch event of different sub-systems, at present there has been no Corresponding solution.
The content of the invention
The embodiment of the present application provides a kind of touch event processing method, device and operating system, to be for operation The touch event of different sub-systems in system carries out fusion treatment.
Touch event processing method provided by the embodiments of the present application, applied to the operating system for including two subsystems, institute It is respectively main system and auxiliary system to state two subsystems, the described method includes：Auxiliary system obtains the notification message of main system, if institute State notification message to be used to indicate the auxiliary system response touch event, then the auxiliary system is responded indicated by the notification message Touch event.
Alternatively, auxiliary system obtains the notification message of main system, including：After the auxiliary system obtains touch event, obtain The notification message that main system is sent, the notification message are used to indicate whether the auxiliary system responds the touch event.
Alternatively, the information for being used for identifying touch event is included in the notification message.
Wherein, the information for being used to identify touch event is timestamp, and the timestamp is used to indicate that touch event is sent out The raw time.
Alternatively, the notification message includes the first configured information or the second configured information, first configured information Window for indicating response touch event belongs to the auxiliary system, and second configured information is used to indicate response touch event Window be not belonging to the auxiliary system；First configured information or that the auxiliary system includes according to the notification message Two configured informations, it is determined whether respond the touch event.
Alternatively, after auxiliary system obtains touch event, the notification message that main system is sent is obtained, including：Auxiliary system obtains After first touch event in touch event sequence caused by contact action, what acquisition main system was sent is used to indicate institute State the notification message whether auxiliary system responds the touch event sequence.
Alternatively, auxiliary system obtains the notification message that main system is sent, including：Auxiliary system according to the touch event when Between stab query messages queue, obtain with the timestamp it is matched be used for indicate whether the auxiliary system responds the touch event Notification message；Wherein, the message queue is used to cache the notification message that the main system is sent.
Alternatively, the notification message includes：The attribute information of touch event.
Touch event processing method provided by the embodiments of the present application, applied to the operating system for including two subsystems, institute It is respectively main system and auxiliary system to state two subsystems, the described method includes：Main system determines to ring according to the touch event of acquisition Answer the system belonging to the window of the touch event；If the main system determines to respond belonging to the window of the touch event System supplemented by system, then notify the auxiliary system to respond the touch event.
Alternatively, main system notifies the auxiliary system to respond the touch event, including：The main system is to the auxiliary system System sends the first notification message, and first notification message includes the first configured information, and first configured information is used to refer to Show that the system belonging to the window for responding the touch event is auxiliary system.
Alternatively, further included in first notification message：For identifying the information of the touch event.
Alternatively, the information for being used to identify the touch event, including：Timestamp, the timestamp are used to indicate The time that the touch event occurs.
Alternatively, the touch event is the first touch thing in touch event sequence caused by a contact action Part；First notification message is used to indicate that the auxiliary system responds touch event sequence caused by the contact action.
Alternatively, further include：If the system that the main system determines to respond belonging to the window of the touch event is principal series System, then touch event described in the host system response, and prevent the auxiliary system from responding the touch event.
Alternatively, the main system prevents the auxiliary system from responding the touch event, including：The main system is to described Auxiliary system sends second notification message, and the second notification message includes the second configured information, and second configured information is used The system belonging to window in the instruction response touch event is not auxiliary system.
Alternatively, further included in the second notification message：For identifying the information of the touch event.
Alternatively, the information for being used to identify the touch event, including：Timestamp, the timestamp are used to indicate The time that the touch event occurs.
Alternatively, the touch event is the first touch thing in touch event sequence caused by a contact action Part；The second notification message is used to prevent the auxiliary system from responding touch event sequence caused by the contact action.
Alternatively, main system notifies the auxiliary system to respond the touch event, including：The main system is to the auxiliary system System sends third notice message, and the third notice message includes：The attribute information of touch event.
The input management service unit that the application further embodiment provides, applied to the operation system comprising two subsystems System, described two subsystems are respectively main system and auxiliary system, and the input management service unit is located in the auxiliary system, institute Stating input management service unit includes：Acquisition module, for obtaining the notification message of main system；Indicating module, for described When notification message is used to indicate the auxiliary system response touch event, the instruction auxiliary systematic difference responds the notification message Indicated touch event.
Alternatively, the acquisition module is specifically used for：After obtaining touch event, the notification message that main system is sent is obtained, The notification message is used to indicate whether the auxiliary system responds the touch event.
Alternatively, the information for being used for identifying touch event is included in the notification message.
Alternatively, the information for being used to identify touch event is timestamp, and the timestamp is used to indicate touch event The time of generation.
Alternatively, the notification message includes the first configured information or the second configured information, first configured information Window for indicating response touch event belongs to the auxiliary system, and second configured information is used to indicate response touch event Window be not belonging to the auxiliary system；The determining module is specifically used for：The first instruction included according to the notification message Information or second configured information, it is determined whether respond the touch event.
Alternatively, the acquisition module is specifically used for：Obtain in touch event sequence caused by a contact action After first touch event, obtain main system transmission is used to indicate whether the auxiliary system to respond the logical of the touch event sequence Know message.
Alternatively, the acquisition module is specifically used for：According to the timestamp query messages queue of the touch event, obtain It is matched for indicating whether the auxiliary system responds the notification message of the touch event with the timestamp；Wherein, it is described to disappear Breath queue is used to cache the notification message that the main system is sent.
Alternatively, the notification message includes：The attribute information of touch event.
The input management service unit that the application further embodiment provides, applied to the operation system comprising two subsystems System, described two subsystems are respectively main system and auxiliary system, and the input management service unit is located in the main system, institute Stating input management service unit includes：Determining module, for the touch event according to acquisition, determines the response touch event System belonging to window；Notification module, is for determining to respond in the determining module belonging to the window of the touch event Supplemented by system during system, the auxiliary system is notified to respond the touch event.
Alternatively, the notification module is specifically used for：The first notification message, first notice are sent to the auxiliary system Message includes the first configured information, and first configured information is belonging to the window of the touch event for indicating to respond System is auxiliary system.
Alternatively, further included in first notification message：For identifying the information of the touch event.
Alternatively, the information for being used to identify the touch event, including：Timestamp, the timestamp are used to indicate The time that the touch event occurs.
Alternatively, the touch event is the first touch thing in touch event sequence caused by a contact action Part；First notification message is used to indicate that the auxiliary system responds touch event sequence caused by the contact action.
Alternatively, the notification module is additionally operable to：If the determining module determines to respond the window institute of the touch event The system of category is main system, then notifies the application in the main system to respond the touch event, and notify the auxiliary system with The auxiliary system is prevented to respond the touch event.
Alternatively, the notification module is specifically used for：Second notification message, second notice are sent to the auxiliary system Message includes the second configured information, and second configured information is belonging to the window of the touch event for indicating to respond System is not auxiliary system.
Alternatively, further included in the second notification message：For identifying the information of the touch event.
Alternatively, the information for being used to identify the touch event, including：Timestamp, the timestamp are used to indicate The time that the touch event occurs.
Alternatively, the touch event touches for first first in touch event sequence caused by a contact action Event, first touch event are triggered when finger is put into and touches on screen；The second notification message is used to prevent described Auxiliary system responds touch event sequence caused by the contact action.
Alternatively, the notification module is specifically used for：Third notice message, the third notice are sent to the auxiliary system Message includes：The attribute information of touch event.
Operating system provided by the embodiments of the present application, including：Main system, for determining to respond according to the touch event of acquisition System belonging to the window of the touch event, however, it is determined that system supplemented by the system belonging to the window of the touch event is responded, The auxiliary system is then notified to respond the touch event；Auxiliary system, for getting the described for indicating of main system transmission After the notification message of auxiliary system response touch event, the touch thing according to indicated by the notification message responds the notification message Part.
Alternatively, the main system includes main system input management service, and the auxiliary system includes auxiliary system input Management service, being established between the main system input management service and the auxiliary system input management service has message channel；Institute Main system input management service is stated, for being according to belonging to the touch event of acquisition determines to respond the window of the touch event System, however, it is determined that the system responded belonging to the window of the touch event is the auxiliary system, then sends the first notification message, described First notification message includes the first configured information, and first configured information is used to indicate the window for responding the touch event Affiliated system is auxiliary system, however, it is determined that the system responded belonging to the window of the touch event is the main system, then sends Second notification message, the second notification message include the second configured information, and second configured information is used to indicate to respond System belonging to the window of the touch event is not auxiliary system；The auxiliary system input management service, for getting When notification message includes the first configured information, the auxiliary systematic difference is notified to respond the touch event, what is got When notification message includes the second configured information, abandon notifying the auxiliary systematic difference to respond the touch event.
Alternatively, the auxiliary system input management service is specifically used for：Obtain and thing is touched caused by a contact action After first touch event in part sequence, what acquisition main system was sent is used to indicate whether the auxiliary system responds the touch thing The notification message of part；If including the first configured information in the notification message got, the auxiliary systematic difference response is notified Touch event sequence caused by the contact action；If including the second configured information in the notification message got, abandon The auxiliary systematic difference is notified to respond touch event sequence caused by the contact action.
Alternatively, the information for being used for identifying touch event is included in the notification message.
Alternatively, the information for being used to identify touch event is timestamp, and the timestamp is used to indicate touch event The time of generation.
Alternatively, the auxiliary system input management service, is specifically used for：Disappeared according to the inquiry of the timestamp of the touch event Queue is ceased, is obtained matched for indicating whether the auxiliary system responds the notification message of the touch event with the timestamp； Wherein, the message queue is used to cache the notification message that the main system is sent.
Alternatively, the main system input management service is specifically used for：After obtaining touch event, however, it is determined that response is described to touch System supplemented by the system belonging to the window of event is touched, then sends third notice message, institute to the auxiliary system input management service State third notice message to be used to indicate that the auxiliary system responds the touch event, the third notice message includes：Touch The attribute information of event；If it is determined that it is main system to respond the system belonging to the window of the touch event, then main system is notified Using the response touch event；The auxiliary system input management service is specifically used for：According to the third notice received Message, notifies the auxiliary systematic difference to respond the touch event indicated by the notification message.
Terminal provided by the embodiments of the present application, including：Memory, for storing computer program instructions；
Processor, is coupled to the memory, for reading the computer program instructions of the memory storage, and conduct Response, performs following operation：Main system in operating system determines to respond the touch event according to the touch event of acquisition System belonging to window, however, it is determined that respond system supplemented by the system belonging to the window of the touch event, then notify the auxiliary system System responds the touch event；Auxiliary system in operating system is used to indicate that the auxiliary system to be rung get main system transmission After the notification message for answering touch event, the touch event according to indicated by the notification message responds the notification message.
In above-described embodiment of the application, after the main system in operating system obtains touch event, send a notification message, if The notification message is used to indicate auxiliary system response touch event, then auxiliary system responds the touch event indicated by the notification message. As it can be seen that message channel has been opened between main system and auxiliary system, so that main system notifies auxiliary system to respond the touch event, so that Realize the fusion treatment of the touch event of different system.
Brief description of the drawings
Fig. 1 is the touch event process flow schematic diagram under triangular web framework in the prior art；
Fig. 2 is YunOS dual systems configuration diagram of the prior art；
Fig. 3 is the touch event schematic diagram under YunOS dual systems framework of the prior art；
Fig. 4 a and Fig. 4 b are respectively the operation for having in scheme one provided by the embodiments of the present application Host/Guest dual systems System architecture schematic diagram；
Fig. 5 a and Fig. 5 b are respectively the touch event process flow schematic diagram in scheme one provided by the embodiments of the present application；
Fig. 6 is an example schematic in scheme one provided by the embodiments of the present application；
Fig. 7 a and Fig. 7 b are respectively the processing of the Host subsystems and Guest subsystems in the scheme one of the embodiment of the present application Flow diagram；
Fig. 8 a and Fig. 8 b are respectively the operation for having in scheme two provided by the embodiments of the present application Host/Guest dual systems System architecture schematic diagram；
Fig. 9 a and Fig. 9 b are respectively the touch event process flow schematic diagram in scheme one provided by the embodiments of the present application；
Figure 10 is the structure diagram of the input service managing apparatus in main system provided by the embodiments of the present application；
Figure 11 is the structure diagram of the input service managing apparatus in auxiliary system provided by the embodiments of the present application；
Figure 12 is the structure diagram of touch apparatus provided by the embodiments of the present application.
Embodiment
Touch event (touch event) is when user's finger is placed on and touches on screen, when sliding on the screen, or from screen Triggered when being removed on curtain.For example, (HTML is the English abbreviation of Hyper Text Mark-up Language to HTML5, is surpassed Text mark up language) include with the relevant several common touch events of touch apparatus defined in specification：
touchstart：Put when finger and trigger on the screen；
touchmove：When finger slides on the screen, continuously trigger；
touchend：Triggered when finger leaves from screen.
It should be noted that event title of the above-mentioned touch event in different standards may be different.Such as Touchstart events are alternatively referred to as touchdown events.
In the operating system framework of triangular web, typical touch event process flow can be abstracted into shown in Fig. 1.
As shown in Figure 1, when user's finger is operating on touching screen, the hardware of touch apparatus captures the touch operation Afterwards, the input equipment driving (English is Input Device Driver) in system kernel, which generates touch event and is sent to, is Input management service (English is Input Manager Service) in system, input management service read the touch event, will The touch event is transmitted to focus window by interprocess communication (Inter-process communication, abbreviation IPC) mechanism The application program at place.Here the window of the expected response touch event in focus window, that is, user interface.Wherein, in system Window management service (English is Windows Manager Service) be responsible for being managed the window of application program, than Such as manage window stack.Window management service can service to input processing and provide focus window information, so that input processing service Application program touch event being sent to where focus window.
Cloud operating system not only can be used for traditional desktop system equipment (such as PC) but also suitable for mobile equipment, it is necessary to simultaneous Hold the application program based on the exploitation of different Mobile operating systems.YunOS is a kind of cloud operating system, by taking YunOS as an example, in order to Provide more naturally smooth experience transition to the user, YunOS employs primary/secondary dual system framework.Wherein, main system becomes Host subsystems, auxiliary system become Guest subsystems, and Guest subsystems are used for compatible existing Android applications.
Fig. 2 schematically illustrates the dual system framework of YunOS, wherein illustrate only and the relevant composition portion of the application Point.As shown in the figure, in the framework of primary/secondary dual system, two subsystems have respective input management service, and (English is Input Manager Service).From the driving of the input equipment of lower floor, (English is the input management service of two subsystems Input Device Driver) touch event is read, handled, touch event is sent to where focus window and applies journey Sequence.Main system (the Host subsystems in figure) and auxiliary system (the Guest subsystems in figure) also have respective window management service (English is Windows Manager Service).Window management service in main system is main window management service, management master All windows of system and auxiliary system；Window management service supplemented by window management service in auxiliary system, is only responsible for auxiliary system System window.
In above-mentioned dual system framework, if same touch event is handled at the same time by two subsystems, punching is likely to result in It is prominent.As an example, as shown in figure 3, main system (Host subsystems) window 301 is non-full screen window, it is covered in auxiliary system Above (Guest subsystems) window 302, auxiliary system windows 302 are more than main system window 301.If user is in main system at this time Carry out slide on window 301, produce touch event, then can cause following auxiliary system windows 302 and main system above Window 301 responds the touch event at the same time, violates user's operation and it is expected.Window management service because supplemented by system only manages auxiliary System windows, it is believed that user is operated to the focus window of auxiliary system, although in this way, auxiliary system windows are by main system Window local complexity, but the touch event acted on main system window can be also responded, lead to a conflict.
For touch apparatus, main user input comes from screen touch, therefore how to merge two subsystems Touch event, is current urgent problem to be solved.
To solve the above-mentioned problems, the embodiment of the present application is proposed draws in the incoming event management service of two subsystems Enter synchronization mechanism, i.e., message channel is established between different sub-systems, a subsystem is after touch event is obtained, however, it is determined that ring Should the window of touch event belong to the application of another subsystem, then another subsystem can be notified to ring by the message channel Should touch event, so as to realize the fusion of touch event under multisystem framework.
In the embodiment of the present application, above application can be that system application can also be user application, can be with It is serviced component.By using exemplified by YunOS operating systems, application component shows as Page forms.Page be to local service and The elementary cell that is abstract, namely servicing of remote service, by the encapsulation to data and method, can provide various services.One A service scenarios can include multiple Page.For example, a Page can be UI (user interface), the service of taking pictures etc., Can be background service, such as account authentication.Each Page can be uniquely identified in YunOS.
The embodiment of the present application can be applied to touch apparatus.The touch apparatus can be specifically to support touch input mode Mobile terminal or equipment, the mobile terminal such as PC (PC) can be mobile phone, PDA (Personal Digital Assistant, palm PC) car-mounted terminal or intelligent wearable device etc..
According to whether each subsystem can obtain touch event, the embodiment of the present application provides two kinds of solutions：
Scheme one：Each subsystem can obtain touch event, and for such a situation, in main system side, main system obtains After touch event, determine to respond the subsystem belonging to the window of the touch event；If it is determined that respond the window of the touch event System supplemented by affiliated subsystem, then send the first notification message, to indicate that auxiliary system responds the touch event to auxiliary system；Such as The subsystem that fruit determines to respond belonging to the window of the touch event is main system, then the host system response touch event, and to Auxiliary system sends second notification message, to prevent auxiliary system from responding the touch event.In auxiliary system side, auxiliary system is being touched After event, the notification message that is sent according to main system, determines that responding the touch event is also to give up responding the touch event, and Respective handling is carried out according to the result determined.
Scheme two：Only a subsystem can obtain touch event, and for kind of a situation, main system obtains touch event Afterwards, determine to respond the subsystem belonging to the window of the touch event；If it is determined that respond the son belonging to the window of the touch event System supplemented by system, then send third notice message, to indicate that auxiliary system responds the touch event to auxiliary system；If it is determined that It is main system to respond the subsystem belonging to the window of the touch event, then the host system response touch event.It is auxiliary in auxiliary system side The third notice message that system is sent according to main system, the touch event responded to indicated needs are handled.
Wherein, main system can respond the touch event of main system window and auxiliary system windows, and auxiliary system can only be rung Answer the touch event of auxiliary system windows.In cloud operating system, main system is Host subsystems, and auxiliary system is Guest subsystems.
Below by taking the operating system with Host/Guest dual system frameworks as an example, with reference to attached drawing to above two solution party Case is described respectively.
Scheme one
It is respectively that there is Host/Guest dual systems in scheme one provided by the embodiments of the present application referring to Fig. 4 a and Fig. 4 b Operating system Organization Chart.
As shown in fig. 4 a, can be obtained in Host subsystems and Guest subsystems from the input equipment driving in system kernel Obtain touch event.Being established between Host subsystems and Guest subsystems has message channel, and by the passage, Host subsystems can Send a notification message to Guest subsystems, to notify Guest subsystem responses touch event or prevent Guest subsystems from ringing Answer touch event.
More specifically, as shown in Figure 4 b, above-mentioned message channel can be established defeated in Host subsystems and Guest subsystems Enter between management service.That is, the Host/Guest dual systems shown in Fig. 4 b compared with the Host/Guest dual systems shown in Fig. 2, Being established between the input management service of Host subsystems and the input management service of Guest subsystems has message channel.
There is the incoming event management service of oneself in Host subsystems and Guest subsystems, can be from system kernel Input equipment driving obtain touch event.Host/Guest dual systems shown in Fig. 4 a and Fig. 4 b and the Host/ shown in Fig. 2 Guest dual systems are compared, and are established between the input management service of Host subsystems and the input management service of Guest subsystems There is message channel, by the passage, Host subsystems can send a notification message to Guest subsystems, to notify Guest subsystems Respond touch event or prevent Guest subsystem responses touch events.
The message channel can use IPC mechanism to realize.More specifically, the IPC channel can be local with operating system Socket is realized.Two application programs realize the exchange of data by two-way communication connection, and one end of this connection is known as one A socket.Socket is also known as " socket ", and application program usually sends request to Correspondent Node by " socket " or should Answer the request of Correspondent Node.
Referring to Fig. 5 a, for the touch event process flow of Host subsystems side in scheme one provided by the embodiments of the present application. As shown in the figure, the flow may include that (the Host subsystems in below scheme can be replaced main system, Guest subsystems to following steps System supplemented by system is replaceable)：
Step 501：Host subsystems obtain touch event.
In the step, when the finger of user is operating on the touch screen of touch apparatus, which is touched by this Equipment captures, and the input equipment driving in the operating system nucleus of the touch apparatus produces touch event, and by the touch of generation Event is sent to Host subsystems and Guest subsystems.More specifically, the touch event of generation is distinguished in input equipment driving Input management service in the input management service and Guest subsystems that are sent in Host subsystems.
According to operation of the finger of user on screen is touched, it can also be bag that caused touch event, which can be one, Touch event sequence containing multiple touch events.For example, if the finger of user is clicked on screen is touched, 2 touch events are then produced, according to time of origin order from front to back, this 2 touch events are respectively touchstart events With touchend events.Again for example, if the finger of user slides on screen is touched, a touch thing is produced Part sequence, according to time of origin order from front to back, the touch event sequence include：Touchstart events, continuous trigger A series of touchmove events and touchend events.User screen touch operation can be singly refer to operation can also It is multifingered manipulation, if multifingered manipulation, it is likely that produce multiple touchstart events.No matter the screen touch of user is grasped Work is singly to refer to operation or multifingered manipulation, or what is carried out is that what type of screen touch operates, caused touch thing A touchstart event (multiple touchstart events are included in the case of multifingered manipulation) is included at least in part.
Step 502：Host subsystems determine to respond the subsystem belonging to the window of the touch event.
In the step, since the window management service in Host subsystems is responsible in Host subsystems and Guest subsystems All application windows management, therefore can determine that the subsystem belonging to the window of the touch event acquired.
Determine to respond the process of the subsystem belonging to the window of the touch event, namely focus is determined according to the touch event The process of window.Qualified window can be chosen from window stack according to the touch event and focus window selection strategy Mouthful, as focus window.For example if the corresponding touch operation of touchstart events acts on touching in Guest subsystems Touch in window and the window is top-level windows, then the Guest subsystem windows are focus window.
Step 503：If the subsystem that Host subsystems determine to respond belonging to the window of the touch event is Guest subsystems System, then be transferred to step 504；If Host subsystems determine that the subsystem belonging to the window of the touch event is Host subsystems, Then it is transferred to step 505.
Step 504：Host subsystems send the first notification message to Guest subsystems, for notifying Guest subsystems to ring Should touch event.
Wherein, the first configured information can be included in the first notification message, for indicating belonging to the window of response touch event Subsystem be Guest subsystems.
Further, the information for being used for identifying touch event can be also included in the first notification message.Alternatively, which can To be timestamp, for indicating the time of touch event generation.Since the time that different touch events occurs differs, then may be used With the time unique mark touch event occurred by touch event.
Step 505：The Host subsystem responses touch event, and second notification message is sent to Guest subsystems, it is used for Prevent the Guest subsystem responses touch event.
Wherein, the second configured information can be included in second notification message, for indicating belonging to the window of response touch event Subsystem be not Guest subsystems.
Further, the information for being used for identifying touch event can be also included in second notification message.Alternatively, which can To be timestamp, for indicating the time of touch event generation.
For example, above-mentioned first notification message and second notification message can use the socket of Host subsystems to realize, it is therein Message body may include two parts content：
-timestamp：Timestamp, can be with integer numerical value, and length is 64；
-is_guest：Configured information, can be Boolean type numerical value, and length is 32.The value of the configured information is used for table Whether the subsystem belonging to the window of bright response touch event is Guest subsystems, for example, when is_guest values are true When, the subsystem for showing to respond belonging to the window of touch event is Guest subsystems；When is_guest values are false, table Subsystem belonging to the window of bright response touch event is Host subsystems.
In certain embodiments, the touch event described in above-mentioned flow can be touched caused by a contact action Sequence of events.
Switching in view of focus window only be able to can just occur in first finger contact screen.First finger without departing from In the case of screen, if other fingers continue contact screen, then subsequent touch event can be sent to first finger and touch institute really Fixed focus window.Therefore, during each first finger contact screen, Host subsystems carry out focus window with Guest subsystems The determination process of mouth.Therefore, in further embodiments, alternatively, in step 501~step 502, Host subsystems are obtaining After touch event sequence caused by contact action, first touch event in the touch event sequence is (i.e. first The touch event of a finger, is touchstart events in this example), determine to respond belonging to the window of the touchstart events Subsystem.Correspondingly, in step 504, Host subsystems send the first notification message to Guest subsystems, for notifying Touch event sequence caused by the Guest subsystem responses contact action；In step 505, Host subsystems are sub to Guest System sends second notification message, for preventing touch event sequence caused by the Guest subsystem responses contact action.
As an example, the value of the first notification message and the timestamp in second notification message are touch events The time that first touchstart event occurs in sequence.The value of is_guest in first notification message is true, the The value of is_guest in two notification messages is false.
Referring to Fig. 5 b, for the touch event process flow of Guest subsystems side in scheme one provided by the embodiments of the present application. As shown in the figure, the flow may include following steps：
Step 511：Guest subsystems obtain touch event.
In the step, when the finger of user is operating on the touch screen of touch apparatus, which is touched by this Equipment captures, and the input equipment driving in the operating system nucleus of the touch apparatus produces touch event, and by the touch of generation Event is sent to Guest subsystems and Host subsystems.More specifically, the touch event of generation is distinguished in input equipment driving Input management service in the input management service and Host subsystems that are sent in Guest subsystems.According to the hand of user Refer to the operation on screen is touched, it can also be the touch for including multiple touch events that caused touch event, which can be one, Sequence of events.
Step 512：Whether Guest subsystems judge the touch event by Guest subsystems according to the notice of Host subsystems System is responded, if so, being then transferred to step 513, is otherwise transferred to step 514.
In the step, since Host subsystems and Guest subsystems can obtain touch event, and Host subsystems can be true Make the subsystem belonging to the window for responding the touch event and notify to give Guest subsystems, therefore Guest subsystems can basis What Host subsystems were sent is directed to the notification message of touch event obtained in step 511, judge the touch event whether by Guest subsystems are responded.
When it is implemented, the information for being used for identifying touch event, Guest are included in the notification message that Host subsystems are sent Subsystem can obtain accordingly Host subsystems transmission be used for indicate whether Guest subsystems respond obtained touch event Notification message.
Step 513：The Guest subsystem responses touch event.
Step 514：Guest subsystems are abandoned responding the touch event.
Further, it is contemplated that the capture of touch operation, the generation of touch event and relevant processing procedure need one Fixed response time, therefore the notification message that Guest subsystems can send Host subsystems is cached to message queue, when Guest After system obtains touch event, the notification message corresponding to the touch event that can cache in query messages queue, according to inquiry To notification message determine whether to respond the touch event.
As it was previously stated, the information for identifying touch event is timestamp, the time occurred for indicating touch event.Phase After Ying Di, Guest subsystem obtain touch event, in the time inquiring message queue occurred according to the touch event Timestamp values are the notification message of the time value, if inquiring qualified notification message, are disappeared according to the notice The value of is_guest in breath, judges whether the touch event acquired by Guest subsystem responses.
In certain embodiments, the touch event described in above-mentioned flow can be touched caused by a contact action Sequence of events.
In further embodiments, alternatively, in step 511~step 512, Guest subsystems are obtaining a touch screen After touch event sequence caused by operation, first touch event in the touch event sequence be (i.e. first finger Touch event, is touchstart events in this example) notice of time for occurring and Host subsystems, judge the touch thing Whether part sequence is responded by Guest subsystems.
Exemplified by including timestamp and is_guest in notification message, the value of the timestamp in notification message is The time that first touchstart event occurs in touch event sequence.The value of is_guest in notification message is true Or false.Correspondingly, after Guest subsystems obtain touch event sequence, according to first in the touch event sequence The time that touthstart events occur, timestamp values are the notification message of the time value in query messages queue, according to The value of is_guest in the notification message inquired, judges whether the touch event acquired by Guest subsystem responses Sequence.
Fig. 6 schematically illustrates the schematic diagram that touch event processing is carried out based on message queue.Wherein, one of user Finger is placed on the screen of touch apparatus and falls into the window of Host subsystem applications, the touchstart event quilts of generation Input management service in Host subsystems and Guest subsystems obtains.
Host subsystems side, the subsystem that input management service determines to respond belonging to the window of the touchstart events are Host subsystems, therefore the focus window that the touchstart events are sent in Host subsystems is responded, and to Guest subsystems send a notification message, to prevent the Guest subsystem responses touch event.In the notification message Timestamp is the time that the touchstart events occur, and is_guest values are false.
Guest subsystems side, the time that input management service occurs according to the touchstart events, team is cached from message Obtain the notification message that timestamp values are the time value in row, the value of the is_guest in the notification message, really Surely it need not be responded by Guest subsystems, therefore abandon responding the touchstart events.
Hereafter, the finger of user slides on the screen of touch apparatus, and the touchmove events of generation are by Host subsystems Obtained with the input management service in Guest subsystems.
Host subsystems side, after input management service obtains touchmove events, since focus window switching not occurring, The application where being sent to current focus window is then kept to be handled.
Guest subsystems side, after input management service obtains touchmove events, since focus window switching not occurring, Then keep abandoning the touchmove events that processing acquires.
By above description as can be seen that in above-described embodiment of the application, after main system obtains touch event, determine to ring Subsystem that should be belonging to the window of touch event, if the subsystem that main system determines to respond described in the window of the touch event is Auxiliary system, then notify auxiliary system to respond the touch event, otherwise prevents auxiliary system from responding the event.As it can be seen that main system and auxiliary system Message channel has been opened between system, so that main system notifies whether auxiliary system responds the touch event acquired, it is achieved thereby that The fusion treatment of the touch event of different sub-systems.
It is right respectively with reference to Fig. 7 a and Fig. 7 b in order to be more clearly understood that the scheme one of the above embodiments of the present application offer The flow of Host subsystems side and the flow of Guest subsystems side illustrate.Alternatively, in actual realization, can be related to leading to Believe channel initialization and fault-tolerant processing etc..
As shown in Figure 7a, in Host subsystems side, step 701, input management service creates local in initialization Socket listening ports and the poll filec descriptor set for adding major cycle.Then, in step 702 to step 703, reception is worked as During the connection request sent to Guest subsystems, Host subsystems receive the request and establish the letter that communicates with Guest subsystems Road.
As shown in step 704 to step 706, whenever there is an event, and the finger is first touch During finger (touch event currently acquired is the first touchstart events in a contact action), according to focus window Mouthful selection strategy, qualified top window in selected window storehouse, and record whether the window is Guest subsystems Window.Host subsystems by the timestamp of the touchstart events with whether be the information package of Guest subsystem windows simultaneously Input management service from the traffic channel between Guest subsystems to Guest subsystems.
Wherein, the process of qualified top window is chosen from window stack according to focus window selection strategy, As determine the process of focus window.The embodiment of the present application is not restricted used focus window selection strategy.Focus window Mouth occurs when switching in first finger contact screen.In the case where first finger is without departing from screen, if other fingers Continue contact screen, then subsequent touch event, which can be sent to, touches determined focus window based on first finger.Therefore, every time During first finger contact screen, Host subsystems carry out the determination process of focus window with Guest subsystems.
As shown in Figure 7b, in Guest subsystems side, such as step 711 to step 713, input management service is in initialization Attempt the input management service of connection Host subsystems.If successful connection, the communication channel between Host subsystems is established. The notification message received from the communication channel is cached in message queue by Guest subsystems.
As shown in step 714 to step 718, whenever there is an event, and the finger is first touch (touch event currently acquired is the first touchstart events in a contact action), Guest subsystems during finger System reads the notification message cached in message buffer queue, and the timestamp in notification message judges that institute is right in notification message Answer whether touch event is the touchstart events currently obtained, and corresponding operating is carried out according to judging result.Specifically, sentence Disconnected result and corresponding operation may include following three kinds of situations：
Situation 1：If the time of the timestamp instruction in notification message earlier than the time that current touchsrart events occur, Then represent not read also the event information of needs, then continue to read next notification message from message buffer queue.
Situation 2：If the time of the timestamp instruction in notification message is later than the time that current touchstart events occur, Then represent that existing event is lost, then return to default value.So do primarily to fault-tolerant, prevent the system shape when there is event loss State malfunctions.
Situation 3：If the time phase that the time of the timestamp instruction in notification message occurs with current touchstart events Together, then it represents that the current event information for having read needs, then take out the is_guest in the notification message, as whether can be with Foundation using Guest subsystems window as focus window.For example if the value of is_guest is ture, show Guest System windows are focus window, i.e., by Guest subsystem responses touch events；If the value of is_guest is false, show Host subsystems window is focus window, and Guest subsystems abandon response touch event.
Further, as shown in step 716 to step 717, in order to strengthen robustness, when in notification message reading process It was found that the communication channel between Host subsystems is already off, then default value is returned to after carrying out cleaning work.Next time into Enter and the input management service for reconnecting Host subsystems is attempted when circulating.
Scheme two
It is respectively that there is Host/Guest dual systems in scheme one provided by the embodiments of the present application referring to Fig. 8 a and Fig. 8 b Operating system Organization Chart.
As shown in Figure 8 a, Host subsystems can obtain touch event from the input equipment driving in system kernel, and input is set Standby driving does not send touch event to Guest subsystems.Being established between Host subsystems and Guest subsystems has message channel, By the passage, Host subsystems can send a notification message to Guest subsystems, to notify Guest subsystem responses to touch thing Part.
More specifically, as shown in Figure 8 b, above-mentioned message channel can be established defeated in Host subsystems and Guest subsystems Enter between management service.
The message channel can use IPC mechanism to realize.More specifically, the IPC channel can be local with operating system Socket is realized.Two application programs realize the exchange of data by a two-way communication connection, and one end of this connection claims For a socket.Socket be also known as " socket ", application program usually by " socket " to Correspondent Node send request or The request of person's response Correspondent Node.
Referring to Fig. 9 a, for the touch event process flow of Host subsystems side in scheme two provided by the embodiments of the present application. As shown in the figure, the flow may include that (the Host subsystems in below scheme can be replaced main system, Guest subsystems to following steps System supplemented by system is replaceable)：
Step 901：Host subsystems obtain touch event.
The specific implementation of the step can be found in the step 501 in Fig. 5 a, and this will not be detailed here.
Step 902：Host subsystems determine to respond the subsystem belonging to the window of the touch event.
The specific implementation of the step can be found in the step 502 in Fig. 5 a, and this will not be detailed here.
Step 903：If Host subsystems determine that the subsystem belonging to the window of the touch event is Guest subsystems, Then it is transferred to step 904；If Host subsystems determine that the subsystem belonging to the window of the touch event is Host subsystems, turn Enter step 905.
Step 904：Host subsystems send third notice message to Guest subsystems, for notifying Guest subsystems to ring Should touch event.
Wherein, the attribute information of touch event can be included in third notice message.For example, the attribute for tracking touch can Including：
clientX：Touch x coordinate of the target in viewport；
clientY：Touch y-coordinate of the target in viewport；
pageX：Touch x coordinate of the target in the page；
pageY：Touch y-coordinate of the target in the page；
screenX：Touch x coordinate of the target in screen；
screenY：Touch y-coordinate of the target in screen.
Part attribute is only listed above, and the embodiment of the present application is not restricted this.
Step 905：The Host subsystem responses touch event.
In above-mentioned flow, Host subsystems are directed to each touch event acquired, if the event is needed by Guest System is responded, then is sent a notification message to Guest subsystems, wherein the attribute information of the touch event is carried, so that Guest subsystems respond touch event according to the notification message.
Referring to Fig. 9 b, for the touch event process flow of Guest subsystems side in scheme one provided by the embodiments of the present application. As shown in the figure, the flow may include that (the Host subsystems in below scheme can be replaced main system, Guest subsystems to following steps System supplemented by system is replaceable)：
Step 911：Guest subsystems obtain the notification message that Host subsystems are sent.
In the step, specifically, the input management service in Guest subsystems is led to from the message between Host subsystems Road receives notification message, and the notification message of Host subsystems transmission can be also obtained from message buffer queue.Wherein, message caches Queue is used to store the notification message that Host subsystems are sent.
The content of notification message can be found in the associated description in Fig. 9 a, and this will not be detailed here.
Step 912：Guest subsystems respond touch event according to the notification message.
By above description as can be seen that in above-described embodiment of the application, after main system obtains touch event, determine to ring System that should be belonging to the window of touch event, is if main system determines to respond supplemented by the system belonging to the window of the touch event System, then notify auxiliary system to respond the touch event, if main system determines to respond based on the system belonging to the window of the touch event System, then the host system response touch event, is not notified that auxiliary system responds the event.As it can be seen that between main system and auxiliary system Message channel has been opened, so that main system notifies auxiliary system response touch event when definite touch event is responded by auxiliary system, It is achieved thereby that the fusion treatment of the touch event of different sub-systems.
Based on identical technical concept, the embodiment of the present application additionally provides a kind of input management service unit.
Referring to Figure 10, service unit structure diagram is managed for input provided by the embodiments of the present application, which is applied to The operating system of two subsystems is included, described two subsystems are respectively main system and auxiliary system, which fills Setting in above-mentioned main system.As shown in the figure, input management service unit may include：Determining module 1001, notification module 1002, wherein：
Determining module 1001, for the touch event according to acquisition, belonging to the window for determining the response touch event System；Notification module 1002, for determining to respond in the determining module supplemented by the system belonging to the window of the touch event During system, the auxiliary system is notified to respond the touch event.
Alternatively, notification module 1002 can be specifically used for：The first notification message is sent to the auxiliary system, described first is logical Know that message includes the first configured information, first configured information is used to indicate belonging to the window of the response touch event System is auxiliary system.
Alternatively, further included in first notification message：For identifying the information of the touch event.
Alternatively, the information for being used to identify the touch event, including：Timestamp, the timestamp are used to indicate The time that the touch event occurs.
Alternatively, the touch event is the first touch thing in touch event sequence caused by a contact action Part；First notification message is used to indicate that the auxiliary system responds touch event sequence caused by the contact action.
Alternatively, notification module 1002 is additionally operable to：If it is determined that module 1001 determines the window institute of the response touch event The system of category is main system, then notifies the application in the main system to respond the touch event, and notify the auxiliary system with The auxiliary system is prevented to respond the touch event.
Alternatively, notification module 1002 is specifically used for：Second notification message, second notice are sent to the auxiliary system Message includes the second configured information, and second configured information is belonging to the window of the touch event for indicating to respond System is not auxiliary system.
Alternatively, further included in second notification message：For identifying the information of the touch event.
Alternatively, the information for being used to identify the touch event, including：Timestamp, the timestamp are used to indicate The time that the touch event occurs.
Alternatively, the touch event touches for first first in touch event sequence caused by a contact action Event, first touch event are triggered when finger is put into and touches on screen；The second notification message is used to prevent described Auxiliary system responds touch event sequence caused by the contact action.
Alternatively, in a further embodiment, notification module 1002 is specifically used for：Third notice is sent to the auxiliary system Message, the third notice message include：The attribute information of touch event.
Based on identical technical concept, the embodiment of the present application additionally provides a kind of input management service unit.
Referring to Figure 11, service unit structure diagram is managed for input provided by the embodiments of the present application, which is applied to The operating system of two subsystems is included, described two subsystems are respectively main system and auxiliary system, which fills Setting in above-mentioned auxiliary system.As shown in figure 11, input management service unit may include：Acquisition module 1101, indicating module 1102, wherein：
Acquisition module 1101, for obtaining the notification message of main system；Indicating module 1102, in the notification message During for indicating the auxiliary system response touch event, the instruction auxiliary systematic difference is responded indicated by the notification message Touch event.
Alternatively, acquisition module 1101 is specifically used for：After obtaining touch event, the notification message that main system is sent is obtained, The notification message is used to indicate whether the auxiliary system responds the touch event.
Alternatively, the information for being used for identifying touch event is included in the notification message.
Alternatively, the information for being used to identify touch event is timestamp, and the timestamp is used to indicate touch event The time of generation.
Alternatively, the notification message includes the first configured information or the second configured information, first configured information Window for indicating response touch event belongs to the auxiliary system, and second configured information is used to indicate response touch event Window be not belonging to the auxiliary system；Correspondingly, the first instruction that indicating module 1102 can include according to the notification message Information or second configured information, it is determined whether respond the touch event.
Alternatively, acquisition module 1101 is specifically used for：Obtain in touch event sequence caused by a contact action After first touch event, obtain main system transmission is used to indicate whether the auxiliary system to respond the logical of the touch event sequence Know message.
Alternatively, acquisition module 1101 is specifically used for：According to the timestamp query messages queue of the touch event, obtain It is matched for indicating whether the auxiliary system responds the notification message of the touch event with the timestamp；Wherein, it is described to disappear Breath queue is used to cache the notification message that the main system is sent.
Alternatively, the notification message includes：The attribute information of touch event.
Based on identical technical concept, the embodiment of the present application additionally provides a kind of terminal.
Referring to Figure 12, for the structure diagram of terminal provided by the embodiments of the present application, which can realize previous embodiment The touch event process flow of description, the terminal may include on the whole：Processor 1201, memory 1202, touch input portion Part 1203.
Wherein, processor 1201 can be general processor (such as microprocessor or any conventional processor etc.), Digital signal processor, application-specific integrated circuit, field programmable gate array either other programmable logic device, discrete gate or Transistor logic, discrete hardware components.Memory 1202 specifically may include internal storage and/or external memory storage, than Such as random access memory, flash memory, read-only storage, programmable read only memory or electrically erasable programmable memory, register Deng the storage medium of this area maturation.Touch input component 1203 may include touch screen control circuit.
There are data communication connection between processor 1201 and other each modules, for example bus architecture can be based on and carry out data Communication.Bus architecture can include the bus and bridge of any number of interconnection, one or more specifically represented by processor 1201 The various circuits for the memory that a processor and memory 1202 represent link together.Bus architecture can also will be such as peripheral Various other circuits of equipment, voltage-stablizer and management circuit or the like link together, these are all well known in the art , therefore, no longer it is described further herein.Bus interface provides interface.Processor 1201 is responsible for total coil holder Structure and common processing, memory 1202 can store the used data when performing operation of processor 1201.
The flow that the embodiment of the present application discloses, can be applied in processor 1201, or realized by processor 1201. During realization, each step can be complete by the integrated logic circuit of the hardware in processor 1201 or the instruction of software form Into.It can realize or perform disclosed each method, step and the logic diagram in the embodiment of the present application.Implement with reference to the application The step of method disclosed in example, can be embodied directly in hardware processor and perform completion, or with the hardware in processor and soft Part block combiner performs completion.Software module can be located at random access memory, and flash memory, read-only storage, may be programmed read-only storage In the storage medium of this area such as device or electrically erasable programmable memory, register maturation.
Specifically, processor 1201, are coupled to memory 1202, for reading the computer program of the storage of memory 1202 Instruction, and in response, perform following operation：
Main system in operating system is according to belonging to the touch event of acquisition determines to respond the window of the touch event System, however, it is determined that respond system supplemented by the system belonging to the window of the touch event, then notify described in the auxiliary system response Touch event；
Auxiliary system in operating system is used to indicate the auxiliary system response touch event get main system transmission Notification message after, the touch event according to indicated by the notification message responds the notification message.
The specific implementation of the above process can be found in previous embodiment, be not repeated herein.
Based on identical technical concept, the embodiment of the present application additionally provides a kind of operating system, which may include Main system and auxiliary system, wherein：
Main system, for determining to respond the system belonging to the window of the touch event according to the touch event of acquisition, if System supplemented by system belonging to the window of the definite response touch event, then notify the auxiliary system to respond the touch thing Part；
Auxiliary system, for disappearing in the notice for being used to indicate the auxiliary system response touch event for getting main system transmission After breath, the touch event according to indicated by the notification message responds the notification message.
The specific implementation of the above process can be found in previous embodiment, be not repeated herein.
The application is with reference to the flow according to the method for the embodiment of the present application, equipment (system) and computer program product Figure and/or block diagram describe.It should be understood that it can be realized by computer program instructions every first-class in flowchart and/or the block diagram The combination of flow and/or square frame in journey and/or square frame and flowchart and/or the block diagram.These computer programs can be provided The processors of all-purpose computer, special purpose computer, Embedded Processor or other programmable data processing devices is instructed to produce A raw machine so that the instruction performed by computer or the processor of other programmable data processing devices, which produces, to be used in fact The device for the function of being specified in present one flow of flow chart or one square frame of multiple flows and/or block diagram or multiple square frames.
These computer program instructions, which may also be stored in, can guide computer or other programmable data processing devices with spy Determine in the computer-readable memory that mode works so that the instruction being stored in the computer-readable memory, which produces, to be included referring to Make the manufacture of device, the command device realize in one flow of flow chart or multiple flows and/or one square frame of block diagram or The function of being specified in multiple square frames.
These computer program instructions can be also loaded into computer or other programmable data processing devices so that counted Series of operation steps is performed on calculation machine or other programmable devices to produce computer implemented processing, thus in computer or The instruction performed on other programmable devices is provided and is used for realization in one flow of flow chart or multiple flows and/or block diagram one The step of function of being specified in a square frame or multiple square frames.
Although having been described for the preferred embodiment of the application, those skilled in the art once know basic creation Property concept, then can make these embodiments other change and modification.So appended claims be intended to be construed to include it is excellent Select embodiment and fall into all change and modification of the application scope.
Obviously, those skilled in the art can carry out the application essence of the various modification and variations without departing from the application God and scope.In this way, if these modifications and variations of the application belong to the scope of the application claim and its equivalent technologies Within, then the application is also intended to comprising including these modification and variations.

Claims (46)

1. a kind of touch event processing method, applied to the operating system for including two subsystems, described two subsystem difference For main system and auxiliary system, it is characterised in that the described method includes：
Auxiliary system obtains the notification message of main system；
If the notification message is used to indicate the auxiliary system response touch event, the auxiliary system responds the notification message Indicated touch event.
2. the method as described in claim 1, it is characterised in that auxiliary system obtains the notification message of main system, including：
After the auxiliary system obtains touch event, the notification message that main system is sent is obtained, the notification message is used to indicate institute State whether auxiliary system responds the touch event.
3. method as claimed in claim 2, it is characterised in that the letter for being used for identifying touch event is included in the notification message Breath.
4. method as claimed in claim 3, it is characterised in that the information for being used to identify touch event is timestamp, institute State timestamp and be used for the time for indicating that touch event occurs.
5. method as claimed in claim 2, it is characterised in that the notification message includes the first configured information or the second finger Show information, first configured information is used to indicate that the window of response touch event to belong to the auxiliary system, second instruction Information is used to indicate that the window of response touch event is not belonging to the auxiliary system；
First configured information or the second configured information that the auxiliary system includes according to the notification message, it is determined whether Respond the touch event.
6. method as claimed in claim 2, it is characterised in that after auxiliary system obtains touch event, obtain what main system was sent Notification message, including：
After auxiliary system obtains the first touch event in touch event sequence caused by a contact action, main system hair is obtained Send be used for indicate whether the auxiliary system responds the notification message of the touch event sequence.
7. method as claimed in claim 2, it is characterised in that auxiliary system obtains the notification message that main system is sent, including：
Auxiliary system obtains matched for indicating institute with the timestamp according to the timestamp query messages queue of the touch event State the notification message whether auxiliary system responds the touch event；Wherein, the message queue is used to cache the main system hair The notification message sent.
8. the method as described in claim 1, it is characterised in that the notification message includes：The attribute information of touch event.
9. a kind of touch event processing method, applied to the operating system for including two subsystems, described two subsystem difference For main system and auxiliary system, it is characterised in that the described method includes：
Main system determines the system belonging to the window of the response touch event according to the touch event of acquisition；
If the main system determines to respond system supplemented by system belonging to the window of the touch event, the auxiliary system is notified Respond the touch event.
10. method as claimed in claim 9, it is characterised in that main system notifies the auxiliary system to respond the touch event, Including：
The main system sends the first notification message to the auxiliary system, and first notification message includes the first instruction letter Breath, the system that first configured information is used to indicate to respond belonging to the window of the touch event is auxiliary system.
11. method as claimed in claim 10, it is characterised in that further included in first notification message：For identifying State the information of touch event.
12. method as claimed in claim 11, it is characterised in that the information for being used to identify the touch event, including： Timestamp, the timestamp are used for the time for indicating that the touch event occurs.
13. the method as any one of claim 10 to 12, it is characterised in that the touch event is grasped for a touch screen First touch event in touch event sequence caused by work；
First notification message is used to indicate that the auxiliary system responds touch event sequence caused by the contact action.
14. method as claimed in claim 9, it is characterised in that further include：
If the system that the main system determines to respond belonging to the window of the touch event is main system, the host system response The touch event, and prevent the auxiliary system from responding the touch event.
15. method as claimed in claim 14, it is characterised in that the main system prevents the auxiliary system from responding the touch Event, including：
The main system sends second notification message to the auxiliary system, and the second notification message includes the second instruction letter Breath, the system that second configured information is used to indicate to respond belonging to the window of the touch event is not auxiliary system.
16. method as claimed in claim 15, it is characterised in that further included in the second notification message：For identifying State the information of touch event.
17. the method described in claim 16, it is characterised in that the information for being used to identify the touch event, including： Timestamp, the timestamp are used for the time for indicating that the touch event occurs.
18. the method as any one of claim 9 to 17, it is characterised in that the touch event is grasped for a touch screen First touch event in touch event sequence caused by work；
The second notification message is used to prevent the auxiliary system from responding touch event sequence caused by the contact action.
19. method as claimed in claim 9, it is characterised in that main system notifies the auxiliary system to respond the touch event, Including：
The main system sends third notice message to the auxiliary system, and the third notice message includes：Touch event Attribute information.
20. one kind input management service unit, applied to the operating system for including two subsystems, described two subsystem difference For main system and auxiliary system, it is characterised in that the input management service unit is located in the auxiliary system, the input management Service unit includes：
Acquisition module, for obtaining the notification message of main system；
Indicating module, for when the notification message is used to indicate the auxiliary system response touch event, indicating the auxiliary system The application of system responds the touch event indicated by the notification message.
21. device as claimed in claim 20, it is characterised in that the acquisition module is specifically used for：After obtaining touch event, The notification message that main system is sent is obtained, the notification message is used to indicate whether the auxiliary system responds the touch event.
22. device as claimed in claim 21, it is characterised in that included in the notification message and be used to identify touch event Information.
23. device as claimed in claim 22, it is characterised in that the information for being used to identify touch event is timestamp, The timestamp is used for the time for indicating that touch event occurs.
24. device as claimed in claim 21, it is characterised in that the notification message includes the first configured information or second Configured information, first configured information are used to indicate that the window of response touch event to belong to the auxiliary system, and described second refers to Show information be used for indicate respond touch event window be not belonging to the auxiliary system；
The determining module is specifically used for：The first configured information included according to the notification message or the second instruction letter Breath, it is determined whether respond the touch event.
25. device as claimed in claim 21, it is characterised in that the acquisition module is specifically used for：
After obtaining the first touch event in touch event sequence caused by a contact action, the use that main system is sent is obtained The notification message of the touch event sequence whether is responded in the instruction auxiliary system.
26. device as claimed in claim 21, it is characterised in that the acquisition module is specifically used for：
According to the timestamp query messages queue of the touch event, obtain matched for indicating the auxiliary system with the timestamp Whether system responds the notification message of the touch event；Wherein, the message queue is used to cache the logical of the main system transmission Know message.
27. device as claimed in claim 20, it is characterised in that the notification message includes：The attribute letter of touch event Breath.
28. one kind input management service unit, applied to the operating system for including two subsystems, described two subsystem difference For main system and auxiliary system, it is characterised in that the input management service unit is located in the main system, the input management Service unit includes：
Determining module, for the touch event according to acquisition, determines the system belonging to the window of the response touch event；
Notification module, for determining to respond system supplemented by the system belonging to the window of the touch event in the determining module When, notify the auxiliary system to respond the touch event.
29. device as claimed in claim 28, it is characterised in that the notification module is specifically used for：
The first notification message is sent to the auxiliary system, first notification message includes the first configured information, and described first The system that configured information is used to indicate to respond belonging to the window of the touch event is auxiliary system.
30. device as claimed in claim 29, it is characterised in that further included in first notification message：For identifying State the information of touch event.
31. device as claimed in claim 30, it is characterised in that the information for being used to identify the touch event, including： Timestamp, the timestamp are used for the time for indicating that the touch event occurs.
32. the device as any one of claim 29 to 31, it is characterised in that the touch event is grasped for a touch screen First touch event in touch event sequence caused by work；
First notification message is used to indicate that the auxiliary system responds touch event sequence caused by the contact action.
33. device as claimed in claim 28, it is characterised in that the notification module is additionally operable to：
If the system that the determining module determines to respond belonging to the window of the touch event is main system, the principal series is notified Application in system responds the touch event, and notifies the auxiliary system to prevent the auxiliary system from responding the touch event.
34. device as claimed in claim 33, it is characterised in that the notification module is specifically used for：
Second notification message is sent to the auxiliary system, the second notification message includes the second configured information, and described second The system that configured information is used to indicate to respond belonging to the window of the touch event is not auxiliary system.
35. device as claimed in claim 34, it is characterised in that further included in the second notification message：For identifying State the information of touch event.
36. device as claimed in claim 35, it is characterised in that the information for being used to identify the touch event, including： Timestamp, the timestamp are used for the time for indicating that the touch event occurs.
37. the device as any one of claim 34 to 36, it is characterised in that the touch event is grasped for a touch screen First first touch event in touch event sequence caused by work, first touch event are put into touch screen in finger Triggered when upper；
The second notification message is used to prevent the auxiliary system from responding touch event sequence caused by the contact action.
38. device as claimed in claim 28, it is characterised in that the notification module is specifically used for：
Third notice message is sent to the auxiliary system, the third notice message includes：The attribute information of touch event.
A kind of 39. operating system, it is characterised in that including：
Main system, for determining to respond the system belonging to the window of the touch event according to the touch event of acquisition, however, it is determined that System supplemented by the system belonging to the window of the touch event is responded, then notifies the auxiliary system to respond the touch event；
Auxiliary system, for getting the notification message for being used to indicate the auxiliary system response touch event of main system transmission Afterwards, the touch event according to indicated by the notification message responds the notification message.
40. operating system as claimed in claim 39, it is characterised in that the main system includes main system input management clothes Business, the auxiliary system include auxiliary system input management service, the main system input management service and the auxiliary system input Being established between management service has message channel；
The main system inputs management service, for being determined to respond the window institute of the touch event according to the touch event of acquisition The system of category, however, it is determined that it is the auxiliary system to respond the system belonging to the window of the touch event, then sends the first notice and disappear Breath, first notification message include the first configured information, and first configured information is used to indicate to respond the touch thing System belonging to the window of part is auxiliary system, however, it is determined that it is the principal series to respond the system belonging to the window of the touch event System, then send second notification message, the second notification message includes the second configured information, and second configured information is used for The system for indicating to respond belonging to the window of the touch event is not auxiliary system；
The auxiliary system input management service, during for including the first configured information in the notification message got, notice institute State auxiliary systematic difference and respond the touch event, when the notification message got includes the second configured information, abandon leading to Know that the auxiliary systematic difference responds the touch event.
41. operating system as claimed in claim 40, it is characterised in that the auxiliary system input management service is specifically used for：
After obtaining the first touch event in touch event sequence caused by a contact action, the use that main system is sent is obtained The notification message of the touch event whether is responded in the instruction auxiliary system；
If including the first configured information in the notification message got, the auxiliary systematic difference is notified to respond the touch screen behaviour Touch event sequence caused by work；
If including the second configured information in the notification message got, abandon notifying the auxiliary systematic difference response is described to touch Touch event sequence caused by screen operation.
42. operating system as claimed in claim 40, it is characterised in that included in the notification message and be used to identify touch thing The information of part.
43. operating system as claimed in claim 42, it is characterised in that the information for being used to identify touch event is the time Stamp, the timestamp are used for the time for indicating that touch event occurs.
44. the operating system as any one of claim 40 to 43, it is characterised in that the auxiliary system input management clothes Business, is specifically used for：
According to the timestamp query messages queue of the touch event, obtain matched for indicating the auxiliary system with the timestamp Whether system responds the notification message of the touch event；Wherein, the message queue is used to cache the logical of the main system transmission Know message.
45. operating system as claimed in claim 39, it is characterised in that
The main system input management service is specifically used for：After obtaining touch event, however, it is determined that respond the window of the touch event System supplemented by system belonging to mouthful, then send third notice message, the third notice to the auxiliary system input management service Message is used to indicate that the auxiliary system responds the touch event, and the third notice message includes：The attribute of touch event Information；If it is determined that it is main system to respond the system belonging to the window of the touch event, then the application response institute of main system is notified State touch event；
The auxiliary system input management service is specifically used for：According to the third notice message received, the auxiliary system is notified The application of system responds the touch event indicated by the notification message.
A kind of 46. terminal, it is characterised in that including：
Memory, for storing computer program instructions；
Processor, is coupled to the memory, for reading the computer program instructions of the memory storage, and as sound Should, perform following operation：
Main system in operating system determines to respond the system belonging to the window of the touch event according to the touch event of acquisition, If it is determined that responding system supplemented by the system belonging to the window of the touch event, then the auxiliary system is notified to respond the touch thing Part；
Auxiliary system in operating system is used to indicate the logical of the auxiliary system response touch event get main system transmission After knowing message, the touch event according to indicated by the notification message responds the notification message.
CN201610974784.7A 2016-11-04 2016-11-04 touch event processing method, device and operating system Pending CN108021456A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610974784.7A CN108021456A (en) 2016-11-04 2016-11-04 touch event processing method, device and operating system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610974784.7A CN108021456A (en) 2016-11-04 2016-11-04 touch event processing method, device and operating system

Publications (1)

Publication Number Publication Date
CN108021456A true CN108021456A (en) 2018-05-11

Family

ID=62084748

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610974784.7A Pending CN108021456A (en) 2016-11-04 2016-11-04 touch event processing method, device and operating system

Country Status (1)

Country Link
CN (1) CN108021456A (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109918016A (en) * 2019-04-01 2019-06-21 广州朗国电子科技有限公司 Multisystem touches the touch control method and touch device of display equipment
CN110708581A (en) * 2019-08-27 2020-01-17 青岛海信电器股份有限公司 Display device and method for presenting multimedia screen saver information
CN113467656A (en) * 2021-06-24 2021-10-01 湖北亿咖通科技有限公司 Screen touch event notification method and vehicle machine

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120110496A1 (en) * 2010-10-29 2012-05-03 Choongryeol Lee Mobile terminal and controlling method thereof
US20120110315A1 (en) * 2010-10-29 2012-05-03 Choongryeol Lee Mobile terminal and controlling method thereof
CN103593185A (en) * 2013-11-04 2014-02-19 浙江大学 Single-Linux-inner-core-based method for multiple Android systems to share input equipment and display equipment
CN103914646A (en) * 2013-01-08 2014-07-09 三星电子株式会社 Touch event processing method and portable device implementing the same
CN104731502A (en) * 2015-03-27 2015-06-24 努比亚技术有限公司 Double-click recognition method and device based on virtual partition touch screen and mobile terminal
CN105653353A (en) * 2015-12-31 2016-06-08 北京元心科技有限公司 Multi-system interactive communication method and device based on container

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120110496A1 (en) * 2010-10-29 2012-05-03 Choongryeol Lee Mobile terminal and controlling method thereof
US20120110315A1 (en) * 2010-10-29 2012-05-03 Choongryeol Lee Mobile terminal and controlling method thereof
CN103914646A (en) * 2013-01-08 2014-07-09 三星电子株式会社 Touch event processing method and portable device implementing the same
CN103593185A (en) * 2013-11-04 2014-02-19 浙江大学 Single-Linux-inner-core-based method for multiple Android systems to share input equipment and display equipment
CN104731502A (en) * 2015-03-27 2015-06-24 努比亚技术有限公司 Double-click recognition method and device based on virtual partition touch screen and mobile terminal
CN105653353A (en) * 2015-12-31 2016-06-08 北京元心科技有限公司 Multi-system interactive communication method and device based on container

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109918016A (en) * 2019-04-01 2019-06-21 广州朗国电子科技有限公司 Multisystem touches the touch control method and touch device of display equipment
CN110708581A (en) * 2019-08-27 2020-01-17 青岛海信电器股份有限公司 Display device and method for presenting multimedia screen saver information
CN110708581B (en) * 2019-08-27 2021-09-24 海信视像科技股份有限公司 Display device and method for presenting multimedia screen saver information
CN113467656A (en) * 2021-06-24 2021-10-01 湖北亿咖通科技有限公司 Screen touch event notification method and vehicle machine

Similar Documents

Publication Publication Date Title
JP7013466B2 (en) Application data processing methods, equipment, and computer programs
CN110378593B (en) Communication status for application of compliance policy updates
US20190324599A1 (en) Method, apparatus, and electronic device for displaying chat windows
US9026583B2 (en) Method and apparatus for polymorphic serialization
KR101750429B1 (en) Document editing system and method for collaborative editing
CN108132735B (en) Terminal and application control method
CN110851248B (en) Asynchronous task data processing method and device and computer readable storage medium
CN104850415A (en) Method and apparatus for loading pages
CN107133309B (en) Method and device for storing and querying process example, storage medium and electronic equipment
CN112162965B (en) Log data processing method, device, computer equipment and storage medium
CN104699378A (en) Information browsing method and information browsing system in multi-person chatting
DE202008000268U1 (en) Portable multifunction device
CN112199442B (en) Method, device, computer equipment and storage medium for distributed batch downloading files
CN111857453B (en) Function interface display method, computer equipment and storage medium
CN113032080A (en) Page implementation method, application program, electronic device and storage medium
EP3757739A1 (en) Method for display when exiting an application, and terminal
CN108021456A (en) touch event processing method, device and operating system
US9830056B1 (en) Indicating relationships between windows on a computing device
CN112000911A (en) Page management method and device, electronic equipment and storage medium
CN111371953A (en) Tag data processing method, device and storage medium
US20200089512A1 (en) Method and Apparatus for Invoking Input Method, Server, and Terminal
EP4318197A1 (en) Virtual live broadcast room display method and apparatus, client, server, and medium
CN112187530A (en) Log analysis method and device, electronic equipment and readable storage medium
CN111444670A (en) Document annotation method and device, computer equipment and storage medium
CN111324398B (en) Method, device, terminal and storage medium for processing latest content

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
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20201221

Address after: Room 603, 6 / F, Roche Plaza, 788 Cheung Sha Wan Road, Kowloon, China

Applicant after: Zebra smart travel network (Hong Kong) Ltd.

Address before: Cayman Islands Grand Cayman capital building, a four storey No. 847 mailbox

Applicant before: Alibaba Group Holding Ltd.

RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20180511