JP3042942B2 - Input event sharing control method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method in which a plurality of terminals connected by a communication line share a display screen and an input operation of a computer, and operate as if one terminal is used in the same place. The present invention relates to an input event sharing control method for efficiently realizing remote teaching, remote maintenance, collaborative design with a small number of people, etc., by providing responsiveness.

[0002]

2. Description of the Related Art In a conventional joint work using a shared screen or the like,
The input operation right is given to a specific user, and when the corresponding user completes a series of input operations, the input right is explicitly given to the next requester of the operation right. Was often done. There is also used a method of executing input from an arbitrary terminal at an arbitrary time without managing the input operation.

As an example using an input operation having a state,
When drawing a line segment in the drawing software, depress the mouse button at one end point, move the mouse as it is, and release the mouse button at the other end position to determine both end points of the line segment Examples are given. The tracking of the mouse coordinates in the pressed state is performed by continuously reading the mouse position from the application triggered by the occurrence of a mouse button pressing event from the terminal.

[0004]

In the control using the floor control of the prior art, the input operation is exchanged with another user during an input having a state such as a coordinate movement while pressing a mouse button. I couldn't do that. Furthermore, if the terminal that acquired the input right and caused the relevant state transition cannot continue communication etc. for some reason, the input right will be retained by the corresponding terminal and the application execution will hang. There was a problem. If the input operation is not managed, the mouse state of another participant's terminal is read when tracking the mouse coordinates, and the mouse button of the other participant's terminal is released, or When transitioning to the released state, it is determined that the mouse button has transitioned from the pressed state to the released state, and the application ends.

[0005] It is an object of the present invention to enable input operations to be exchanged between terminals during execution of input operations such as coordinate update input when a joystick or a mouse button is pressed in a joint work using a shared screen or the like. By doing so, it is intended to efficiently realize work such as collaborative drafting and collaborative editing.

[0006]

In order to achieve the above object, according to the first aspect of the present invention, there is provided a system for simultaneously inputting operations from a plurality of terminals to an application executed on one computer. With the occurrence of the state change event, a buffer unit for storing a terminal identifier and a state change event flag coming from the terminal, a register unit for holding the terminal identifier of the terminal in which the state change event has occurred immediately before, and a terminal of the buffer unit. A comparison unit for comparing an identifier with a terminal identifier of the register unit, and when the status change event flag of the buffer unit indicates an input operation, the comparison unit takes a set state irrespective of the comparison result, and changes the status of the buffer. When the event flag indicates a recovery operation,
A counter unit that is reset when the comparison result of the comparison unit indicates a match, and notifies the application of an input operation when the counter unit is set, and a recovery operation when the counter unit is reset, to the application. And a processing unit for performing the processing.

According to a second aspect of the present invention, in a system in which an application to be executed on one computer is operated and input from a plurality of terminals at the same time, the application arrives from the terminal when a status change event of the terminal occurs. A buffer unit that stores a terminal identifier and a state change event flag, a register unit that holds a terminal identifier of a terminal in which a state change event has occurred immediately before, and a comparison that compares the terminal identifier of the buffer unit with the terminal identifier of the register unit. Unit, when the state change event flag of the buffer unit indicates an input operation, and the comparison result of the comparison unit indicates a mismatch,
A counter that counts up and counts down irrespective of the comparison result of the comparing unit when the status change event flag of the buffer unit indicates a recovery operation; and for the application, the count value of the counter unit is 1 or more. And a processing unit for notifying an input operation when the count value becomes zero and notifying a recovery operation when the count value becomes zero.

[0008]

In the input event sharing control method according to the first aspect of the present invention, when a mouse pressing event occurs from an arbitrary terminal (hereinafter, referred to as a terminal A), the identifier of the terminal A is set in the register section and the counter section is set. Is set. Thereafter, the state is a button pressed state. If another terminal (this is referred to as terminal B) depresses the mouse button while terminal A changes the coordinates while holding down the mouse button, the identifier of terminal B is set in the register section. Here, when the terminal B starts changing the mouse coordinates and the terminal A stops operating the mouse coordinates and releases the button, a state recovery event occurs. However, since the identifier of the register unit is the terminal B, the comparison is performed. The result of the comparison does not match, the corresponding event is ignored, and the terminal B can continue to input coordinates while the button is pressed. Conversely, when the terminal B releases the button first, the comparison results of the comparison unit match, and the state is restored at that point. If the terminal A forcibly shifts to the button release state in a state where the identifier of the terminal B is set in the register unit, the set value of the register unit is returned to the identifier of the A again by depressing the button once. Just release the button.

As described above, in the input event sharing control method according to the first aspect of the present invention, an arbitrary terminal participates in coordinate input when the mouse button is pressed, and the terminal that participated in the coordinate input last releases the button. When the button is released for the first time, but for some reason you want to forcibly switch to the button released state from a terminal other than the terminal that initiated the last button press input, click the mouse button from the terminal (continuous pressing down). / Release operation).

In the input event sharing control method according to the second aspect of the present invention, when a mouse button down event occurs from an arbitrary terminal (this is referred to as terminal A), the identifier of the terminal A is set in the register section and the counter is set. The counter value of the section is set to 1. Thereafter, the state is a button pressed state. When another terminal (this is referred to as terminal B) presses the mouse button while terminal A changes the coordinates while holding down the mouse button, the identifier of terminal B is set in the register section, and the counter section is set. Is set to 2.
Here, when the terminal B starts changing the mouse coordinates, the terminal A stops operating the mouse coordinates, and releases the button, the count value of the counter unit becomes 1 due to the occurrence of the state recovery event.
Then, when the terminal B releases the button, the count value of the counter unit becomes 0, and the state becomes the button released state. Similarly, when the terminal B releases the button before the terminal A, the state becomes the button released state only when the terminal A releases the button. That is, terminals A and B
Can execute coordinate movement with the mouse button pressed down, and the mouse button is released only when both release the button. Here, when the terminal A wants to forcibly release the button while the terminals A and B are pressing the button (register = B, counter = 2) (for example, when the communication path with the terminal B is suddenly disconnected) Terminal A releases the mouse button once (register = B, counter = 1) and depresses the mouse button again (register = A, counter = 2),
Then release (register = A, counter = 1). When the terminal A depresses the mouse button again, the terminal identifier of the register section is already A, and the counter does not increase. Therefore, the register is set to A, the counter is set to 1, and when released continuously, the register is set to A, the counter is set to 0, The state becomes the button released state.

As described above, in the input event sharing control method according to the second aspect of the present invention, an arbitrary terminal participates in coordinate input when the mouse button is pressed, and the button is released only when all terminals release the button. However, if for some reason it is desired to forcibly shift to the button released state despite the presence of a terminal in the button pressed state, a continuous clicking operation of the mouse button may be executed from any terminal.

[0012]

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram of a first embodiment of the present invention. In the figure, 100 is an application process requesting an input, 110 is an input event sharing control unit which is the center of this embodiment, 120 is a terminal interface unit for receiving an input signal from each terminal (not shown), and 130 is an input event An input interrupt signal 140 transmitted from the sharing control unit 110 to the application process 100 is input from the terminal interface unit 120 to the input event sharing control unit 110.
This is an input interrupt signal transmitted to.

The input event sharing control unit 110 is a communication buffer 1 that stores a terminal identifier input from the terminal interface unit 120 and a flag indicating a button state.
11, a register unit 112 in which the identifier of the terminal whose button is currently pressed is set, and a comparing unit 11 for comparing the terminal identifier of the communication buffer 111 with the terminal identifier of the register unit 112
3, a counter unit 114 that indicates a button pressed / released state, and a processor unit 115 that controls the operation of each of these units and notifies the application process 100 of a change in the state of an event.

FIG. 2 is a state transition diagram of the first embodiment.
The operation of FIG. 1 will be described accordingly.

Now, it is assumed that both the register unit 112 and the counter unit 114 of the input event sharing control unit 110 are reset (false) and are in the button released state (201).
When a mouse press event occurs at any terminal and an input signal arrives at the terminal interface unit 120 from the terminal, the input interrupt signal 140 is transmitted to the input event sharing control unit 11.
Informed to 0. When the processor 115 of the input event sharing controller 110 receives the input interrupt signal 140,
The terminal identifier and the button status flag are read from the terminal interface unit 120 into the communication buffer 111 and output to the signal lines 116 and 117, respectively.

Here, when the input button state flag on the signal line 117 is a button press event, the counter 1
14 is in the reset (false) state, the processor unit 11
5 notifies the application process 100 of the button press event as the input interrupt signal 130 (2
10). At the same time, the processor unit 115
Is set in the register unit 112, and the signal line 11
7 is sent to the counter unit 114. In the reset state, the counter unit 114 changes to the set state (true) when a button state flag indicating a button press event is sent. That is, the state is a button pressed state (202).

Thereafter, when an input signal from the terminal arrives at the terminal interface unit 120, the processor unit 115 reads the identifier of the terminal and the button status flag into the communication buffer 111, and transfers the input terminal identifier via the signal line 116. To the register 112,
The identifier of the terminal whose button is currently pressed down, which has been set in the register unit 112, is compared via the signal line 118 to the comparison unit 1.
13 and the input button state flag is
7 to the counter unit 114. The comparison unit 113 compares the terminal identifiers of the signal lines 116 and 118, and sends a true comparison result to the counter unit 114 via the signal line 119 if they match, and a false comparison result if they do not match. When the input button state flag on the signal line 117 is a button pressing event, the counter unit 114 maintains the set state (button pressing state) regardless of whether the comparison result of the comparing unit 113 is true or false (203, 203). 204). However, when the comparison result of the comparing unit 113 is false, the terminal identifier of the register unit 112 is the identifier of another terminal input later.

Next, when this button is pressed, the signal line 1
When the input button state flag on the button 17 indicates a button release event, and the comparison result of the comparison unit 113 is true, the counter unit 114 changes to the reset state (false) (20).
5). In response, the processor unit 115 notifies the application process 100 of the button release event as the input interrupt signal 130 (220), and resets the register unit 112. This returns to the button released state (201). Thereafter, the terminal stays in the button released state while an input signal arrives from the terminal and the button state flag of the terminal input indicates a button released event (206).

As described above, in the first embodiment, the terminal that last executed the input in the button pressed state has the right to shift to the button released state. Further, in the operation of the present embodiment, even if the event that the mouse button changes between the released state and the pressed state is not transmitted, a flag indicating the button released state or the button pressed state may be given at the time of inputting the coordinates. Therefore, the present invention can be applied to a case where a change in the button state cannot be detected by the interrupt processing unit of the terminal.

FIG. 3 shows a block diagram of a second embodiment of the present invention. In the figure, reference numeral 300 denotes an application process requesting an input, 310 denotes an input event sharing control unit which is the center of the present embodiment, 320 denotes a terminal interface unit that receives an input signal from each terminal (not shown), and 330 denotes an input event. An input interrupt signal 340 transmitted from the sharing control unit 310 to the application process 300 is transmitted from the terminal interface unit 320 to the input event sharing control unit 310.
This is an input interrupt signal transmitted to.

The configuration of the input event sharing control unit 310 is as follows.
Although the operation is basically the same as that of the first embodiment shown in FIG. 1, the operation of the counter unit 314 is different. That is, the counter unit 11 of FIG.
4 is either set or reset, the counter unit 314 in FIG. 3 counts the number of state transitions such as button presses. The processor unit 315 determines that the button is released when the counter unit 314 is in the reset state, and determines that the button is pressed when the counter unit 314 takes a value of 1 or more (here, n).

FIG. 4 is a state transition diagram of the second embodiment.
The operation of FIG. 3 will be described accordingly.

Now, it is assumed that both the register section 312 and the counter section 314 of the input event sharing control section 310 are reset (false) and are in the button released state (401).
When a mouse down event occurs at any terminal and an input signal arrives at the terminal interface unit 320 from the terminal, the input interrupt signal 340 is transmitted to the input event sharing control unit 31.
Informed to 0. When receiving the input interrupt signal 340, the processor unit 315 of the input event sharing control unit 310
The terminal identifier and the button state flag are read from the terminal interface unit 320 into the communication buffer 311 and output to the signal lines 316 and 317, respectively.

Here, when the input button state flag on the signal line 317 is a button press event, the counter unit 3
14 is in the reset (false) state, the processor unit 31
5 notifies the application process 300 of the button press event as the input interrupt signal 330 (4
10). At the same time, the processor unit 315
Is set in the register unit 312, and the signal line 31
7 is sent to the counter unit 314. In the reset state, the counter unit 314 sets the count value (n) to 1 when a button state flag indicating a button pressed state is sent (402). That is, the state becomes the button pressed state (403).

Thereafter, when an input signal from the terminal arrives at the terminal interface unit 320, the processor unit 315 reads the identifier of the terminal and the button status flag into the communication buffer 311 and transmits the input terminal identifier via the signal line 316. To the register section 312
The identifier of the terminal whose button is currently depressed, which has been set in the register unit 312, is compared via the signal line 318 to the comparison unit 3.
13 and the input button state flag is signal line 31
7 to the counter section 314. The comparing unit 313 compares the terminal identifiers of the signal lines 316 and 318, and sends a true comparison result to the counter unit 314 via the signal line 319 if they match, and a false result if they do not match. The counter unit 314 includes the button state flag of the signal line 317 and the signal line 3.
According to the 19 comparison results, the operation is performed as follows. That is, when the button state flag is a button press event and the comparison result is true, the count value (n) is neither increased nor decreased (404). When the button state flag is a button press event and the comparison result is false, the counter value (n) is increased by 1 (405). When the button state flag is a button release event, if the count value (n) is 2 or more (n> 1), the count value is decreased by 1 regardless of the comparison result (406). In any of these cases, the state of the counter unit 114 after the operation remains the button pressed state because the count value indicates at least one or more values.

Thereafter, when the button is in the pressed state, an input signal is received from an arbitrary terminal, and the button state flag indicates a button release event.
If the count value of 4 is 1 (n = 1), it is decreased by 1 to 0
(Reset state) (407). In response to this, the processor unit 315 sets the application process 300
In response, a button release event is notified as an input interrupt signal 330 (420), and the register unit 312 is reset. That is, the state returns to the button released state (401).

As described above, in the second embodiment, the button is released only when all the terminals that have executed the input in the button depressed state shift to the button released state. In addition,
In the operation of the present embodiment, the event itself that the mouse button changes between the released state and the pressed state needs to be transmitted.

[0029]

As described above, according to the input event sharing control method of the present invention, when operating the same application from a plurality of terminals while using a shared screen or the like,
Since input operations such as coordinate input while pressing a joystick or a mouse button can be transferred between a plurality of terminals, collaborative drawing and collaborative editing can be efficiently executed.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a first embodiment of the present invention.

FIG. 2 is a state transition diagram for explaining the operation of FIG.

FIG. 3 is a configuration diagram of a second embodiment of the present invention.

FIG. 4 is a state transition diagram for explaining the operation of FIG. 3;

[Explanation of symbols]

 100, 300 application process 110, 310 input event sharing control unit 111, 311 communication buffer 112, 312 register unit 113, 313 comparison unit 114, 314 counter unit 115, 315 processor unit 120, 320 terminal interface unit

──────────────────────────────────────────────────続 き Continued on the front page (58) Field surveyed (Int. Cl. ⁷ , DB name) G06F 13/00 G06F 3/00 G06F 15/00 H04N 7/15

Claims (2)

(57) [Claims] In a system for simultaneously inputting an operation from a plurality of terminals to an application executed on one computer, a terminal identifier and a state change event coming from the terminal are generated when a terminal state change event occurs. A buffer unit for storing a flag, a register unit for holding a terminal identifier of a terminal in which a state change event has occurred immediately before, a comparing unit for comparing a terminal identifier of the buffer unit with a terminal identifier of the register unit, and the buffer unit When the status change event flag of the buffer indicates an input operation, the comparator takes a set state regardless of the comparison result, and when the status change event flag of the buffer indicates a recovery operation, the comparison result of the comparator matches. And a counter unit that is in a reset state when indicating that the counter unit is in a set state for the application. That the notified input operation, the input event sharing control scheme in which the counter unit is characterized by comprising a processing unit for notifying the recovery operations and in the reset state, the. 2. A system for simultaneously inputting operations from a plurality of terminals to an application executed on one computer, wherein a terminal identifier and a state change event coming from the terminal are generated in response to the occurrence of a terminal state change event. A buffer unit for storing a flag, a register unit for holding a terminal identifier of a terminal in which a state change event has occurred immediately before, a comparing unit for comparing a terminal identifier of the buffer unit with a terminal identifier of the register unit, and the buffer unit When the status change event flag of the comparison unit indicates an input operation and the comparison result of the comparison unit indicates inconsistency, the count is incremented. When the status change event flag of the buffer unit indicates a recovery operation, A counter unit that counts down regardless of the comparison result; Cement value notifies the input operation to become 1 or more, the input event sharing control method according to the count value becomes 0 and the processing unit for notifying the recovery operation, characterized in that the provided.