JPS61151753A - Computer with guide function - Google Patents

Abstract

PURPOSE:To obtain a computer with excellent user's interface by utilizing input history information of the user in case of error message and guide display to give a proper message to the user. CONSTITUTION:When the user inputs a user code for identifying user from an input device 1, a personal controller of a controller 5 starts extracting the input history corresponding to the user code. The personal controller reads an input every time the user applies input from the input device 1, the input is stored tentatively in an internal storage 4, and the input is copied in an input history file in an external storage device 3 of the user. Then the input is transmitted to a utilization function utility section in the controller 5. The utility section controls processing utilities such as an editor, an electronic mail or document processing in response to the request of the user. The utility section applies required processing to the input and returns a message to the personal controller in the controller 5.

Description

[Detailed Description of the Invention] [Technical Field of the Invention] The present invention provides a method for a computer to process errors such as user input errors.
The present invention relates to a calculator with a guide function that displays error messages and provides input guidance using user input history information in response to exception handling.

[Technical background of the invention and its problems]

In a computer system, the same guide message and error message (collectively referred to as a message) are displayed on the display for input error 9 exception handling for all users of the system, and the same operation is performed. Ru. However, there are individual differences among users, and the messages necessary for beginners and those necessary for experts are essentially different. Also, it is naturally preferable that the message sent when the same mistake is made several times is different from the message sent when the same mistake is made for the first time. This is because if the user repeatedly makes the same mistake, the user either does not know about the function or has a misunderstanding.

A more detailed explanation there.

Guide functions will be required.

However, the conventional total J! On machines, error handling and out-of-line processing are built into utility functions such as editors.
Messages were being output due to system conditions and circumstances. Therefore, even if the user repeatedly made the same mistake, the message from the computer was often not understood. In the end, users either repeat mistakes and stop using the product, look it up in the manual, or learn from other users who know better.

As described above, it is not possible to display appropriate messages or provide guidance to each user, who has various individual differences and different levels of proficiency, resulting in a drawback that the efficiency of the user is reduced.

[Purpose of the invention]

An object of the present invention is to provide a computer with an excellent user interface by giving an appropriate message to the user by also using the user's input history information when displaying error messages and guides.

[Summary of the invention]

The present invention stores the user's input history in the computer, and when the user makes an input error or handles an exception, a message is displayed based only on the system status, unlike conventional methods. (, while considering the user's input history,
A guide fl that displays matching messages
! You can create a functional calculator. In other words, when the utility detects the input error 0 exception handling, conventionally, it would simply write the message 11! from the error table, etc.
However, in the present invention, the bird becomes -, and related patterns on the input history are found in the input history. By using these several patterns, the stomach view at the time of the user's input is , contains information regarding usage status. This makes it possible to display more appropriate information to the user than before.

〔Effect of the invention〕

According to the present invention, at the time of input error 9 exception processing, by tracing the input history information of the user, it is possible to change the content of the message for the user who has repeatedly made the same error. can. Therefore, since it is possible to display a message appropriate to the user's situation, operability for the user can be improved. Also, users can learn functions naturally.

[Embodiments of the invention]

Hereinafter, one embodiment of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of the present invention. In FIG. 1, l is a keyboard having character keys and function keys, or an input device such as a mouse or a light pen. Reference numeral 2 denotes a display device such as a CRT for displaying input character strings, guide messages for performing the functions to be used, error messages, and the like. The functions used here are
It means an editor, '@E-mail, form processing, etc. performed by a computer.

3 is an external storage device in which files for programs, data, user input history matching rules, messages and commands (these will be described later) are stored;
4 is an internal storage device for temporarily storing and processing the contents stored in the external storage device 3, and 5 is a control device for controlling these contents.

FIG. 2 shows one file necessary for the present invention in an external storage device. 6 is a manual history file for collecting and retaining each user's input history% 7 is a matching rule file for pattern-matching each feature in the input history and applying the corresponding rule 9 is a message file in which each message outputted is collected; and 9 is a command file that describes the processing to be performed by applying the rules. FIG. 3 is a block diagram of the control device. lO is the user interface 1ltIl#l
], and 11 is a utility section for various functions to be used, such as an editor, e-mail, form processing, etc.

FIG. 4 shows a response message sent from the usage function utility section to the personal controller. here 12
is a response message in the normal state <S>.

Reference numeral 13 indicates a response message such as an error number, an exception processing number, etc. in 3 during error temporary processing and exception processing (F).

14 is a response message at the time of termination or interruption.

FIG. 5 is a flow diagram of the processing of the personal controller of the control device. FIG. 6 shows an example of the contents of each file. Here, (+1) is an example of the contents of the input history file.

Here is an example of an input history for a line editor called ed. (b) is an example of a matching rule.

TC) is an example of a message output from a display device, (d
) are commands and command examples.

More? &#J#Processing flow in the personal controller of the device The operation of this embodiment will be explained using FIG. 5.

First, the user inputs a user code (user number, password, etc.) for identifying the user using the input device 1 shown in FIG. 1 (step 15 in FIG. 5).

Control (2) The personal controller of the device opens the input history file corresponding to this user code.

Collection of input history is started (step 16 in FIG. 5).

Here, an input history file is held for each user.

Each time the user makes an input from the input device (step 17 in Figure 5), the personal controller reads it, temporarily stores it in the internal memory (4), and then copies this input to the user's input history file. (Step 18 in Figure 5). Thereafter, the input is sent to the usage function utility section (FIG. 3, 11) (step 19 in FIG. 5). The Utility Department will provide editors and e-mails at the request of users.

Form Processing II rA Controls which processing utilities.

After the usage function utility section performs necessary processing on this input, it returns the message shown in FIG. 2 to the personal controller. If the processing is performed normally based on the input, a flag (8) indicating normality shown in FIG. 4 and a response message are returned. When an error-2 exception occurs due to the input, a flag (g) indicating the occurrence of an error (exception) shown in FIG. 4 and an error-1 number are returned. If the input terminates or interrupts the function, a flag (CF) is returned.

The personal controller has 1 function from the utility section.
Monitor whether these responses come (step 20.21 in Figure 5). 1III! If no response message is received from the utility section, after entering the wait state,
Check again to see if there is a response message. When a response message arrives, the flag for that response message is normal (S).
or error CE) or termination (interruption) (F) (1
Figure 15 Step 22).

If normal <S>, a response message or message is output to the display device. If there is no response message, it is assumed that the message has been sent. Then, the next input is read from the input device (#II Fig. 1).

If the personal computer operator fails to respond to the exception response (II/E4 Fig. 13) from the usage function utility section (error @), the operator learns the error number (exception handling number). This serves as a trigger, and each rule in the matching rule file shown in FIG. 2 is compared with the history pattern in the input history file (step 26 in FIG. IN5). This verification method is explained in the sixth
Illustrated using diagrams. For example, in the case of an editor called ed, an example of the user's input history is shown in Figure 6 (Figure 6). Error (13
) or i (interrupt) (F).

Consider the case where a command input error (E) is returned from the utility section. Here, the first error number is l.

The personal controller first identifies the error number. Then, a condition pattern corresponding to the aa pattern of the input layer 1 file is found from the condition term of the rule of the matching file (@Step 26 in Figure 5).

The rules in the matching file are shown in Figure 6(b) tζ
show. Rules are generally if (conditional patterns) then
Cffl message, applied command].

Here, the application message and application command of the rule whose input history pattern matches the condition pattern are executed. There are cases where more than one rule can be applied from the search of the matching file, but in that case it may be better to apply it, or it can be applied appropriately and the one with the largest weight is selected. They may be applied, the last one may be applied, or perhaps they may be applied sequentially and the user makes a decision.

In matching rule 2 in (b), PN refers to the current input (after Nt) in the input history file. Therefore, PN←
q indicates that the last input is not equal to q. P.N.
,←q means that the previous input is not equal to q. Similarly, PN-1 to q indicate that the two inputs before the current one are not equal to q. Error 1 number -1 indicates that the Error 1 number is equal to 1. The characters pN- and ~PN-1 indicate that the two inputs before the current input, the input one before the current input, and the current input are all [one character] inputs.

Further, in the condition pattern, application pattern, and application command, Δ and ■ indicate AND and OR of the conditions, respectively.

1, that is, AAB is equivalent to AANDB (A and B), and AVB is equivalent to AQRB (A or B).'' In the example of the input history file in (a) of Figure 6, the condition pattern of the matching rule in (b) is Therefore, the applied message number given by the condition pattern (message a, message b, message C in the example) and applied command number (Prog 1 in 'tl'lj) are obtained.The applied message number given there The message corresponding to is extracted from the message file ($2, FIG. 8) and output to the display device (step 27 in FIG. 5).

Therefore, three messages corresponding to message (a), message (b), and message (C) in FIG. 6(C) are output to the display device.

Next, the command corresponding to the applied command number is extracted from the command file (FIG. 2, 9) and sent to the usage function utility section for execution (FIG. 5, step 28). After this is completed, the input is read from the human input device (FIG. 1).

If the flag of the response message is completed (interrupted) (F), the collection of input fertility history is ended (step 25 in FIG. 5).

After that, the personal controller performs a termination operation (fifth
Figure step 29). A series of processes and operations are performed in this manner.

As described above, when displaying error messages and guides, an appropriate message can be given to the user by using the user's input history. Therefore, the number of erroneous operations is greatly reduced, and operability is improved.

Note that the present invention is not limited to the above embodiments.

For example, even if the response message file flag in Figure 5 is normal, it is possible to search for applicable rules in the input history file and matching file and display a guide message in addition to the response message. It is. Furthermore, in the above embodiment, the input history and matching file are searched when the input information is sent to the usage function utility section and a response message is returned, but this is not limited to this. Before sending the information to the functional utility section, it is possible to search the five-component matching file and the input history file, search for applicable rules, and actually apply and execute the rules to detect errors in advance.

[Brief explanation of drawings]

@Figure 1 is a block diagram of an embodiment of the present invention, Figure 2 is an explanatory diagram of the files necessary for the present invention in the device, and Figure 3 is a block diagram of the device between devices. 4 is a diagram showing a response message sent from the usage function utility unit to the personal controller; FIG. 5 is a six-step flow diagram of the present invention (this shows the processing flow in the personal controller of the control device); FIG. 6 is a diagram showing an example of the contents of an input history file, an example of a matching rule, an example of a message, and an example of a command, which are used to explain the present invention. 1...Input device@, 2...Display device, 3...External 4
1 storage device, 4... internal storage device, 5... wholesale 11 wholesale, 6... input history file, 7... matching rule file, 8... message file, 9...
Command file, 10...Personal controller, 11...Used function utility section, 12-14...
・Used function utility department response message, 15-1
9...Explanation and explanation of each step of the processing flow O- of the present invention.

Claims (1)

[Claims] An input means for inputting a user code and input information, an input history storage means for storing a history of input information for each user code, and a characteristic pattern of the history of input information and a message corresponding to this characteristic pattern. The control means includes a stored matching rule storage means, a control means for processing a usage function based on the input information inputted from the input means, and an output means for outputting the usage function processed by the control means. writes the history of the input information to the input history storage means in correspondence with the user code inputted from the input means, and the input history information stored here corresponds to the characteristic pattern stored in the matching rule storage means. A computer with a guide function, characterized in that when a match occurs, a message stored in correspondence with this feature pattern is output to the output means.