JPH06290049A - Method for operating menu - Google Patents

Abstract

PURPOSE:To improve an operation environment and working efficiency by making it possible to process also non-resident programs (application) by operation similar to that of a resident program. CONSTITUTION:Working efficiency is improved by setting up the operation environment of non-resident programs A, B to the same operation environment as that of a resident program to be easily operated by a hot key or the like and the contents of the resident program are included in the program B. In a routine (B), the processing of a conventional program C is separated preformed in a step 10, the processing of the programs A, B are divided in a step 11, the program A is processed in a step 12, and the program B turns on/off a flag for inhibiting the start of the resident program before and after the processing of a step 14. When the hot key is ON and an inhibition flag is off, the resident program executes processing (A). Thereby the resident program and its contents included in the program B are not allowed to compete with each other.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a menu operating method for a program operating on a single task type operating system.

[0002]

2. Description of the Related Art Programs operating on a single task type operating system (hereinafter referred to as "OS") such as MS-DOS are resident in memory and from an external storage device such as a disk driver each time. There are non-resident programs that are loaded into memory.

Since the resident program always remains in the memory like the OS after it is loaded after the OS at the time of starting the computer, software interrupts from other programs and hardware interrupts such as hot key operations are performed. For example, the operation right can be started immediately after the execution right is given by an external event.

Therefore, if an event for operating a resident program is assigned to a specific key on the keyboard, the resident program required can be activated by an operator's hot key operation at any time even while another program is being executed. Single task OS
Even in this case, the work can be switched quickly as in the multi-task type OS, but there is a problem that the free area of the memory is limited by the resident operation.

On the other hand, the non-resident program is loaded into the memory from the external storage device as needed, and then given the execution right to start the operation. After the program is executed, another new program is loaded into the same memory area. Erased by the overlay.

Therefore, the non-resident program that operates on the single-task type OS must be called from the external storage device, loaded into the memory, and activated as necessary. Further, when switching to another program during execution, it is necessary to interrupt the processing once to call and start the other program, so that there is a problem that the operation is complicated and takes time as compared with the multitasking OS. .

Despite the above problems, at present, the single task type OS is the multitask type OS.
It is used more frequently than the above and can be considered to coexist in the future.
Therefore, generally, those requiring immediate processing are classified as resident type, and relatively large programs are classified as non-resident type according to their functions.

[0008]

However, in the conventional program, the programs are classified according to their functions, so that their operability is not unified, or even if the operation methods are unified, the screen design etc. are different. Depending on the environment, it takes time for the operator to learn the input procedure and operation method, and there are many mistakes and it is inefficient.

The present invention has been made in view of the above points, and enables a non-resident program operating on a single-task OS to be processed by the same operation as a resident program,
The purpose is to improve the menu operation environment and work efficiency.

[0010]

In order to achieve the above object, the present invention is a program that is used in an information processing apparatus and operates on a single-tax type operating system, which resides in a memory and is externally supplied. Each of the resident programs displayed on the display means by the operator includes a resident program which is given an execution right by an event and operates, and a non-resident program which is loaded from an external storage device to a memory by an operating system and then given an execution right and operates. In a menu operating method for operating by referring to a menu of a program, the operating environment of a non-resident program is made the same as the operating environment of a resident program.

Alternatively, the contents of the resident program may be included in the non-resident program. Further, it is preferable to prohibit the activation of the resident program during the operation of the non-resident program including the contents of the resident program.

[0012]

According to the above menu operating method, the operating environment of the non-resident program is the same as the operating environment of the resident program, so the operating method and screen design are unified, the operation becomes easy, and the operator's learning speed is increased. , Mistakes are reduced and work efficiency is improved.

Alternatively, by including the contents of the resident program in the non-resident program, not only the operating environments of the two are unified, but the non-resident program, like the resident program, is hot even when another program is being executed. It can be switched by simple operation such as key operation.

Further, by prohibiting the activation of the resident program during the operation of the non-resident program including the contents of the resident program, the corresponding portion in the resident program is executed when the contents of the resident program in the non-resident program are executed. There is no fear of accidentally starting the product and causing a malfunction.

[0015]

EXAMPLE FIG. 2 shows a single-task type OS on a memory.
It is a figure which shows an example of a memory map which shows arrangement | positioning of an (operating system) and an application program (henceforth "application") which is a resident program and a nonresident program.

Hereinafter, the applications A and B are programs having the same function (same operating environment) as the resident program, and the application B is a program including the contents of the resident program. Application C
Is a conventional non-resident program that has different functions from the resident program.

Of the memory map shown in FIG. 2, (A) of FIG. 2 shows that the OS is first stored in the memory from an external storage device such as a disk device immediately after the information processing device, for example, a computer is powered on, that is, at the time of startup. (B) in the figure shows a state in which the resident program is subsequently read and waits for an instruction from the operator.

If only the resident program is to be operated, the menu of the resident program can be displayed in the state shown in FIG. 2B and the designated program can be activated by hot key operation or the like to execute the processing. Good.

2C and 2D show memory maps when the application A or B or the application C is read from the disk device and processed. The memory occupancy size of these differs only depending on the read program, and there is no change in the memory map.

Areas other than the program in the memory shown in FIGS. 2A to 2D are free areas that can be used by the operator to store data, and the smaller the area occupied by the program, the smaller the free area. Take wide,
Processing becomes easy.

Generally, when reading other applications, an overlay method is used. Therefore,
Unlike the resident program that can be used at any time, when you use the previous application after reading and processing another application, you need to read it again.
If it is a program in the same application, there is no need to read it from the outside.

FIGS. 3 and 4 are menu hierarchy diagrams showing an example of the program structure of the resident program and the applications A, B, and C. FIG. 3A shows the resident program.
4B shows the menu hierarchy of the application A or C, and FIG. 4 shows the menu hierarchy of the application B.

When a resident program is designated or an application is read and then started, the program menu as shown at the top is displayed, and the hot key corresponding to the target program or its number is pressed (event occurrence: application A , B)),
When the program name is keyed in (in the case of application C), a menu corresponding to each process as shown in the middle row is displayed.

Similarly, when a program displayed on the menu is selected, a submenu corresponding to each menu as shown in the lower stage is displayed. In this way, the target program is designated (menu operation) by the menus into which the programs are classified into the major classification, the middle classification, and the minor classification, and the execution processing is performed.

In this menu operation, the conventional application C is different from the resident program in the function of displaying the menu and the method of selecting or designating the program, so that the currently displayed menu or the process being executed is You must always be aware of whether it is a resident program or an application and use different processes.

However, since the application A or B according to the present invention has the same function as that of the resident program, it is a single-task type OS, but the operator can operate it in the same way as the multi-task type OS without being aware of it. You can do it.

Furthermore, in the case of the application B, since the contents of the resident program are included as shown in FIG. 4, the operation is exactly the same as that of the resident program, and the operability is significantly improved.

FIG. 1 is a flow chart showing an example of a routine for activating and executing the above-mentioned resident program or application. FIG. 1A is a subroutine for activating the resident program, and FIG. ) Indicates a routine for starting the application.

The resident program start-up subroutine shown in FIG. 1A is always started at a preset timing because the resident program is preferentially executed when the hot key is pressed even while other processing is being executed. .

When this subroutine is started, it is first judged in step 1 whether or not the hot key is pressed, and if not, the process immediately returns. If the hot key is pressed, the routine proceeds to step 2, where it is judged whether or not the prohibition flag for prohibiting the activation of the resident program is on, and if the flag is on (inhibition of activation), the routine directly returns.

If the prohibition flag is off, that is, if the activation is not prohibited, the process proceeds to step 3, the processing by the resident program is executed (after stopping the program currently being processed), and when the processing is completed, the process returns. (Returns to the canceled program.)

The application starting routine shown in FIG. 1B is started after the desired application is read on the memory. First, the application read in step 10 has the same function as the resident program (application A according to the present invention.
Or B) or not (conventional application C), and if not, jump to step 16.

If they have the same function, the process proceeds to step 11 and it is judged whether or not it is the application A. If the application B contains the contents of the resident program, the process jumps to step 13 to find the application A. If so, the process proceeds to step 12, the program A is processed and executed, and the process ends.

When jumping to step 13, the prohibition flag is turned on to prohibit the activation of the resident program in the same memory, the program proceeds to step 14 to execute the program B, and the prohibition flag is turned off and activated at step 15. Remove the ban and go to the end.

In the case of the conventional application C, the process jumps from step 10 to step 16 and the instruction for starting is input and processed. When it is confirmed in step 17 that the starting instruction is completed, the process proceeds to step 18 and the program is executed. Execute C and go to the end.

Although there does not seem to be much difference in the flow diagram, the conventional application C requires complicated operations before starting, and if the processing by the resident program is interrupted during execution, the operating environment changes. As described above, the erroneous operation is likely to occur.

The application A according to the present invention is easier to operate than the application C, and the operating environment does not change even if the resident program is interrupted.
The probability of erroneous operation is greatly reduced, and work efficiency is improved.

Further, since the application B includes the contents of the resident program, even if the interrupt of the resident program is prioritized, when returning to the program that was being executed, the operation is as easy as the interrupt. , Work efficiency is further improved.

Further, as shown in step 13 and step 15 of FIG. 1B, since the activation of the resident program is prohibited during execution, even if the contents of the resident program to be included are activated by hot key operation. , No erroneous processing due to competition will occur.

[0040]

As described above, according to the menu operating method of the present invention, a non-resident program operating on a single-task OS can be processed by the same operation as a resident program, and the menu operating environment and work efficiency are improved. improves.

[Brief description of drawings]

FIG. 1 is a flowchart showing an example of a routine for starting a resident program or a non-resident program according to the present invention.

FIG. 2 is a memory map showing an example of arrangement of an operating system, a resident program, and a nonresident program on a memory.

FIG. 3 is a menu hierarchy diagram showing an example of the configuration of a resident program and a non-resident program that does not include its contents.

FIG. 4 is a menu hierarchy diagram showing an example of the configuration of a non-resident program including the contents of a resident program.

Claims (3)

[Claims] 1. A resident program which is used in an information processing apparatus and operates on a single-tax type operating system, which is resident in a memory and operates by being given an execution right by an external event, A menu operating method in which an operator operates a non-resident program that is loaded from the external storage device onto the memory by the operating system and then given an execution right to operate, with reference to the menu of each program displayed on the display means. The menu operating method according to claim 1, wherein the operating environment of the non-resident program is the same as the operating environment of the resident program. 2. A resident program which is used in an information processing apparatus and operates on a single-tax type operating system, which is resident in a memory and operates by being given an execution right by an external event, A menu operating method in which an operator operates a non-resident program that is loaded from the external storage device onto the memory by the operating system and then given an execution right to operate, with reference to the menu of each program displayed on the display means. In the menu operating method, the contents of the resident program are included in the non-resident program. 3. The menu operating method according to claim 2, wherein activation of the resident program is prohibited during operation of the non-resident program including the contents of the resident program.