CN102681845A - Method and device for managing input events - Google Patents
Method and device for managing input events Download PDFInfo
- Publication number
- CN102681845A CN102681845A CN2012101206159A CN201210120615A CN102681845A CN 102681845 A CN102681845 A CN 102681845A CN 2012101206159 A CN2012101206159 A CN 2012101206159A CN 201210120615 A CN201210120615 A CN 201210120615A CN 102681845 A CN102681845 A CN 102681845A
- Authority
- CN
- China
- Prior art keywords
- incoming event
- event
- thread
- application program
- state
- 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
Links
Images
Abstract
The invention discloses a method for managing input events. The method includes steps: establishing an input event thread used for receiving input equipment by a preset event service program; performing standardizing processing for the input events and acquiring the standard input events according to the input events received by the thread; and distributing the standard input events to an application program. By the aid of the method and the device for managing the input events, various application programs can be effectively managed, switching back and forth among the various application programs is conveniently realized, and experience of users is improved.
Description
Technical field
The present invention relates to field of set-top, relate in particular to a kind of incoming event management method and device.
Background technology
STB is very universal at present; But each business procedure with Presentation Function all can only isolated operation, and can not move simultaneously, and existing way is to set up a plurality of threads for each separate application program; So that receive the incident of sending without the types of events source; But develop and debug all pretty troublesome like this, and increase as new Event origin, the developer must spend great amount of time and energy carries out the modification and the test of code.For the user, can only carry out a business procedure at every turn, handle other business; Get earlier current service ending; And then start the business that will handle, and bring great inconvenience to user's operation, can't realize that the multiple business program moves simultaneously; Can't be implemented between each business procedure and switch back and forth, can not satisfy the different mutual phase demand of various users.
Summary of the invention
Embodiment of the invention technical matters to be solved is, a kind of incoming event management method and device are provided, and can realize that the multiple business program is moved simultaneously and switching back and forth between each business procedure, satisfies the different mutual phase demand of various users.
In order to solve the problems of the technologies described above, the embodiment of the invention provides a kind of incoming event management method, comprising:
The Event Service program creation that presets is used to receive the thread of the incoming event of input equipment;
Incoming event according to said thread receives carries out standardization to said incoming event and obtains the standard incoming event;
Said standard incoming event is distributed to application program.
Wherein, the thread of said establishment comprises in the end points SOCKET input thread of USB input thread, infrared input thread and process communication any or several kinds.
Wherein, the said incoming event that receives according to said thread, carry out standardization to said incoming event and obtain the standard incoming event and comprise:
When said thread was USB input thread, said USB input thread was used for the incoming event of the local USB device of barrage reception, and with the incoming event of said local USB device as the standard incoming event;
When said thread is infrared input thread; Said infrared ray input thread is used for the incoming event of barrage reception infrared equipment; And in the inner Drive Layer of infrared input thread, the incoming event that receives being modeled to keyboard and/or mouse incoming event, keyboard that simulation is obtained and/or mouse incoming event are as the standardization incoming event;
When said thread is SOCKET input thread; Said SOCKET input thread is used for the incoming event of barrage reception RTU; And in the inner Drive Layer of SOCKET input thread, the incoming event that receives is converted into the keyboard and/or the mouse event of standard, with the keyboard that obtains and/or mouse incoming event as the standardization incoming event.
Wherein, said incident with the standardization of said process comprises before being distributed to application program:
When application program need be obtained the incoming event service, said application program was to said Event Service program registration.
Wherein, also comprise:
In the application program that the application program management mechanism that said Event Service program basis presets guarantees in said Event Service program, to register; There is and has only an application program to be in state of activation STATE_ACTIVE, guarantee to have only an application program can receive incident at every turn.
Wherein, also comprise:
Said Event Service program is carried out self-defined processing according to the customized event treatment mechanism that presets to said user-defined incident when receiving user-defined incident.
Wherein, also comprise: Event Service program creation status monitoring thread, wherein,
The formation of said status monitoring thread periodic polling registrer application according to its state of process instruction character detection of said application program, and is safeguarded said registrer application formation.
Correspondingly, the embodiment of the invention also provides a kind of incoming event management devices, comprising:
The thread creation unit, the Event Service program creation thread that is used to preset is so that receive the incoming event of input equipment;
The standardization unit is used for receiving according to said thread creation unit the incoming event of input equipment, said incoming event is carried out standardization obtain the standard incoming event;
Transmitting element is used for the standard incoming event that the standardization with said standardization unit obtains and is distributed to application program.
Wherein, said standardization unit comprises:
The first standardization unit is used for when said thread is USB input thread, to the incoming event of the local USB device of said USB input thread barrage reception, and with the incoming event of said local USB device as the standard incoming event;
The second standardization unit; Be used for when said thread is infrared input thread; Said infrared ray input thread is used for the incoming event of barrage reception infrared equipment; And in the inner Drive Layer of infrared input thread, the incoming event that receives being modeled to keyboard and/or mouse incoming event, keyboard that simulation is obtained and/or mouse incoming event are as the standardization incoming event;
The 3rd standardization unit; Be used for when said thread is SOCKET input thread; Said SOCKET input thread is used for the incoming event of barrage reception RTU; And in the inner Drive Layer of SOCKET input thread, the incoming event that receives is converted into the keyboard and/or the mouse event of standard, with the keyboard that obtains and/or mouse incoming event as the standardization incoming event.
Wherein, comprising:
The application program registering unit is used for when application program need be obtained the incoming event service, and said application program is to said Event Service program registration.
Wherein, comprising:
The application program management unit is used for guaranteeing in the application program that said Event Service program is registered, have and have only an application program to be in state of activation STATE_ACTIVE state, guarantees to have only an application program can receive incident at every turn.
Wherein, also comprise:
The customized event processing unit is used for said Event Service program when receiving the User Defined incident, and said user-defined incident is carried out self-defined processing.
Wherein, also comprise:
Condition Monitoring Unit is used for the formation of periodic polling registrer application, according to its state of process instruction character detection of said application program, and safeguards said registrer application formation.
Embodiment of the present invention embodiment has following beneficial effect:
Event server in the embodiment of the invention has shielded the type of Event origin and incident has been carried out standardization, makes procedure development convenient, and has favorable expansibility; Improved development efficiency, effectively managed each application program simultaneously, for a plurality of application programs that have Presentation Function; Can easily realize seeing a film; Business procedure such as online and browsing pictures move simultaneously, do not disturb mutually, and can be implemented in switching back and forth between each business procedure; Greatly facilitate user's operation, promoted user experience.
Description of drawings
Fig. 1 is the process flow diagram of first embodiment of a kind of incoming event management method of the present invention;
Fig. 2 is the process flow diagram of second embodiment of a kind of incoming event management method of the present invention;
Fig. 3 is the process flow diagram of the 3rd embodiment of a kind of incoming event management method of the present invention;
Fig. 4 is the process flow diagram of the 4th embodiment of a kind of incoming event management method of the present invention;
Fig. 5 is the structural representation of first embodiment of a kind of incoming event management devices of the present invention;
Fig. 6 is the structural representation of second embodiment of a kind of incoming event management devices of the present invention;
Fig. 7 is the structural representation of the 3rd embodiment of a kind of incoming event management devices of the present invention;
Fig. 8 is the structural representation of the 4th embodiment of a kind of incoming event management devices of the present invention.
Embodiment
To combine the accompanying drawing in the embodiment of the invention below, the technical scheme in the embodiment of the invention is carried out clear, intactly description, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills are not making the every other embodiment that is obtained under the creative work prerequisite, all belong to the scope of the present invention's protection.
See also Fig. 1, be the process flow diagram of first embodiment of a kind of incoming event management method of the present invention.Said method comprises:
S101, the Event Service program creation that presets are used to receive the thread of the incoming event of input equipment;
Concrete; The thread of the Event Service program creation that presets described in the embodiment of the invention comprises in the end points SOCKET input thread of USB input thread, infrared input thread and process communication any or several kinds; Wherein, Said USB input thread is used for the incoming event of the local USB device of barrage reception (mouse, keyboard); And with the incoming event of said local USB device as the standard incoming event, when said thread was infrared input thread, said infrared ray input thread was used for the incoming event of barrage reception infrared equipment; And in the inner Drive Layer of infrared input thread, the incoming event that receives is modeled to keyboard and/or mouse incoming event; Keyboard that simulation is obtained and/or mouse incoming event are as the standardization incoming event, and when said thread was SOCKET input thread, said SOCKET input thread was used for the incoming event of barrage reception RTU (mobile phone, pad etc.); And in the inner Drive Layer of SOCKET input thread, the incoming event that receives is converted into the keyboard and/or the mouse event of standard, with the keyboard that obtains and/or mouse incoming event as the standardization incoming event.
Need to prove that barrage reception described in the embodiment of the invention is meant that under blocking model program is when calling receiver function, if there is not data arrives, this function can wait for always that promptly current thread can get clogged, and when data are arranged, just returns.
Need to prove, also can increase Bluetooth input equipment etc. in the embodiment of the invention.
S102, the incoming event according to said thread receives carries out standardization to said incoming event and obtains the standard incoming event;
Concrete; In the embodiment of the invention, the incoming event of each peripherals that the thread of being created according to the Event Service program that presets in the S101 step receives is analyzed the incoming event of the said input equipment that receives; And be translated into the linux incoming event of standard; Obtain the standard incoming event, said standard incoming event is sent to corresponding application, the incoming event of the local USB device (mouse, keyboard) that arrives for said USB input thread barrage reception; Because the incoming event that said local USB device obtains has been a standard Event; So without standardization, and with the incoming event of said local USB device as the standard incoming event, when said thread is infrared input thread; Said infrared ray input thread is used for the incoming event of barrage reception infrared equipment (telepilot); And in the inner Drive Layer of infrared input thread, the incoming event that receives being modeled to keyboard and/or mouse incoming event, keyboard that can simulation be obtained according to the ID that obtains and/or mouse incoming event are as the standardization incoming event, when said thread is SOCKET input thread; Said SOCKET input thread is used for the incoming event of barrage reception RTU (mobile phone, pad etc.); And in the inner Drive Layer of SOCKET input thread, the incoming event that receives being converted into the keyboard and/or the mouse event of standard, the xml information in the incoming event that can receive through parsing obtains the type and the key assignments ID of said incoming event; Obtain keyboard and/or mouse incoming event; Said standardization is meant that the incoming event with external unit changes into complete keyboard incoming event structure, mouse incoming event structure, and wherein, said keyboard incoming event structure comprises key_id, key_symbol, key_scancod, key_event (down/up); Wherein, said mouse incoming event structure comprises button_type (left button, right button, roller), button_event (press, upspring, move), value (displacement) etc.
S103 is distributed to application program with said standard incoming event.
Concrete; The client of the said Event Service program that presets of the embodiment of the invention is each application program, and service end is the Event Service program, and said Event Service program has comprised an incident distribution mechanisms; Said incident distribution mechanisms; The incoming event of each peripherals that the said Event Service program creation thread that presets is received carries out standard treated, and is translated into the linux incoming event of standard, obtains the standard incoming event; And said standard incoming event sent to corresponding application with the mode of Parcel; Said application program does not spend and distinguishes is the input equipment of which kind of type, and promptly the type of the input equipment of shielding brings great convenience and favorable expansibility to program development like this.
Need to prove that the present invention realizes on the inter4100 platform.
The Event Service program creation that presets in the embodiment of the invention is used to receive the thread of the incoming event of input equipment; Said thread comprises in USB input thread, infrared input thread and the SOCKET input thread any or several kinds; For use in the incoming event that receives different peripherals; These peripherals comprise infrared equipment, keyboard and mouse, remote equipment, Bluetooth input equipment etc.; Because the incoming event of the peripherals that said service routine receives not is unified standard Event; Obtain the standard incoming event so need carry out standardization, be converted into the linux incoming event of standard, will pass through the standard incoming event that standardization obtains then and be distributed to each application program said incoming event.
See also the process flow diagram of Fig. 2 for second embodiment of a kind of incoming event management method of the present invention.Said method comprises:
S201, the Event Service program creation that presets are used to receive the thread of the incoming event of input equipment;
S202, when said thread was USB input thread, said USB input thread was used for the incoming event of the local USB device of barrage reception, and with the incoming event of said local USB device as the standard incoming event;
Concrete; In the embodiment of the invention; When the thread of said S201 establishment is USB input thread; The incoming event of the said local USB device of USB input thread barrage reception such as mouse or keyboard; Because the incoming event that said local USB device obtains has been a standard Event, so need not analyze and be converted into the linux incoming event of standard to the incoming event of the said local USB device that receives, the incoming event of the local USB device that directly will receive sends to each application program in the client.
S203; When said thread is infrared input thread; Said infrared ray input thread is used for the incoming event of barrage reception infrared equipment; And in the inner Drive Layer of infrared input thread, the incoming event that receives being modeled to keyboard and/or mouse incoming event, keyboard that simulation is obtained and/or mouse incoming event are as the standardization incoming event;
Concrete; In the embodiment of the invention, when the thread of said S201 establishment is infrared ray input thread, the incoming event of said infrared ray input thread barrage reception infrared equipment (telepilot); And the incoming event of the said infrored equipment that receives analyzed; And be translated into the linux incoming event of standard, in the inner Drive Layer of infrared input thread the incoming event that receives is modeled to keyboard and/or mouse incoming event
Concerning said infrared equipment, the communication between said long-range infrared equipment and the said Event Service program needs the agreement of an infrared communication, and promptly said Event Service program will receive remote events; Must said Event Service program inside have with telepilot between the agreement of communicating by letter, described communication protocol is exactly infrared communication protocol, as for what content of this protocol transmission; Usually by developer oneself definition, inside STB, the driver of individual infrared communication is arranged usually; Receive the incoming event that said infrared equipment such as telepilot send through said driver, concrete steps are that said telepilot only can send the key assignments ID of this key when pressing key of said telepilot; Generally speaking; The key assignments ID that this key assignments ID and keyboard are corresponding is the same, and the key assignments ID that said infrared equipment such as telepilot send over has been modeled to the key assignments ID of keyboard, and for the keyboard incoming event of standard; Not only need key assignments ID; Also need KEY_SYMBOL, key assignments such as KEY_TYPE are described, so when said Event Service program receives this key assignments ID; Need carry out standardization to said incoming event, so that obtain the standard incoming event.
S204; When said thread is SOCKET input thread; Said SOCKET input thread is used for the incoming event of barrage reception RTU; And in the inner Drive Layer of SOCKET input thread, the incoming event that receives is converted into the keyboard and/or the mouse event of standard, with the keyboard that obtains and/or mouse incoming event as the standardization incoming event.
Concrete, when the thread of creating as said S201 in the embodiment of the invention is SOCKET input thread, the incoming event of said SOCKET input thread barrage reception RTU; Concerning said RTU, said RTU intercoms through socket with said Event Service program mutually, wherein; The content of the communication between the two is exactly XML, when said Event Service program receives the XML content, according to the evt_class label; Can judge that this incident is keyboard incoming event or mouse incoming event, according to the evt_type label, can judge user input the incident of upspringing, press incident or moving event; When judgement is KeyEvent,, obtain key assignments ID then according to the key_id label; Said Event Service program is carried out standardization according to said key assignments ID; When judgement is a mouse event, then carry out standardization, so that obtain the standard incoming event according to described XML form.
Need to prove that said expandable mark language XML is a formative character string, similarly be:
<message><evt_class>EVT_CLASS_KEY</evt_class><evt_type></evt_type><key_id></key_id></message>, wherein<message>The representative beginning,</message>Representative finishes, and said message is a tag name, can be defined by developer oneself usually by user oneself definition.
S205 is distributed to application program with said standard incoming event.
The embodiment of the invention is through creating the incoming event that different input threads receives different external equipment; It is carried out standardization; Be translated into the linux incoming event of standard, obtain the standard incoming event, and said standard incoming event is sent to corresponding application.
The embodiment of the invention has been created USB input thread, infrared input thread and SOCKET input thread respectively; Said USB input thread is used for the incoming event of the local USB device of barrage reception; Said infrared ray input thread is used for the incoming event of barrage reception infrared equipment; Said SOCKET input thread is used for the incoming event of barrage reception RTU, for each application program in the client, has effectively shielded the type of Event origin and the difference of different input equipments in the program of Event Service described in the program development process; And incoming event carried out standard treated, brought convenience and favorable expansibility to program development.
See also Fig. 3, be the process flow diagram of the 3rd embodiment of a kind of incoming event management method of the present invention.Said method comprises:
S301, the Event Service program creation that presets are used to receive the thread of the incoming event of input equipment;
S302, the incoming event according to said thread receives carries out standardization to said incoming event and obtains the standard incoming event;
S303, when application program need be obtained the incoming event service, said application program was to said Event Service program registration;
Concrete; The embodiment of the invention is carried out standardization through creating the incoming event that different input threads receives different external equipment to it, is translated into the linux incoming event of standard; So that obtain the standard incoming event; And said standard incoming event sent to each application program in the client, that is to say that said standard incoming event is to send to each application program in the client by said service routine, if when said application program need obtain the Event Service of said standard incoming event; Then must be in advance to said Event Service program registration; Just might obtain said standard incoming event, that is to say said application program if expect the standard incoming event that obtains through standardization, after receiving the ESC incident when application program; Program withdraws from, and said application program will obtain the incident value of standard incoming event from said Event Service program.
In the embodiment of the invention; Behind said Event Service program start; Can create a fifo fifo and supply said application program registration; If when said application program need obtain the Event Service of standard incoming event; Then must be in advance to said Event Service program registration; The information of said registration comprises synchronizing information mgcnum, process PID, process status, event filter and master-slave mode MS (MASTER-SLAVE) state, and wherein, said process PID is used for this process of unique identification; The object of process status monitoring after this process PID also becomes; Said process status comprise unactivated state (STATE_INACTIVE), state of activation (STATE_ACTIVE), deletion state (STATE_DELETE), non-activation not switching state (STATE_INACT_NOSWITCH), activate not switching state (STATE_ACT_NOSWITCH), said event filter is to be used for said application program to filter one or more of input equipment keyboard, mouse, telepilot, RTU according to interest and needs, said MS state then is to show whether this application program is primary application program.
Need to prove that the application program in the embodiment of the invention is sent registered events through login mechanism and given said Event Service program.
S304 is distributed to application program with said standard incoming event;
S305; In the application program that the application program management mechanism that said Event Service program basis presets guarantees in said Event Service program, to register; There is and has only an application program to be in state of activation STATE_ACTIVE, guarantee to have only an application program can receive incident at every turn.
Concrete, there are two parts in the incoming event source that the Event Service program that presets of the embodiment of the invention receives, and a part is registration of application program, Logout Events; Another one partly is the incoming event of input equipment; Wherein, input equipments such as said Event Service program unified management keyboard, mouse, telepilot, telecommunication network, but the management here is not the management to equipment; But the incident that this equipment produces is managed; Through unified management to said input equipment, promptly pass through unified management to the incoming event of said input equipment, the switching back and forth and the key that can be implemented between said application program return the homepage function.
Event Service program in the embodiment of the invention also comprises the administrative mechanism of application program; What said application program was sent through login mechanism and is registered, Logout Events is given said Event Service program; Said Event Service program receives after these incidents; Judge at first whether said process PID is present in the registration formation that said Event Service program safeguarded; If exist, then contrast the state in login state and the formation, and make corresponding state transition process; The supported state exchange of said registered events unactivated state (STATE_INACTIVE), state of activation (STATE_ACTIVE), deletion state (STATE_DELETE), non-activation not switching state (STATE_INACT_NOSWITCH), do not activate and change between the switching state (STATE_ACT_NOSWITCH), concrete is:
A、?STATE_INACTIVE?->?STATE_ACTIVE
B、STATE_INACTIVE?->?STATE_DELETE
C、STATE_INACTIVE?->?STATE_ACTIVE_NOSWITCH
D、STATE_INACTIVE?->?STATE_INACTIVE_NOSWITCH
E、STATE_ACTIVE?->?STATE_INACTIVE
F、STATE_ACTIVE?–>?STATE_DELETE
G、STATE_ACTIVE?->?STATE_ACTIVE_NOSWITCH
H、STATE_ACTIVE?->?STATE_INACTIVE_NOSWITCH
I、STATE_ACTIVE_NOSWITCH?->?STATE_ACTIVE
J、STATE_ACTIVE_NOSWITCH?->?STATE_INACTIVE
K、STATE_ACTIVE_NOSWITCH?->?STATE_INACTIVE_NOSWITCH
L、STATE_ACTIVE_NOSWITCH?->?STATE_DELETE
I、STATE_INACTIVE_NOSWITCH?->?STATE_ACTIVE
J、STATE_INACTIVE_NOSWITCH?->?STATE_INACTIVE
K、STATE_INACTIVE_NOSWITCH?->?STATE_ACTIVE_NOSWITCH
L、STATE_INACTIVE_NOSWITCH?->?STATE_DELETE
The program of Event Service described in the embodiment of the invention is kept at registration of application program information in the registration formation; In said registration formation; The state that has and have only an application program is STATE_ACTIVE; The MS state that has and have only an application program is MASTER, the embodiment of the invention as in the state exchange of incoming event support be:
A、STATE_INACTIVE?->?STATE_ACTIVE
B、STATE_INACTIVE?->?STATE_DELETE
C、STATE_ACTIVE?->?STATE_INACTIVE
D、STATE_ACTIVE?–>?STATE_DELETE
In the embodiment of the invention; In state conversion process; If do not relate to the ACTIVE state, the state of simply revising corresponding application programs in the said registration formation both can, if relate to the ACTIVE state; The application program of supposing current ACTIVE is active_current, the switching of a few step completion statuses below then dividing:
The first step judges whether the state of active_current application program is to activate not switching state STATE_ACTIVE_NOSWITCH, if incoming event is not then done any processing, directly ignores this state handover event; If registered events then carried out for second step;
In second step, from said registration formation, find the next one can activate the application program (active_next) of ACTIVE;
The 3rd step, send non-activation INACTIVE incident to the active_current application program, it is non-enable mode STATE_INACTIVE that the state of this application program in said registration formation is set;
The 4th step, send activation ACTIVE incident to the active_next application program, it is enable mode STATE_ACTIVE that the state of this application program in the registration formation is set.
In the embodiment of the invention, when said application program need obtain the Event Service of standard incoming event, then must be in advance to said Event Service program registration; Behind the said Event Service program start; Can create a fifo fifo and supply said application program registration, said application program is given said Event Service program through login mechanism transmission registration, Logout Events, and said Event Service program is kept at registration of application program information in the registration formation; Said Event Service program also comprises application program management mechanism; And guarantee in the application program of said registration have and have only an application program to be in the STATE_ACTIVE state through said application program management mechanism, also just mean; Have only an application program can receive said standard incoming event at every turn; After said Event Service program received said registration of application program incident, whether the process PID that at first judges this said application program was present in the registration formation that said Event Service program safeguarded, if exist; Then contrast the state in login state and the formation, and make corresponding state transition process.
See also Fig. 4, be the process flow diagram of the 4th embodiment of a kind of incoming event management method of the present invention.Said method comprises:
S401, the Event Service program creation that presets are used to receive the thread of the incoming event of input equipment;
S402, the incoming event according to said thread receives carries out standardization to said incoming event and obtains the standard incoming event;
S404 is distributed to application program with said standard incoming event.
S405, said Event Service program is carried out self-defined processing according to the customized event treatment mechanism that presets to said user-defined incident when receiving user-defined incident;
Concrete; Special event described in the embodiment of the invention is user-defined incident, such as F1 is a mode switching key; F2 is back the homepage key; After said Event Service program was received said special event F1, the management of process mechanism of said Event Service program was carried out the state exchange between process according to the state of current application program, after said Event Service program is received special event F2; If any action does not then take place for activating non-switch mode STATE_ACT_NOSWITCH in the current application program state; If the current application program state is state of activation STATE_ACTIVE; Then send non-activation INACTIVE incident and give current application program; To return homepage BACK_HOME incident then, to send to master-slave mode MS state be the application program of MASTER; Simultaneously, described Application Status is set to state of activation STATE_ACTIVE.
S406, the formation of said status monitoring thread periodic polling registrer application according to its state of process instruction character detection of said application program, and is safeguarded said registrer application formation.
Concrete, the Event Service service routine comprises the status monitoring thread described in the example according to the invention, said monitoring thread is that said application program is launched; The said registrer application formation of this status monitoring thread periodic polling, its state of process instruction character pid detection according to said application program withdraws from if said application program is improper; Judge that at first this withdraws from Application Status; If enable mode STATE_ACTIVE or activate non-switch mode STATE_ACT_NOSWITCH, then by returning homepage BACK_HOME event handling, otherwise; Directly this application program is deleted from said registrer application formation; The formation of said status monitoring thread periodic polling registrer application according to its state of process instruction character detection of said application program, and is safeguarded said registrer application formation.
Application program in the embodiment of the invention has comprised the customized event treatment mechanism; Said Event Service program is when receiving user-defined incident; According to the customized event treatment mechanism that presets said user-defined incident is carried out self-defined processing; Said user-defined incident comprises the mode switch incident, returns the homepage incident, and the embodiment of the invention has comprised the state-detection thread, the formation of said status monitoring thread periodic polling registrer application; Process instruction character according to said application program detects its state, and safeguards said registrer application formation.
See also Fig. 5, be the structural representation of first embodiment of a kind of incoming event management devices of the present invention.Said incoming event management devices comprises: thread creation unit 10, standardization unit 20, transmitting element 40, wherein:
Concrete, the unit of thread creation described in the embodiment of the invention 10 is used to create thread so that receive the incoming event of input equipment, wherein; The thread that said thread creation unit 10 is created comprises in USB input thread, infrared input thread and the SOCKET input thread any or several kinds, and wherein, said USB input thread is used for the incoming event of the local USB device of barrage reception (mouse, keyboard); In said USB input thread, can wait for that said infrared ray input thread is used for the incoming event of barrage reception infrared equipment (telepilot) through the method getEvent () that the SDL interface provides; In said infrared input thread; Can wait for receiving that when said thread was SOCKET input thread, said SOCKET input thread was used for the incoming event of barrage reception RTU (mobile phone, pad etc.) through the method that infrared ray ir interface provides; In said SOCKET input thread; Create UDP socket, and set special interface, barrage reception.
Concrete, in the embodiment of the invention, according to the thread of said thread creation unit 10 establishments; So that receive the incoming event of input equipment, wherein, the thread that said thread creation unit 10 is created comprises in USB input thread, infrared input thread and the SOCKET input thread any or several kinds; Said standardization unit 20 is exactly the incoming event according to the input equipment that thread received of said thread creation unit 10 establishments, the incoming event of the said input equipment that receives is analyzed, and be translated into the linux incoming event of standard; So that obtain the standard incoming event, the incoming event of the local USB device (mouse, keyboard) that arrives for said USB input thread barrage reception is because the incoming event that said local USB device obtains has been a standard Event; So without standardization, for the incoming event of said infrared ray input thread barrage reception infrared equipment (telepilot), because said infrared equipment is modeled to keyboard or mouse device with it in Drive Layer; And in the inner Drive Layer of infrared input thread, the incoming event that receives is modeled to keyboard and/or mouse incoming event; Keyboard that simulation is obtained and/or mouse incoming event can carry out standardization to said incoming event according to the key assignments ID that obtains as the standardization incoming event, for the incoming event of said SOCKET input thread barrage reception RTU (mobile phone, pad etc.); In the inner Drive Layer of SOCKET input thread, the incoming event that receives is converted into the keyboard and/or the mouse event of standard; With the keyboard that obtains and/or mouse incoming event as the standardization incoming event, for said RTU such as mobile phone, pad etc., can be through resolving the xml information in the incoming event; Obtain the type and the key assignments ID of incoming event; Carry out standardization, said standardization is meant that the incoming event with external unit changes into complete keyboard incoming event structure, mouse incoming event structure, wherein; Said keyboard incoming event structure comprises key_id; Key_symbol, key_scancod, key_event (down/up); Wherein, Said mouse incoming event structure comprises button_type (left button, right button, roller), button_event (press, upspring, move), value (displacement) etc.
Transmitting element 40 is used for the standard incoming event that the standardization with said standardization unit 20 obtains and is distributed to application program.
Concrete; The standard incoming event that transmitting element described in the embodiment of the invention 40 obtains according to the standardization of said standardization unit 20; The standard incoming event that the standardization of said standardization unit 20 is obtained is distributed to corresponding application; Said Event Service program has comprised an incident distribution mechanisms, and said incident distribution mechanisms receives said Event Service program and send to corresponding application through the incoming event of standardization with the mode of Parcel; The incoming event that is to say the 20 pairs of said input equipments that receive in said standardization unit is analyzed; And be translated into the linux incoming event of standard, obtain the standard incoming event, and will pass through the standard incoming event that the standardization of said standardization unit 20 obtains through said transmitting element 40 and send to application program; For said application program; Not spending differentiation is the input equipment of which kind of type, and promptly the type of the input equipment of shielding brings great convenience and favorable expansibility to program development like this.
Event Service program in the embodiment of the invention is created a plurality of different threads through thread creation unit 10; For use in the incoming event that receives different peripherals; These peripherals comprise infrared equipment, keyboard and mouse, remote equipment, bluetooth etc.; Because the incoming event of the peripherals that said service routine receives not is unified standard Event; So the incoming event through 20 pairs of said thread creations unit, said standardization unit 10 carries out standardization, is converted into the linux incoming event of standard,, the standard incoming event of obtaining is distributed to corresponding application so that will passing through the standard incoming event that the standardization of standardization unit 20 obtains through transmitting element 40 then; For said application program; Not spending differentiation is the input equipment of which kind of type, and promptly the type of the input equipment of shielding brings great convenience and favorable expansibility to program development like this.
See also Fig. 6, be the structural representation of a kind of incoming event management devices second embodiment of the present invention.Said incoming event management devices comprises thread creation unit 10, standardization unit 20, the transmitting element 40 among first embodiment of the described incoming event management devices of Fig. 5; In the present embodiment; Said standardization unit 20 further comprises: the first standardization unit 201, the second standardization unit 202, the 3rd standardization unit 203, wherein:
The said first standardization unit 201 is used for when said thread is USB input thread, to the incoming event of the local USB device of said USB input thread barrage reception, and with the incoming event of said local USB device as the standard incoming event;
Concrete; In the embodiment of the invention; When the thread of creating when said thread creation unit 10 is USB input thread; The USB input thread that the said first standardization unit 201 is created according to said thread creation unit 10 is through the incoming event of the said local USB device of USB input thread barrage reception such as mouse or keyboard, because the incoming event that said local USB device obtains has been a standard Event; So need not analyze and be converted into the linux incoming event of standard to the incoming event of the said local USB device that receives, directly the incoming event with the said local USB device that receives sends to corresponding application.
The said second standardization unit 202; Be used for when said thread is infrared input thread; Said infrared ray input thread is used for the incoming event of barrage reception infrared equipment; And in the inner Drive Layer of infrared input thread, the incoming event that receives being modeled to keyboard and/or mouse incoming event, keyboard that simulation is obtained and/or mouse incoming event are as the standardization incoming event;
Concrete, in the embodiment of the invention, when the thread of creating when said thread creation unit 10 is infrared ray input thread; The infrared ray input thread that said second processing unit 202 is created according to said thread creation unit 10, the incoming event through said infrared ray input thread barrage reception infrared equipment (telepilot) is concerning said infrared equipment, and the communication between said long-range infrared equipment and the said Event Service program needs the agreement of an infrared communication; Be that said Event Service program will receive remote events, must said Event Service program inside have with telepilot between the agreement of communicating by letter, described communication protocol is exactly infrared communication protocol; As for what content of this protocol transmission, usually by developer oneself definition, inside STB; The driver that individual infrared communication is arranged usually receives the incoming event that said infrared equipment such as telepilot send through said driver, when pressing key of said telepilot; Said telepilot only can send the key assignments ID of this key, and generally speaking, this key assignments ID is the same with the corresponding key assignments ID of keyboard; The key assignments ID that said infrared equipment such as telepilot send over has been modeled to the key assignments ID of keyboard; And, not only need key assignments ID for the keyboard incoming event of standard, also need KEY_SYMBOL; Key assignments such as KEY_TYPE are described; So when said Event Service program receives this key assignments ID, need carry out standardization, so that obtain the standard incoming event to said incoming event.
Said the 3rd standardization unit 203; Be used for when said thread is SOCKET input thread; Said SOCKET input thread is used for the incoming event of barrage reception RTU; And in the inner Drive Layer of SOCKET input thread, the incoming event that receives is converted into the keyboard and/or the mouse event of standard, with the keyboard that obtains and/or mouse incoming event as the standardization incoming event.
Concrete, when the thread of creating when said thread creation unit 10 in the embodiment of the invention is SOCKET input thread, the SOCKET input thread that said the 3rd standardization unit 203 is created according to said thread creation unit 10; Through the incoming event of said SOCKET input thread barrage reception RTU, concerning said RTU, said RTU intercoms through socket with said Event Service program mutually; Wherein, the content of the communication between the two is exactly XML, when said Event Service program receives the XML content; According to the evt_class label, can judge that this incident is keyboard incoming event or mouse incoming event, according to the evt_type label; Can judge user input the incident of upspringing, press incident or moving event; When judgement is said KeyEvent,, obtain key assignments ID then according to the key_id label; Said Event Service program is carried out standardization according to said key assignments ID; When judgement is said mouse event, then carry out standardization, so that obtain the standard incoming event according to described XML form.
The embodiment of the invention is created the incoming event that different input threads receives different external equipment through said thread creation unit 10; To it carries out standardization through said standardization unit 20; Be translated into the linux incoming event of standard; And the standardization incoming event that obtains after the standardization being sent to corresponding application through transmitting element 40, the embodiment of the invention has been created USB input thread, infrared input thread and SOCKET input thread respectively.Accordingly; Said standardization unit 20 comprises the first standardization unit 201, the second standardization unit 202, the 3rd standardization unit 203; Wherein, The USB input thread that the said first standardization unit 201 is created according to said thread creation unit 10, through the incoming event of the local USB device of said USB input thread barrage reception, the incoming event of said local USB device is standardized incident; Need not carry out standardized processing to the incoming event of the local USB device that receives this moment; The infrared ray input thread that the said second standardization unit 202 is created according to said thread creation unit 10 through the incoming event of said infrared ray input thread barrage reception infrared equipment, and carries out standardization to the incoming event of the infrared equipment that receives; The SOCKET input thread that said the 3rd standardization unit 203 is created according to said thread creation unit 10; Through the incoming event of said SOCKET input thread barrage reception RTU, and the SOCKET incoming event that receives carried out standardization, therefore; For each application program in the client; Effectively shielded the type of Event origin and the difference of different input equipments at event server described in the program development process, and incident has been carried out standardization, brought convenience and favorable expansibility to program development.
See also Fig. 7, be the structural representation of the 3rd embodiment of a kind of incoming event management devices of the present invention.Said incoming event management devices comprises thread creation unit 10, standardization unit 20, the transmitting element 40 among first embodiment of the described incoming event management devices of Fig. 5; In the present embodiment; Said incoming event management devices further comprises: application program registering unit 30, application program management unit 50, wherein:
Said application program registering unit 30 is used for guaranteeing in the application program that said Event Service program is registered, have and have only an application program to be in state of activation STATE_ACTIVE state, guarantees to have only an application program can receive incident at every turn;
Concrete; The embodiment of the invention is created the incoming event that different input threads receives different external equipment through said thread creation unit 10; The incoming event of the 20 pairs of said external units in said standardization unit carries out standardization, is translated into the linux incoming event of standard, so that obtain the standard incoming event; Said transmitting element 40 sends to corresponding application with the standard incoming event; That is to say that said standard incoming event is by said service routine distribution corresponding application, for said application program, if said application program need obtain the Event Service of standard incoming event; Then must pass through application program registering unit 30 in advance to said Event Service program registration; Just might obtain the Event Service of said standard incoming event, that is to say said application program if the standard incoming event after expecting the standardization of standardization unit 20, such as; After application program receives the ESC incident; Program withdraws from, and said application program will be passed through application program registering unit 30 to said Event Service program registration in advance, just might from said Event Service program, obtain the incident value of said standard incoming event.
In the embodiment of the invention; Behind said Event Service program start; Can create a fifo fifo and supply said application program registration; If when said application program need obtain the Event Service of standard incoming event; Then must pass through application program registering unit 30 in advance to said Event Service program registration; The information of said registration comprises synchronizing information mgcnum, process PID, process status, event filter and MS (MASTER-SLAVE) state, and wherein, said process PID is used for this process of unique identification; The object of process status monitoring after this process PID also becomes, said process status comprise unactivated state (STATE_INACTIVE), state of activation (STATE_ACTIVE), deletion state (STATE_DELETE), non-activation not switching state (STATE_INACT_NOSWITCH), activate not switching state (STATE_ACT_NOSWITCH).
Said application program management unit 50; In the application program that the application program management mechanism that said Event Service program basis presets guarantees in said Event Service program, to register; There is and has only an application program to be in state of activation STATE_ACTIVE, guarantee to have only an application program can receive incident at every turn.
Concrete; The login mechanism of application program described in the embodiment of the invention through application program registering unit 30 sends registration, Logout Events and gives said Event Service program; Said Event Service program receives after the registered events; Judge through said application program management unit 50 whether said process PID is present in the registration formation that said Event Service program safeguarded; If exist; Then contrast the state in login state and the formation, and make corresponding state transition process, the supported state exchange of said registered events unactivated state (STATE_INACTIVE), state of activation (STATE_ACTIVE), deletion state (STATE_DELETE), non-activation not switching state (STATE_INACT_NOSWITCH), do not activate and change between the switching state (STATE_ACT_NOSWITCH); Said Event Service program is kept at registration of application program information in the registration formation; In said registration formation, having and have only the state of an application program is STATE_ACTIVE, and the MS state that has and have only an application program is MASTER.
In the embodiment of the invention; In state conversion process; If do not relate to the ACTIVE state, the state of simply revising corresponding application programs in the said registration formation both can, if relate to the ACTIVE state; The application program of supposing current ACTIVE is active_current, the switching of a few step completion statuses below then dividing:
The first step judges whether the state of active_current application program is to activate not switching state STATE_ACTIVE_NOSWITCH, if incoming event is not then done any processing, directly ignores this state handover event; If registered events then carried out for second step;
In second step, from said registration formation, find the next one can activate the application program (active_next) of ACTIVE;
The 3rd step, send non-activation INACTIVE incident to the active_current application program, it is non-enable mode STATE_INACTIVE that the state of this application program in said registration formation is set;
The 4th step, send activation ACTIVE incident to the active_next application program, it is enable mode STATE_ACTIVE that the state of this application program in the registration formation is set.
In the embodiment of the invention, when said application program need obtain the Event Service of standard incoming event, then must be in advance to said event server registration; Behind the said Event Service program start; Can create a fifo fifo and supply said application program registration, said application program is given said Event Service program through login mechanism transmission registration, the Logout Events of application program registering unit 30, and said service end is kept at registration of application program information in the registration formation; Said Event Service end also comprises application program management mechanism; Said Event Service program guarantees in the application program of said registration have and have only an application program to be in the STATE_ACTIVE state through said application program management unit 50, also just mean; Have only an application program can receive incident at every turn; Said Event Service program receives after these incidents, judges at first whether this process PID is present in the registration formation that said Event Service end safeguarded, if exist; Then contrast the state in login state and the formation, and make corresponding state transition process.
See also Fig. 8, be the structural representation of the 4th embodiment of a kind of incoming event management devices of the present invention.Said incident management device comprises thread creation unit 10, standardization unit 20, the transmitting element 40 among first embodiment of the described incoming event management devices of Fig. 5; In the present embodiment; Said incoming event management devices further comprises: customized event processing unit 60, Condition Monitoring Unit 70, wherein:
Said customized event processing unit 60 is used for said Event Service program when receiving the User Defined incident, and said user-defined incident is carried out self-defined processing.
Concrete; Application program in the embodiment of the invention has comprised the customized event treatment mechanism, and said Event Service program is carried out self-defined processing according to the customized event treatment mechanism that presets to said user-defined incident when receiving user-defined incident; Said user-defined incident comprises the mode switch incident, returns the homepage incident; Such as F1 is a mode switching key, and F2 is back the homepage key, after said Event Service program is received said special event F1; The management of process mechanism of said Event Service program is carried out the state exchange between process according to the state of current application program; After said Event Service program is received special event F2, if the current application program state for activating non-switch mode STATE_ACT_NOSWITCH any action does not take place then; If the current application program state is state of activation STATE_ACTIVE; Then send non-activation INACTIVE incident and give current application program; To return homepage BACK_HOME incident then, to send to master-slave mode MS state be the application program of MASTER; Simultaneously, described Application Status is set to state of activation STATE_ACTIVE.
Said Condition Monitoring Unit 70 is used for the formation of periodic polling registrer application, according to its state of process instruction character detection of said application program, and safeguards said registrer application formation.
Concrete, the Event Service service routine comprises Condition Monitoring Unit 70 described in the example according to the invention, the monitoring thread in the said monitoring means 70 is that said application program is launched; The said registrer application formation of this status monitoring thread periodic polling, its state of process instruction character pid detection according to said application program withdraws from if said application program is improper; Judge that at first this withdraws from Application Status; If enable mode STATE_ACTIVE or activate non-switch mode STATE_ACT_NOSWITCH, then by returning homepage BACK_HOME event handling, otherwise; Directly this application program is deleted from said registrer application formation; The formation of said status monitoring thread periodic polling registrer application according to its state of process instruction character detection of said application program, and is safeguarded said registrer application formation.
One of ordinary skill in the art will appreciate that all or part of flow process that realizes in the foregoing description method; Be to instruct relevant hardware to accomplish through computer program; Described program can be stored in the computer read/write memory medium; This program can comprise the flow process like the embodiment of above-mentioned each side method when carrying out.Wherein, described storage medium can be magnetic disc, CD, read-only storage memory body (Read-Only Memory, ROM) or at random store memory body (Random Access Memory, RAM) etc.
Above disclosedly be merely preferred embodiment of the present invention; Certainly can not limit the present invention's interest field with this; One of ordinary skill in the art will appreciate that all or part of flow process that realizes the foregoing description; And, still belong to the scope that invention is contained according to the equivalent variations that claim of the present invention is done.
Claims (13)
1. an incoming event management method is characterized in that, comprising:
The Event Service program creation that presets is used to receive the thread of the incoming event of input equipment;
Incoming event according to said thread receives carries out standardization to said incoming event and obtains the standard incoming event;
Said standard incoming event is distributed to application program.
2. the method for claim 1 is characterized in that, the thread of said establishment comprises in the end points SOCKET input thread of USB input thread, infrared input thread and process communication any or several kinds.
3. the method for claim 1 is characterized in that, the said incoming event that receives according to said thread carries out standardization to said incoming event and obtains the standard incoming event and comprise:
When said thread was USB input thread, said USB input thread was used for the incoming event of the local USB device of barrage reception, and with the incoming event of said local USB device as the standard incoming event;
When said thread is infrared input thread; Said infrared ray input thread is used for the incoming event of barrage reception infrared equipment; And in the inner Drive Layer of infrared input thread, the incoming event that receives being modeled to keyboard and/or mouse incoming event, keyboard that simulation is obtained and/or mouse incoming event are as the standardization incoming event;
When said thread is SOCKET input thread; Said SOCKET input thread is used for the incoming event of barrage reception RTU; And in the inner Drive Layer of SOCKET input thread, the incoming event that receives is converted into the keyboard and/or the mouse event of standard, with the keyboard that obtains and/or mouse incoming event as the standardization incoming event.
4. the method for claim 1 is characterized in that, said incident with the standardization of said process comprises before being distributed to application program:
When application program need be obtained the incoming event service, said application program was to said Event Service program registration.
5. method as claimed in claim 4 is characterized in that, also comprises:
In the application program that the application program management mechanism that said Event Service program basis presets guarantees in said Event Service program, to register; There is and has only an application program to be in state of activation STATE_ACTIVE, guarantee to have only an application program can receive incident at every turn.
6. the method for claim 1 is characterized in that, also comprises:
Said Event Service program is carried out self-defined processing according to the customized event treatment mechanism that presets to said user-defined incident when receiving user-defined incident.
7. the method for claim 1 is characterized in that, also comprises: Event Service program creation status monitoring thread, wherein,
The formation of said status monitoring thread periodic polling registrer application according to its state of process instruction character detection of said application program, and is safeguarded said registrer application formation.
8. an incoming event management devices is characterized in that, comprising:
The thread creation unit, the Event Service program creation thread that is used to preset is so that receive the incoming event of input equipment;
The standardization unit is used for receiving according to said thread creation unit the incoming event of input equipment, said incoming event is carried out standardization obtain the standard incoming event;
Transmitting element is used for the standard incoming event that the standardization with said standardization unit obtains and is distributed to application program.
9. device as claimed in claim 8 is characterized in that, said standardization unit comprises:
The first standardization unit is used for when said thread is USB input thread, to the incoming event of the local USB device of said USB input thread barrage reception, and with the incoming event of said local USB device as the standard incoming event;
The second standardization unit; Be used for when said thread is infrared input thread; Said infrared ray input thread is used for the incoming event of barrage reception infrared equipment; And in the inner Drive Layer of infrared input thread, the incoming event that receives being modeled to keyboard and/or mouse incoming event, keyboard that simulation is obtained and/or mouse incoming event are as the standardization incoming event;
The 3rd standardization unit; Be used for when said thread is SOCKET input thread; Said SOCKET input thread is used for the incoming event of barrage reception RTU; And in the inner Drive Layer of SOCKET input thread, the incoming event that receives is converted into the keyboard and/or the mouse event of standard, with the keyboard that obtains and/or mouse incoming event as the standardization incoming event.
10. device as claimed in claim 8 is characterized in that, comprising:
The application program registering unit is used for when application program need be obtained the incoming event service, and said application program is to said Event Service program registration.
11. device as claimed in claim 8 is characterized in that, comprising:
The application program management unit is used for guaranteeing in the application program that said Event Service program is registered, have and have only an application program to be in state of activation STATE_ACTIVE state, guarantees to have only an application program can receive incident at every turn.
12. device as claimed in claim 8 is characterized in that, also comprises:
The customized event processing unit is used for said Event Service program when receiving the User Defined incident, and said user-defined incident is carried out self-defined processing.
13. device as claimed in claim 8 is characterized in that, also comprises:
Condition Monitoring Unit is used for the formation of periodic polling registrer application, according to its state of process instruction character detection of said application program, and safeguards said registrer application formation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101206159A CN102681845A (en) | 2012-04-24 | 2012-04-24 | Method and device for managing input events |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101206159A CN102681845A (en) | 2012-04-24 | 2012-04-24 | Method and device for managing input events |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102681845A true CN102681845A (en) | 2012-09-19 |
Family
ID=46813822
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012101206159A Pending CN102681845A (en) | 2012-04-24 | 2012-04-24 | Method and device for managing input events |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102681845A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103257893A (en) * | 2013-05-28 | 2013-08-21 | 腾讯科技（深圳）有限公司 | Method, device and system for obtaining input event state |
| CN104253842A (en) * | 2013-06-28 | 2014-12-31 | 华为技术有限公司 | Method and device for synchronizing terminal mirrors, terminal and server |
| CN105117223A (en) * | 2015-08-20 | 2015-12-02 | 广东欧珀移动通信有限公司 | Processing method and system of input event |
| CN107704115A (en) * | 2017-08-28 | 2018-02-16 | 北京翼辉信息技术有限公司 | The input equipment information management system and method for a kind of embedded real-time operating system |
| CN110362353A (en) * | 2019-07-04 | 2019-10-22 | Oppo广东移动通信有限公司 | Peripheral hardware control method, peripheral controller, storage medium and electronic equipment |
| CN113687925A (en) * | 2021-07-22 | 2021-11-23 | 成都鲁易科技有限公司 | Equipment operation processing method and device, storage medium and computer equipment |
| CN113835788A (en) * | 2021-11-25 | 2021-12-24 | 广州朗国电子科技股份有限公司 | Method for quickly acquiring input event and method for quickly responding to input event |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6457064B1 (en) * | 1998-04-27 | 2002-09-24 | Sun Microsystems, Inc. | Method and apparatus for detecting input directed to a thread in a multi-threaded process |
| CN1486093A (en) * | 2002-09-27 | 2004-03-31 | 上海贝尔有限公司 | Channel scheduling device based on operation system in embedded system |
| CN102314348A (en) * | 2011-09-15 | 2012-01-11 | Tcl集团股份有限公司 | Android system development framework and development device |
-
2012
- 2012-04-24 CN CN2012101206159A patent/CN102681845A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6457064B1 (en) * | 1998-04-27 | 2002-09-24 | Sun Microsystems, Inc. | Method and apparatus for detecting input directed to a thread in a multi-threaded process |
| CN1486093A (en) * | 2002-09-27 | 2004-03-31 | 上海贝尔有限公司 | Channel scheduling device based on operation system in embedded system |
| CN102314348A (en) * | 2011-09-15 | 2012-01-11 | Tcl集团股份有限公司 | Android system development framework and development device |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014190788A1 (en) * | 2013-05-28 | 2014-12-04 | Tencent Technology (Shenzhen) Company Limited | Method, apparatus and system for acquiring input events |
| CN103257893B (en) * | 2013-05-28 | 2016-06-15 | 腾讯科技（深圳）有限公司 | A kind of methods, devices and systems obtaining input state-event |
| CN103257893A (en) * | 2013-05-28 | 2013-08-21 | 腾讯科技（深圳）有限公司 | Method, device and system for obtaining input event state |
| CN104253842A (en) * | 2013-06-28 | 2014-12-31 | 华为技术有限公司 | Method and device for synchronizing terminal mirrors, terminal and server |
| US9832259B2 (en) | 2013-06-28 | 2017-11-28 | Huawei Technologies Co., Ltd. | Method and apparatus for cell configuration |
| CN104253842B (en) * | 2013-06-28 | 2018-03-06 | 华为技术有限公司 | Method, apparatus, terminal and the server of synchronous terminal mirror image |
| CN105117223B (en) * | 2015-08-20 | 2018-11-27 | 广东欧珀移动通信有限公司 | The processing method and system of incoming event |
| CN105117223A (en) * | 2015-08-20 | 2015-12-02 | 广东欧珀移动通信有限公司 | Processing method and system of input event |
| CN107704115A (en) * | 2017-08-28 | 2018-02-16 | 北京翼辉信息技术有限公司 | The input equipment information management system and method for a kind of embedded real-time operating system |
| CN110362353A (en) * | 2019-07-04 | 2019-10-22 | Oppo广东移动通信有限公司 | Peripheral hardware control method, peripheral controller, storage medium and electronic equipment |
| CN113687925A (en) * | 2021-07-22 | 2021-11-23 | 成都鲁易科技有限公司 | Equipment operation processing method and device, storage medium and computer equipment |
| CN113687925B (en) * | 2021-07-22 | 2023-09-29 | 成都鲁易科技有限公司 | Equipment operation processing method and device, storage medium and computer equipment |
| CN113835788A (en) * | 2021-11-25 | 2021-12-24 | 广州朗国电子科技股份有限公司 | Method for quickly acquiring input event and method for quickly responding to input event |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102681845A (en) | Method and device for managing input events | |
| CN104301373B (en) | Via the synchronous sending out notice of file-sharing service | |
| US10587453B2 (en) | Method and apparatus for IPMI-bridge-server for non-IPMI devices | |
| CN105426189A (en) | Notification bar combining method and system | |
| CN107277162B (en) | Intelligent home management system and method based on network cloud | |
| CN103677858A (en) | Method, system and device for managing virtual machine software in cloud environment | |
| CN103069747A (en) | Method and apparatus for establishing communication | |
| CN105827428A (en) | Management method and device of asset information | |
| CN105307024A (en) | Graphic and text information interface control method and device based on internet of videos | |
| CN102724334A (en) | Notification and acquisition method, device and system for address information change in digital living network alliance (DLNA) | |
| JP2019530108A (en) | Method and apparatus for centralized management of personnel and equipment based on instant messaging applications | |
| CN113037545A (en) | Network simulation method, device, equipment and storage medium | |
| CN111913884A (en) | Distributed test method, device, equipment, system and readable storage medium | |
| CN106909327A (en) | A kind of display control unit for industrial control equipment | |
| CN102436350A (en) | Remote application window display method, server and user terminal | |
| CN111078348B (en) | Interface management method, device, equipment and storage medium | |
| US20200272514A1 (en) | Information processing terminal, non-transitory recording medium, and control method | |
| CN103716230A (en) | Message sending method, device and server | |
| CN102222008A (en) | Systems and methods for interface management | |
| CN106341463A (en) | A mobile internet audio/video management and control system based on an internet of things | |
| CN110178353A (en) | Method for processing business, Cloud Server and terminal device | |
| CN106797393A (en) | For being the method for labeling assignments action in network, corresponding network and control device | |
| CN105808313B (en) | Intelligent terminal data interactive system and method | |
| CN103475870A (en) | Distributed extendable intelligent video surveillance system | |
| CN108234584A (en) | The method and apparatus that structure moving advertising is subscribed to based on change |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20120919 |
|
| RJ01 | Rejection of invention patent application after publication |