CN101364190B - Method for executing synchronous and asynchronous operation on graphical user interface and device - Google Patents
Method for executing synchronous and asynchronous operation on graphical user interface and device Download PDFInfo
- Publication number
- CN101364190B CN101364190B CN2008101612940A CN200810161294A CN101364190B CN 101364190 B CN101364190 B CN 101364190B CN 2008101612940 A CN2008101612940 A CN 2008101612940A CN 200810161294 A CN200810161294 A CN 200810161294A CN 101364190 B CN101364190 B CN 101364190B
- Authority
- CN
- China
- Prior art keywords
- incident
- event
- filtrator
- event queue
- handling thread
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- User Interface Of Digital Computer (AREA)
Abstract
The invention discloses a method and a device for synchronous and asynchronous operation executed by a graphical user interface. The method for synchronous and asynchronous operation executed by the graphical user interface comprises the following steps: an event queue filter receives events output by an event queue, wherein, the event queue filter is used for filtering the events; the event queue filter checks whether events are identical with the events received existing in a background event treatment thread pool, if the events are identical with the events received existing in the background event treatment thread pool, the identical events are filtered; the background event treatment thread pool is used for managing correlation relation between the events and an event treatment thread corresponding to the events; an event dispatching thread dispatches events from the event queue filter. Through the invention, the asynchronous operation effectively prevents the misoperation of a user.
Description
Technical field
The present invention relates to the user interface techniques field, relate in particular to graphic user interface and carry out method and device synchronous, asynchronous operation.
Background technology
When graphic user interface GUI operates the execution user, two kinds of patterns are arranged: synchronous mode of operation and asynchronous operation pattern.Synchronous mode of operation is meant carries out user's next one operation after complete to one of user operation.The asynchronous operation pattern is meant when operation carrying out the user, needn't wait for that this EO just can carry out user's the next one immediately and operate.
Development kit as graphic user interface, Swing carries out user's operation and is specially: Swing becomes each incident with user's operation map, and each incident is put in the event queue (Event Queue), incident is distributed thread (EDT, Event Dispatch Thread) and the incident in the event queue is distributed to the button.onrelease Event Listener of corresponding assembly is handled.When carrying out synchronous mode of operation, EDT waits for that Event Listener handles the notice of an incident, just distributes next incident.Therefore, the current incident of handling can be blocked successor.When carrying out the asynchronous operation pattern, Event Listener can start new thread and come processing events, just notifies EDT to distribute incident once more after can handling incident like this.
The inventor is in research process, find that prior art comprises following shortcoming at least: for synchronous mode of operation, when the execution user operates, after EDT waits for that Event Listener handles an incident, just distribute next incident, in the EDT wait process, the user may carry out screen-refresh etc. and the irrelevant operation of functional performance, at this moment, the incident of these operation map will can not distributed by EDT, therefore, the ash screen can appear in graphic user interface, brings relatively poor operating experience to the user.And, in EDT wait process, the user also might carry out unwanted operation bidirectional originally to graphic user interface, the for example operation relevant such as input operation with functional performance, these operation bidirectionals of user can the incident of being mapped as be put in the event queue, therefore EDT carries out the incident of operation bidirectional in the back extended meeting, and the user does not wish to carry out operation bidirectional.
For the asynchronous operation pattern, can't stop misoperation of users.Be specially:, cause twice identical operations all to be performed because the user may trigger identical operations twice.
Summary of the invention
In view of this, the invention provides a kind of graphic user interface and carry out method and device synchronous, asynchronous operation, when carrying out synchronous operation, bring operating experience preferably, when carrying out asynchronous operation, stop misoperation of users to the user.
A kind of graphic user interface is carried out the method for synchronous operation, and described method comprises:
The event queue filtrator receives the incident of event queue output, and wherein, described event queue filtrator is used for incident is filtered;
Incident is distributed thread and distribute first incident from described event queue filtrator, and exports described first incident to button.onrelease;
Button.onrelease is not handled described first incident, starts the event handling thread, by described first incident of event handling thread process; Button.onrelease notifies described event queue filtrator to filter out incident a, and notifies described incident to distribute thread and continue to distribute next event from described event queue filtrator, and described incident a is the incident of the operation map relevant with functional performance;
The event handling thread receives described first incident of described button.onrelease output, according to the described first incident executable operations.
Alternatively, after described event handling thread executed operation according to described first incident, described method also comprised:
Described event handling thread is notified the filtration of described event queue filtrator end to incident a.
Alternatively, before described event handling thread was notified the filtration of described event queue filtrator end to incident a, described method also comprised:
Described event handling thread refresh graphics user interface.
A kind of graphic user interface is carried out the method for asynchronous operation, and described method comprises:
The event queue filtrator receives the incident of event queue output, and wherein, described event queue filtrator is used for incident is filtered;
Described event queue filtrator checks in backstage event handling thread pool whether the incident identical with the incident that receives is arranged, if have, then filter out described identical incident, described backstage event handling thread pool is used for the incidence relation of Admin Events and the event handling thread corresponding with it;
Incident is distributed thread and distribute incident from described event queue filtrator;
Described incident is distributed thread and is exported the incident of distributing to button.onrelease; Button.onrelease is not handled the incident of distributing, and starts the event handling thread, by the incident executable operations of event handling thread to distributing.
Alternatively, start in the process of event handling thread at described button.onrelease, described method also comprises:
The incidence relation that described button.onrelease is put into the event handling thread of described incident of distributing and startup is put into backstage event handling thread pool.
A kind of graphic user interface is carried out the device of synchronous operation, and described device comprises:
The event queue filtrator is used to receive the incident of event queue output, filters out incident a, and described incident a is the incident of the operation map relevant with functional performance;
Incident is distributed thread units, is used for distributing first incident from described event queue filtrator, and exports described first incident to the button.onrelease unit;
The button.onrelease unit is not handled described first incident, is used to start the event handling thread units, handles described first incident by the event handling thread units; The button.onrelease unit notifies described event queue filtrator to filter out incident a, and notifies described incident to distribute thread units and continue to distribute next event from described event queue filtrator;
The event handling thread units is used to receive described first incident that described button.onrelease unit is exported, according to the described first incident executable operations.
Preferably, described event handling thread units comprises:
Notification unit is used to notify the filtration of described event queue filtrator end to incident a;
Refresh unit is used for the refresh graphics user interface.
A kind of graphic user interface is carried out the device of asynchronous operation, and described device comprises:
The event queue filtrator, be used to receive the incident of event queue output, in backstage event handling thread pool, check whether the incident identical with the incident that receives is arranged, if have, then filter out described identical incident, described backstage event handling thread pool is used for the incidence relation of Admin Events and the event handling thread corresponding with it;
Incident is distributed thread units, is used for distributing incident from described event queue filtrator, exports the incident of distributing to the button.onrelease unit;
Described button.onrelease unit is not handled the incident of distributing, and starts the event handling thread units;
Described event handling thread units is used to receive the incident from described button.onrelease unit, according to the incident executable operations that receives.
As can be seen, for synchronous operation, because button.onrelease is processing events no longer, but start the event handling thread, by event handling thread process incident, like this, button.onrelease just can the fast notification incident be distributed thread and is continued to distribute incident, and, the event queue filtrator can filter out the operation relevant with functional performance, and therefore, the screen-refresh that the user carries out etc. can in time be distributed and be handled with the incident of the operation map that the functional form operation has nothing to do, the generation of the user interface ash screen that effectively stops has brought operating experience preferably to the user.And when event handling thread process incident, the event queue filtrator can filter out the incident relevant with functional performance, so, effectively stoped the user not wish the operation bidirectional of carrying out originally.
For asynchronous operation, since the event queue filtrator can filter out with backstage event handling thread pool in identical incident, so the incident identical with incident in the backstage event handling thread pool will do not distributed, so stoped the user because twice identical operations that maloperation causes.
Description of drawings
Fig. 1 carries out the method flow diagram of synchronous operation for graphic user interface of the present invention;
Fig. 2 carries out the method specific embodiment process flow diagram of synchronous operation for graphic user interface of the present invention;
Fig. 3 carries out the method flow diagram of asynchronous operation for graphic user interface of the present invention;
Fig. 4 carries out the method specific embodiment process flow diagram of asynchronous operation for graphic user interface of the present invention;
Fig. 5 carries out the structure drawing of device of synchronous operation for graphic user interface of the present invention;
Fig. 6 carries out the structure drawing of device of asynchronous operation for graphic user interface of the present invention.
Embodiment
For above-mentioned feature of the present invention, advantage are become apparent more, the present invention is described in detail below in conjunction with embodiment.
Please refer to Fig. 1, show the method flow diagram that graphic user interface of the present invention is carried out synchronous operation, comprising:
Step 101: the event queue filtrator receives the incident of event queue output, and wherein, described event queue filtrator is used for incident is filtered;
Step 102: incident is distributed thread and distribute first incident from described event queue filtrator, and exports described first incident to button.onrelease;
Step 103: button.onrelease starts the event handling thread, notify described event queue filtrator to filter out incident a, and notify described incident to distribute thread and continue from described event queue filtrator, to distribute next event, described incident a is the incident of the operation map relevant with functional performance;
Step 104: the event handling thread receives described first incident of described button.onrelease output, according to the described first incident executable operations.
Below in conjunction with embodiment step shown in Figure 1 is elaborated.
Please refer to Fig. 2,, can comprise for the present invention carries out synchronous operation method embodiment process flow diagram:
Step 201: the user is executable operations on graphic user interface;
Step 202: in Swing, the operation map that the user is carried out is each incident, and each incident is put into Event Queue;
Step 203:Event Queue exports each incident to event queue filtrator Event QueueFilter;
Step 204:EDT distributes incident A from Event Queue Filter, incident A is distributed to EventListener;
Step 205:Event Listener starts event handling thread A Event Worker A, notice EventQueue Filter filters out the incident of the operation map relevant with functional performance, and notice EDT continues to distribute next incident from Event Queue Filter.
Because Event Queue Filter falls the event filtering of the operation map relevant with functional performance, therefore, EDT can only distribute the incident of the operation map that has nothing to do with functional performance from Event Queue Filter.Wherein, the operation relevant with functional performance comprises: input character etc., the operation irrelevant with functional performance comprises: screen-refresh, window amplify or dwindle etc.
Incident A is handled by Event Worker A.The incident with the irrelevant operation map of functional performance that EDT distributes is handled by the Event Worker that Event Listener starts equally, can be a new Event Worker B, can also after handling incident A, Event Worker A continue to handle by Event Worker A.
As can be seen, because Event Listener is processing events no longer, but start Event Worker, by Event Worker processing events, like this, Event Listener just can continue to distribute incident by fast notification EDT, and therefore, the incident of the operation map that has nothing to do with functional performance among the Event Queue Filter can be distributed away fast to be handled.It needs to be noted, Event Listener also will notify EventQueue Filter to filter out the incident of the operation map relevant with functional performance this moment, for the user, the operation of carrying out on graphic user interface this moment relevant with functional performance is promptly by " pinning ".Because the operation relevant with functional performance is filtered, EDT can only distribute from Event Queue Filter and the irrelevant operation of functional performance.Therefore, effectively stoped the generation of graphic user interface ash screen, brought operating experience preferably to the user.
Event WorkerA handles after the incident A, the refresh graphics user interface, notice Event QueueFilter stops the incident of the operation map relevant with functional performance is filtered, for the user, no longer after the filter event, the operation relevant with functional performance promptly is " unlocked " Event Queue Filter.At this moment, the operation relevant with functional performance can continue the incident of being mapped as and handle.
And when Event WorkerA processing events A, Event Queue Filter can filter out the operation relevant with functional performance, so, effectively stoped the user not wish the operation bidirectional of carrying out originally.
Please refer to Fig. 3, the method flow diagram for graphic user interface execution asynchronous operation of the present invention comprises:
Step 301: the event queue filtrator receives the incident of event queue output, and wherein, described event queue filtrator is used for incident is filtered;
Step 302: described event queue filtrator checks in backstage event handling thread pool whether the incident identical with the incident that receives is arranged, if have, then filter out described identical incident, described backstage event handling thread pool is used for the incidence relation of Admin Events and the event handling thread corresponding with it;
Step 303: incident is distributed thread and distribute incident from the event queue filtrator.
Below in conjunction with embodiment step shown in Figure 3 is elaborated.
In the asynchronous operation pattern, EDT distributes incident and gives Event Listener, Event Listener starts Event Worker thread, handle by Event Worker thread, Event Listener puts into backstage event handling thread pool with the incidence relation of the Event Worker of the incident and the incident of execution, and backstage event handling thread pool is used for the incidence relation of the Event Worker of the Admin Events and the incident of execution.
Please refer to Fig. 4,, can comprise for the present invention carries out asynchronous operation method embodiment process flow diagram:
Step 401: the user is executable operations on graphic user interface;
Step 402: in Swing, the operation map that the user is carried out is each incident, and each incident is put into Event Queue;
Step 403:Event Queue exports each incident to event queue filtrator Event QueueFilter;
Step 404:EDT distributes incident from Event Queue Filter;
Event Queue Filter checks in backstage event handling thread pool, whether the incident in the backstage event handling thread pool of checking has the incident identical with the incident that receives, if have, filter out in the incident that receives with backstage event handling thread pool in the identical incident of certain incident.
Therefore, in step 404, the incident identical with certain incident in the event handling pond, backstage is left in the basket, will do not distributed.
Wherein, whether have with the incident that receive identical incident be specially: the incident that receives according to Event QueueFilter if checking, the all incidence relations of traversal in backstage event handling thread pool, the incident with the incidence relation correspondence compares with the incident that receives again.
Step 405:EDT exports the incident of distributing to Event Listener;
Step 406:Event Listener starts Event Worker thread, is handled by Event Worker thread, and incident and the incidence relation of the Event Worker of the incident of execution are put into backstage event handling thread pool.
As can be seen, since Event Queue Filter can filter out with backstage event handling thread pool in identical incident, so the incident identical with incident in the backstage event handling thread pool will do not distributed, so stoped the user because twice identical operations that maloperation causes.
Please refer to Fig. 5, the structure drawing of device for graphic user interface execution synchronous operation of the present invention comprises:
Event queue filtrator 501 is used to receive the incident of event queue output, filters out incident a, and described incident a is the incident of the operation map relevant with functional performance;
Incident is distributed thread 502, is used for distributing first incident from described event queue filtrator, and exports described first incident to button.onrelease;
Button.onrelease 503 is used to start the event handling thread, notifies described event queue filtrator to filter out incident a, and notifies described incident to distribute thread and continue to distribute next event from described event queue filtrator;
Event handling thread 504: be used to receive described first incident of described button.onrelease output, according to the described first incident executable operations.
In conjunction with the method embodiment of graphic user interface execution synchronous operation, the event handling thread can comprise:
Notification unit is used to notify the filtration of described event queue filtrator end to incident a;
Refresh unit is used for the refresh graphics user interface.
The operation that each unit is carried out is elaborated below.
Event queue filtrator Event Queue Filter501 receives the incident of event queue output, incident is distributed thread EDT502 and distribute incident A from event queue filtrator 501, incident is distributed the Listener503 to button.onrelease Event, button.onrelease 503 starts event handling thread Event Worker A, notification event formation filtrator 501 filters out the incident of the operation map relevant with functional performance, and notification event is distributed thread 502 continue to distribute next incident from event queue filtrator 501.Incident A is handled by event handling thread A.
When incident A handled, incident was distributed thread A refresh graphics user interface, and notification event formation filtrator 501 stops the incident of the operation map relevant with functional performance is filtered.
Because can the fast notification incident distributing thread 502, button.onrelease 503 continues to distribute next incident, and event queue filtrator 501 filters out the operation relevant with functional performance, incident is distributed thread can only be distributed the operation map that has nothing to do with functional performance from the event queue filtrator incident, therefore, effectively stoped the ash screen phenomenon of graphic user interface, brought operating experience preferably to the user.
And when Event WorkerA processing events A, Event Queue Filter can filter out the operation relevant with functional performance, so, effectively stoped the user not wish the operation bidirectional of carrying out originally.
Please refer to Fig. 6, the structure drawing of device for graphic user interface execution asynchronous operation of the present invention comprises:
Event queue filtrator 601, be used to receive the incident of event queue output, in backstage event handling thread pool, check whether the incident identical with the incident that receives is arranged, if have, then filter out described identical incident, described backstage event handling thread pool is used for the incidence relation of Admin Events and the event handling thread corresponding with it;
Incident is distributed thread 602, is used for distributing incident from described event queue filtrator.
In conjunction with the method embodiment of graphic user interface execution asynchronous operation, device shown in Figure 6 can also comprise:
Button.onrelease is used to receive described incident and distributes the incident that thread is distributed, and starts the event handling thread;
The event handling thread is used to receive the incident from described button.onrelease, according to the incident executable operations that receives.
The operation that each unit is carried out is elaborated below.
Event queue filtrator Event Queue Filter601 receives the incident of event queue output, in backstage event handling thread pool, check, whether the incident in the backstage event handling thread pool of checking has the incident identical with the incident that receives, if have, filter out in the incident that receives with backstage event handling thread pool in the identical incident of certain incident.Incident is distributed the incident that thread EDT602 will distribute and is exported button.onrelease to from event queue filtrator 601, button.onrelease Event Listener starts event handling thread Event Worker, and the event handling thread is handled incident.The event handling thread is put into backstage event handling thread pool with the incidence relation of the event handling thread of incident and this incident of execution.
As can be seen, since event queue filtrator 601 can filter out with backstage event handling thread pool in identical incident, so the incident identical with incident in the backstage event handling thread pool will do not distributed, so stoped the user because twice identical operations that maloperation causes.
At last, also need to prove, in this article, relational terms such as first and second grades only is used for an entity or operation are made a distinction with another entity or operation, and not necessarily requires or hint and have the relation of any this reality or in proper order between these entities or the operation.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thereby make and comprise that process, method, article or the equipment of a series of key elements not only comprise those key elements, but also comprise other key elements of clearly not listing, or also be included as this process, method, article or equipment intrinsic key element.Do not having under the situation of more restrictions, the key element that limits by statement " comprising ... ", and be not precluded within process, method, article or the equipment that comprises described key element and also have other identical element.
One of ordinary skill in the art will appreciate that: all or part of step that realizes said method embodiment can be finished by the relevant hardware of programmed instruction, aforementioned program can be stored in the computer read/write memory medium, this program is carried out the step that comprises said method embodiment when carrying out; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CD.
More than to graphic user interface provided by the present invention carry out synchronously, the method and the device of asynchronous operation be described in detail, used specific case herein principle of the present invention and embodiment are set forth, the explanation of above embodiment just is used for helping to understand method of the present invention and core concept thereof; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, the part that all can change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention.
Claims (8)
1. a graphic user interface is carried out the method for synchronous operation, it is characterized in that described method comprises:
The event queue filtrator receives the incident of event queue output, and wherein, described event queue filtrator is used for incident is filtered;
Incident is distributed thread and distribute first incident from described event queue filtrator, and exports described first incident to button.onrelease;
Button.onrelease is not handled described first incident, starts the event handling thread, by described first incident of event handling thread process; Button.onrelease notifies described event queue filtrator to filter out incident a, and notifies described incident to distribute thread and continue to distribute next event from described event queue filtrator, and described incident a is the incident of the operation map relevant with functional performance;
The event handling thread receives described first incident of described button.onrelease output, according to the described first incident executable operations.
2. method according to claim 1 is characterized in that, after described event handling thread executed operation according to described first incident, described method also comprised:
Described event handling thread is notified the filtration of described event queue filtrator end to incident a.
3. method according to claim 2 is characterized in that, before described event handling thread was notified the filtration of described event queue filtrator end to incident a, described method also comprised:
Described event handling thread refresh graphics user interface.
4. a graphic user interface is carried out the method for asynchronous operation, it is characterized in that described method comprises:
The event queue filtrator receives the incident of event queue output, and wherein, described event queue filtrator is used for incident is filtered;
Described event queue filtrator checks in backstage event handling thread pool whether the incident identical with the incident that receives is arranged, if have, then filter out described identical incident, described backstage event handling thread pool is used for the incidence relation of Admin Events and the event handling thread corresponding with it;
Incident is distributed thread and distribute incident from described event queue filtrator;
Described incident is distributed thread and is exported the incident of distributing to button.onrelease; Button.onrelease is not handled the incident of distributing, and starts the event handling thread, by the incident executable operations of event handling thread to distributing.
5. method according to claim 4 is characterized in that, starts in the process of event handling thread at described button.onrelease, and described method also comprises:
The incidence relation that described button.onrelease is put into the event handling thread of described incident of distributing and startup is put into backstage event handling thread pool.
6. a graphic user interface is carried out the device of synchronous operation, it is characterized in that described device comprises:
The event queue filtrator is used to receive the incident of event queue output, filters out incident a, and described incident a is the incident of the operation map relevant with functional performance;
Incident is distributed thread units, is used for distributing first incident from described event queue filtrator, and exports described first incident to the button.onrelease unit;
The button.onrelease unit is not handled described first incident, is used to start the event handling thread units, handles described first incident by the event handling thread units; The button.onrelease unit notifies described event queue filtrator to filter out incident a, and notifies described incident to distribute thread units and continue to distribute next event from described event queue filtrator;
The event handling thread units is used to receive described first incident that described button.onrelease unit is exported, according to the described first incident executable operations.
7. device according to claim 6 is characterized in that, described event handling thread units comprises:
Notification unit is used to notify the filtration of described event queue filtrator end to incident a;
Refresh unit is used for the refresh graphics user interface.
8. a graphic user interface is carried out the device of asynchronous operation, it is characterized in that described device comprises:
The event queue filtrator, be used to receive the incident of event queue output, in backstage event handling thread pool, check whether the incident identical with the incident that receives is arranged, if have, then filter out described identical incident, described backstage event handling thread pool is used for the incidence relation of Admin Events and the event handling thread corresponding with it;
Incident is distributed thread units, is used for distributing incident from described event queue filtrator, exports the incident of distributing to the button.onrelease unit;
Described button.onrelease unit is not handled the incident of distributing, and starts the event handling thread units;
Described event handling thread units is used to receive the incident from described button.onrelease unit, according to the incident executable operations that receives.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101612940A CN101364190B (en) | 2008-09-24 | 2008-09-24 | Method for executing synchronous and asynchronous operation on graphical user interface and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101612940A CN101364190B (en) | 2008-09-24 | 2008-09-24 | Method for executing synchronous and asynchronous operation on graphical user interface and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101364190A CN101364190A (en) | 2009-02-11 |
| CN101364190B true CN101364190B (en) | 2011-10-12 |
Family
ID=40390566
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101612940A Active CN101364190B (en) | 2008-09-24 | 2008-09-24 | Method for executing synchronous and asynchronous operation on graphical user interface and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101364190B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| BR112012001629B1 (en) | 2009-07-28 | 2019-10-22 | Ericsson Telefon Ab L M | method of synchronizing event processing associated with application sessions on a telecommunications processing platform, resource adapter, and java enterprise edition teaming |
| CN104932946B (en) * | 2009-07-28 | 2022-01-25 | 瑞典爱立信有限公司 | Device and method for handling events in a telecommunications network |
| CN102385510A (en) * | 2010-09-06 | 2012-03-21 | 上海可鲁系统软件有限公司 | Interface refreshing method of graphical user interface based on different development tools |
| CN104580716A (en) * | 2014-12-31 | 2015-04-29 | 苏州乐米信息科技有限公司 | Multi-interface management mechanism and method of mobile game |
| CN106155794B (en) * | 2016-07-21 | 2019-11-19 | 浙江大华技术股份有限公司 | A kind of event dispatcher method and device applied in multi-threaded system |
| CN109308219B (en) * | 2018-08-23 | 2021-08-10 | 创新先进技术有限公司 | Task processing method and device and distributed computer system |
| CN116107778B (en) * | 2023-04-13 | 2023-07-11 | 深圳复临科技有限公司 | Front-end event response realization method, device, terminal equipment and readable storage medium |
-
2008
- 2008-09-24 CN CN2008101612940A patent/CN101364190B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN101364190A (en) | 2009-02-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101364190B (en) | Method for executing synchronous and asynchronous operation on graphical user interface and device | |
| JP5491388B2 (en) | How to selectively enable multiple input controls | |
| CN107786730A (en) | A kind of task management method and terminal | |
| CN103116456B (en) | Realize apparatus and method and the intelligent terminal of file merging | |
| CN1333611C (en) | Garbage collection system and method for a mobile communication terminal | |
| CN103902258A (en) | Method and device for displaying self-defined menu in webpage | |
| CN103019661A (en) | Event prompting method and system | |
| CN102833120B (en) | The abnormal method and system of NM server are processed in a kind of rapid automatized test | |
| CN105760259A (en) | Data backup method and device and electronic equipment | |
| CN102722358A (en) | Electronic equipment and method for presenting widgets | |
| CN101963882A (en) | Unlocking method of touch screen, system and touch screen device | |
| CN107368255B (en) | Unlocking method, mobile terminal and computer readable storage medium | |
| CN103677571A (en) | Method, module and system for locking screen direction and gravity sensing module | |
| CN102215427A (en) | Method and device for synchronously playing multimedia information on television, and television | |
| CN106126287A (en) | Application program launching method and system | |
| CN106355054B (en) | Anti-theft method for mobile terminal and system | |
| CN106406662A (en) | Management method and system of application with function of generating replications | |
| CN107861853A (en) | Progress prompt method, terminal and computer-readable medium | |
| CN104837064A (en) | Control method for media player of open-type operation system and media player | |
| Uselton et al. | State refinement in process algebra | |
| CN106055253A (en) | Virtual key triggering method and mobile terminal employing same | |
| Jalender et al. | Drag and drop: influences on the design of reusable software components | |
| CN107608498A (en) | Application management method and terminal device | |
| CN117395132B (en) | Distributed alarm monitoring method, system, storage medium and electronic equipment | |
| CN103646216A (en) | Method and device for monitoring folder of terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |