JPH022452A - Document forming device - Google Patents

Abstract

PURPOSE:To make it unnecessary to store all of plural kinds of user character information in a storage part by recovering only the user character information used by respective edition parts to a storage area of the storage part to be used by a display control part at the time of switching the edition parts. CONSTITUTION:The edition part 56 executes the formation and edition of a document and a user character control part 59 executes the formation or the like of user characters. The edition part 56 is constituted of a document edition part 561 and an area edition part 562. At the time of switching the edition part (window), only the user character information to be used for respective edition parts (windows) is recovered to the storage area of the storage part 3 used for the display control part 55.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a document creation device, and particularly to a document creation device that creates documents by mixing different types of data such as Japanese and English characters, graphs, and figures. 9. Regarding a document creation device for editing.

[Conventional technology]

In recent years, document creation devices such as word processors handle not only character (text) data, but also figures and graphs.

There are more and more types, such as tables and images. In addition, creating a document containing a mixture of these multiple data9
As described in JP-A-61-18036, the editing method is to specify the area where the data to be edited is stored on the page layout of the created document, and then add detailed information for that area to the above page layout. The method used was to display and edit the screen in separate areas.

[Problem to be solved by the invention]

The above conventional technology allows users to edit another area while editing a certain area, or refer to the layout of a page other than the page where that area exists while editing a certain area. Therefore, if you need to perform the above operations, you must first finish editing the area you are currently creating, or edit the document you are currently creating. After printing the document, it is necessary to resume editing the area while referring to the document, which poses a problem in that document creation efficiency decreases.

Therefore, when creating a document containing a mixture of multiple data,
Document creation efficiency is improved by providing a document creation device that can switch to other editing operations without having to complete the creation and editing of various data, editing of areas on layout display, switching of display parts, etc. can be improved. However, when editing documents and areas, if user characters, which are common resources of character systems, are used in addition to standard prepared characters such as JIS Level 1 and Level 2, when handling multiple characters such as Japanese and English, each There has been a problem in that an enormous amount of storage (memory) capacity is required in order to constantly store all of the different types of user character information used by the editorial department in the storage section.

An object of the present invention is to provide an inexpensive document creation device by controlling the plurality of types of user character information with a smaller memory capacity.

[Means to solve the problem]

The above-mentioned problems include: an input section for inputting description elements to be written in a document for each area; a storage section for storing input description elements; and a display section for displaying various description elements stored in the storage section. An area editing department that creates and edits data in each area,
a document editing section that displays the page layout of the created and edited text on the display section, edits the area according to the display, and starts the area editing section for the area that is instructed to be created or updated; Window display control means for controlling display of the contents of the editing section and the area editing section in separate display areas, editing switching means for switching editing by the document editing section and the area editing section, and creation of user characters. In the document creation device, the document creation device has a user character creation means that performs operations including: a registration means that registers and updates user characters based on user character management information that manages the user characters; and a user character that is used by the window display control means. A notification registration means for notifying and registering a type, and a user character recovery means for recovering user character information of a window switched based on the user character type and the user character management information when the editing section is switched by the editing switching means. This problem is solved by a document production device.

[Effect]

The registration means registers the user characters in the storage unit, and updates the registered user character information and user character management information when an update is requested, and the notification registration means registers the user characters used in each window. The type is stored in the storage unit, the user character type is used as a parameter, and the user character to be used is notified to the window display means. The user character information is restored to the storage area of the storage unit used by the window display control means. Due to this recovery action, it is not necessary to always store all the plural types of user character information in the storage area of the storage section used by the window display control means.

〔Example〕

Embodiments of the Japanese word processor according to the present invention will be described below with reference to FIGS. 1 to 34.

FIG. 1 is a block diagram showing the configuration of an embodiment of a Japanese word processor, in which 19 characters and 9 figures are input using a keyboard for inputting characters, a pointing device such as a mouse for indicating operation targets, function names, etc. 2. A display section such as a CRT display that displays the following information. RAM3
1. Fixed disk device 32 and floppy disk device 33
A fixed disk device 32 stores document editing programs, area editing programs, etc., which will be described later, and the programs are transferred to the RAM when necessary.
31 and executed. Further, the floppy disk device 33 is used to add the program to the fixed disk device 32 and to store the contents of created documents. The printing unit 4 uses a wire dot printer or the like.

The control section 5 including a microprocessor or the like for controlling each of the above-mentioned sections includes an input control section 51. Window management section 52
．． System control unit 53. Print control section 54, display control section 5
52 Editorial Department 56. System management department 57. File editing department 58. It is composed of a user character management section 59.

In this embodiment, document creation and editing are performed by the editing department 5.
6, and the 1 editing section 56 further performs the document editing section 561.6.
The area editing section 562 is composed of two parts. Also,
Creation of user characters is performed by the user character management section 59.

A screen 21 showing the screen displayed on the display unit 2 in FIG. 2 is a menu area 22. It consists of an IW collection area 23° and an icon area 24. Each editing department has its own rectangular frame 25 (hereinafter referred to as a window) in the editing area 23.
The types of windows that display data within a window and edit document data individually within that window are:
There are mask windows used to perform main tasks, sub-windows used to perform auxiliary tasks, and alarm windows used to display messages to warn users.

In the menu area 22, there are function classification names 26 (
When the operator points to the pull-down menu name 26 with the mouse, a window is set (hereinafter referred to as opening the window), and a detailed function item list 28 is displayed inside. (Hereafter referred to as a pull-down menu). For example, as shown in FIG. 2, pull-down menu names 26 such as edit and print are displayed in the menu area 22, and when the operator instructs editing using the mouse, a pull-down menu 28 opens and function items such as new creation and update are displayed. is displayed. In this state, when the operator specifies a function item with the mouse, the specified function will be executed. The window 25 includes a caption area 251 . . . that displays a window name, for example. Data area 252 for displaying data. It consists of a control area 253 for the operator to instruct operations such as closing, moving, and changing the size of the window. In the icon area 24, pictograms (hereinafter referred to as icons) 27 representing each program of the editing department, etc. are displayed, and when an icon is selected by the operator, the corresponding program is activated.

FIG. 3 shows a mouse 31, which is composed of 1 an execution button 3112 for selecting an operation object, a function, etc., and a cancel button 312 for canceling the selected operation object. The mouse cursor 30 moves within the screen 21 following the movement of the mouse 31 by the operator, and is used to indicate an operation target within the screen 21.

Each part constituting the control section 5 will be explained below.

The system management unit 57 starts programs such as the file editing unit 582 and the document editing unit 561, which correspond to the icons notified from the input control unit 51. The correspondence between icons and programs is managed by the icon management table shown in Table 1, and the icon management table in Table 1 stores icon numbers and corresponding program numbers. The program number is an identification number assigned to each program, and each program is managed by the program control table 572 shown in FIG.

As shown in Table 1, the Data Name Definition Table (hereinafter referred to as DNDT)
(abbreviated as). Therefore, the data name is processed as an attribute based on the data number.

Table 2 Data Number Data Name The program control table 572 arranges program control programs 573 (hereinafter abbreviated as PCB) in order of program number. The PCB 573 contains program start address information 5731 and stack address information 573.
2. Priority information 5733.

Parent program number 5734. Data type 5735 and other program attributes 5736 are stored.

The parent program number 5734 indicates from which program the program is started.

The data type 5735 indicates what kind of data the program handles, such as text or graphics, and a data number is preferably stored.

Further, the data name corresponding to the data number is the second file.The second file editing section 58 displays a list of documents stored in the storage section 3 in a window, and edits the specified document.

Here, editing one document is a general term for updating, deleting, printing, etc. of a document.

The document editing section 561 displays in a window the layout of the relevant part of the document that the file editing section 58 has instructed to create or update, and edits the purchase area. Here, editing an area means creating new element data within the area, instructing updates, and also deleting and moving.

It is a general term for things such as copying.

The area editing unit 562 instructs in the window the contents of the area for which new creation or updating has been instructed in the 1-document editing unit 561, and performs creation and editing of data within the area. The area editing section 562 includes various editing sections depending on the type of data. That is, the text data editing section, the graph data editing section 9
This includes the concave data editing department.

Among the various editing sections mentioned above, the executable editing section after the start of document creation is always the editing section in the topmost window on the screen.

Furthermore, in order to bring the window to the top, that is, to switch the editing section, move the mouse cursor 30 onto the displayed window and press the execution button 311. This specified change in the stacking order of windows is performed by the window management unit 52.

In addition to changing the stacking order of windows, the window management section 52 also opens and refrozes windows on the screen in accordance with requests from each editing section. In addition, windows are given priorities, and when open requests conflict, control is performed so that a window with a higher priority is opened preferentially. The alarm window has the highest priority, followed by the sub window and then the mask window. Windows opened on the screen are managed by a window management table 521 shown in FIG. 5(a).

The window management table 521 has window management blocks 522 (hereinafter abbreviated as WCB) arranged in order of window number. The WCB 522 stores the following information.

1) Window setting position and size information 5221 screen 2
The upper left X coordinate, Y coordinate, lower right X coordinate, and Y coordinate of the window when the origin is the upper left of window 1 are stored.

2) Window overlapping order information 5222 When multiple windows are opened on the screen, information indicating the order in which they overlap is stored.

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

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

Each editing section is generated as one task, and a task number is given by the system control section 53 described below when the editing section is generated as a task.

5) 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 there. The window display image storage location 5225 stores the location of the corresponding window display buffer, and the information is used to recover the display image of the portion hidden under the window when changing the stacking order of the windows.

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

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

8) Window type information 5228 Stores information that identifies whether the window is a mask window, subwindow, or alarm window.

9) Input state information 522g Stores the character input mode etc. when the window is opened at the top level. Character input modes include Mincho mode, Gothic mode, etc. depending on the font, and full-width mode, half-width mode, etc. depending on the font size. These modes can be switched, for example, by selecting from a dedicated key or menu.

10) User character type 5230 Stores the user character type used in the relevant window.

The window management unit 52 changes the stacking order of windows, opens and closes them, etc. based on the above information. Then, when changing the stacking order, the window management section 52 sends a message to the system control section 53.

The above task number 52 interrupts the editing that was being edited and restarts the editing section of the specified window.
24 to the system control unit 53. In addition, when window open requests conflict, control is performed based on the window priority order such that a request with a lower priority is made to wait until a higher window is closed. This waiting control is performed by connecting or disconnecting the requested task to the open queue 523, ie, a task control block to be described later, as shown in FIG. 5(b). Furthermore, the input control unit 5 is configured to display a menu corresponding to the window that becomes the highest level by operating the window according to the menu data storage position 5226.
1, requests the input control section 51 to recover the input state information according to the input state information 5229, and requests the display control section 55 to recover the user character data according to the user character type 523o.

The system control unit 53 suspends the corresponding task based on the request from the window management unit 52.

Controls restart, etc. In addition, the system control unit 53 generates a corresponding editorial department as a task based on a request from each editorial department, starts a task corresponding to a corresponding editorial department based on a startup request from each editorial department, and 1 Based on the termination request from the editorial department, the task corresponding to the relevant editorial department is terminated. Furthermore, in order to enable information exchange between tasks, the system control unit 53 transmits messages to the corresponding editorial department based on requests from each editorial department, and sends messages sent from the corresponding editorial department. Perform the process of receiving. Each task is managed by a table called a task control table 531 shown in FIG.
(abbreviated as B) arranged in order of task number,
One TCB 532 is assigned to one task.

The TCB 532 stores, for example, all information necessary for starting and resuming a task as shown below.

1) Link field 5321 Used when connecting TCB 532 to a list.

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

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

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

5) Suspension plug information 5325 Information indicating that a task suspension request has been made is stored.

6) Task start and restart address information 5326 Stores the start address of the task or the address at the time of interruption.

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

8) CPU state information 5328 Saves all register contents at the time the task was interrupted.

Here, the status of the task is as shown below, for example.

b) N0NEXISTENT state Indicates that the program does not exist as a task. At this time, the task number corresponding to the TCB becomes unused.

(Example) DORMANT state indicates that the program exists as a task, but its execution is prohibited.

c) READY state Indicates a state in which a program can be executed when a CPU is assigned to a task. The part that assigns tasks to CPUs is called a task dispatcher.

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

e) WAITING state indicates a state where the execution of a task is suspended until a certain event occurs 0 For example, waiting for a message to be received until a message is sent, or input/output that is waited until the input/output is completed. Waiting for completion etc.

As shown in FIG. 7, tasks in the READY state are managed, for example, by connecting the corresponding TCBs 532 to one list in order of priority, and this list is called a READY queue. The header 533 of the READY queue contains the TCB 53 corresponding to the task in the READY state with the highest priority.
The link field 5321 of the TCB 532 stores a pointer to the TCB 532 corresponding to the task with the next highest priority.
The TCBs 532 are connected by pointers in order of priority, and the link field of the last TCB 532 stores information indicating that it is the last TCB 532 in the list. The task/device batcher is connected to the READY queue.
The task corresponding to the one with the highest priority among the CBs 532 is assigned to the CPU and executed.

For example, a task in VAITING state is
The TCB 532 is connected and managed to a list prepared for each cause according to the cause of each waiting, and when the waiting is canceled due to the occurrence of a certain event, the TCB 532 is removed from the corresponding list and the RE
It is connected to the ADY queue 533, and the task is resumed from the interrupted position by the task dispatcher.

Messages are managed by a message control table 534, as shown in FIG. 8, and the message control table 534 is an arrangement of message control blocks 535 (hereinafter abbreviated as MCB), one MCB 535 for one message. will be assigned. MCB53
5 includes, for example, a status 5351 indicating whether the MCB 535 is used, and a sending task number 5.
352, receiving side task number 5353. Message size 5354. A message buffer 5355 that temporarily holds transmitted messages is stored. Also, according to the parameters at the time of a message reception request, when a message reception request is made and the message has not yet been sent from the other task, the TCB 532 corresponding to the task that requested reception is removed from the READY queue 533.
It is also possible to connect to the message reception queue 536 shown in the figure and put the task in the WAITING state until the message is sent, or the task that requested reception can be
It is also possible to simply notify the task that the message has not been sent without setting it to the lAITING state. Here, the overall processing flow of the system control section 53 will be shown using FIG. When a processing request is issued from a task to the system control unit 53, first, in step 1001, the execution environment at the time when the task issued the request is saved in the TCB 532. Next, the requested functions in steps 1003 to 1008 are identified, and in step 1002, processing corresponding to each function is activated. After completing the processing corresponding to each function, step 1011
It is determined whether or not the task is to be switched based on the state of the READY queue 533, for example, and if the task has been switched, the task dispatcher 1013 is activated. If not, the execution environment saved in step 1001 is saved in step 1012.
The task then recovers from the TCB 532 and restarts the task that issued the request. Furthermore, when an input/output end interrupt occurs from an input/output device, the execution environment at the time of occurrence of the interrupt is saved in the TCB 532 in step 1009. Next, for example, the input character code etc. is passed to the input request task, and step 10
After performing input/output termination processing such as releasing the input task from waiting in step 10, the task dispatcher 1013 is activated. The task dispatcher 1013 is shown in FIG.
As shown in j), it is determined in step 1191 whether the TCB is connected to the READY queue, and if it is not connected in step 1197, an infinite loop is performed until an interrupt occurs, and if it is connected, step 11
At step 92, the TCB 532 with the highest priority is acquired from the pointer stored in the header 533 of the READY queue, and it is determined from the suspension flag information 5325 of the TCB 532 whether there is a suspension request for the task. If there is an interruption request, the pointer is updated in step 1193 and the corresponding T
The CB 532 is removed from the READY queue, and the process starts again from step 1191. If there is no interruption request, the TCB 532 is set to ACTIVE in step 1194, the execution environment is recovered from the TCB 532 in step 1195, and the corresponding task is started in step 1196. Let it restart.

The functions required for the system control unit 53 are 1.
For example, the task generation/deletion process (step 1003), the task start/end process (step 100) in FIG.
4), task forced termination processing (step 1005), task suspension/resumption processing (step 1006), message sending/receiving function between tasks (step 1007),
There is input/output request processing (step 1008), and step 1008 of the input/output request processing accepts an input/output request from a task to a keyboard, display device, etc., and puts the requested task in a WAITING state until the input/output is completed. R the task in the 1dAITING state at the end of input/output.
or transition to the EADY state. Other processing flows are shown in FIGS. 10(a) to 10(i). Note that details of each flow will be described later.

The input control unit 51 passes character codes input from the keyboard and coordinate values input from the mouse to the task,
According to the area on the screen 21 designated by the mouse, notification of the designated icon to the system management unit 57, notification of the designated menu task, and window management unit 5 are performed.
2 to request switching of the specified window.

As shown in FIG. 11, first, in step 13o1, input data from the input unit 1 is analyzed to determine whether or not the input is from a mouse. If the input is not from the mouse, the input is from the keyboard, and in step 1311 the character code corresponding to the pressed key is acquired, and in step 1312 the acquired character code is passed upon the input request. for example,
When the operator presses the character key for "A" on the keyboard, the character code for "A" is passed to the task that requested input. If it is determined in step 1301 that the input was from a mouse, coordinates are determined in step 1302 to find out which location on the screen the operator has indicated, and in step 1301 the mouse cursor 30 is displayed at the mouse movement position. do.

As a result of step 1302, if the operator's instruction is inside a window that is not at the top level, step 1304 determines that it is a window switching instruction, and step 1316 requests the window management unit 52 to switch the window.

If it is determined in step 1305 that the operator's instruction is for the icon area 24, step 1313
In step 1314, it is determined which icon has been designated, and after acquiring the icon number, the acquired icon number is notified to the system management unit 57 in step 1314. Furthermore, the system management unit 57 determines the program corresponding to the notified icon from the icon management table 571, generates the program as a task, and instructs the system control unit 53 to generate and activate the task. request. In addition, in the case of an instruction to operate within the topmost window in step 1306, the instruction coordinate values are converted from on-screen coordinates to relative coordinate values within the window in step 1317, and then in step 1318. Pass the coordinate values to the task that requested input. If the operator's instruction is for the menu area 22 in step 1307, a request is made to the window management unit 52 to open a pull-down menu in step 1315. Further, if the operator's instruction is in the pull-down menu area 28 in step 1308, it is determined which function item was instructed, and in step 1319, the instructed function item number and pull-down menu number are passed to the task that requested the input. . Step 13
At 09, the operator's instructions are displayed in control area 2 in the window.
53 or the caption area 251, a code for closing, scrolling, etc. is passed to the task that requested the input in step 1310. If other areas are specified, do nothing. Further, in the above case, when passing the code to the input requesting task, the system control unit 53 causes the task that requested the input to transition from the VAITING state to the READY state.

The menu is stored in the menu management table 52 shown in FIG.
3. Managed by pull-down menu management table 525. In the menu management table 523, the number of pull-down menus 5231 is stored, followed by the menu management block 524, which stores the number of pull-down menus in numerical order. The menu management block 524 includes
Pull-down menu name 5241, maximum number of characters for function item 5242. Number of function items: 5243. A pointer 5244 to the pull-down menu management table 525 is stored. In addition, the pull-down menu management table 525 includes
Function item name 5251. Valid/invalid flags 5252 indicating whether a functional item is valid or not are stored in the order of functional item number for the number of functional items.

Based on the above information, the input control unit 51 displays the pull-down name of the topmost window in the menu area 22 when a window is opened or switched when there is a request from the window management. Further, if a pull-down name is specified by the mouse, the function item name is acquired from the corresponding pull-down menu management table 525, and if the function item is valid, it is displayed normally, and if it is invalid, it is displayed in half-brightness in the pull-down menu area 28. to be displayed.

The print control section 54 is for controlling the printing section 4 based on a document printing request from the editing section 56 .

The display control section 55 includes an editing section 56 and a window management section 5.
In response to a display request from 2, the window management block 52
This is for writing display data of only the portion that can be developed in the topmost window based on the overlapping order information of No. 2 into the memory for displaying on the display section 2 in units of dots. In addition, the display control unit 55 has a function of registering a plurality of user characters, which are system common resources, in addition to standard prepared characters such as JIS 1st level and 2nd level, and a function of displaying the user characters. Furthermore, it has a function of storing user character types used for each window.

When registering the user characters, the user character management section 59
The display controller 5 uses the user character type and user character location as parameters when the device is powered on or when a change occurs in the content of the user character such as when creating or updating a new user character.
5 to request registration. The display control unit 55 controls user character registration using the user character management table.
First, an example of the configuration of the user character management table is shown in Figure 31 (a
). The user character management table 551 stores the information shown below.

1) Memory registered character type 5511 Stores the user character type stored inside the display control unit 55.

(Nos not registered, N1: type, Nz: type 2...) 2) Registered character type 5512 Stores the user character type for which user character registration has been instructed. (No: Not registered, N1: Type, N2: Type 2...
3) Registered character location 5513 Stores the location of user character data for which user character registration has been instructed. The location of the user character data is
Fixed disk device 32 or RAM 31 of the registration request source
It shows the location of etc.

Next, an example of the structure of user character data will be explained with reference to FIG. 31(b). The following information is stored in the user character data 552.

1) Number of registered characters: 5521 Stores the number of characters to be registered.

2) Character size information 5522 Stores the character size of the character to be registered (for example, 16×16 dots or 24×24 dots, etc.).

3) User character code 5523 Stores the character code of the user character. For example, when requesting character display using JIS code, etc., consecutive unused codes of the JIS code, A to A, are assigned as user character codes.

4) User character pattern data 5524 Stores information such as a dot image of the user character corresponding to the user character code 5523 above.

FIG. 32 shows the initial state of the user character management table and an example of registration of registered character types, and FIG.
12 is in an unregistered state, and registered character location 5513
is in an undefined state.

FIG. 32(b) shows that N1 is registered in the registered character type 5512, and FIG. 32(c) shows that N1 is registered in the registered character type 5512.
2 is registered, and in both cases the registered character type is 55.
12 corresponds to the registered character location 5513 and is stored in the memory as user character data 552.

Here, the user character registration process of the display control unit 55 is performed in a third manner.
This will be explained based on Figure 3. First, the user character type requested to be registered in step 6001 is compared with the memory registered character type 5511 currently stored in the display control unit 55, and if they match, the user character data requested to be registered in step 6002 is Display control unit 5 from the area of the location
5 Transfer internally.

Next, in step 6003, the user character type of the registration request source is compared with the user character type 5512 in the user character management table 551, and if the types match or the number is
Find the location 5512.5 in step 6004.
513 stores the type and location of the registration request source. If the type to be registered in step 6o01 is different from the type currently stored in the memory.

(2) When the editing section 56 requires a user character, it is notified of the user character type 5230 to be used, so that it is stored in the memory in the display control section 55 at that timing.

■ The user characters of other editing sections 56 that are currently operating are destroyed. Therefore, the process of step 6003 is performed without transferring the character data of the registration request to the memory.

When using the user characters, the editing section 56 notifies the display control section 55 of the use of the user characters, using the user character type to be used as a parameter. The processing contents of the display control section 55 will be explained based on FIG. 34.

First, in step 6101, the requested user character type is stored in the user character type 5230 of the requesting WCB 522, and in step 6102, it is determined whether the corresponding window is at the top. If it is at the top, step 6103
The requested user character type is compared with the memory registered character type 5511, and if they do not match, the registered character type 5512 in the user character management table 551 is searched for in step 6104, and the matched W9 character type 5512 is matched in step 6105. Information on the area displayed in Registered Character Location [5513 is transferred to the inside of the display control unit 55. In step 6102, only the top-level window can be displayed, and when that window becomes the top-level window, necessary information may be transferred to the memory. Therefore, if the window is not at the top level, the process ends as is.

Furthermore, if the requested type and the type on the memory match in step 6103, it means that the user character pattern is stored in the memory in the latest state, so the process ends without transferring the contents of the used characters to the memory. . In this case, there is no particular problem if the data is transferred, but it is just a waste of time.

Next, when displaying user characters, the display is performed using user character data inside the display control unit 55.

For example, when displaying the user character code Am, the character size information 5522 is used to calculate the position of the next user character code 5523, the number of registered characters 5221 is compared with the display requested character code, and the user character code that matches - 5
User character pattern data 5524 paired with 523 is displayed. Note that if there is no matching user character code, a character pattern representing an unregistered character is displayed.

Further, although the process when switching windows (editing section) will be described later, user character data is recovered in the same manner as when notifying user character usage.

Now, document creation and editing in the Japanese word processor of this embodiment is performed as follows.

First, in the initial state, an operator starts creating a new document or editing an already created document by pointing the corresponding icon using the mouse.

In response to this instruction from the operator, the input control unit 51 determines which icon is instructed from the screen instruction coordinates,
The icon number is notified to the system management section 57. on the other hand,
As shown in the flowchart of FIG. 16, in the initial state, the system management section displays an icon in step 1701, requests reception of a message in step 1702, and, if the message is received, identifies the sender of the message in step 17o3. If it is a message from the input control section 51, the program number corresponding to the specified icon is acquired based on the icon management table 571 in step 1704, and the corresponding editing section is assigned a task in step 1705. Generated as.

to start. The generation and activation of this task is as shown in the processing flow of FIGS. 10(a) and 10(c).
In step 1101, when the system management unit 57 requests the system control unit 53 to generate a task based on the program number, the system control unit acquires an unused task number from the task management table based on the request and creates a corresponding TCB.
532 and DORM the task in step 1102.
The task is placed in the ANT state and the acquired task number is returned to the request source in step 1103.

Next, the system management unit 57 issues a task activation request according to the task number, and in step 1121 the system control unit 53 sets the TCB 532 corresponding to the specified task number to READY state, and in step 1122
connects the TCB 532 to the READY queue, thereby making the editor ready for execution.

Further, the above-mentioned notification is performed by sending and receiving messages via the system control unit 53.

For example, as described above, when transmitting a message from the input control section 51 to the system management section 57, first,
In step 1706 in FIG. 16, the input control section 51 requests the system control section 53 to send a message to the system management section 57. Accordingly, the system control unit 53 performs step 1 as shown in FIG. 10(h).
At step 171, it is determined from the message control table whether or not a reception request has been received from the system management section. If a reception request has been received, the transmitted message is transferred to the message buffer of the corresponding MCB 535 at step 1174, and at step 1175, the task waits for reception.

That is, the TCB 532 of the system management section is removed from the message queue and connected to the READY queue. Also,
If there is no reception request yet in step 1171, the system control unit 53 in the system 1172 receives an unused MCB 535.
is acquired, and the message is transferred to the message buffer of the M CB 535 in step 1173.

On the other hand, when the system management section requests the system control section 53 to receive a message, as shown in FIG. If so, in step 1184 the above MCB
535, and transfers the message to the system management section that made the request. In the above, MCB
If there is no message in 535, it is determined in step 1182 whether the task that issued the macro made the request by specifying waiting, and if not waiting, in step 1185 a message is returned to the task in question to the effect that there is no message. The process ends. In addition, if there is a wait, the unused MCB 53 is
5, removes the TCB of the task from the READY queue, connects it to the message reception queue, and transfers control to the dispatcher. Therefore, when a message is transferred to the MCB 535 in response to a message transmission request, the task waiting for reception is connected to the READY queue, so the task is restarted and executed again from the message reception process, and the contents of the MCB 535 (message ) will be accepted by the task.

As a result, if the instruction from the operator is to create a new document, the document editing section 58 will instruct the operator to create a new document, and if the instruction is to edit an already created document, the file editing section 58 will instruct the operator as to which document to edit next. are activated by the system management unit 57, respectively.

Next, the processing contents of the file editing section 58 will be explained based on the flow shown in FIG. 17. In the file editing section 58, first,
A window is opened in step 2001, and a list of documents stored in the storage unit 3 is displayed in the window in step 2002. After displaying, step 2003
Then, the file editing section 58 makes an input request to the input control section 51, and if there is an input, the contents are determined in step 2004. If the input from the operator is an instruction for a document to be operated, determine which document was specified,
In step 2005, the document name is registered in the operation target document table 581 shown in FIG.

Note that the operation target document table 581 has a specified number of documents 58.
11 and designated document name 5812. Also, if the instruction is to update or print in step 2006, update,
The system management unit 57 is notified that the printing instruction has been given, together with the name of the currently designated document and the data type number corresponding to the document, and the document is copied in step 2007.

In the case of an editing instruction such as deletion, processing such as copying or deletion of the document specified as the target is performed; in the case of a scroll instruction in step 2008, a scrolling display of the document name-list is performed; in the case of an end instruction, closes the window in step 20o9, notifies the system management unit 57 that the file editing process has been completed in step 2010, and requests completion of the task in step 2011. Along with this termination request.

As shown in FIG. 10(d), the system control unit 53
In step 1131, DOR the TCB 532 of the requesting task.
The task is placed in the MANT state, and the resources used by the task are released in step 1132. Here, resources include memory and CPU.
refers to

Now, the above-mentioned window opening/closing process is performed by the window management section 52, and the contents of the process will be explained based on the flowcharts of FIGS. 13 and 14.

The processing in steps 1501 to 1505 in FIG. 13 is for displaying an open waiting mark when there is a window with a high priority. First, in the case of opening a window, the window management unit 52.

In step 1501, it is determined whether the window already exists, and if it does exist, in step 1502, the window type is obtained from the WCB 522 of the topmost window, and in step 15o3, the window type specified from the task and the obtained window are The types are compared, and in step 1504, if the highest priority window has a higher priority, the TCB 532 of the requested task is connected to the open queue 523, and the task is placed in a waiting state.

Further, in step 1505, a request is made to the display control to display the mark 524 in a blinking manner as shown in FIG. This prompts the operator that there are windows waiting to be opened.

Next, in step 1013, the task is made READY in step 1525 of FIG. 14, which will be described later, and when the task dispatcher is ready to resume the task, the process returns to step 1501.

On the other hand, if there is no window on the screen in step 1501, no waiting process is performed and step 1503
If the priority of the currently displayed window is low, the W window is displayed based on the information specified by the task in step 1506.
Generate CB522. Note that steps 1506 to 15
Processing No. 10 interrupts the task of the window, if there is one. Next, step 15
In step 07, it is determined whether the window already exists, and if it does exist, in step 1508, the task using the currently top window is temporarily interrupted,
In step 15o9, the display image of the topmost window is saved to the display buffer.

Furthermore, the input state information at the time of the open request in step 1510 is saved in the input state information storage area 522.9 of the topmost window WCB 522.

Then, in step 1511, the window is displayed according to the position and size specified by the task, and in step 1512, the number of the window management block generated is returned to the requesting task.

On the other hand, in the case of window closing, as shown in the flowchart of FIG. 14, first, in step 1521, the image of the specified window is erased, and in step 1522, the image of the specified window is deleted from the window management table (WCB) 522. The window hidden by the window is identified, the display image is retrieved from the display buffer mentioned above, the display image of the window below the erased window is recovered, and in step 1523, the WCB 522 of the erased window is made unused. In steps 1524 to 1527, the window (task) waiting to be opened becomes operable at the window closing timing.

Also, in step 1524, it is determined from the open queue whether there is a task waiting to be opened, and if so, in step 1525, the task with the highest priority is read.
The state is set to Y and the task is executable. Further, in step 1526, it is determined whether there are any more tasks waiting to be opened. If there are no more tasks, in step 1527, the display control is requested to erase the mark indicating that there is a window waiting to be opened.

Also, if there are no tasks waiting to be opened in step 1524, the process ends without doing anything, and in step 1526, there may be multiple tasks waiting to be opened, so if there are tasks remaining waiting to be opened, This process ends without erasing the wait mark.

When the task is restarted, it is executed again from the window open request, and the window is opened.

Note that the task interruption process described above will be described later.

As described above, when the request from the operator is for new creation, in step 1705 of FIG.
7 is a document editing section 56 based on the notification from the input control section 51.
1 as a task, it is activated in a new creation mode in step 1707.

In addition, in the case of updating an already created document, in step 1708, the corresponding program number is obtained from the program control table (FIG. 4) based on the data type number notified from the file editing section 58, and in step 1709, the document editing section is assigned a task. In step 171o, startup parameters for the editing section are sent, and in step 1711, the document editing section is started in update mode.

Further, the system management unit 57 deletes the task when it receives the termination notification from the g-tobu that it generated and activated in step 1712.

Similar to the generation request described above, task deletion is processed by the system control unit 53, and the system control unit 53
As shown in Figure 0 (b), the TCB 532 corresponding to the task specified in step 1111 is N0NEXISTE.
Set to NT state. Sunawachi leaves the TCB532 in an unused state.

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

Now, FIG. 19 shows the processing of the activated document editing section 561.
This will be explained based on the flowcharts in FIGS. 20(a) to (Q).

In the initial processing of step 3001, the document editing unit 561 first receives startup parameters by message in step 3101, as shown in FIG. 20(a) in detail.
Based on the contents of the parameters, the startup mode, new creation or document update, is determined in step 3102. In the case of new creation, the document data is initialized in step 3103, and in the case of document update, in step 3104, the data to be updated is called from the storage unit 3 according to the document name specified by the parameter. Note that the structure of the document data will be described later. Then, from the program control table shown in FIG. 4, a support area editing management table (hereinafter abbreviated as SFMT) is created, which shows a list of area editing units that can create or update new areas in a document. SFMT is the second
As shown in FIG. 4, the program number 5682 of the area editing section that can be supported and the type number 5683 of data that can be created by this area editing section are held as a pair, and the number of area editing copies 5681 is also held. At the same time, in order to notify the operator of what kind of data areas can be created at present, the name of the data for the area editing section is set in the pull-down menu data in step 3105.

Then, when editing a region to be described later, the specified number of regions 5684 in the operation target region table shown in FIG. Initializes the valid/invalid state of. As shown in FIG. 25, the operation target area table includes the number of designated areas currently designated as the target of operation 5684, the type of the designated area 5685, and so on. and number 5 of the specified area
686 (area types will be described later).

This switching of pull-down menu data validity/invalidity will be described later. Next, in step 3108, the document editing unit 561 opens a window, and in step 31
In step 09, the layout of the first page of the edited document is displayed in the window as shown in FIG. 28(a). When opening the window, the size of the window is set to correspond to the size of the display paper, and the task number of the document editing section 561 is added to a part of the title of the window.

Now, the above-mentioned SFMT FIG. 24 and the menu data creation process (step 3105 in FIG. 20(a)) will be explained in more detail.

As shown in Figure 24, SFMT is useful for the document editing department.
This is a table showing a list of program numbers 5682 and data type numbers 5683 of bootable area editing units,
Create a new area as described below.

It is used to determine whether a corresponding program exists for updating and displaying the layout, and as a parameter when creating a task.

As shown in FIG. 20(b), the creation method is to clear the program number P and registration number E to 0 in steps 3111 and 3112, and
(Figure) starting from the first block.

In step 3114, it is determined whether the parent program number matches the program number of the document editing section itself, and if they match, in step 3115, the document editing section is regarded as the PCB 573 for the area editing section to be started, and the program is The number P and the data type number DP set in the PCB 573 are registered in the SFMT FIG.

Also, the name of the data corresponding to the data type number (for example, "Figure".

``Graph'' etc.) is acquired by DNDT (Table 2), and its name is registered in step 3116 as the name of the pull-down menu data for creating a new area in the menu data (Fig. 21) held by the document editing department itself. , step 31
17, the registration number E is incremented. Step 31
18 and step 3113, the above processing is repeated for the number of program management blocks, and finally, in step 3119, the registration number E is set to the number of area editing copies 5681. This makes it possible to display, as a pull-down menu, only the names of area editing units that are currently actually incorporated into the system. Furthermore, when adding a new area editing program to the system, there is no need to change the document editing program, and only the corresponding area editing program needs to be added. Therefore, the user can add only the editing program for the area that he/she wants to create according to his/her purpose without changing the existing program. One method of incorporating programs such as a document editing program and an area editing program into the system is as follows: For example, the program and the program number are stored on a floppy disk.

Stores the information necessary to create the PCB 573 such as priority and data type, reads the program stored on the floppy disk from the floppy disk device, stores it on the fixed disk, and further information necessary to create the PCB 573 This is done by reading the program from the floppy disk device and creating a PCB 573 in the area of the program control table corresponding to the obtained program number.

Here, the structure of the document data will be explained using FIG. 22.

Document data As shown in FIG. 22, the chapter management table 56
10. Page management table 5620. Page format table 563
0. Area management table 5640, further area data 5
660, and each table is composed of a plurality of blocks. Each table will be explained below.

(1) Chapter management table 561゜ Manage how many chapters the entire document consists of,
Page pointer 5611, 5 indicating the first/last page for each chapter
612. In addition, the chapter 1 management table contains print information 5613 for displaying and printing headers, footers, etc. for each chapter.
hold.

(2) Page management table 5620 Area pointers 5623, 5624 that indicate the first/last areas of the areas set within the page, and page format pointer 5625 that indicates which format data is used on each page.
and has. In addition, each block has a backward pointer 562
1 and the forward pointer 5622, the pages are linked in ascending order, and the first/last pages are pointed to from the chapter management table described above. In addition, the pages in this document data are
It has a configuration as shown in FIG. 23 (5671 indicates a page). The page size and margins can be found in the page format table described below, and in the basic area 5672. Regarding the internal area 5673, see the area management table 56 described later.
40 respectively.

(3) Page format table 5630 The paper type (A
3. A4, etc.), paper orientation (portrait, landscape), top, bottom, left, right margins, etc.

(4) Area management table 5640 The area management table stores data to be stored within a document (within a page), such as text data, graphic data, graph data, etc., in what position and size within the page. Manage what you do. Therefore, the area management table 5640 uses the upper left X coordinate 564 of the area whose origin is the upper left of the page excluding the margin as the area setting position within the page.
3. Data type 5647, which has the same Y coordinate 5644, lower right X coordinate 5645, and same Y coordinate 5646, and also indicates the type of data in the area. Area attribute 5648 indicating the attribute of the area itself. It has a data pointer 5650 that points to data 5660 within the area. In addition, the attribute of the area itself is whether it is transparent or opaque (in the case of opaque,
The area covered by the area becomes invisible), and
There are line types for area frames, etc. Also, in this table,
In order to manage the order in which areas within the same page overlap, they are linked to each other by a backward pointer 5641 and a forward pointer 5642. 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. Furthermore, among these, the first and last areas are respectively pointed to from the page management table described above. Further, the area management table includes status information 5649 indicating whether the area is being edited or not, and whether or not an area editing unit corresponding to the area data type currently exists in the system.

Further, the areas existing within one page can be roughly divided into the following two areas as shown in FIG.

(a) Internal area 5673 This area exists on the basic area, and the position and size are determined by the operator's operation. Moreover, one of various data such as text, graphics, graphs, and images can be stored in the area. Furthermore, editing of this area enables all area editing such as new area creation, updating, movement, copying, and deletion.

(b) Basic area 5672 Refers to the part of the page excluding the top, bottom, left, and right margins, and when a page is generated by an operator's operation, one main area is also generated,
It is always the first area (the lowest area) within a page. Also.

This area stores only the text data that becomes the main body of the document, and in addition to editing the above areas, it is possible to create new areas, update, move, copy, and delete from this area. For editing operations such as
Perform editing operations on pages such as moving, copying, and deleting pages.

(5) Data within area 5660 Data stored within the area, including text, graphics, graphs, image data, and the like.

Now, in FIG. 19, after the initial processing in step 3001, the document editing section 561 requests input from the input control section 51 in step 3002. and step 300
In step 3004, the input result from the operator is determined, and if the instruction is for the area to be operated, then in step 3004, which area is specified based on the specified position within the page number 2 and the set position of the area is determined from the document data. The area number is determined and registered in the operation target area table. The determination method at this time will be explained in more detail using the flow shown in FIG. 20(c).

First, in step 3201, the designated position is in the basic area 5672.
It is determined whether it is within the basic area, and if it is outside the basic area, there is no area corresponding to the specified position, so it is determined as an instruction error.

If it is within the basic area, in steps 3202 to 32o5, the uppermost area of the internal area 5673 within the page (
Starting from the end area of the page), it is determined whether the indicated position is in the internal area, and as a result of the determination, if it is within the internal area,
At step 3206, the operator's instructions include
If the internal area instruction flag is set to 1 as an operation instruction for 673, and the specified position is ultimately not within the internal area of the currently displayed purchase (internal area instruction flag is 0). (in this case), the operator assumes that the basic area 5672 has been specified and processes it. Now, if the designated position is within the internal area 5673, then in step 3207 it is determined whether the island area has already been designated as a target, that is, whether the number of the area has already been registered in the operation target area table. However, if the target has already been specified, the next area (in the document data, the area indicated by the forward pointer 5642 of the area management block of the area currently being determined as shown in FIG. 22) is checked. In addition, if it has not been specified yet, it is assumed that the area has been specified and the number of the area is registered in the operation target area table, but at this time, the basic area 5672 has already been specified as the target in step 3208. If specified, the number of specified areas 5684 in the operation target area table of FIG. The area type is registered in the operation target area table, and the number of designated areas 5684 in FIG. 25 is set to +1. Note that in the above, if the basic area 5672 is registered as an operation target, the designation will be forcibly canceled if the basic area 5672 and internal area 5673 can be specified at the same time, as described later. This is because there will be no area edits corresponding to . Further, in the above process, if the internal area 5673 is not registered, step 32
In step 12, it is determined whether the internal area designation flag is 0, and if it is O, it is assumed that there is no internal area 5673 at the specified position and that the operator has specified the basic area 5672 as the target. Next, the number of the basic area 5672 is registered in the table. At this time, it is determined whether the optical basic area 5672 has already been specified as a target in step 3212. If it has not been specified, step 3214
Next, it is determined whether the internal area 5673 has been specified as a target, and if it has been specified, step 321
After clearing the operation target area table in step 5, the basic area number and area type are registered in the operation target area table in step 3216, and the number of designated areas is set to 1.

Further, in step 3205, the designated position is set to the internal area 567.
3, or if no area is specified in step 3207, the next area number is set to the last area in the page in step 3211, and the process returns to step 3204.

Now, if the instruction from the operator is an instruction to cancel the designation of the area currently being designated as a target, step 300 in FIG.
In step 5, it is determined from the document data which area is specified based on the specified position within the page number 1 and the setting position of the area,
The area number is deleted from the operation target area table. The determination method at this time will be explained in more detail using the flow shown in FIG. 20(d).

First, in step 3251, it is determined whether the designated position is within the basic area, and if it is outside the basic area, the operation target area table is unconditionally cleared. That is, step 3
In step 258, all areas registered in the table are deselected.

Meanwhile, step 3252. If it is within the basic area in step 3253, it is determined whether the indicated position is within the area in order from the highest area on the page (the last area on the page), and as a result of the determination, if it is within the area, , step 3254
In step 3257, it is determined whether the area is registered in the operation target area table, and if it is registered in step 3257, the area number is deleted from the table. On the other hand, if the indicated position is not within the area in step 3253, or if the area is not registered in the table in step 3254, step 3255.
The same determination is made for the areas after 3256.

Now, along with the above region designation/cancellation operation, the region editing operations that can be performed change sequentially. 2
This will be explained using FIG. 0(e).

Third Table area editing operations can be classified into three types depending on the number of areas designated as operation targets, as shown in Table 3. That is, first, in step 3301, the number of regions being specified as a target is determined, and if the number of regions is 0, step 3301 is performed.
In step 302, only the pull-down menu for creating a new area is enabled, and all other area editing is disabled. Conversely, if the number of regions being specified as a target is 1, in step 3303 only the pull-down menu for creating a new region is disabled for the time being, and all other region editing is enabled.

Furthermore, if the number of areas being specified as a target is two or more, in step 3304 only move, copy, and delete are enabled, and all other area edits are disabled. In addition, if the number of target designations is 1, it is determined in step 3305 whether the further designated area is the basic area 5672, and the basic area 5672 is determined.
In the case of 672, attribute changes and size changes are also disabled in step 3306, and then in step 3307 it is determined whether the status of the specified area is other than 0, and if it is other than 0 (the area is currently being edited). (or, if the area editing unit 562 that can update the area does not exist in the system), the update is also invalidated in step 3308. In addition, if the number of specified targets is 1 or more, step 33
It is determined whether an area with a status of 1 (area currently being edited) exists among the areas specified in step 09, and if so, the deletion is also invalidated in step 3310.

Next, the case where the instruction from the operator in step 3006 in FIG. 19 is an instruction to create a new area will be described based on the flow in FIG. 20(f).

In this case, the operator instructs new creation by instructing the data name displayed in the pull-down menu, but the document editing section 561
In step 34o1, the program number and data type number of the corresponding data are acquired based on the above-mentioned SFMT (Fig. 24), and in step 3402, it is determined which data was instructed to be newly created. judge. At this time, if the instructed data is data to be created as the internal area 5673, area settings for the area and attribute settings for the area are performed in step 3403. Then, in step 34o4, an area management block is generated based on the above information, and in step 3405, the area editing unit 562 is activated. Note that the startup process will be described later.

Now, if the instruction from the operator in step 30o7 of FIG. 19 is an instruction to update an already created area, the information is registered in the operation target area table 5686 of FIG. 25 in step 3411 as shown in FIG. 20(g). In step 3412, SFMT is performed based on the data type of the area management block from that number (Fig. 24).
Then, in step 3413, the corresponding area editing section 562 is activated as a task.

In the activation of the area editing section 562 in the above, the second
As shown in FIG. 0 (h), first, the document editing unit 561 requests the system control unit 53 to generate a task based on the program number obtained in step 3451, and in step 3452, the task number returned as a result is , and the number of the corresponding area in the active editing task management table (hereinafter referred to as ET).
(abbreviated as MT). As shown in FIG. 26, the ETMT holds the task number 5688 and the area number 5889, and also has the number of activated tasks 5687 indicating how many area editing units 562 are currently activated. Then, in step 3453, the status of the area management block is changed from 0 to 1 to indicate that the corresponding area is being edited.

After the above processing, in step 3454, the document editing unit 561 requests the system control unit 53 to start a task.
Further, in step 3455, the activation parameters are sent as a message to the area editing unit 562 that activates them. At this time, the startup mode that indicates whether to create a new area or update the area is used as a startup parameter.

The task number of the document editing section 561, the task number of the area editing section 562 to be activated, and, in the case of new creation, the size of the area are transmitted.

If other editing operations, such as moving or deleting an area, inserting or adding a page, are instructed, step 3 in FIG.
The processing corresponding to each of 008 to 3o11 is performed, and the next instruction from the operator is awaited in step 3002.

Now, the instructions from the operator are step 3o in Figure 19.
In the case of an instruction to switch display pages in 12, for example, a previous page or a second page, the layout of each corresponding page is redisplayed in the window as shown in FIG. This will be explained in more detail using .

In displaying this layout, first, in steps 3501 and 3502, paper frames, headers, footers, etc. are displayed based on the document data described above, and in steps 3503 to 3514, the following areas set within the page are displayed. The areas are displayed in order from the area with the lowest priority (the first area within the page). In displaying this area, first, in step 3504, the area is displayed, and then in step 3505
In step 3511, 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 SFMT Figure 24. If there is no editing program, the status of the area management block is set to 2 in step 3511. At the same time, in step 3512, the area is displayed completely in black to notify the operator that no editing program for this area exists in the system. Also,
If the above exists in step 3506, then it is determined whether the attribute for the area is transparent, and if it is opaque, the area is partially cleared in step 3507, and then the data within the area is displayed in step 3508. Furthermore, after displaying the area, it is determined in step 3509 whether the area is being edited (1 or not) based on the status information for the area, and if it is being edited, step 351
If the value is 0, the entire area is shaded to notify the operator that the area is currently being edited. Thereafter, similar processing is performed on all areas existing within the page to be displayed in steps 3513 and 3514.

In addition, processing in step 3o13 in FIG. 19 in the case of an activation input by a window switching operation, which will be described later, will be described later. Also, the first
If termination is instructed at step 3015 in FIG. 9, editing of the document is terminated, and the details of this processing will be described later.

Now, when the document editing section 561 requests the activation of the area editing section 562, for example, the graphic data editing section, due to the creation or updating of a new area, the system control section 53, in accordance with this request, creates a new graphic data Start the data editing department as a task.

Next, the processing contents of this graphic data editing section will be explained based on the processing flow shown in FIG. 27.

First, in step 4001, the 1-graphic data editing unit receives a startup parameter via a message, and in step 4002, determines whether the startup mode is new creation or area update. In the case of new creation, the data is initialized in step 4003, and in the case of update in step 4004,
The data to be updated is called from the storage unit 3.

Then, in step 4005, a window is opened,
In step 4006, the graphic data is displayed in the window. At this time, the size of the window is set to correspond to the size of the area, and a part of the title of the window is written as the starting document Add the eastern task number. As a result, when editing multiple documents at the same time, and editing several areas within each document, the second area determines which area corresponds to which document.
As shown in FIG. 9, it can be easily identified by the task number 254 displayed as part of the title of this window. Also, at this time, the display state of the screen is 28th.
The result will be as shown in figure (b).

After steps 4007 to 4009, the graphic data editing section performs creation and editing of graphic data in accordance with instructions from the operator within the set window. Note that when the graphic data editing unit receives an instruction from the operator to finish editing within the area in step 4010, it stores the created graphic data in the storage unit 3, closes the window in step 4011, and sends a message indicating the completion of area editing in step 4012. is sent to the document editing unit 561 that is the startup source, and the task is ended in step 4013. In addition, in order to enable the started document editing section 561 to determine which region editing has finished, this end message includes an end code indicating the end of editing in the region and the task number of the figure editing section itself. set.

As described above, it is possible to create and edit the entire document and each area.
This will be explained using FIG. 8 and FIG. 15.

First, as shown in FIGS. 28(b) and 28(c), 1
When switching to editing the document layout while editing the graphic area, move the mouse cursor 30 onto the window of the document editing section 561 and press the execution button of the mouse 31 in the same way as specifying the operation target described above. Based on this input instruction, the input control section 51 first determines that the specified position is outside the window of the figure editing section that was being edited up to that point, and inputs this input not to the figure editing section but to the window management section 51.
hand over to. The window management section 52 determines from the position indicated by the mouse 31 and the window management table that the window of the document editing section 561 has been indicated in step 1531, and uses the window that was the highest until then in step 1532. The task, that is, the graphic editing section is temporarily interrupted, and the display image of the topmost window is saved in the display buffer in step 1533.

Furthermore, in step 1534, the input state information at the time point specified by the mouse 31 is stored in the WC of FIG. 5 in the topmost window.
It is saved to the input state information storage area 5229 of B522. Then, in step 1535 of FIG. 15, the window of the newly instructed document editing section 561 is displayed at the top, the stacking order of the WCB 522 is updated in step 1536, and the input state information saved in the WCB 522 is further updated in step 1537. , and reset the font mode etc.
In step 1538, user character type 52 of WCB522
30 and the user character management table 551, the user character data is restored to the RAM 31 used by the display control unit 55 as necessary in the same manner as the user character usage notification described above.

In addition, in order to notify the document editing unit 561, which restarts processing anew, in step 1539, that the window has been switched, an activation code is returned to the window usage task, and in step 1540, the document editing unit 561 restarts the process. The current task, that is, the document editing section 561, is restarted. Thereby, it is possible to automatically return the input state information to the state before switching by switching the window, and it is also possible to restore user character data of the type used in the window to the RAM 31.

Note that the above-mentioned interruption and restart of the editing section 56 is processed by the system control section 53. Below, Figure 10(e)
, and the flow of FIG. 10(f), the suspension and restart processing will be explained.

When a task interruption request occurs, in step 1141 the system control unit 53 suspends the TC corresponding to the specified task.
B 532 interrupt plug is set, step 1142
Determine whether the task is in the READY state with
If it is in the Y state, the corresponding TCB is
532 from the READY queue so that no CPU is assigned to it by the dispatcher.

In response to a task restart request, the interrupt flag of the corresponding TCB 532 specified in step 1151 is reset, and in step 1152 it is determined whether the task is in the READY state. Connect to a queue. TCB532
If the interrupt plug is set, the task dispatcher does not start the task and removes it from the READY queue.

Also, from the state shown in FIG. 28(c), the basic area 567
If update 2 is performed, the screen changes as shown in FIG. 28(d). In this state, each editing section can be switched between text, figure, and layout.

This can be done arbitrarily between each other using the same operating method as described above. For example, when switching between the area editing sections, that is, from text to graphics, the screen display state becomes as shown in FIG. 28(e).

Now, when the window is switched as described above, an activation code is returned as input to the restarted task from the window management section.

For example, in the above example, when switching from the graphic editing section to the document editing section 561, the document editing section 56]- receives the above activation input after restarting, and according to this,
Perform the following processing. This will be explained below with reference to FIG. 20(j) and FIG. 20(k).

That is, first, in step 3601, it is determined from the document data whether or not there is an area being edited within the currently displayed page;
If there is, the display flag is set to 1 in step 3602 since the contents of that area may have been updated by editing, but if not, the display flag is set to 0 in step 3603, and the following steps are performed. After processing the message,
Performs layout redisplay processing. Next, step 360
4 to 3606, a message reception request is made to the system control unit 53, and if there is a message, the following process is performed as a termination process of the corresponding area editing unit 562.

That is, first, the task number of the area editing unit 562 stored in the message in step 3651.

And obtain the area number from ETMT (Figure 26),
In step 3652, the status of the corresponding area management block is reset to O, in step 3653 information regarding the task is deleted from the ETMT (Figure 26), and finally in step 3654 the task itself is deleted.

Now, in the above case, if there are no more messages, it is determined in step 3607 whether the display flag is set to 1, and if it is set in step 3608, the layout of the page is redisplayed.

Finally, the second section regarding the termination process in the document editing section 561.
This will be explained using FIG. 0 (Q) and FIG. 10 (g).

If the operator instructs you to finish, proceed to step 3.
In step 702, it is determined whether or not there is an active editing task based on the above-mentioned ETMT (Fig. 26), and if there is, in step 3703, the task number and area number are obtained from the ETMT (Fig. 26), and step After resetting the status of the area to 0 in step 3704, a request is made to the system control unit 53 to forcibly terminate the task in step 3705.

Accordingly, as shown in FIG. 10(g), the system control unit 53 first releases the resources used by the specified task in step 1161, requests the window manager to perform forced termination processing in step 1162, and In window management, processing similar to the closing processing shown in FIG. 14 is performed.

Then, based on the specified task number, the corresponding T
If CB 532 is connected to the READY queue,
removed from the READY queue 533 in step 1163;
The state of TCB 532 is set as the DORMANT state.

After the above forced termination processing, the document editing unit 561 deletes the task in step 3706.

The above process is repeated for the editing tasks that are running in step 37o7, and when all the running tasks have been forcibly terminated, the document data is registered in step 3708, and the document editing section itself opens in step 3709. In step 3701, a message is sent to the system management unit 57 to inform that the process has been completed, and in step 3711, the task is ended.

In this way, when a termination request is made to the document editing section 561, the area editing sections 562 that are being edited can be terminated all at once.

〔Effect of the invention〕

As described above, according to the present invention, when switching editing sections (windows), only the user character information used in each editing section (window) is restored to the storage area of the storage section used in the display control section. Therefore, there is no need to store all of the plurality of types of user character information in the storage area of the storage unit that is always used by the display control unit, and an inexpensive document creation device can be provided.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention, FIG. 2 is a diagram showing an example of a display screen in the display section of FIG. 1,
Figure 3 is a diagram showing the configuration of mouse buttons, Figure 4 is a diagram showing the configuration of the program control table, Figure 5 (a) is a diagram showing the configuration of the window management table, and Figure 5 (b) is a diagram showing the open queue. , FIG. 6 is a diagram showing the configuration of the task control table, FIG. 7 is a diagram showing the READY queue, FIG. 8 is a diagram showing the configuration of the message control table, FIG. 9 is a diagram showing the message reception queue, and FIG. FIG. 10(a) is a flowchart showing the processing of the system control unit in FIG. 1, FIG. 10(a) is a drawing showing task generation processing, FIG. A diagram showing the process of starting a task,
FIG. 10(d) is a diagram showing the task termination process, FIG. 10(e) is a diagram showing the task interruption process, FIG. 10(f) is a diagram showing the task restarting process, and FIG. ) is a diagram showing the task forced termination process, FIG. 10(h) is a diagram showing the message sending process, FIG. 10(i) is a diagram showing the message receiving process, and FIG. 10(j) is a diagram showing the dispatcher's process. 11 is a flowchart showing the processing of the input control section of FIG. 1, and FIG. 12 is a menu management table. FIG. 13 is a flowchart showing the window opening process; FIG. 14 is a flowchart showing the window closing process; FIG. 15 is a flowchart showing the window switching process. 16 is a flowchart showing the processing of the system management section in FIG. 1, FIG. 17 is a flowchart showing the processing of the file editing section in FIG. 1, and FIG. 18 is a configuration diagram of the operation target document table. FIG. 19 is a flowchart showing the processing of the document editing section in FIG. 1;
FIG. 20(a) is a diagram showing the initial processing of the document editing section;
Figure 20(b) is a diagram showing the support area management table creation process in the initial processing of the document editing department, Figure 20(c) is a diagram showing the area specification process of the document editing department, and Figure 20(d) is a diagram showing the document editing process. FIG. 20(e) is a diagram showing the process of canceling the designation of a section; FIG. 20(e) is a diagram showing the valid state switching process of the pull-down menu in the document editing department; FIG. 20(f) is a diagram showing the process of creating a new area in the document editing department. FIG. 20(g) is a diagram showing area update processing in the document editing section, FIG. i) is a diagram showing the layout display processing of the document editing section, FIG. 20(j) is a diagram showing the activation processing of the document editing section, and FIG. 20(k) is a diagram showing the area editing section in the activation processing of the document editing section. FIG. 20 (Q) is a diagram showing the end processing of the document editing section. FIG. 21 is a configuration diagram of the menu table of the document editing section.
Figure 2 is a configuration diagram of document data. Figure 23 is a diagram showing the structure of a document page, Figure 24 is a diagram of the configuration of the support area editing department management table, Figure 25 is a diagram of the configuration of the operation target area table, and Figure 26 is the configuration of the startup editing task management table. 27 is a diagram showing the processing of the graphic data editing section, FIGS. 28(a) to (e) are diagrams showing switching of screens by document editing operations, and FIG. 29 is a diagram showing identification name display when editing an area. FIG. 30 is a diagram showing an example of a screen display while waiting for a window to open, and FIG. 31 (
a) and (b) are configuration diagrams of the user character management table and user character data, Figures 32 (a) to (Q) are diagrams showing the initial state of the user character management table and examples of registration of registered character types, and Figure 33. FIG. 34 is a flowchart showing user character registration processing, and FIG. 34 is a diagram showing user character usage notification processing. 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, 57... System Management Department, 58.
...File editing department, 59...User character management department, 5
61...Document Editorial Department, Invitation Ward Bizu 3j Fusu Amu Daizu Yu 32 Sad Zuwazu Nerogusa ■ Blocked Zuzu (Ku) Diagram Takusen (C) Kuzu 10zu (Me) Fuku Ce ) Kaya Ward Bi) Beimu Ward (a-) 1 Ward tA> 58 I8 Long Guest Table Ward No. 20 (ku) Hato 2oB Ib) No. 20 (C) Tokuni<d-) 5, 20 ;21 (S) Taku 20th figure (e) Mine 20th figure (, l) Certain 20th figure (ta) Figure ()] shi≠ Most of the 24th figure Li 25 Sheep 2 Otsu 7 Plan c1 Figure screen Figure 30 Not shown Figure 32 Figure

Claims (1)

[Claims] 1. An input section for inputting description elements to be written in a document in each area, a storage section for storing input description elements, a display section for displaying various description elements stored in the storage section, and each area. an area editing section for creating and editing data in the area, and displaying the page layout of the created and edited text on the display section;
A document editing section that edits the area according to the display and starts the area editing section for the area that is instructed to be created or updated; and separate display areas for displaying the contents of the document editing section and the area editing section. A document creation device comprising: a window display control means for controlling display on the screen; an edit switching means for switching editing by the document editing section and the area editing section; and a user character creation means for performing work including creation of user characters. , a registration means for registering and updating user characters based on user character management information for managing user characters, a notification registration means for notifying and registering user character types used in the window display control means, and the editing switching means. A document creation device comprising: user character recovery means for recovering user character information of a switched window based on the user character type and the user character management information when the editing section is switched by the means.