JPH0660038A - Event control method - Google Patents

Abstract

PURPOSE:To provide the event control method which is good in event throughput efficiency by sequentially taking events out of an event queue stored with events to be reported and analyzing their kinds, and individually processing a specific kind of events which possibly cause interference and other kinds of events. CONSTITUTION:A work station 11 is equipped with a keyboard 12 and a pointing device 13. An event control part 14 is equipped with a user input process part 15 and a MisicEvents (other events) process part 16. The event control part 14 fetches an event from the event queue and analyzes the kind of the event to judge whether or not the event is a user action event. Here, a user action is an event which causes interference owing to operation on the keyboard 12 or operation of the pointing device 13. When the event is the user action event, the event is sent to the user input process part 15, but when not, the event is sent to the event process part 16.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an event control method, and more particularly to an event control method in a server client system which executes corresponding processing according to the contents of an event notified from a server.

[0002]

2. Description of the Related Art A server client system, eg X
In the window system, an event is notified from the server to the client via the event queue. The client sequentially retrieves events from the event queue and executes processing corresponding to each event (for example, Ryoichi Kinoshita "X-windows Ver.11 Programming" First Edition 8th edition (July 17, 1992) Nikkan Kogyo Shimbun P.100, JP-A-2-8920, JP-A-3-144846, etc.). When processing events on the client side, it is necessary to process them so that they do not interfere with each other. For example, an event caused by a user's action such as a pointing device or a key operation may not be executed properly in data input and processing unless the processing is performed in the order of the event. Therefore, in the conventional event handler (Event Handler), the processing procedure of taking out the next one from the event queue after completing the processing of one event is taken, and the event which is not interfered by this is processed. During that time, processing of other events was prevented from being performed (see FIG. 10). When event processing takes a long time, a fork from the event processing unit is used.

[0003]

However, in the above-mentioned conventional method, the load of the event queue depends on the efficiency of the event processing. Therefore, even if the overlapping state of the windows changes, the repainting is not performed immediately. The phenomenon such as, occurred, and the processing efficiency was poor. Also, when dealing with a fork, it was necessary to pay close attention so that the processing did not interfere with other events. An object of the present invention is to eliminate such drawbacks of the prior art and provide an event control method with high event processing efficiency.

[0004]

In order to achieve the above object, according to the invention of claim 1, in the server client system for executing the corresponding processing according to the content of the event notified from the server, the notified event is Events are sequentially extracted from the stored event queue, their types are analyzed, and predetermined types of events that may interfere with each other and other types of events are processed separately. According to a second aspect of the invention, in the event control method according to the first aspect, the predetermined type of event is stored in a processing queue, the events are sequentially taken out from the processing queue, and the corresponding processing is executed. According to the invention of claim 3, in the event control method according to claim 1 or 2, the other event is stored in a plurality of processing queues, and an event is extracted for each of the processing queues. The process corresponding to each is performed. According to the invention of claim 4, in the event control method according to claim 1, claim 2 or claim 3,
Add or change the processing registration for the specified event.

[0005]

According to the first aspect of the invention, events are sequentially taken out from the event queue and their types are analyzed. For example, following the above example, if the event related to the user's mouse operation and key operation is assumed to be "a predetermined type of event that may cause interference," this predetermined type of event and other types of events, for example, Events such as changing the overlapping state of windows are processed separately. According to a second aspect of the invention, in the event control method according to the first aspect, the predetermined type of event is stored in the processing queue, and the events are sequentially extracted from the processing queue and the corresponding processing is executed. According to a third aspect of the invention, in the event control method according to the first or second aspect, the other event is stored in a plurality of processing queues, and the event is extracted for each of the processing queues. Then, the corresponding processing is executed. According to the invention of claim 4, in the event control method according to claim 1, claim 2 or claim 3, processing registration for an event is added or changed.

[0006]

The details of the present invention will be described below with reference to the illustrated embodiments. 1 to 5 show a first embodiment. This embodiment is an embodiment of the invention of claim 1 and claim 4 which cites it. In FIG. 1, reference numeral 11 denotes a workstation, which includes a keyboard 12 and a pointing device 13 (mouse or the like). An event control unit 14 includes a user input processing unit 15 and a MiscEvents processing unit 16. "Misc Events" means "Miscelaneous Events"
(Other events) ". Event controller 1
The functions of No. 4 are shown in FIG. The control unit 14 takes in an event from an event queue (not shown) (S11). Next, the type of the event is analyzed (S12), and it is determined whether the event is a user action event (S13).
Here, the user action refers to an event that occurs due to the operation of the keyboard 12 or the pointing device 13, and is a typical event that causes interference. In this embodiment, this is referred to as the "predetermined type of event" in the claims. It should be noted that what is specifically set as the predetermined type of event is determined by each system. If it is a user action event (S13 “YES
(Yes) ”), the event is the user input processing unit 15
(S14). Otherwise (S13 "NO
(No) ”), and the event is sent to the MiscEvents event processing unit 16 (S15).

The configuration of the user input processing section 15 is shown in FIG. This processing unit 15 is generally called "Notifier", and when the sending of an event is detected, the content thereof is analyzed and sent to the operation defining unit 152. Behavior definition part 1
52 determines the action corresponding to the event and sends it to the action definition part 153 of each upper application. As a result, the process corresponding to the event is executed. MiscEven
The function of the ts processing unit 16 is shown in FIG. Upon receiving the event, the processing unit 16 searches the event processing registration data list DL (FIG. 5) for the event (S21).
If registered (S22 “YES”), the event process is executed (S23). Otherwise (S2
2 "NO") No processing is performed for that event,
A search for the next event (S21) is performed.
The event process registration unit 17 registers the addition or change of the process in the event process data list DL on the basis of a request from the host application. This process corresponds to the addition or change mentioned in claim 4.

6 and 7 show the configuration of the second embodiment. This embodiment is an embodiment of the invention of claim 2 and claim 4 which cites it. There are two differences from the first embodiment. Others are the same as the first embodiment. The same parts are designated by the same reference numerals and the description thereof is omitted. One of the differences is that the processing queue 1 is located at the position of the user input processing unit 15 of the first embodiment.
8 is arranged, and the original user input processing unit 15 is connected to the processing queue 18. In order to distinguish it from that of the first embodiment, reference numeral 1 is attached to the event control unit of the second embodiment.
Mark 9. Another difference is that this event control unit 1
9 is that the contents of step S16 corresponding to step S14 of the event control unit 14 of the first embodiment are changed. In step S16, the event is supplied to the processing queue 18. And the user input processing unit 1
5 retrieves the event from this queue 18 and executes the corresponding process.

8 and 9 show the configuration of the third embodiment. This embodiment is an embodiment of the invention of claim 3 and claim 4 which cites it. There are two differences from the first embodiment. Others are the same as the first embodiment. The same parts are designated by the same reference numerals and the description thereof is omitted. One of the differences is that the processing queue 1 is located at the position of the user input processing unit 15 of the first embodiment.
8 is arranged, and the event processing units 22-1 to 22-n are connected to the respective processing queues 18. The event processing units 22-1 to 22-n have the same functions as the user input processing unit 15 of the first embodiment. In order to distinguish from the event control unit 14 of the first embodiment, the event control unit of this embodiment is designated by the reference numeral 20. Another difference is that in the event control unit 20, the contents of step S17 corresponding to step S14 of the first embodiment are changed. In step S17, the processing queues 21-1 to 21 are processed according to their types.
-N. And each event processing unit 22-1.
22-n extracts an event from each of the queues 21-1 to 21-n and executes the corresponding process.

[0010]

As described above, according to the first aspect of the present invention, events are sequentially extracted from the event queue and their types are analyzed, and predetermined types of events and other types of events are processed separately. It was to so. According to the second aspect of the invention, the predetermined type of event is stored in the processing queue, and the event is sequentially taken out from the processing queue to execute the corresponding processing. According to the invention of claim 3, the other event is stored in a plurality of processing queues, the event is extracted for each of the processing queues, and the corresponding processing is executed. Further, in the invention of claim 4, the processing registration is added or changed to the event. Therefore, for example, events that interfere with each other, for example, an event group related to user actions are distinguished as the predetermined type of event, and other events that do not cause interference are distinguished as the other events. Notifier
Process (command processing process; user input processing unit 15, event processing units 22-1 to 22-n in the embodiment)
Can be executed so that interference between events divided into respective groups does not occur.

That is, the interfering events are classified into the same group and are sequentially processed one by one by the Notifier process of the group, during which other events of the same group, that is, other events that interfere with it, are not processed. This prevents the occurrence of interference. In this case, the process for protecting from interference, that is, the process for each event group is executed regardless of the extraction of the event from the event queue. Therefore, retrieval from the event queue is performed one after another, and the load on the event queue is reduced as compared with the conventional system. Further, since there are a plurality of Notifiers, it is possible to start processing for each event not related to interference without waiting for processing for each interfering event. Therefore, the processing speed is improved as compared with the conventional case. Further, it can be easily realized that the Notifier for the event that does not interfere is not restricted by the Notifier of the event that interferes. For this reason, when designing a higher-level system, conventionally, it was necessary to carefully consider, for example, which event processing should be bound to user action processing, but for unrelated events, this Since the process corresponding to the event is performed only by specifying and registering the process, the burden on the programmer is reduced.

[Brief description of drawings]

FIG. 1 is a block diagram showing the configuration of a first embodiment.

FIG. 2 is a diagram showing functions and the like of an event control unit of the first embodiment.

FIG. 3 is a block diagram showing the configuration of a user input processing unit.

FIG. 4 is a diagram showing the function of the MiscEvents processing unit.

FIG. 5 is a block diagram showing a configuration of an event processing registration unit.

FIG. 6 is a block diagram showing the configuration of a second embodiment.

FIG. 7 is a diagram showing functions and the like of an event control unit of the second embodiment.

FIG. 8 is a block diagram showing the configuration of a third embodiment.

FIG. 9 is a diagram showing functions and configurations of an event control unit and the like of a third embodiment.

FIG. 10 is a diagram showing a conventional control method.

[Explanation of symbols]

 18, 21 Processing queue 15, 22 Event processing section 17 Event processing registration section

Claims (4)

[Claims] 1. A server client system for executing corresponding processing according to the contents of an event notified from a server, sequentially fetching events from an event queue in which the notified event is stored and analyzing their types. However, the event control method is characterized in that a predetermined type of event that may possibly interfere and an event of another type are processed separately. 2. The event control method according to claim 1, wherein the predetermined type of event is stored in a processing queue, the events are sequentially taken out from the processing queue, and the corresponding processing is executed. 3. The method according to claim 1, wherein the other event is stored in a plurality of processing queues, the event is extracted for each processing queue, and the corresponding processing is executed. The event control method according to item 2. 4. The event control method according to claim 1, wherein the process registration for the designated event is added or changed.