JPH09198426A - Drawing editing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To simultaneously edit the same drawing from plural terminals by adding exclusive information for every entity corresponding to a drawing using request from the terminal and delivering these data out of a database. SOLUTION: When the drawing using request to the side of a server 2 is inputted to an input part 31 of a client 3, that request is dispatched from a client side transmission/reception part 32 through a server side transmission/ reception part 23 to a data base change part 24 and registered in a client list storage part 25 as a client using drawing. In this case, drawing data are paid out from the server 2 and displayed on a display part 33. Concerning the displayed drawing data, an entity operating request dispatched for every entity from the client side transmission/reception part 32 through the server side transmission/reception part 23 by the input part 31. When the entity is not used, the entity is made exclusive and changed later by the data base change part 24. The changed information is transmitted to all the clients 3 using drawing.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a drawing editing apparatus having a plurality of terminals connected on a network.

[0002]

2. Description of the Related Art Conventionally, it has been desired to improve workability of a drawing editing apparatus in which a plurality of terminals such as CAD terminals are connected on a network.

In the conventional drawing editing apparatus, when the drawing data stored in the database is edited, when one terminal accesses the drawing data, it cannot be accessed from other terminals.

This is because exclusion of each drawing in the database prevents the drawing data from being corrupted by editing at a plurality of terminals (including the terminal itself). However, in this case, the same drawing cannot be simultaneously handled by a plurality of terminals, which causes a problem of lowering work efficiency.

[0005]

As described above, in the above-mentioned conventional drawing editing apparatus, exclusion is applied to each drawing, and the same drawing cannot be accessed from a plurality of terminals at the same time, which causes a problem that work efficiency is deteriorated. there were.

The present invention has been made to solve such a problem, and an object thereof is to provide a drawing editing apparatus capable of simultaneously editing the same drawing from a plurality of terminals.

[0007]

In order to achieve the above-mentioned object, the invention according to claim 1 is a database in which data of a drawing composed of a plurality of entities having a hierarchical structure is stored, and a database of the database. Receiving means for receiving a drawing use request for the data from the plurality of terminals and an operation request for each entity of the drawing, and terminal registration means for registering terminal information on which the drawing use request and the operation request are received by the receiving means. And exclusive information adding means for adding exclusive information indicating whether or not the data being paid out to the terminal whose terminal information is registered by the terminal information registration means is being used for each entity, and the receiving means during the data payout When a drawing use request is newly received from the terminal, the terminal information of the terminal registration means and the drawing requested Confirmation means for checking the exclusive information added to the entity, and the confirmation result, the terminal is different from the terminal that is issuing the data, and there is at least an unused entity in the data of the drawing requested to be used. In this case, the data is provided from the database to a new terminal.

According to the first aspect of the invention, exclusion information is added to each entity for a drawing use request from a certain terminal, and the data is paid out from the database. Then, in response to a new drawing use request, it is checked whether or not the same terminal is used and whether or not it is being used for each entity.

As a result of this confirmation, if the terminal is different from the terminal that is currently issuing data and if there is an unused entity, only that data is delivered from the database.

That is, since exclusion is applied for each entity, which is a concept lower than the concept of the drawing, it is possible to simultaneously access the same drawing from a plurality of terminals.

As a result, the same drawing can be edited simultaneously from a plurality of terminals, and the work efficiency can be improved.

[0012]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a diagram showing one embodiment of a drawing editing apparatus of the present invention.

As shown in FIG.
A server machine on the network 1 (hereafter called a server)
2 and a plurality of client machines (hereinafter referred to as clients) 3 are connected to each other. The server 2 has a server side transmitting / receiving unit 23, a database changing unit 24, a client list storage unit 25, a database 26, and the like. The server-side transmitting / receiving unit 23 is a communication means for exchanging data with the client 3 side. The database changing unit 24 manages each client by the client list storage unit 25, determines whether or not the entity can be changed, and changes the database 26.

The client 3 has an input section 31, a client side transmitting / receiving section 32, and a display section 33. The input unit 1 is used to perform various requests such as edit commands to the server 2 and entity operations.
The client side transmitting / receiving unit 32 is a communication unit for exchanging data with the server 2 side.

In the database 26 of the server 2, lines,
Basic elements data such as circles and ellipses, parts data that is a collection of them, entities (constituent elements) such as layer data (face data) where each element exists are stored in a tree structure.

The basic element data is, as shown in FIG. 2, an element number 41, an element type 42, a layer 43, a line type 44,
Parent part 45, color 46, coordinate data 47 of each of these elements
And an exclusive flag 48 and other areas.

Further, the parts data are, as shown in FIG.
Each area includes an element number 51, an element type 52, a parent part number 53, a parent part element number 54, a child part element number 55, an element number 56 under a part, and an exclusive flag 57.

Further, as shown in FIG. 4, the layer data is made up of areas such as a layer number 61, an element number 62 under the layer and an exclusion flag 63.

In the area of element numbers 41 and 51, the numbers assigned to the respective elements are entered. Numbers for identifying lines, circles, ellipses, parts, etc. are put in the regions of the element types 42 and 52. In the area of the layer 43, information indicating a layer in which an element exists (a surface for each vector element) is entered. Information indicating the line type and color of each element is entered in each area of the line type 44 and the color 46. Parent part element number 5
Since the part is treated as one element in the area of 4, the element number is entered as a pointer to the parent part. In the area of the child part element number 55, the element number is entered as a pointer to the child part, like the parent part. Note that it is possible to insert a plurality of element numbers in this area. The element number under the part is entered in the area of the element number 56 under the part. This can also be inserted in multiple numbers.

That is, in the part data, as shown in FIG. 5, child parts bbb, ccc, ddd exist under the TOP part (parent part) aaa, etc., and under these child parts bbb, ccc, ddd, respectively. Furthermore, child parts eee, fff, basic element data ggg, etc. exist,
By designating a desired element number, the data structure is such that the part of the element number and the parts of the lower hierarchy can be read. For example, in this data structure, when the element number of the child part bbb is specified, the child part bbb and the child parts eee and fff under the child part bbb are dispensed, and the parent part aaa, the child part ccc, and the child part d
dd, basic element data ggg, etc. are not paid out.

Next, a first operation example of the drawing editing apparatus will be described with reference to the flowchart of FIG. This first operation example is an editing operation for the basic element data shown in FIG.

In this case, the input unit 1 of a certain client 3
When a drawing use request is input from the server 2 to the server 2 side (step S1), the drawing use request is delivered from the client side transmitting / receiving unit 32 to the database changing unit 24 through the server side transmitting / receiving unit 23.

Then, the database changing unit 24 registers the client in the client list storage unit 25 as a client who is using the drawing (step S2).

Here, the drawing data is paid out from the server 2, and the drawing data is displayed on the display unit 33 from the server side transmitting / receiving unit 23 through the client side transmitting / receiving unit 32 (step S3).

When the input unit 31 performs an operation for each entity (component), here, for each basic element data, on the drawing data displayed on the display unit 33 (Y in step S4), the client side An entity operation request is delivered from the transmitting / receiving unit 2 through the server side transmitting / receiving unit 23.

The database changing unit 24 requested to operate the entity checks the exclusive flag 48 shown in FIG. 2 to check whether the corresponding entity is in use (exclusive flag is "1") or unused (exclusive flag is "0"). ") Is determined (step S5).

If, for example, the entity is in use (Y in step S5), it waits for input of the next operation.

On the other hand, when the entity is not used (N in step S5), the database changing unit 24 applies exclusion to the entity (sets "1" in the exclusion flag area of the corresponding data (step S6). .

After the exclusion, the database changing unit 24 changes the entity (step S).
7).

After the entity operation, the server side transmitting / receiving unit 2
3 through the client side transmitting / receiving unit 32, the changed entity information is used for all clients 3 using the drawing.
To be displayed on the display unit 33 (step S8).

After transmitting the information to all the clients 3, the database changing device 24 releases the exclusion of the entity (changes the exclusion flag to "0"). However, with respect to the deletion of the entity, the exclusion is not released because it is deleted from the database 26.

Then, the input of the next operation is awaited (step S9).

When the editing of the drawing data is completed (N in step S4), a request for ending the editing is input from the input unit 1 (step S10).

Then, the client side transmission / reception unit 32 sends a request for completion of editing to the database change unit 4 through the network 1 and the server side transmission / reception unit 23.

Upon receipt of this edit end request, the database changing unit 4 deletes the registration from the client list storage unit 25 in use of the drawing (step S11).

As described above, according to this drawing editing apparatus, exclusion is applied to each entity and the database 26
Since data is paid out from the entity unit from,
The same drawing can be edited from multiple terminals.

Next, a second operation example of the drawing editing apparatus will be described with reference to the flowchart of FIG. The second operation example is an editing operation for the part data shown in FIG.

In this case, the same client 3 as above
When the drawing use request is sent from the server to the database changing unit 24, the database changing unit 24 registers the client in the client list storage unit 25 as a client who is using the drawing, and the server 2 issues the drawing data to the client 3.

Then, when the editing operation is performed on the drawing data displayed on the display unit 33 of the client 3 by the parts designation by the input unit 31, the database changing unit from the client side transmitting / receiving unit 2 through the server side transmitting / receiving unit 23. The edit request is delivered to 24 (step S21).

By this request, the database changing unit 24
Checks the exclusive flag 56 of the part data shown in FIG. 3 to determine whether the corresponding part is in use (exclusive flag is “1”) or not used (exclusive flag is “0”) (step S22). .

If, for example, the part is in use (Y in step S22), the input of the next operation is awaited.

On the other hand, if the parts are unused (step S
22 N), the database changing unit 24 applies exclusion to the part (sets "1" in the exclusion flag area of the corresponding data (step S23).

Further, the database changing unit 24 locks the lower elements of the part (step S24),
After that, it becomes possible to edit the parts (step S
25).

After the parts are edited, the information of the changed parts is transmitted from the server side transmitting / receiving unit 23 through the client side transmitting / receiving unit 32 in the same manner as described above to all the clients 3 in use of the drawing and displayed on the display unit 33. . After transmitting the information to all the clients 3, the database changing device 24
Cancels exclusion of parts (changes exclusion flag to "0") (step S26). However, regarding the deletion of the parts, the exclusion is not released because the parts are deleted from the database 26 itself.

As described above, according to the drawing editing apparatus of the second operation example, exclusion is applied to each part and data is paid out from the database 26 in each part. Can be edited at the same time.

Next, a third operation example of the drawing editing apparatus will be described with reference to the flowchart of FIG. The third operation example is an editing operation for the layer data shown in FIG.

In this case, the same client 3 as above
When the drawing use request is sent from the server to the database changing unit 24, the database changing unit 24 registers the client in the client list storage unit 25 as a client who is using the drawing, and the server 2 issues the drawing data to the client 3.

When the input section 31 performs an editing operation on the drawing data displayed on the display section 33 of the client 3 by designating a layer, the client side transmitting / receiving section 2 through the server side transmitting / receiving section 23 changes the database. The edit request is delivered to 24 (step S31).

By this request, the database changing unit 24
Checks the exclusive flag 63 of the layer data shown in FIG. 4 to determine whether the corresponding layer is in use (exclusive flag is “1”) or unused (exclusive flag is “0”) (step S32). .

Here, for example, if the layer is in use (Y in step S32), the input of the next operation is awaited.

On the other hand, if the layer is unused (step S
32 N), the database changing unit 24 applies exclusion to the layer (sets "1" in the exclusion flag area of the corresponding data (step S33).

Further, the database changing unit 24 locks the lower elements of the layer (step S34),
After that, it becomes possible to edit the layer (step S
33).

After the layer is edited, the information of the changed layer is transmitted from the server side transmitting / receiving section 23 to the client side transmitting / receiving section 32 in the same manner as described above to all the clients 3 in use of the drawing and displayed on the display section 33. . After transmitting the information to all the clients 3, the database changing device 24
Cancels the exclusion of the layer (changes the exclusion flag to "0") (step S36). However, the layer is deleted from the database 26 itself, so the exclusion is not released.

As described above, according to the drawing editing apparatus of the third operation example, exclusion is applied on a layer-by-layer basis, and data is paid out from the database 26 on a layer-by-layer basis. Can be edited at the same time.

[0056]

As described above, according to the present invention, exclusion is applied not for each drawing but for each entity, each part or each layer, so that a drawing in a database can be simultaneously accessed from a plurality of terminals. become.

As a result, the same drawing can be simultaneously edited from a plurality of terminals, and the work efficiency can be improved.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment of a drawing editing apparatus according to the present invention.

FIG. 2 is a diagram showing a structure of graphic element data.

FIG. 3 is a diagram showing a structure of parts data.

FIG. 4 is a diagram showing a structure of layer data.

FIG. 5 is a diagram for explaining a hierarchical structure of parts data.

FIG. 6 is a flowchart showing a first operation example of this drawing editing apparatus.

FIG. 7 is a flowchart showing a second operation example of the drawing editing apparatus.

FIG. 8 is a flowchart showing a third operation example of the drawing editing apparatus.

[Explanation of symbols]

1 ... Network, 2 ... Server, 3 ... Client, 2
3 ... Server side transmitting / receiving unit, 24 ... Database changing unit, 2
5 ... Client list storage unit, 31 ... Input unit, 32 ...
Client side transmitting / receiving unit, 33 ... Display unit.

Claims (1)

[Claims] 1. A database in which drawing data composed of a plurality of hierarchically structured entities is stored, a drawing use request from the plurality of terminals for the data in the database, and an operation request for each entity of the drawing. Receiving means for receiving, terminal registration means for registering terminal information for which the drawing means request and operation request have been received by the receiving means, and data being paid out to the terminal for which terminal information is registered by the terminal information registration means Exclusive information adding means for adding exclusive information indicating whether or not each entity is in use, and a terminal of the terminal registration means when a new drawing use request is received from the terminal by the receiving means during data payout. A confirmation means to check the information and the exclusive information attached to the drawing entity requested to be used As a result of the confirmation, if the terminal is a terminal different from the terminal for which data is being paid out, and if there is at least an unused entity in the data of the drawing requested to be used, then there is provided a payout means for paying out that data from the database. A drawing editing device characterized by the above.