JPS63138452A - Document producing device - Google Patents

Abstract

PURPOSE:To improve the operability of a document producing device when a document compiling job is over by adding a control means for start area compiling part which controls the started area compiling part to a document compiling part together with a forcible finishing means for area compiling part which finishes forcibly the working area compiling part when the end of a document compiling job is indicated by an operator. CONSTITUTION:A control means for start area compiling part which controls a started area compiling part 562 is provided to a document compiling part 561 together with an enforced finishing means for area compiling part which finishes forcibly the working part 562. The control means for start area compiling part controls a specific area under compilation within a document. While the enforced finishing means finishes forcibly an area under compilation base on the contents controlled by said control means when the end of a document compiling job is indicated by an operator. Thus it is not needed for the operator to finish each area under compilation is case an area under compilation exists when an overall compiling job is through with a document. As a result, the operability of a document producing device is improved when a document compiling job is through.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a document creation device, more specifically, a document creation device that creates documents by mixing different types of data such as text, graphs, figures, etc. The present invention relates to an improvement of a document creation device that collects documents.

[Conventional technology]

In recent years, in document creation devices such as word processors,
The type of data handled is not only text (character) data, but also figures, graphs, and tables.

There are more and more types as shown in the image.

In addition, the 2gI collection method for creating a document containing a plurality of data as described above is described in, for example, Japanese Patent Application Laid-open No. 18036/1983, and according to the document creation device described in the publication, the page of the created document is After specifying the area where the data to be edited is stored on the layout, the detailed information for that area is displayed and edited in a separate area on the screen from the page layout. According to this method, when modifying data in a document, there is an advantage that the operator does not have to traverse the most suitable application program for handling the data to be modified.

[Problem that the invention seeks to solve]

However, in the prior art described above.

It is recognized that an operator edits another area while editing an area, or refers to the layout of a page other than the page where the area exists, while editing another area. Therefore, if you need to perform the above operations, either finish editing the area you are currently creating, or print the document you are currently creating, and then refer to it. You have to take steps such as editing the corresponding area again while doing so.

Therefore, when creating a document containing a mixture of multiple data as described above, it is necessary to create various data.

If you switch to other editing operations without finishing editing, editing areas on the layout display, switching display parts, etc., the operability will be improved compared to previously proposed document creation devices, but the document When an operator wants to finish editing the document as a whole, if the operator finishes editing the area one by one, there is a problem in that the operability at the end of document editing deteriorates.

The present invention has been made in consideration of one or more points,
The purpose of this is that if there are areas currently being edited when editing the entire document, the operator does not have to finish editing these areas one by one. It is an object of the present invention to provide an improved document creation device that is capable of forcibly terminating processing, thereby improving operability when completing document editing.

[Means for solving problems]

The purpose is to provide a document in which multiple types of written elements are mixed, an input section for inputting written elements to be written in the document for each area, and a storage section for storing written elements entered manually in the input section. a display section for displaying various description elements stored in the storage means; an area editing section for creating and editing data in each area; and a page layout of the created document on the display section; In a document creation device that includes a document editing unit that edits an area and activates an area editing unit for an area that is instructed to be created or updated, and an editing unit switching unit that switches editing by each of the editing units, an activated area The document editing unit is provided with a startup area editing unit management unit for managing the editing unit and an area editing unit forced termination unit for forcibly terminating the activated area editing unit when an operator instructs to finish editing one document. This is achieved by having

[Effect]

In the above configuration, the starting area editing unit management means manages which area in the document is currently being edited.

Furthermore, when an operator instructs the operator to terminate editing of a document, the area editing unit forced termination means forcibly terminates the area currently being edited based on the content managed by the startup area editing unit management unit.

〔Example〕

Hereinafter, the present invention will be explained based on the drawings, taking as an example a case where the present invention is implemented in a Japanese word processor. FIG. 1 is a block diagram showing the overall configuration of the apparatus of the present invention.

In FIG. 1, reference numeral 1 indicates an input unit, and the input unit 1 is equipped with a keyboard for inputting characters, etc., and a pointing device using a mouse for indicating operation targets, function names, etc. 2 displays characters, 2 figures, etc., e.g. CR
A display section 3 is constituted by a T-display, and a storage section 3 is composed of a semiconductor memory, a magnetic storage device, etc. The storage section 3 stores the contents of a document created in 1, window management information to be described later, and the like. Reference numeral 4 denotes a printing section constituted by, for example, a wire dot printer. Reference numeral 5 denotes a control section consisting of a microprocessor or the like for controlling each of the above-mentioned sections.

The control section 5 includes an input control section 51. window management section 52,
System control unit 53. Print control section 542 Display control section 55
9 Editorial Department 56. System management department 57゜File editing department 5
In this embodiment, document creation and editing are performed by one editing section 56;
It consists of two parts: a document editing section 561° and an area editing section 562.

FIG. 2 shows an example of the screen display of the display unit indicated by reference numeral 2 in FIG. m collection area 23. It consists of an icon area 24, and each editing section has a rectangular frame 2 in the editing area 23.
5 (hereinafter referred to as a window), and document data is individually edited within the window. The menu area 22 displays function classification names 26 (hereinafter referred to as pull-down menu names) of each editing department, and when the operator points to the pull-down menu name 26 with the mouse, a window is set (hereinafter referred to as window open). )1 Edit area 2
3, a detailed function item list 28 is displayed (hereinafter referred to as a pull-down menu area). For example, as shown in FIG.

In the menu area 22, pull-down menu names 26 such as edit and print are displayed, and when the operator instructs editing using the mouse, the pull-down menu area 28
is opened and function items such as new creation and update are displayed, and when the operator instructs a function item with the mouse in this state, the specified function will be executed. The window 25 includes a caption area 251 . . . that displays a window name, for example. Data area 2 to display data
52. Operator closes the window.

It is composed of a control area 253 for instructing operations such as movement and resizing. In the icon area 24, pictograms (hereinafter referred to as icons) 27 representing each program such as the editorial department are displayed.

When an icon is selected by the operator, the corresponding program is started.

In FIG. 3, the mouse 31 includes 1, for example, an execution button 23111 for selecting an operation target, 2 functions, etc., and a cancel button 312 for canceling the selected operation target.

Further, in FIG. 2, the mouse cursor 30 moves on the screen 21 in a manner that does not closely follow the movement of the mouse 31 by the operator, and indicates an object to be operated on the screen 21.

Next, the configuration of each part of the control section indicated by reference numeral 5 in FIG. 1 will be explained.

In FIG. 1, the system management section 57 includes the input control section 5
For example, programs such as the file editing section 581 and the document editing section 561 are activated, corresponding to the icons notified from 1. The correspondence between icons and programs is managed by an icon management table 571 shown in FIG. 4, and the icon management table 571 stores program numbers corresponding to icon numbers. This program number is an identification number assigned to each program, and each program is managed by a program control table 572 shown in FIG. The program control table 572 has program control blocks 573 (hereinafter abbreviated as PCB) arranged in order of program number. PCB573 has
Program start address information 5731, stack address information 5732. Priority information 5733. Parent program number 5
734. Data type 5735 and other program attributes 5736 are stored. The parent program number 5734 is
This indicates from which program the program is started. The data type 5735 indicates what kind of data, such as text or graphics, the program handles, and a data number is stored in the data type 5735. In addition, the data name corresponding to the data number is shown in the data name definition table (hereinafter referred to as "data name definition table"), as shown in FIG.

(abbreviated as DNDT) 574.

In FIG. 1, the file editing section 58 displays a list of documents stored in the storage section 3 in the window of FIG. 2, and edits the specified document.

Here, editing one document means updating or deleting the document.

It is a general term for printing, etc.

The document editing unit 561 displays in a window the layout of the relevant part of the document that the file editing unit 58 has been instructed to create or update, and edits the area one page above. This is a general term for new creation, update instructions, deletion, movement, copying, etc. of internal element data.

The area editing unit 562 displays the contents of the area for which new creation or updating has been instructed by the document editing unit 561 in a window, and creates and m-sets data within the area. Note that the area editing section 562 includes various editing sections depending on the type of data. That is, they include a text data editing section, a graph data editing section, a graphic data editing section, and the like.

Among the above editing sections, the editing section that can be executed after the start of document creation is always the editing section in the topmost window on the screen. In addition, to bring the window to the top level, that is, to switch the editing section, move the mouse cursor 30 in FIG. 2 over the displayed window, and click the execution button 3 in FIG.
The window management unit 52 changes the specified window stacking order by pressing 11.

In addition to changing the stacking order of windows, the window management section 52 opens and closes windows on the screen according to requests from each editing section. Windows opened on the screen are managed by a window management table 521 shown in FIG. The window management table 521 includes the window management block 52
2 (hereinafter abbreviated as WCB) arranged in order of window number. The following information is stored in the 11cB522.

(Window setting position and size information 5221) Stores the upper left X coordinate, y coordinate, lower right X coordinate, and y coordinate of the window when the upper left of the screen shown by reference numeral 21 in FIG. 2 is set as the origin.

(Window overlapping order information 5222) When a plurality of windows are opened on the screen 21, information indicating the order in which they overlap is stored.

(Window name information 5223) Stores the window name to be displayed in the caption area 251 of the window 25.

(Task number 5224) The number of the task that set the window is stored.

Each Ig collection unit is generated as one task, and a task number is given by the system control unit 53 when one editing unit is generated as a task.

(Window display image storage position information 5225) One window display buffer is prepared for each window, and the display image data of the window is stored therein. The window display image storage location 5225 stores the location of the corresponding window display buffer. This information is used when changing the stacking order of windows.
Used to recover the display image of the hidden part of the window.

(Menu data storage location information 5226) Menu area 22. Stores the storage address of menu data to be displayed in the pull-down menu area 28.

(In use flag information 5227) Stores information indicating whether the WCB 522 is in use.

Then, the window management unit 52 in FIG. 1 changes the stacking order of windows based on one or more pieces of information.

Open, close, etc. Note that when changing the stacking order of windows, the window management section 52 instructs the system control section 53 to suspend the editing section that was being edited up to that point, and also to restart the editing section of the specified window.
The system control unit 5 uses the task number information 5224.
Request 3.

Further, the window management unit 52 requests the input control unit 51 to display the menu corresponding to the window that has become the topmost window by operating the window, according to the menu data storage position 5226.

Based on a request from the window management unit 52, the system control unit 53 suspends or re-generates a corresponding task, or activates a task corresponding to a corresponding editorial department based on a startup request from each editorial department. or, based on a termination request from the editorial department, performs termination processing for the task corresponding to the corresponding editorial department.

Furthermore, in order to enable information exchange between tasks, the system control unit 53 sends a message to the corresponding editorial department based on a request from each editorial department, or receives a message sent from the corresponding editorial department. or receive it. Each task is managed by a table called a task control table 531 shown in FIG. One TCB 532 is assigned to a task. TCB5
32: 1 For example, as shown below, the start of the task.

All information necessary for restarting is stored.

(Link field 5321) Used when connecting TCB532 to a list.

(Task priority information 5322) Stores priority information when executing tasks.

(Program number 5323) Stores the number of the program that generated the task.

(Task status information 5324) Stores information indicating what status the task is currently in.

(Suspension flag information 5325) Information indicating that a suspension request has been made to the task is stored.

(Task start/resume address information 5326) Stores the start address of the task or the address at the time of interruption.

(Stack status information 5327) Stores the stack position at the time the task was suspended.

(CPU status information 5328) Saves all register contents at the time the task was interrupted.

Here, the state of the task is 1, for example, as follows ( There is one thing to show.

(NONEXIST state) Indicates a state in which the program does not exist as a task. At this time, the task number corresponding to the TCB becomes unused.

(DORMANT state) - Indicates a state in which the program exists as a task, but execution is prohibited.

(READY state) When a CPU is assigned to a task, this indicates a state in which the program can be executed (the part that assigns tasks to the CPU is called a task dispatcher).

(RUNNING state) Indicates the state in which the task program is being executed.

(WAITING state) 0 indicates a state where the execution of the task is suspended until a certain event occurs. For example, waiting for a message to be received, where the task is kept waiting until a message is sent, or end of input/output, where the task is kept waiting until the input/output is completed. There is a wait etc.

As shown in FIG. 9, a task in the READY state is managed, for example, by connecting corresponding TCBs to a list in order of priority, and this list is called a READY queue (numeral 533 in FIG. 9). The header of the READY queue 533 stores a pointer to the TCB corresponding to the task in the READY state with the highest priority, and the link field 5321 of the TCB stores a pointer to the TCB corresponding to the task with the first highest priority. A pointer is stored, and thereafter TCBs are similarly connected by pointers in order of priority, and the link field of the last TCB stores information indicating that it is the last TCB in the list. The task dispatcher allocates and executes a task corresponding to the highest priority TCB among the TCBs connected to the READY queue 533 to the CPU.

Tasks in the VAITING state are
B is connected and managed in a list prepared for each cause based on the cause of each wait, and when the wait is canceled due to the occurrence of the above event, the TCB is removed from the corresponding list 1~ and RE
The ADY queue 533 is connected and the task dispatcher resumes the task from the point where it was interrupted.

Messages are managed by a message control table 534, as shown in FIG. 10, and the message control table 534 is managed by a message control block 535 (hereinafter referred to as
(abbreviated as MCB), and one MCB 535 is assigned to one message.

The MCB 535 includes, for example, a status 5351. Sender task number 5352. Receiving side task number 5353. A message size 5354 and a message buffer 5355 for temporarily holding the transmitted message are stored.

Also, if a message reception request is made according to the message reception request parameters, and the message has not yet been sent from the other task, the TCB 532 corresponding to the task that requested reception is sent to the READY queue 533.
from the message receiving queue 53 shown in FIG.
6 and put the task in the IIAITING state until the message is sent, or you can simply indicate that the message has not been sent without putting the task that requested reception into the WAITING state. It can also be passed to the task.

Here, the overall processing flow of the system control unit indicated by reference numeral 53 in FIG. 1 will be explained based on FIG. 12. When a processing request is issued from a task to the stem control unit 53,
First, the execution environment at the time when the task issued the request is TCB.
532 (step 1001 in FIG. 12).

Next, the requested functions (steps 1003 to 1008) are identified and processes corresponding to each function are activated (step 10
02).

After the processing corresponding to each function is completed, it is determined whether or not the task will be switched based on the state of the READY queue 533, for example (step 1011). If the task is switched, the task dispatcher 1o13 is activated. If the task is not switched, the execution environment saved in step 1o01 is restored from the TCB 532 (step 1012), and the task that issued the request is restarted. Also, when an input/output end interrupt occurs from an input/output device, the execution environment at the time of the interrupt is set to TCB532.
(step 1009). Next, after performing input/output termination processing such as passing the input character code etc. to the input request task and releasing the input task from waiting (step 1010).

Activate the task dispatcher 1013.

As shown in FIG. 12(j), the task dispatcher 1013 sends the TCB5 to the READY queue 533 in FIG.
Step 119 to determine whether or not 32 is connected.
1) If the TCB 532 is not connected to the READY queue 533, an infinite loop is performed (step 1197) until an interrupt occurs, and the READY queue 533
If the TCB 532 is connected to the READY queue 533, the TCB 532 with the highest priority is acquired from the pointer stored in the header of the READY queue 533, and the task is It is determined whether there is an interruption request (step 119).
2).

Then, if there is a suspension request for the task, the pointer is updated and the relevant TCB 532 is removed from the READY queue 533 (step 1193), and the process is performed again from step 1191.
Step 1194: Set CB532 to ACTIVE state.
), the execution environment is recovered from the TCB 532 (step 1195), and the corresponding task is restarted (step 1195).
196).

The functions required for the system control unit 53 are 1.
For example, task creation/deletion processing (step 1 in Figure 12)
003), task startup/termination processing (step 100S
), task forced termination processing (step 1005), task suspension/resumption processing (step 1006), message sending/receiving function between tasks (step 1007), and input/output request processing (step 1008). Request processing (step 1008″f′, accepts input/output requests from the task to the keyboard, display device, etc., and sends the request to R
or transition to EDY state. Note that the other processing flows are shown in FIGS. 12a to 12i, and the details of each of these flows will be described later.

In FIG. 1, the input control unit 51 passes character codes input from the keyboard and coordinate values input from the mouse (reference numeral 31 in FIG. In accordance with the area 21) in the figure, the system management section 57 is notified of the designated icon, the designated menu task is notified, and a window switching request instruction is issued to the window management section 52.

FIG. 13 shows the processing system of the input control section 51 described above,
First, in step 1301 in FIG. 13, input data from the input unit (reference numeral 1 in FIG. 1) is analyzed to determine whether the input is from the mouse 31 in FIG. 3. If the input is not from the mouse 31.

This is an input from the keyboard, and the character code corresponding to the pressed key is acquired (step 1311), and this acquired character code is passed to the input request task (step 1312).
). For example, if an operator presses the letter "a" on the keyboard, the task that requested the input will be filled with "a".
Pass the character code.

If it is determined in step 1301 that the input is from the mouse 31, coordinates are determined to find out which location on the screen the operator has indicated (step 1302);
The mouse cursor 30 in FIG. 2 is displayed at the mouse movement position (step 1303).

As a result of step 1302, if the operator's instruction is inside a window that is not at the top level, it is determined that it is a window switching instruction (step 1304), the window management unit 52
to request window switching (step 13
16).

In step 1305, if the operator's instruction is the icon area 24 in FIG.
13) Notify the system management unit 57 of the acquired icon number (step 1314), and in FIG. 1, the system management unit 57 stores the program corresponding to the notified icon in the icon management table 571 of FIG.
, and generate the program as a task.
In order to start the generated task, the system control unit 53 is requested to generate and start the task.

Also, in step 1306 of FIG.

If there is an instruction for an operation target within the topmost window, the instruction coordinate values are converted from coordinates on one screen to relative coordinate values within the window (step 1317).
, passes the coordinate value to the task that requested the input (step 1318).

In step 1307, if the operator's instruction is the menu area 22 in FIG.
is requested to open the pull-down menu area 28 (step 1315).

Further, in step 1307, if the operator's instruction is the pull-down menu area 28 (step 13
08), determine which function item has been specified, and pass the specified function item number and pull-down menu number to the task that requested the input (step 1319).

In step 1309, the operator's instructions are in the control area 253 or caption area 2 in the window.
If it is 51, the code for closing, scrolling, etc. is passed to the task that requested the input (step 1310).

Further, in step 13o9, the operator selects the control area 253 or caption area 2 within the window.
If an area other than 51 is specified, nothing is executed.

Note that when passing a code to an input requesting task, the system control unit 53 in FIG.
Transition from ING state to READY state.

The menu is stored in the menu management table 523. shown in FIG. It is managed by a pull-down menu management table 525.

In FIG. 14, the menu management table 523 includes:
Number of pull-down menus: 5231. The subsequent menu management block 524 is stored in the order of the pull-down menu numbers by the number of pull-down menus. The menu management block 524 includes a pull-down menu name 524.
1. Maximum number of characters for function item: 5242. Number of function items: 524
3. A pointer 5244 to the pull-down menu management table 525 is stored.

In addition, the pull-down menu management table 525 includes one function item name 5251. Valid/invalid flags 5252 indicating whether a function item is valid or not are stored in the order of function item number for the number of function items.

Based on one or more pieces of information, the input control unit 51 in FIG. Menu area 22 in the figure
to be displayed. Also, the pull-down name is Mouse 3 in Figure 3.
1, the function item name is acquired from the corresponding pull-down menu management table 525 in FIG. 14, and if the function item is valid, it is normally displayed.

If it is invalid, it is displayed in half-brightness in the pull-down menu area 28 of FIG. 2.

In FIG. 1, a print control section 54 controls the printing section 4 based on a document printing request from an editing section 56. Also,
In response to a display request from the first editing section 56 and the window management section 52, the display control section 55 displays data for only the portion that can be developed in the topmost window based on the stacking order information of the window management block 522 shown in FIG. is written to the corresponding memory dot by dot.

Here, a case will be described below in which the Japanese word processor shown in this embodiment is used to create and edit a document.

First, in the initial state, in order to start creating a new document or editing an already created document, the operator points to the corresponding icon using the mouse 31 in FIG.

In response to the instruction from the operator, the input control section 51 in FIG. 1 determines which icon is specified from the one-screen specified coordinates, and notifies the system management section 57 of the icon number. On the other hand, as shown in the flowchart of FIG. 18, after displaying the icon in the initial state (step 1701), the system management unit 57 requests the reception of a message and requests step 1 to receive the message.
702), if the message is received in step 1702.

Determine the sender of the message (Step 1703)
, if the sender of the message is the input control unit 51, the program number corresponding to the designated icon is first acquired based on the icon management table 571 in FIG. 4 (step 1704), if applicable. The editing department is generated as a task and activated (step 1705).

The generation and activation of the task described above is first performed by the system management section 57 to the system control section 53, as shown in the processing flows of FIGS. 12(a) and 12(c).

When a task generation request is made based on the program number,
Based on this, the system control unit 53 obtains an unused task number from the task control table 531 in FIG.
Create a TCB532 corresponding to this (Fig. 12 (a)
), the task is placed in the DORMANT state (step 1102).

Return the obtained task number to the requester (Step 1
103).

Next, when the system management unit 57 issues a task activation request according to the task number, the system control unit 53
REA the TCB532 corresponding to the specified task number
Step 1121) in FIG. 12 (Q) as DY state,
By connecting this TCB 532 to the READY queue 533 in FIG.

The relevant editorial department becomes executable (step 11)
22).

Note that the notification of the icon number described above is performed by sending and receiving messages via the system control unit 53. For example, as described above, from the input control unit 51 to the system management unit 5
7, the input control unit 51 first requests the system control unit 53 to send a message to the system management unit 57 (step 1706 in FIG. 18).

Then, as shown in FIG. 12(h), the system control unit 53 determines from the message control table whether or not a reception request from the system management unit 57 has arrived.
Step 1171 in Figure 2 (h), if a reception request has arrived, the transmitted message is transferred to the corresponding MCB (first
0) message buffer (also the first
Step 1174) is transferred to step 5355) in Figure 0.
The task waiting for reception, that is, the TCB of the system management unit 57
(reference numeral 532 in FIG. 8) is removed from the message reception queue 536 in FIG.
33 (step 1175 in FIG. 12(h))
.

Further, in step 1171 of FIG. 12(h), if there is no reception request yet, the system control unit 53 acquires an unused MCB (step 1172), and transfers the message to the message buffer of this MCB (step 1173). ).

On the other hand, when the system management section 57 requests the system control section 53 to receive a message, as shown in FIG.
As shown in FIG. 12, the system control section 53 determines whether or not the message for the system management section 57 is in the MCB (step 1181 in FIG. 12(i)). For example, the message is retrieved from the MCB and transferred to the system management unit 57 that is the request source (step 1184).

Note that if there is no message in the MCB in step 1181, it is determined whether the task that issued the macro made the request specifying waiting (step 1182).
, if there is no waiting, returns that there is no message for the task and ends the process (step 1185).
.

In addition, in step 1182, if there is a wait,
After acquiring the unused MCB, the TCB of the task is removed from the READY queue 533 in FIG. 9 and connected to the message reception queue 536 in FIG. 11 (step 1183).
, transfer control to the dispatcher (step 1186);
In other words, a message is sent to M by a message sending request.
When the task is transferred to the CB, the task waiting for reception is transferred to the R
Since it is connected to the EADY queue 533, this task is restarted and executed again from the message reception process, and the M
The contents (message) of the CB are received by the task.

If the operator's instruction is to create a new document, the document editing section indicated by reference numeral 561 in FIG. In the case of editing, the system management section 57 starts up the r-file editing section 58 which instructs which document to edit next.

Next, the processing contents of the file editing section 58 will be explained based on the flow shown in FIG. 19.

In FIG. 19, the file editing section 58 first opens a window (step 2001 in FIG. 19), and displays a list of documents stored in the storage section 3 in the window (step 2002). After displaying the document list described above, the file editing section 58 requests input from the input control section 51 (step 2003), and if there is an input, determines its contents. In step 2004.

If the input from the operator is an instruction for a document to be operated, it is determined which document has been instructed (step 2004), and the operation target document table 5 shown in FIG.
81 (step 2005);
The operation target document table 581 shown in FIG. 20 is composed of a designated document number 5811 and a designated document name 5812.

Has an update/print instruction been given to the ring section 57? Step 20
06) In the case of an editing instruction such as copying or deleting a document, processing such as copying or deleting the specified document is performed (step 2007).

If it is a scroll instruction, a scroll display of the document name list is performed (step 2008); if it is an end instruction, the window is closed (step 2009);
To the system management department 57.

Step 2 to notify you that the file editing process has finished
010), requests termination of the task (step 2011
), in response to this termination request, the system control unit 53
As shown in Figure 2(d), the TCB (8th
(see reference numeral 532 in the figure) is set to the DORMANT state and the first
In step 1131 of FIG. 2(d), resources used by the task are released (step 1132), where resources refer to memory and CPU.

Further, the window opening/closing process is performed in the window management unit 52 shown in FIG. 1, and the contents of the process will be explained based on the flowcharts shown in FIGS. 15 and 16.

First, in the case of a window oven, the window management section 5
2 generates the VCB 522 shown in FIG. 7 based on the information specified by the task (step 15 in FIG. 15).
01). At this time, it is determined whether the window already exists (step 1502), and if it does exist, the task using the currently topmost window is temporarily interrupted (step 1503), and The display image of the window is saved in the display buffer (step 1504).

Then, the window is displayed according to the position and size specified by the task (step 1505).

Furthermore, the number of the generated window management block is returned to the requesting task (step 1506).

On the other hand, in the case of window closing, the image of the specified window is first erased (step 1511 in FIG. 16), and then the window management table 52 in FIG.
1, the window hidden by the window to be closed is identified, the display image is retrieved from the display buffer described above, and the display image of the window below the erased window is restored.Step 1512
), the VCB 522 of the erase window is made unused (step 1513). Note that the task interruption process will be described later.

If the request from the operator is to create a new document, the system management section 57 generates the one-document editing section 561 as a task based on the notification from the input control section 51 (step 1705 in FIG. 18).

Start up in new creation mode (step 1707).

In addition, if the request from the operator is to update an already created document, the corresponding program number should be obtained from the program control table (numeral 572 in FIG. 5) based on the data type number notified from the file editing section 58. Step 1
708), generate the document editing section 561 as a task, step 1709), send startup parameters to the i editing section 561, step 1710), and start the document editing section 561 in update mode (step 1711).

Furthermore, when the system management section 57 receives a completion notification from the editing section that it generated and activated, it deletes the task (step 1712 in FIG. 18).

The deletion of a task is processed by the system control unit 53 in the same way as the task generation request described above, and the system control unit 53 deletes the TCB (No. (see reference numeral 532 in Figure 8) to N
0NEXISTENT state (step 1111 in FIG. 12(b)). In other words, the TCB is placed in an unused state.

Note that when the system management section 57 starts up the document editing section 561, it sends the mode and the generated task number as a starting parameter to the document editing section 561 by a message. In addition, in the case of document update mode, the name of the document to be updated notified from the file editing section 58 is also transmitted.

Now, the processing when the document editing section 561 is activated will be explained based on the flowcharts of FIG. 21 and FIGS. 22(a) to (Q).

First, as an initial process (step 3001 in FIG. 21), the document editing unit 561 receives startup parameters by message (step 3101 in FIG. 22(a)), and creates a new document based on the contents of the parameters. 2, the startup mode is determined (step 3102).
),and.

When creating a new document, initialize the document data (
Step 3103), in case of document update.

(Step 3104), and the structure of one document data will be described later. Then, the program control table (fifth
572) in the figure, a support area editing department management table (hereinafter abbreviated as SFMT) is created which shows a list of area editing departments that can create new areas and update areas in the document. science fiction
As shown in FIG. 27, the MT holds the program number 5682 of the area editing unit that can be supported and the data type editing unit 5683 that can be created by this area editing unit as a pair, and further stores the number of area editing copies 5681. have. At the same time, the name of the data for the area editing section is set in the pull-down menu data in order to inform the operator of what kind of data it is currently possible to create an area for (Fig. 22(a)). step 3105)
, and then.

When editing the area described later, the specified area of the operation target area table (FIG. 28) indicating which area is the operation target is cleared to 0 (Step 3106), and then the valid/invalid state of the pull-down menu data is initialized. I do(
Step 3107), the operation target area table is
As shown in FIG. 28, the number of specified areas 5684 currently specified as the operation target, the type 5685 of the area specified as the operation target, and the number 5686 of the area specified as the operation target are held. do. Note that the type of area will be described later. Furthermore, switching between valid and invalid pull-down menu data 1 will be described later. Next, the document editing section 561 in FIG. 1 opens a window (step 3108 in FIG. 22(a)).
, displays the layout of the first page of the edited document in the window as shown in FIG. 31(a) (step 3109).
, When opening the window, the size of this window should correspond to the size of one display paper.

Also, part of the title of the window is
Add task number 1.

Here, the SFMT shown in FIG. 27 and FIG. 22, (a)
Next, the menu data creation process shown in step 3105 will be explained in more detail.

The SFMT shown in FIG. 27 is the document editing section 561 of FIG.
For this, program number 56 of the area editing section that can be activated
This is a table showing a list of 82 and data type number 5683, and is used as a parameter when creating a new area, updating an area, and displaying a layout, which will be described later, to determine whether a corresponding program exists or not, and when creating a task. .

The method for creating it is shown in FIG. 22(b).

First, the program number P and registration number E are cleared to 0 (steps 3111 and 3112), and the parent program number is set in the document editing section (steps 3111 and 3112) starting from the first block of the program control table (572 in FIG.
) It is determined whether the program number matches its own program number (step 3114), and if it matches, the 1 document editing section 5
The program number P and the data type number tDp set in the PCB 573 are registered in the SFMT of FIG. Step 3
115). Also, the name of the data corresponding to the data type number (for example, "Graphic $1.11 Graph", etc.) should be entered in the DN.
DT (reference numeral 574 in FIG.
Step 3116), increment the registration number E (step 3117), repeat the above process for the number of program management blocks (step 3118).
and 3113), and finally the registration number E is the number of area editing copies 5
681 (step 3119)
This makes it possible to display only the names of area editing units that are currently actually incorporated in the system as a pull-down menu.

Next, the structure of document data will be explained using FIG. 24.

The document data is stored in chapter management table 5610. as shown in FIG. Page management table 5620. Buying table 5
630. The area management table 5640° is further composed of area data 5660, and each table is composed of a plurality of blocks. The respective tables (5610 to 5640) and the intra-area data 5660 will be explained below.

(Chapter management table 5610) Manages how many chapters the entire document consists of,
Page pointer 5611.5 indicating the first/last page for each chapter
612. It also holds print information 5613 for displaying and printing headers, footers, etc. for each chapter.

(Page management table 5620) Area pointers 5623, 5624 . Furthermore, a true format pointer 5 indicating which format data is used on each page
625. Also, each block has a backward pointer 5
621 and the forward pointer 5622, the pages are linked in ascending order.

Regarding the first/last page, please refer to the above-mentioned car management table 5.
610 points. Note that the pages in this document data are structured as shown by reference numeral 5671 in FIG. 25. Of these, the page size and margins are determined by the true format table 5630 described below, and by the basic area 567.
2. Regarding the internal area 5673, area management table 5
640, respectively.

(True format table 5630) The paper type (A
3. A4, etc.), paper orientation (portrait, landscape).

Manage top, bottom, left, right margins, etc.

(Area management table 5640) This table manages where and in what size data to be stored within a document (within a page), such as various data such as text data, graphic data, and graph data, is stored within the page. Therefore, the area management table 5640 defines the area setting position within one page as the area upper left X coordinate 5643. Same y coordinate 56
44° lower right X coordinate 5645. It has the same y coordinate of 5646.

Furthermore, data type 5647 indicating the type of data in the area
, an area attribute 5648 that indicates the attributes of the area itself, and a data pointer 565 that points to data within the area 5660.
has 0. Note that the attributes of the area itself include whether it is transparent or opaque (in the case of opaqueness, the area covered by the area below becomes invisible), the line type of the area frame, etc. In addition, one table (area management table) 5
At 640, in order to manage the order in which areas within the same page overlap, a backward pointer 5641 and a forward pointer 5642 are used to link them to each other. Links in this area link from areas of low priority to areas of high priority, that is, from the lowest area to the highest area within the page. Further, among these, the first/last areas are each pointed to from the above-mentioned page management table 562o. Furthermore, the area management table 5640 includes status information 5649 indicating whether the area is being edited or not, and whether or not the area editing department corresponding to the area data type currently exists in the system.

On the other hand, the areas existing within the page indicated by the reference numeral 5671 in FIG. 25 can be roughly divided into the following two areas.

(i) Internal area 5673 An area existing on the basic area whose position and size are determined by an operator's operation. Moreover, one of various data such as text, graphics, graphs, and images can be stored in the area.

Furthermore, editing this area involves creating a new area.

All area editing is possible, including updating, moving, copying, and deleting.

(it) Basic area 5672 Refers to the part of the page excluding the top, bottom, left, and right margins. When a page is generated by an operator's operation, one basic area is also generated. Within the page, it is always the first area (the lowest area). In addition, only text data that is the main text of one document is stored in this area, and when editing this area, it is possible to create a new area, update it, and move to this area.

For editing operations such as copying and deleting, move the page.

Perform editing operations such as copying and deleting.

(Region data 5660) Data stored within an area, including text and shapes.

Graphs, image data, etc. are stored.

Now, in FIG. 21 showing the processing system of the document editing section indicated by reference numeral 561 in FIG. request (step 3002), and
Step 3003: Judging the input result from the operator
), if the determination result is an instruction for the area to be operated, it is determined based on the document data which area was specified based on the specified position within the page number 7 and the setting position of the area, and the area is The number is registered in the operation target area table of FIG. 28 (step 3004). The determination method at this time will be explained in more detail using the flow of FIG. 22(c).

In FIG. 22(c), it is first determined whether the designated position is in the basic area 5672 of FIG. 25 in step 3.
201), if the indicated position is outside the basic area 5672, there is no area corresponding to the indicated position, so it is determined as an instruction error.

In step 3201, the designated position is the basic area 567.
If it is within 2, the following internal area 5 within page 1 5671
Steps 3202 to 3205) determine whether or not the indicated position is within the internal area 5673, starting from the area at the highest level (the last area within the page). If there is, the operator's instruction is in the internal area.On the other hand, if the specified position is not within the internal area 5673 (inner area instruction flag is 0), the operator is assumed to have specified the basic area 5672 and the process is performed. . Now, if the designated position is within the internal area 5673, the first step is to check whether the area 5673 has already been designated as a target, that is, whether the number of the area 5673 has already been registered in the operation target area table of FIG. (Step 3207), it is determined whether or not the area 5
673 has already been specified as a target, the primary area (on the document data, the forward pointer of the area management block of the area currently being judged (reference numeral 564 in FIG.
2)) (area indicated by step 3)
211), on the other hand, if the internal area 5673 has not yet been specified as a target, it is assumed that the area 5673 has been specified, and the number of the area 5673 is registered in the operation target area table. Already basic area 5
672 is specified as the target (step 3
208).

Once the number of specified areas 5684 in the operation target area table is cleared to 0 (in other words, after the target designation for the basic area 5673 is canceled in step 3209), the internal area number and area type are registered in the operation target area table. , and further increments the number of designated areas 5681 by 1 (step 3210).

In the above, when the basic area 5672 is registered as an operation target, forcibly canceling the designation is as follows:
This is because, as will be described later, if the basic area 5672 and internal area 5673 can be specified at the same time, there will be no area editing corresponding to this. Further, in the above process, if the internal area 5673 is not registered, it is determined whether the internal area designation flag is 0 or not (step 3212).

If the internal area designation flag is O, there is no internal area 5673 at the specified position, and the operator selects the basic area 5673.
72 is considered to have been specified as the target. Next, the number of the basic area 5672 is registered in the table, but at this time, it is determined whether or not the basic area 5672 has already been specified as a target (step 3213). 1 if not
Next, it is determined whether the internal area 5673 is specified as a target (step 3214), and the internal area 567
3 is specified as the target, the operation target area table is cleared once (step 3215), the basic area number and area type are registered in the operation target area table of FIG. 8, and the number of specified areas is set to 1. (step 3216).

Now, if the instruction from the operator is to cancel the designation of the area that is currently being designated as a target, then the page number.

Based on the document data, it is determined which area is specified from the specified position within the page and the set position of the area, and the area number is deleted from the operation target area table (step 3005 in FIG. 21). The method for determining the time will be explained in more detail using the flow shown in FIG. 22(d).

In FIG. 22(d), it is first determined whether the indicated position is within the basic area 5672 of FIG. Clear unconditionally. That is, the designation of all areas registered in the table is canceled (step 3258). On the other hand, if the specified position is within the basic area front 5672 in step 3251, the designation of all areas registered in the table is canceled (step 3258). Step 3252: Step 3252 to determine whether the indicated position is within the area 5672 in order from the area where it is located (the last area in the page).
and 3253), as a result of the determination, the indicated position is the area 5
672, step 32 determines whether the corresponding area 5672 is registered in the operation target area table.
54), if the area 5672 is registered in the operation target area table, the area number is deleted from the table (step 3257); on the other hand, if the indicated position is not within the area 5672 in step 3253, If the area 5672 is not registered in the table in step 3254, step 325
5 and 3256, similar determinations are made for subsequent areas.

However, along with the above area designation/cancellation operation.

The area editing operations that can be performed change sequentially, but next, the process of switching the valid/invalid state of the pull-down menu related to area operations (step 3014 in FIG. 21) is shown in FIG. 22(e).
Explain using.

By the way, as shown in FIG. 26, editing operations on regions can be classified into three types depending on the number of regions designated as operation targets. That is, first of all, Fig. 22 (e
), the number of areas being specified as a target is determined, the step is performed, and all other area editing is invalidated (step 3302). Also, if the number of areas being specified as a target is 1, conversely, For now, only the pull-down menu for creating a new area is disabled, and all other area editing is enabled (step 3303). Furthermore, if the number of target areas is 2 or more, only move, copy, and delete operations are enabled, and all other area edits are disabled (step 3).
304), and if the number of specified targets is 1, it is further determined whether the specified area is a basic area or not (step 33).
05), If the specified area is a basic area, attribute changes and size changes are also disabled (step 3306), then it is determined whether the status of the specified area is other than O (step 3307), the status of the specified area If is other than O (that is, the area is currently being edited or there is no area editing unit in the system that can update the area), the update is also invalidated (step 3308).
. If the specified number of targets is 1 or more, it is determined whether there is an area (area currently being edited) in which the status is 1 among the specified areas (step 3309), and an area where the status is 1 in the specified areas. If exists, the deletion is also invalidated (step 3310).

Now, next, in the flow of Fig. 21, the case where the instruction from the operator is an instruction to create a new area (step 3006 in Fig. 21) will be explained based on the flow of Fig. 22 (f). .

By the way, what are the instructions for new creation by the operator?

This is done by specifying the data name displayed using a pull-down menu, but the document editing section 56 in FIG.
Step 1 is to obtain the program number and data type number of the corresponding data based on the SFMT in FIG. 27 according to the pull-down menu number passed from the input control unit 51 (step 3401 in FIG. 22(f)). , determine which data has been instructed to create new data (step 34
02).

At this time, if the instructed data is data to be created as an internal area, area setting for the next area and area attribute setting are performed (step 3403).

Then, an area management block is generated based on one or more pieces of information (step 3403), and the area editing unit 562 shown in FIG. 1 is activated (step 3405). In addition, the area editing department 56
The second startup process will be described later.

In addition, in the blow shown in Fig. 21, if the instruction from the operator is an instruction to update the already created area (step 3007 in Fig. 21), the operation in Fig. 28 is performed as shown in Fig. 22 (g). Step 3411 in FIG. 22(g) to obtain the number of the area registered in the target area table.
Based on the number and the data type of the area management block, the program number is obtained from the SFMT in FIG. 27 (step 3412), and the corresponding area editing section 562 is activated as a task (step 3413).

Note that when the area editing section 562 is activated.

First, based on the obtained program number, 1 document editing section 561
requests the system control unit 53 to generate a task (step 3451 in FIG. 22(h)).

The task number returned as a result and the number of the corresponding area are stored in the startup editing task management table (hereinafter referred to as ETMT).
) (step 3452).

ETMT has task number 568 as shown in FIG.
8 and area number 5689 as a pair, and also has the number of activated tasks 5687 indicating how many area editing units are currently activated. Then, set the status of the area management block to 0 to indicate that the corresponding area is being edited.
to 1 (step 3453 in FIG. 22(h)
). After the above processing, the document editing unit 561 in FIG. 1 requests the system control unit 53 to start the task (second
Step 3454 in FIG. 2(h)), and a message is sent to the area editing section that starts the startup parameters (step 3455).

At that time, as the startup parameters, the startup mode indicating whether to create a new area or update the area, the task number of the document editing section 561, the task number of the startup area editing section, and, in the case of new creation, the size of the area are transmitted.

Other editing operations 1 For example, if an instruction is given to move or delete an area, or insert or add a page, perform the corresponding processing (steps 3008 to 3011 in Figure 21) and wait for the next operator's instruction. (Step 3002).

Now, the instruction from the operator is instruction 1 to switch the display page.
For example, if the instruction is for the previous page or the second page (step 3012), the layout of each corresponding page is redisplayed in the window. This will be explained in more detail.

In displaying this layout, first the paper frame, header, footer, etc. are displayed based on the document data described above (steps 3501 and 3502 in FIG. 22(i)), and then the area set within the page is displayed. are displayed in order from the area with the lowest priority (first area within the page) (step 350).
3-3513 and 3514). Therefore, when displaying this area, the area is first displayed (step 3).
504), Next, it is determined whether an editing program exists for the data in the area based on the data type number in the area management block and the SFMT (Step 3505); if no editing program exists, the area The status of the management block is changed to 2 (step 3511), and the area is displayed completely black to inform the operator that there is no editing program for the area in the system (step 35).
12).

In addition, if there is one editing program in the above, then it is determined whether the attribute for the area is transparent or not (step 3506), and if the attribute for the area is opaque, after clearing the area once, (Step 35
07) Display data within the area (step 3508)
Further, after displaying the area, it is determined whether the area is being edited (1 or not) based on the status information for the area (step 3509). If the area is being edited, In order to inform the operator of this fact, the entire area is displayed with shading (step 3510).

Thereafter, similar processing is performed for all areas existing within the page to be displayed (steps 3513 and 3514).

In addition, the process (step 3013 in FIG. 21) for the case of activation input by window switching operation, which will be described later, will be described later.

Further, when an instruction to end is given, editing of one document is ended, and the details of this processing (step 3015 in FIG. 21) will be described later.

Now, in the above processing, when the document editing section 561 requests activation of the area editing section 562, for example, the graphic data editing section due to new creation or updating of a region, the system control section 53, in accordance with this request, creates a new graphic data. Start the data editing department as a task. Here, the processing contents of the graphic data editing section will be explained based on the processing flow shown in FIG. 30.

In FIG. 30, first, the graphic data editing section.

Step 4: Receive startup parameters via message
001), determine whether the startup mode is new creation or area update (step 4002), and.

If the startup mode is new creation, the data is initialized (step 4003), and if it is update, the data to be updated is called from the storage unit 3 in FIG. 3 (step 4004), and the window is (Step 4005), and display the graphic data in the window (Step 4006). At this time, the size of the window is set to correspond to the size of the area, and part of the title of the window is document editing department 561
Add the same task number as. By adopting the above configuration, when multiple documents are being edited at the same time, and several areas within each document are being edited, which area corresponds to which document can be determined as shown in Figure 32. It can be easily identified by the task number 254 displayed as part of the window title, as shown in FIG. Also, at this time, the display state of the screen is as shown in Figure 31 (b
).Now, from now on, the first graphic data Ig collection is as follows.

In the set window, graphic data is created and edited according to instructions from the operator (steps 4007 to 4009). In addition, the graphic data editing department is
When the operator instructs to finish editing within the area 1. Store the created graphic data in the storage unit 3 shown in Figure 1.
Step 4010) in the figure, the window is closed (Step 4011), and a region editing completion message is sent to the document editing section 561 that is the startup source (Step 4012).

The task is ended (step 4013), and this end message includes an end code indicating the end of editing in the area so that the started document editing unit 561 can determine which area editing has ended. Set the task number of the figure editing department itself.

As described above, the entire document and each area are created, I
Next, we will explain how to switch the editing section using window operations and the processing contents in Part 3.
This will be explained using FIG. 1 and FIG. 17.

First, as shown in FIGS. 31(b) and 31(C), when switching to document layout editing while editing one graphic area, the window of one document editing section 561 Move the mouse cursor 30 in FIG. 2 upwards and press the mouse execution button 3 indicated by reference numeral 31 in FIG.
11 is pressed, it is determined that it is outside the window of the figure editing section, and this input is sent to the window management section 5 instead of the figure editing section.
2, the window management unit 52 determines that the window of the document editing unit 561 has been designated based on the position designated by the mouse 31 and further from the window management table 521 in FIG. 7 (step 1521 in FIG. 17). The task using the window that was at the top until now, that is, the figure editing section, is temporarily suspended (step 1522).
, and saves the display image of the topmost window to the display buffer (step I 523). Then, the window of the newly instructed document editing section is displayed at the top (step 1524), the stacking order of the window management blocks is updated (step 1525), and the window is displayed for the document editing section 561 that newly restarts the process. Step 1526) returns an activation code to the task using the window in order to notify that the task has been switched, and the task using this window, that is, the document editing unit 5
61 is restarted (step 1527).

In addition, if the editing department is interrupted or restarted, the system control section 5
3. The following is based on the flowcharts in FIGS. 12(e) and 12(f).

The processing of suspending and resuming the editing department will be explained.

When a task interruption request occurs, the system control unit 53 in FIG.
Please set the interrupt flag (see reference numeral 532 in the figure).
Step 1141 in Figure 2(e)), the task is REA
Step 1142) to determine whether it is in the DY state;
If the task is in the READY state, the corresponding TCB 532 is removed from the READY queue 533 in FIG. 9, and the task dispatcher 1013 in FIG.
Prevent PU from being allocated (step 1143)
).

In response to a task restart request, the first
Step 1151 in Figure 2(f)), the task is REA
Step 1152) to determine whether it is in the DY state;
If the task is in READY state, the corresponding T
Connect CB to READY queue 533 (Step 1
153).

If the interrupt flag of TCB532 is set,
The task dispatcher 1013 does not activate the task and removes it from the READY queue 533.

Furthermore, if the basic area is updated from the state shown in FIG. 31(c), the screen changes as shown in FIG. 31(d). In this state, each editing section can be switched between text, graphics, and layout using the same operation method as described above.

It can be done arbitrarily. For example, when switching between area editing sections, that is, from text to graphics, the display state of the screen becomes as shown in FIG. 31 (6).

Now, when the window is switched as described above, the activation code is returned as input to the task restarted from the window management section. conduct(
Figure 22 (j) and (k)).

That is, first, it is determined from the document data whether or not the area being edited exists within the currently displayed page (step 3601 in FIG. 22(j)), and the area being edited exists within the currently displayed page. If the area being edited does not exist in the currently displayed page, set the display flag to O (step 3603), and after processing the message below, redisplay the layout. I do. Next, a message reception request is made to the system control unit 53 in FIG. 1 (step 3604), and if there is a message (
Step 3605), and the next process as termination processing of the corresponding area editing section is performed (Step 3606). That is, first, the task number of the area editing unit stored in the message and the area number are obtained from the ETMT (Fig. 29) (step 3651 in Fig. 22(k)), and the status of the corresponding area management block is checked. 3652), and the information regarding the task is deleted from the ETMT in FIG. 29 (Step 3653).

Finally, delete the task itself (step 36
54), Now, in step 3605 of FIG. 22(j), if there are no more messages, the display flag is set to 1.
Step 3607
), if the display flag is set to 1, the layout of the page is redisplayed (step 3608).

Regarding the termination process in the one-document editing unit 561,
This will be explained using FIG. 22 (I2) and FIG. 12 (g).

If the operator instructs you to terminate, please follow the above E.
Step 3 in Figure 22 (Q) to determine whether there is an active editing task in the TMT (Figure 29).
702), if there is an active editing task, the second
After acquiring the task number and area number from the ETMT in Figure 9 (Step 3703) and resetting the status of the area to O (Step 3704), a request for forced termination of the task is made to the system control unit 53 in Figure 1. (Step 3705), in accordance with this request, the system control unit 5
Step 3 first releases the resources used by the specified task (step 1161 in FIG. 12(g)), requests the window manager to perform forced termination processing (step 1162),
In window management, the same process as the close process shown in FIG. 16 is performed, and the corresponding TCB (numeral 532 in FIG. 8) is connected to the READY queue 533 in FIG. 9 based on the specified task number. If so, this T
Remove CB 532 from READY queue 533 and
The state of B is set to the DORMANT state (step 11%3).

After the above forced termination process, the document editing unit 561 deletes the task (step 3706 in FIG. 22(Q)).

Then, the process is repeated for the editing tasks that are running (step 3707), and when all the running tasks have been forcibly terminated, one document data is registered.Step 37
08), the Bunn V editorial department closes the window it had opened itself (step 3709), sends a message to the system management department 57 in Figure 1 to the effect that the process has been completed (step 3710), and ends the task. In step 3711), in this way, when a termination request is made to the document editing section 561, the area editing sections that are being edited can be terminated all at once.

〔Effect of the invention〕

The present invention is as described above, and as is clear from the description of the illustrated embodiment, according to the present invention, when editing the entire document, if there is an area currently being edited, the operator can edit the area currently being edited. There is no need to terminate the areas being edited one by one, and the editing process for those areas can also be forcibly terminated.

Therefore, the operability of the document creation device at the end of document editing can be improved.

[Brief explanation of the drawing]

The drawings show an embodiment of the present invention, FIG. 1 is a block diagram showing the overall configuration of a document creation device according to the present invention, FIG. 2 is a diagram showing an example of a screen display, and FIG. 3 is a configuration of mouse buttons. Figure 4 is a configuration diagram of the icon management table, Figure 5 is a configuration diagram of the program control table, Figure 6 is a configuration diagram of the data name definition table, and Figure 7 is a configuration diagram of the window management table. 11 is a diagram showing the contents of the message reception queue, FIG. 12 is a processing system diagram of the system control unit, FIG. 12(a) is a processing system diagram for task generation, and FIG. 12(b) is a diagram showing the contents of the message reception queue. 12(c) is a processing system diagram for task deletion, FIG. 12(c) is a processing system diagram for task activation, FIG. 12(d) is a processing system diagram for task termination, and FIG.
) is a processing system diagram for task interruption, Figure 12(f) is a processing system diagram for task restart, Figure 12(g) is a processing system diagram for forced termination of a task, and Figure 12(h) is a processing system for sending a message. Figure 12(i) is a message reception processing system diagram,
FIG. 12(j) is a processing system diagram of the task dispatcher,
Fig. 13 is a processing system diagram of the input control unit, Fig. 14 is a configuration diagram of the menu management table and pull-down menu table, Fig. 15 is a processing system diagram of window opening, and Fig. 16 is a processing system diagram of window closing. Figure 17 is a processing system diagram for window switching, Figure 18 is a processing system diagram for the system management section, Figure 19 is a processing system diagram for the file editing section, Figure 20 is a configuration diagram of the operation target document table, and Figure 21 is a diagram of the processing system for the file editing section. 22(a) is a diagram showing the initial processing system of the document editing section, and FIG. 22(b) is a diagram showing the processing system for creating the support area management table during the initial processing of the document editing section. 22(a) is a diagram showing the area designation processing system of the document editing department, FIG. 22(d) is a diagram showing the designation cancellation processing system of the document editing department, and FIG. Figure 22(f) is a diagram showing the valid/invalid state switching processing system of the pull-down menu in the eastern region, Figure 22(f) is a diagram showing the area new creation processing system of the document editing department, and Figure 22(g) is the area update processing system of the document editing department. Figure 22 (h) is a diagram showing the startup processing system of the area editing unit during area new creation and area update processing in the document editing unit, and Figure 22 (i) is a diagram showing the layout display processing system of the document editing unit. FIG. 22(j) is a diagram showing the 7 activation processing system of the document editing section, FIG. 22(k) is a diagram showing the region editing section termination processing system during activation processing of the document editing section, and FIG. Figure (fl) is a diagram showing the editing completion processing system of the document editing section. Figure 23 is a configuration diagram of the menu table in the document editing section, Figure 24 is a configuration diagram of document data, Figure 25 is a diagram showing the configuration contents of a page, and Figure 26 is a diagram showing the number of areas specified as operation targets and execution. Figure 27 is a diagram showing the relationship with possible supervisory area editing operations, Figure 27 is a configuration diagram of the support area editing department management table, Figure 28 is a configuration diagram of the operation target area table, and Figure 29 is a configuration diagram of the startup editing task management table. , FIG. 30 is a processing system diagram of the graphic data editing section, FIG. 31 is a diagram showing an example of screen changes during document editing operations, and FIG. 32 is a specific example of identifying a specific area from the screen display during document editing. FIG. 1... Input section, 2... Display section, 3... Storage section, 4
...Printing section, 5...Control section, 51...Input control section, 52...Window management section, 53...System control section, 54...Print control section, 55...Display control unit,
56...Editorial department. 561... Document editing department, 562... Area editing department, 5
7...System management department, 58...File editing department.

Claims (1)

[Claims] 1. Targeting documents in which multiple types of written elements are mixed, an input section for inputting written elements to be written in the document for each area;
a storage unit that stores description elements input into the input unit;
a display section for displaying various description elements stored in the storage means; an area editing section for creating and editing data in each area; and a page layout of the created document displayed on the display section, and according to this display. A document creation device comprising: a document editing section that edits each region and starts an area editing section for an area for which creation or updating is instructed; and an editing section switching means that switches editing by each of the editing sections. a startup area editing unit management means for managing the area editing unit that has been started; and an area editing unit forced termination unit for forcibly terminating the activated area editing unit when an operator instructs to finish document editing. A document creation device characterized by being equipped in a department.