JPH11143726A - Application shared operation processor and method therefor and medium for storing the same program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow plural users to attain a cooperative work by the same application without any load (computer literacy) of a user related with an application shared operation processor. SOLUTION: Plural event processing parts 2 are made correspond to each of plural applications having a window for inputting an event. Then, an inputting means corresponding to the window is generated, an event inputted to the inputting means is received, and this event is transmitted to an event integrating part 4. The event integrating part 4 integrates and manages plural events received from the plural event processing part 2, and transmits the event following a prescribed condition. Plural application operating parts 1 are made correspond to the plural applications, and operate the corresponding application according to the event transmitted by the event integrating part 4.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an application sharing operation processing apparatus and method, and a program storage medium therefor, and more particularly to an application capable of performing a joint work by operating an existing application by a plurality of users. The present invention relates to a sharing operation processing device and method, and a program storage medium therefor.

[0002]

2. Description of the Related Art In recent years, most applications (application programs), especially applications widely used in personal computers, are mostly
It has a UI (graphical user interface).
A plurality of users may collaborate while sharing information using an application having a GUI that is widely used in general.

For example, a plurality of users connect each computer to each other. Then, a plurality of users jointly perform processing by the same application on each computer while sharing information with other computers. For example, when the application is a document creation program, the same document is created in each computer.

As described above, in order to obtain the same result by the same application in a plurality of computers, it is essential to share information among the plurality of computers. That is, it is necessary that information input by a certain user from its own computer is transmitted to other computers with priority without fail. Also,
When information is updated by a user's input, it is necessary to prevent another computer from performing a process using the information before update once the information is updated.

[0005] Therefore, when certain information is input, the information is updated in its own computer, the information is transmitted to another computer, and the information is referred to and updated during the input and update or transmission of the information. Must be performed inseparably. Therefore, conventionally, a dedicated tool having a mechanism for sharing information is used in order to enable the above-described processing. For example, as dedicated tools, there are tools for controlling memory sharing and exclusive control.

[0006]

As described above, it is necessary to use a dedicated tool in order for a plurality of users to share information and to work together with the same application. For this reason, conventionally, software and hardware for executing information sharing are required separately from the application, and it is necessary to purchase the software and learn how to use it (necessity of computer literacy). This is a heavy burden on the user.

[0007] Further, according to the dedicated tool, the user uses the application via the tool, so that the user cannot work with the existing familiar application. For this reason, the productivity does not improve much while performing the collaborative work, and it is necessary to always be aware of the occurrence of errors due to erroneous operations.

An object of the present invention is to provide an application sharing operation processing device that allows a plurality of users to perform a joint work with the same application while sharing information without burdening the user (computer literacy). Aim.

[0009] The present invention also provides an application sharing operation processing apparatus that allows a plurality of users to share information and perform collaborative work with the same application without making the user aware of the existence of a dedicated tool. The purpose is to provide.

[0010] Another object of the present invention is to provide an application sharing operation processing apparatus which enables a plurality of users to share information with one another and to perform a joint work with the same application with high productivity.

Further, the present invention realizes an application sharing operation processing apparatus that allows a plurality of users to perform a joint work with the same application while sharing information without burden on users (computer literacy). To provide a program storage medium in which a program for storing the program is stored.

[0012]

FIG. 1 is a block diagram showing the principle of the present invention, and shows an application sharing operation processing apparatus 100 according to the present invention.

The application sharing operation processing device 100
Is composed of a plurality of event processing units 2 corresponding to each of a plurality of applications, an event integration unit 4, and a plurality of application operation units 1 corresponding to each of the plurality of applications. Each application has a window for entering events. Each of the event processing units 2 generates an input unit corresponding to the window, receives an event input to the input unit, and sends the event to the event integration unit 4. The event integration unit 4 integrates and manages a plurality of events received from the plurality of event processing units 2, and sends an event according to a predetermined condition to the event processing unit 2. The application operation unit 1 operates a corresponding application according to the event sent by the event integration unit 4.

According to the application sharing operation processing apparatus 100 of the present invention, before an event, which is an input from a mouse or a keyboard for operating an application, is input to the application by the input means generated by the event processing unit 2. Be captured. The input means is a pseudo window that is not noticed by the user.
Therefore, the user is conscious only of inputting into the window of the application, but is actually inputting to the input means generated by the event processing unit 2. Events are not input to the application directly from the application window. Therefore, the event is input to the event processing unit 2 instead of the application operation unit 1.

The event captured at a stage before being sent to the application is stored in a single event integration unit 4.
And are managed as one time series (queue) of events. The event integration unit 4 transmits a predetermined event in the event sequence to the event processing unit 2. As a result, the same event is transmitted to the plurality of event processing units 2 at the same time, so that existing applications running in a plurality of environments are operated while always maintaining the same state. For this reason, the sharing operation of the existing application can be performed by a plurality of users each using a different event processing unit 2 and application operation unit 1.

Further, according to the present invention, since it does not depend on the type of the existing application, any existing application that can generate input means can be targeted. Furthermore, according to the present invention, since events to be integrated are only events corresponding to user operations such as mouse and keyboard events, there is no need to be aware of other events handled by existing applications. , Simple processing becomes possible.

[0017]

FIG. 2 is an explanatory diagram of an embodiment of the present invention, and shows a configuration of an application sharing operation processing apparatus 100.

Application sharing operation processing device 100
Generates input means 10 corresponding to the window 7 of the existing application 6 having a GUI,
It receives events input to 0, integrates these events, and performs collaborative work while maintaining the same state in multiple environments.

Application sharing operation processing device 100
Is composed of a processing device 9 and an input / output device 11. Processing device 9
Is composed of a CPU and a memory, and includes an application 6, an application operation unit 1, and a sharing operation processing unit 8. The sharing operation processing unit 8 includes an event processing unit 2, an event transmission unit 3, an event reception unit 5, and an event integration unit 4. The application 6, the application operation unit 1, and the sharing operation processing unit 8 are realized by a program existing on a memory. The input / output device 11 includes a mouse 13 and a keyboard 12, which are input devices, and a display device 14 having a display screen.

In the shared operation processing unit 8, only one event integration unit 4 is provided because it is necessary to integrate all events. On the other hand, the event processing unit 2, the event transmission unit 3, and the event reception unit 5 are provided corresponding to each of the plurality of applications 6 and the plurality of application operation units 1.

A plurality of application operation units 1 are provided corresponding to each of the plurality of applications 6. The application operation unit 1 starts the application 6 and operates the application 6 by giving an event to the application 6. The application operation unit 1 receives the event sent from the event integration unit 4 via the event processing unit 2, and operates the application 6 in response thereto.

The application 6 has a GUI window 7, which is displayed on the screen of the display device 14. The user looks at the window 7 opened on the screen of the display device 14 and moves the mouse 13 and / or
Alternatively, a predetermined event is input using the keyboard 12. The event input to the window 7 by the user is normally input to the application operation unit 1 (when the sharing operation processing unit 8 is not activated). Application 6
Is activated by an instruction input to the window 7 by the user.

The application 6 and the application operation unit 1 are provided with an input / output device 11 and a display
Is provided corresponding to each of. For example, the processing device 9
When the application 6 or the application operation unit 1 is started from the input / output device 11 and the display device 14, the application 6 or the like corresponding to the input / output device 11 or the like is generated accordingly.

A plurality of event processing units 2 are provided corresponding to the plurality of applications 6 and the application operation unit 1. The event processing unit 2 includes an application 6
A window 10A as the input means 10 corresponding to the window 7 is generated and displayed on the screen of the display device 14. When the user looks at the window 10A and inputs an event into the window 10A, the event processing unit 2
An event input by the user is received via A and sent to the event transmitting unit 3. As a result, events of the mouse 13 and the keyboard 12 that operate the existing application 6 are captured at a stage before being sent to the existing application 6. Further, the event processing unit 2 receives an event from the event receiving unit 5 and gives the event to the application operation unit 1.

The input means 10 or the window 10 A is a GUI interface established on the screen of the display device 14. Window 10A is a pseudo window corresponding to window 7. The user cannot see the window 7 but only the window 10A. Therefore,
The event input by the user is input to the window 10A. The user does not need to be aware that the input is to the window 10A. Therefore, when using the application sharing operation processing apparatus 100, computer literacy for the user is unnecessary.

The events received by the event processing unit 2 via the window 10A are only events corresponding to the user's operation, such as events of the mouse 13 and the keyboard 12, among all the events input by the user. For this reason, since the event processing unit 2 does not need to be aware of other events handled by the existing application 6, simple processing can be performed.

The event received by the event processing unit 2 can be executed when all of a plurality of pieces of information are completed. Therefore, as will be described later, when an event occurs, the event integration unit 4 is connected to an event sequence and waits. When all inputs enabling execution of the event are completed, the event integration unit 4 sends the event to the event reception unit. 5 is sent. An event input that allows the user to immediately operate the application 6 by inputting one event is input to the application operation unit 1 without being received by the event processing unit 2, for example. Actually, once received by the event processing unit 2, it is sent to the application operation unit 1, and the application operation unit 1 operates the application 6 accordingly.

Application sharing operation processing device 100
Can be applied without depending on the type of the existing application 6 as long as the application 6 can generate the input means 10 and receive an event using the input means 10. Therefore, the sharing operation can be performed for any existing application 6.

The window 10 as the input means 10
The generation of A and the reception of the event by the window 10A will be described later. The event transmitting unit 3 transmits the event transmitted by the event processing unit 2 to the event integrating unit 4. The event receiving unit 5 receives the event sent from the event integrating unit 4 and gives the event to the event processing unit 2.
Therefore, the event transmission unit 3 and the event reception unit 5 are communication means between the event processing unit 2 and the event integration unit 4.

The event transmitting section 3 and the event receiving section 5 may be included in the event processing section 2. That is, the event processing unit 2 may have a communication unit with the event integration unit 4 therein. The event transmitted by the event integration unit 4 is transmitted to the application operation unit 1.
May be received directly. According to the configuration in FIG. 1 or the configuration in which the event processing unit 2 includes the event transmitting unit 3 and the event receiving unit 5, the communication function may be provided only in the event processing unit 2 (and the event integration unit 4).

The event integration unit 4 arranges the received events once and transmits them in a predetermined order. Specifically, the event integration unit 4 integrates a plurality of events received from the plurality of event processing units 2 and manages them as a sequence of events (queue), and sends out an event according to a predetermined condition. That is, among the events that are connected to the event sequence and are in the waiting state, all of the inputs that enable the execution of the event are provided, and are sent from the event integrating unit 4 to the event receiving unit 5. As a result, since the events are integrated in one place to form a time series of events, the applications 6 running in a plurality of environments are always maintained in the same state and operated. Therefore, the sharing operation of the application 6 can be performed by a plurality of users. Note that the event integration unit 4 includes communication means (not shown) similar to these for performing communication with the event transmission unit 3 and the event reception unit 5.

Here, the processing performed by the application sharing operation processing apparatus 100 will be described in that order. Display device 14
The application operation unit 1 activates the application 6 in response to a predetermined input from the mouse 13 or the keyboard 12 of the user who has viewed the screen. For example, when the predetermined application 6 is activated, the shared operation processing unit 8 is also automatically activated by the operating system of the processing device 9. Therefore, the user does not need to be aware of the shared operation processing unit 8. Further, a user who has a qualification to start the application 6 can perform the sharing operation processing of the application 6 using the sharing operation processing unit 8.

Upon activation of the sharing operation processing unit 8, the event processing unit 2 generates the input means 10 or the window 10A corresponding to the window 7 of the application 6. The event processing unit 2 includes the input mouse 13 and keyboard 1
The second event is received by the input means 10 and passed to the event transmitting unit 3. The event transmission unit 3 sends the received event to the event integration unit 4. The event integration unit 4 integrates the events sent from the plurality of event transmission units 3 so as to form a sequence of events in the order of reception.

The event integration unit 4 extracts a predetermined (executable) event from the event column, and transmits (activated) the event.
Is transmitted to the event receiving unit 5 corresponding to. When receiving the event, the event receiving unit 5 passes the event to the event processing unit 2. Upon receiving the event, the event processing unit 2 sends the event to the application operation unit 1.

The application operation unit 1 sends a command given from the event processing unit 2 to the application 6. In response, the application 6 performs a process corresponding to the event.

As can be understood from the above description, the application sharing operation processing apparatus 100 manages information to be shared by each event processing unit 2 when performing joint work using the same application 6. You. That is, actually, the shared information is distributed to each event processing unit 2 only in a predetermined order, and is not managed. In addition, a person who can start the application 6 can jointly work on processing using the application 6 that is being started by another user.

By easing the management of the shared information in this manner, the shared operation processing unit 8 (dedicated tool) can be used without the burden on the user (computer literacy) or the user.
It allows multiple users to work together on the same application while sharing information, without being aware of the existence of. Further, since the management of the shared information is relaxed, the application 6 is started not by one in the host computer but by the number corresponding to each event processing unit 2 (or data processing device). . As a result, when the application 6 is, for example, a document creation program, the document is created not in the host computer but in each event processing unit 2 (or data processing device).

The application sharing operation processing apparatus of the present invention, including the application sharing operation processing apparatus 100 shown in FIG. 2, is implemented using a program for operating a computer as shown in the above description and the description with reference to the following flowcharts. Is done. The program is stored on various suitable program storage media for storing the program. This program is actually provided as a program for realizing the shared operation processing unit 8.

FIG. 3 shows a flowchart of the application sharing operation processing in the application sharing operation processing device 100 of the present invention. First, the user starts the application operation unit 1 by a predetermined input and starts the application 6. The application 6 displays the window 7 on the screen of the display device 14. The above is the same as in the prior art.

Next, when the application operation unit 1 or the application 6 is started, the shared operation processing unit 8 is started, and the event processing unit 2 is operated by the input unit 10 or the window 1.
0A is generated and displayed on the window 7 on the screen of the display device 14. As a result, the window 7 becomes invisible to the user, and the input means 10 or the window 10
Only A can be seen, and only this can be input. Thereafter, the following processing is executed.

S1: The user inputs an event from the input means 10 (or the window 10A). S2: The event processing unit 2 sends the event input to the input unit 10 to the event transmission unit 3.

S3: The event transmitting section 3 sends the event from the event processing section 2 to the event integrating section 4. S4: The event integration unit 4 arranges the events received from the plurality of event transmission units 3 in the order of arrival, and creates an event sequence.

S5: The event integration unit 4 selects an executable event from the events arranged in the order of arrival,
The events are sent to the plurality of event receiving units 5 in order from the event before the event sequence.

S6: The event receiving unit 5 converts the event received from the event integrating unit 4 into the corresponding event processing unit 2.
Send to S7: The event processing unit 2 sends the event received from the event receiving unit 5 to the corresponding application operation unit 1.

S8: The application operation unit 1 sends the event received from the event processing unit 2 to the application 6. S9: The application 6 performs a process according to the event received from the application operation unit 1.

FIG. 4 shows a flowchart of the processing executed by the event processing unit 2, and shows processing corresponding to S1, S2 and S7 of the processing of FIG. S10: Information of the application 6 (of the window 7) held in the application operation unit 1 is obtained. Prior to this, the application 6 in S30 of FIG.
Is started, and in S31, the application operation unit 1
Has obtained information about the window 7 from the application 6.

S11: A pseudo input means 10 (window 10A) for the window 7 is generated based on the information of the application 6. S12: It is checked whether an event has been input to the input means 10. If it has been input, execute S13,
If not, S15 is executed.

S13: It is checked whether the input event is a target event. The target event is an event caused by operating the mouse 13 or the keyboard 12. If the input event is the target event, S14 is executed, and if it is not the target event, S15 is executed.

S14: The input event is sent to the event transmitting section 3. S15: Check whether an event has been sent from the event receiving unit 5. If it has been sent, S16 is executed, and if it has not been sent, S17 is executed.

S16: The sent event is sent to the application operation unit 1. S17: Check whether the application 6 has been terminated. If the processing has been completed, the processing is completed, and if not completed, S12 and subsequent steps are executed.

FIG. 5 is a flowchart of the process executed by the event transmitting unit 3, and shows a process corresponding to S3 in FIG. S18: Check whether an event has been sent from the event processing unit 2. If it has been sent, S19 is executed, and if it has not been sent, S20 is executed.

S19: The sent event is sent to the event integration section 4. S20: Check whether the application 6 has been terminated. If the processing has been completed, the processing is completed, and if not completed, S18 and subsequent steps are executed.

FIG. 6 shows a flowchart of the processing executed by the event integration section 4, and shows processing corresponding to S4 and S5 in FIG. S21: Check whether the processing is completed. If the processing is to be ended, the processing is ended; if not, S22 is executed.

S22: It is checked whether or not an event has been sent from any of the event transmitting units 3. If it has been sent, S23 is executed, and if it has not been sent, S21 and subsequent steps are executed.

S23: The data of the sent event is read. Based on this result, if the event is a completely new event, it is arranged at the end of the event sequence, and if the event is information on an event that occurred earlier, this is arranged at an appropriate position in the event sequence. .

S24: One event is read from the head of the event sequence in which the events sent from the plurality of event transmitters 3 are arranged in the order of arrival, and the event information is cut out from the first event information.

S25: The cut out event is sent to the event receiving section 5. S26: It is checked whether or not there is no event in the event sequence. If the event has run out, S22 and subsequent steps are executed, and if events still remain in the event sequence, S24 and subsequent steps are executed.

FIG. 7 is a flowchart of the process executed by the event receiving unit 5, and shows a process corresponding to S6 in FIG. S27: Check whether an event has been sent from the event integration unit 4. If it has been sent, S28 is executed, and if it has not been sent, S29 is executed.

S28: The sent event is sent to the event processing unit 2. S29: Check whether the application 6 has been terminated. If the processing has been completed, the processing is completed, and if not completed, S27 and subsequent steps are executed.

FIG. 8 is a flowchart of a process executed by the application operation unit 1, and shows a process corresponding to S8 in FIG. S30: Activate application 6.

S31: Information for sending an event to the corresponding application 6 and information on the window 7 of the application 6 are obtained from the application 6.

S32: It is checked whether or not the event has been sent from the event processing unit 2. S33 if sent
Is executed, and if not sent, S32 is repeatedly executed at predetermined time intervals.

S33: The event received from the event processing unit 2 is sent to the application 6. S34: Check whether the application 6 has been terminated. If the processing has been completed, the processing is completed, and if not completed, S32 and subsequent steps are executed.

Here, the window 10A which is the input means 10 in the application sharing operation processing apparatus 100
And the reception of the event by the window 10A will be described.

The event processing unit 2 generates a window 10A that overlaps the window 7 of the application 6 as the input means 10 and superimposes the generated window 10A on the window 7 of the application 6, via the generated window 10A. To receive the entered event. In the present invention, since the user must not be conscious of the existence of the input unit 10, the input unit 10 includes a window 7 of the application 6 for the user.
Those that look the same as are preferred. The input means 10
Should be something that does not make the user aware of its existence and can receive the input event.

Specifically, the window 10A is, for example, a transparent window 10B. Event processing unit 2
Is a transparent window 10B having the same position and the same size as the window 7 of the application 6 as the input means 10.
Generate The transparent window 10B is a colorless and transparent window in which only the event input area is defined exactly the same as the window 7. Therefore, the transparent window 10B completely overlaps the window 7, and the user does not see the transparent window 10B but sees the window 7 as it is. The user inputs an operation of the mouse 13 or an operation of the keyboard 12 on the window 10B as an event.

Thus, the user can use the application 6
Can be viewed through the transparent window 10B, and the same operation as the existing application 6 can be performed. When the user inputs an event to an area of a window that is recognized as the window 7, the event is actually input to the same area of the window 10B that overlaps the event.
Accordingly, the event processing unit 2 receives an operation of the mouse 13 or an operation of the keyboard 12 on the transparent window 10B overlapping the window 7 as an event.

FIG. 9 shows a flowchart of a process executed by the event processing unit 2 using the transparent window 10B. S35: The information of the application 6 stored in the application operation unit 1 is obtained. Further, the position and size of the window 7 of the application 6 are checked.

S36: A transparent window 10B having the same size as the window 7 of the application 6 is generated and superimposed on the window 7. The event received (targeted) by the transparent window 10 </ b> B is an event caused by operating the mouse 13 or the keyboard 12.

S37: Window 10 whose event is transparent
It is checked whether or not B has been input. If it has been input, S38 is executed. If it has not been input, S39 is executed.
Execute

S38: The input event is sent to the event transmitting section 3. S39: Check whether an event has been sent from the event receiving unit 5. If it has been sent, S40 is executed, and if it has not been sent, S41 is executed.

S40: The sent event is sent to the application operation unit 1. S41: Check whether the application 6 has been terminated. If the processing has been completed, the processing is completed, and if not completed, S37 and subsequent steps are executed.

Here, instead of the window 10B, the window 10A may be a window 10C having the same image as the window 7 of the application 6. The event processing unit 2 generates a window that overlaps (has the same position and the same size) as the window 7 of the application 6 and attaches the same image as the window 7 of the application 6 to the generated window to form a window 10C. Therefore, the window 10C is a window having the same image as the window 7. Window 10C of the same image
Completely overlaps the window 7, and the user sees only the window 10C but recognizes that the window 7 is visible as it is. The user inputs an operation of the mouse 13 or an operation of the keyboard 12 on the window 10C as an event.

For this purpose, the event processing section 2 checks the position, size, color, etc. of each of the images contained in the window 7 of the application 6, generates the same image for each, and generates these images. And paste it on the window. Since the window 7 of the application 6 changes each time an event is input, the event processing unit 2 checks the image of the window 7 of the application 6 each time an event is input to the application operation unit 1 and generates the window. Paste on. As a result, a window 10C in which the latest event is always executed is obtained.

Thus, the user can use the application 6
The same screen as the window 7 can be viewed, and the same operation as the existing application 6 can be performed.
When the user inputs an event to an image in the window 7 (a window that is recognized to be), the event is actually input to the same image in the window 10C that overlaps the event. . Therefore, the event processing unit 2 operates the mouse 13 or the keyboard 12 on the window 10C of the same image overlapping the window 7.
And other operations are received as events.

FIG. 10 shows a flowchart of the processing executed by the event processing unit 2. S42: Information of the application 6 stored in the application operation unit 1 is obtained. Further, the position, size, and image of the window 7 of the application 6 are adjusted.

S43: A window 10C having the same size and the same image as the window 7 of the application 6 is generated and superimposed on the window 7 of the application 6. The event that the generated window 10C receives is mouse 1
3 or an event by operating the keyboard 12.

S44: It is checked whether or not an event has been input to the window 10C of the same image. If it has been input, S45 is executed. If it has not been input, S45 is executed.
Step 46 is executed.

S45: The input event is sent to the event transmitting section 3. S46: Check whether an event has been sent from the event receiving unit 5. If it has been sent, S47 is executed, and if it has not been sent, S50 is executed.

S47: The sent event is sent to the application operation unit 1. S48: An image of the window 7 of the application 6 is obtained. S49: The image in the window 10C is updated with the image obtained in S48. Thus, even if the image changes due to the execution of the event sent in S47, the pseudo window 10C matches the latest window 7 after the change.

S50: Check whether the application 6 has been terminated. If the processing has been completed, the processing is completed. If not completed, the processing from S44 is performed. In the application sharing operation processing apparatus 100, various functions are added to the window 10A or the like (input means 10) in the sharing operation processing of the application 6 using the pseudo window 10A or 10C generated as the input means 10. can do. These functions include, for example, input prohibition to a region at a specific position, input prohibition to a region having a specific attribute, exclusive input to an input prohibition region, and the like. As a result, the functions of the application 6 can be easily limited, and functions suitable for the sharing operation processing can be added without special knowledge (computer literacy).

For example, input prohibition to an area at a specific position is performed as follows. The event processing unit 2 restricts the function of the application 6 by prohibiting input of a specific area in the window 10A. For this purpose, the event processing unit 2 has information on the input-prohibited area, checks whether the position of the event received by the user's operation is within the input-prohibited castle, and determines that the event is only when the event is within the area. The event is sent to the event transmitter 3. On the other hand, the event processing unit 2 restricts the input of the specific area by preventing the user from inputting an event even if the user performs an operation on the specific area in the window 10A.

The setting of the input prohibition area is performed as described below.
For example, a certain user uses the mouse 13 or the keyboard 12 on the window 10A to specify the area by any method. For this purpose, the sharing operation processing unit 8 generates a guide or a palette for the input,
It is displayed on a part of the screen inside or outside the window 10A, a menu bar, or the like.

The event processing unit 2 ignores the event that has occurred in the input prohibited area even if an event is input to the window 10A, so that the function of the existing application 6 can be limited. For example, by prohibiting the input of an event in a region determined to be a region of an important matter, the user can prevent the careless updating of the important matter and save the important matter.

FIG. 11 shows a flowchart of the processing executed by the event processing unit 2. S51: Information of the application 6 stored in the application operation unit 1 is obtained. Further, the information of the application 6 is operated so as to deprive the event sent to the application 6.

S52: Input means 10 (window 10A)
Or 10C). S53: It is checked whether an event has been input to the input means 10. If it has been entered, execute S54,
If not, S57 is executed.

S54: It is checked whether the input event is a target event. The target event is an event caused by operating the mouse 13 or the keyboard 12. If the event is the target event, execute S55,
Otherwise, S57 is executed.

S55: It is checked whether or not the occurrence position of the input event in the window 10A is within the input prohibition area. When it is within the input prohibition area, S57 is executed, and when it is not within the input prohibition area, S56 is executed.

S56: The input event is sent to the event transmitting section 3. S57: Check whether an event has been sent from the event receiving unit 5. If it has been sent, S58 is executed, and if it has not been sent, S59 is executed. Therefore, the event is not sent to the event transmitting unit 3,
It will be ignored.

S58: The sent event is sent to the application operation unit 1. S59: Check whether the application 6 has been terminated. If the processing has been completed, the processing is terminated, and if not completed, S53 and subsequent steps are executed.

Application sharing operation processing device 100
In, the setting of the input prohibition area is performed by, for example, using a mouse 13 or a keyboard 12 on the window 10C by a user using the attribute (specific color, transparency, etc.) of the area.
By specifying For example, when the color of the area is red or when the transparency of the area is equal to or less than a certain value, the event processing unit 2 determines that input to the area is prohibited. As a result, input to an area having a specific attribute can be prohibited. The color or transparency indicating the input prohibited area is predetermined.

The event processing section 2 allows the user to edit the image of the window 10C by a well-known image editing means. For this purpose, the sharing operation processing unit 8 displays a guide or a palette for the editing input on a part of the screen inside or outside the window 10C, a menu bar, or the like. When the user designates, for example, the above-mentioned predetermined color as an attribute of a certain area by the image editing means, the input of the certain area is prohibited.

The event processing section 2 determines an input-prohibited area on the basis of the attribute of the pixel of the window 10C at the position where the event has occurred among the windows 10C. Since an input-prohibited area is determined based on a specific attribute (a specific color, transparency, and the like) of the image of the window 10C, the input-prohibited area can be easily set by attaching the attribute to the area whose input is to be prohibited. . For example, when the input prohibition attribute is set by color, the attribute can be easily set by painting the area with a known image editing tool.

FIG. 12 shows a flowchart of the processing executed by the event processing section 2. S60: Information of the application 6 stored in the application operation unit 1 is obtained. Further, the information of the application 6 is operated so as to deprive the event sent to the application 6.

S61: Input means 10 (window 10
C). S62: It is checked whether or not an event has been input to the input means 10. If so, execute S63,
If not input, S66 is executed.

S63: It is checked whether the input event is a target event. The target event is an event caused by operating the mouse 13 or the keyboard 12. If the event is the target event, execute S64,
If not, execute S66.

S64: It is checked whether or not the occurrence position of the input event in the window 10C is within the input prohibition area. Specifically, the determination is made based on whether or not the attribute of the pixel at the position where the input event occurs is the input prohibition attribute. When it is within the input prohibition area, S66 is executed, and when it is not within the input prohibition area, S65 is executed.

S65: The input event is sent to the event transmitting section 3. S66: Check whether an event has been sent from the event receiving unit 5. If it has been sent, S67 is executed, and if it has not been sent, S68 is executed. Therefore, the event is not sent to the event transmitting unit 3,
It will be ignored.

S67: The sent event is sent to the application operation unit 1. S68: Check whether the application 6 has been terminated. If the processing has been completed, the processing is completed. If the processing has not been completed, S62 and subsequent steps are executed.

Application sharing operation processing device 100
In the above, only a certain user can exclusively input to the area using the input prohibition area set as described above. For this, the window 10C
The event processing unit (hereinafter, referred to as an upper event processing unit) 2 having received an input of the image input prohibition region transmits the region to another event processing unit (hereinafter, referred to as a lower event processing unit) 2. As a result, in the lower event processing unit 2, input to the area is prohibited, and only the upper event processing unit 2 can exclusively input an event in the input prohibited area.

The upper event processing unit 2 is, for example, the event processing unit 2 for which the input of the image is prohibited before the other. Therefore, when a plurality of images are included in the window 10C, the upper event processing unit 2 may be used for a certain image, and the lower event processing unit 2 may be used for another image. Note that the event processing unit 2 corresponding to the application operation unit 1 that activated the application 6 first may be set as the upper event processing unit 2.

The event processing section 2 generates the same image as the image included in the window 10C generated as the input means 10, and adds an input prohibition attribute to pixels in an area of which input is prohibited. The input prohibition attribute is added by giving a specific color and a specific transparency to the image as described above. The addition of the input prohibition attribute is performed by causing the user to edit the image using a well-known image editing unit. For this purpose, the sharing operation processing unit 8 displays a guide or a palette for the editing input on a part of a screen inside or outside the window 10A, a menu bar, or the like.

The event processor 2 sends the edited image to the event transmitter 3. The event transmitting unit 3 sends the image as an event to the event integrating unit 4, and the event integrating unit 4 sends the image to the event receiving unit 5, and the event receiving unit 5 sends the image to the event processing unit 2. If the image received as the event is not the plane image transmitted by itself, the event processing unit 2 updates the pixel of the plane image to which the input prohibition attribute is added so that the attribute of the corresponding pixel is set to the input prohibition attribute. I do. As a result, only a certain user can exclusively input in the input prohibited area, and it is possible to prevent a plurality of users from trying to input in the same area at the same time.

FIG. 13 and FIG. 14 show one flowchart in total, and show a flowchart of the processing executed by the event processing unit 2. S69: Information of the application 6 stored in the application operation unit 1 is obtained. Further, the information of the application 6 is operated so as to deprive the event sent to the application 6.

S70: Input means 10 (window 10
C). S71: It is checked whether or not the input prohibited area information has been input. If it has been input, S72 is executed, and if it has not been input, S73 is executed.

S72: The input prohibition area information is sent to the event transmitting section 3. As described above, the input prohibition area information is sent to the event integrating unit 4 by the event transmitting unit 3 and further, by the event integrating unit 4.
Is sent to the event processing unit 2 via

S73: It is checked whether an event has been input. If it has been input, S74 is executed, and if it has not been input, S77 is executed. S74: Check whether the input event is a target event. The target event is an event caused by operating the mouse 13 or the keyboard 12. If the event is the target event, S75 is executed; otherwise, S77 is executed.

S75: It is checked whether or not the occurrence position of the input event in the window 10C is within the input prohibition area. Specifically, the determination is made based on whether or not the attribute of the pixel at the position where the input event occurs is the input prohibition attribute. When it is within the input prohibition area, S77 is executed, and when it is not within the input prohibition area, S76 is executed.

S76: The input event is sent to the event transmitting section 3. S77: Check whether an event has been sent from the event receiving unit 5. If it has been sent, S78 is executed, and if it has not been sent, S81 is executed. Therefore, the event is not sent to the event transmitting unit 3 and is ignored.

S78: It is checked whether or not the sent event is input prohibition area information. If it is the input prohibited area information, S79 is executed, and if it is not the input prohibited area information, S8 is executed.
Execute 0.

S79: Input prohibited area information is set. Therefore, thereafter, input to the area from the event processing unit 2 is prohibited. S80: Send the sent event to the application operation unit 1.

S81: Check whether the application 6 has been terminated. If the processing has been completed, the processing is completed, and if not completed, S71 and subsequent steps are executed. FIG.
5 is an application sharing operation processing device 100 of the present invention
5 illustrates another embodiment of the present invention and illustrates a more general embodiment of the present invention.

The application sharing operation processing device 100
Is one server 101 (or host computer)
And a plurality of data processing devices (clients or terminals) 102 connected thereto via a line or a network. Each data processing device 102 includes an application 6, an application operation unit 1, an event processing unit 2, an event transmission unit 3, and an event reception unit 5. The event transmitting unit 3 and the event receiving unit 5 may be included in the event processing unit 2. The server 101 includes an event integration unit 4. The server 101 may be connected to the plurality of data processing apparatuses 102 and may include the event integration unit 4.

Each of the data processing devices 102 operates the application 6 according to the event, and transmits and receives the event to and from the server 101 for this purpose. That is, the plurality of data processing apparatuses 102 transmit an event to the server 101, and the server 101
Then, a predetermined event is transmitted to each of the data processing apparatuses 102 by integrating the events received from the data processing apparatus 102.

Specifically, a plurality of data processing devices 102
(The event processing unit 2) of the application 6
Generates an input unit 10 (not shown) corresponding to the window 7 of the server, receives an event input to the input unit 10, and sends the event to the server 101. The server 101 (the event integration unit 4 thereof) receives a plurality of events from each of the plurality of data processing devices 102, integrates and manages these, and generates a plurality of events according to a predetermined condition among the plurality of events to be managed. To each of the data processing devices 102. Multiple data processing devices 10
2 (the event processing unit 2 thereof) operates the application 6 according to the event received from the server 101. That is, the event processing unit 2 sends the received event to the application operation unit 1, and the application operation unit 1 operates the application 6 according to the event.

Thus, as in the case of FIG. 2, a plurality of users can connect their own data processing device 102 to the server 10.
1 and can work together using the same application 6. Especially,
Even when the data processing apparatuses 102 are remote from each other, the collaborative work can be easily performed using the same application 6.

The application sharing operation processing apparatus 100 shown in FIG. 15 is realized by using a program for operating a computer as described above. The program is stored on various suitable program storage media for storing the program.

[0118]

As described above, according to the present invention,
In an application sharing operation processing device that shares and processes a plurality of identical applications, an existing application is operated by generating input means corresponding to a window of the application and integrating events input to the input means. Events that are mouse and keyboard inputs can be captured and integrated before they enter the application, so that existing applications running in multiple environments can always operate in the same state. As a result, the sharing operation of the existing application can be performed by a plurality of users, and the user is not made aware of the existence of the dedicated tool. Literacy) can be eliminated.

[Brief description of the drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is an explanatory view of an embodiment of the present invention.

FIG. 3 is a flowchart of an application sharing operation process.

FIG. 4 is an event processing flowchart.

FIG. 5 is a flowchart of an event transmission process.

FIG. 6 is a flowchart of an event integration process.

FIG. 7 is a flowchart of a data reception process.

FIG. 8 is an event processing flowchart.

FIG. 9 is a flowchart of an event process.

FIG. 10 is an event processing flowchart.

FIG. 11 is an event processing flowchart.

FIG. 12 is an event processing flowchart.

FIG. 13 is a flowchart of an event process.

FIG. 14 is an event processing flowchart.

FIG. 15 is an explanatory view of another embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Application operation part 2 Event processing part 3 Event transmission part 4 Event integration part 5 Event reception part 6 Application 7 Window 8 Shared operation processing part 9 Processing device 10 Input means (window) 11 Input / output device 12 Keyboard 13 Mouse 14 Display device

Claims (5)

[Claims] 1. A method according to claim 1, wherein each of the plurality of applications has a window for inputting an event.
Each generating input means corresponding to the window,
A plurality of event processing units for receiving the event input to the input means and transmitting the event to an event integration unit; integrating and managing the plurality of events received from the plurality of event processing units; An application comprising: an event integration unit for transmitting an event according to a condition; and a plurality of application operation units corresponding to the application and operating the corresponding application according to the event transmitted by the event integration unit. Shared operation processing device. 2. The event processing unit generates a window that overlaps a window of the application as the input unit, superimposes the generated window on a window of the application, and, via the generated and superimposed window, The application sharing operation processing device according to claim 1, wherein the application sharing operation processing device receives an input event. 3. An application operation unit that operates an application having a window for inputting an event in accordance with the event, and an input unit corresponding to the window is generated, and the event input to the input unit is generated. A plurality of data processing devices comprising: an event processing unit that receives and transmits and receives events to and from an event integration unit; and integrates and manages the plurality of events received from each of the event processing units; And a server having an event integration unit that sends an event according to the following to each of the event processing units. Each of the event processing units of the plurality of data processing devices receives the event input to the corresponding input unit. The event integration unit, and the event integration unit transmits the plurality of data processing devices. A plurality of the events are received from each of the event processing units, and these are integrated and managed, and an event according to a predetermined condition among the plurality of the managed events is determined by the event processing unit of the plurality of data processing devices. The event processing unit sends the event received from the event integration unit to the application operation unit, and the application operation unit operates the application according to the event sent by the event processing unit. An application sharing operation processing device characterized in that: 4. An application sharing operation processing device comprising: a plurality of data processing devices that operate the same application in response to an event; and a server that transmits and receives the event to and from the plurality of data processing devices. An operation processing method, wherein each of the plurality of data processing devices generates an input unit corresponding to a window for inputting an event, which is a window of the application, and the event input to the input unit And the server sends the event to the server. The server receives the plurality of events from each of the plurality of data processing devices, and integrates and manages them. Sending an event according to a predetermined condition to each of the plurality of data processing devices; An application sharing operation processing method, wherein each of the plurality of data processing devices operates the application in accordance with an event received from the server. 5. An application corresponding to an application having a window for inputting an event, each generating input means corresponding to the window, receiving the event input to the input means, and integrating the window with an event A plurality of event processing units for sending to the unit; an event integration unit for integrating a plurality of the events received from the plurality of event processing units to send the events in a predetermined order; A program storage medium for storing a program for realizing an application sharing operation processing device including a plurality of application operation units for operating a corresponding application in response to an event sent by a unit.