JP6828533B2 - Programs and information processing equipment - Google Patents

Description

The present invention relates to a program and an information processing device.

For example, if a display item such as a menu screen is displayed or deleted at a timing not intended by the user, when the user performs some operation, an operation of another display item such as an icon or button not intended by the user is executed. It may be done.

Conventionally, there has been known a technique capable of suppressing the execution of an operation unintended by the user by temporarily disabling the touch operation at the timing of displaying / erasing the screen without the user operation. (See, for example, Patent Document 1).

However, in the conventional technology, a display item is displayed as a mechanism for suppressing the execution of an operation unintended by the user by temporarily disabling the touch operation at the timing of displaying / erasing the screen. The program itself had to implement it.

An object of the embodiment of the present invention is to provide a program capable of suppressing the execution of an operation unintended by the user by a general-purpose mechanism.

In order to achieve the above-mentioned problem, claim 1 of the present application is a monitoring control target screen registration receiving means for receiving a selection of the screen to be monitored and controlled from a user from the history of the screen displayed on the display unit, and the display. The display detecting means for detecting the display of the screen on the unit, the operation detecting means for detecting the operation by the user, and the monitoring control in which the screen whose display on the display is detected by the display detecting means is selected by the user. The target screen is a program for functioning as a determination means for invalidating the operation by the user detected by the operation detection means for a predetermined time.

According to the embodiment of the present invention, it is possible to prevent the user from executing an operation unintended by the general-purpose mechanism.

It is a hardware block diagram of an example of a computer. It is a processing block diagram of an example of the computer which concerns on this embodiment. It is a sequence diagram of an example of the process of registering a monitoring control target dialog. It is a block diagram of an example of the whole dialog history database. It is an image diagram of an example of a dialog selection screen. It is an image diagram of an example of a dialog registration screen. It is an image diagram of an example of a dialog editing screen. It is a block diagram of an example of a monitoring control target dialog database. It is a sequence diagram of an example of the process of editing a monitoring control target dialog database. It is a sequence diagram of an example of processing when a dialog is displayed. It is a sequence diagram of an example of processing when a dialog is cleared.

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

<Hardware configuration>
The dialog display program and the dialog monitoring control program described later are executed by a computer having a hardware configuration as shown in FIG. 1, for example. FIG. 1 is a hardware configuration diagram of an example of a computer.

The computer 500 shown in FIG. 1 includes an input device 501, a display device 502, an external I / F 503, a RAM 504, a ROM 505, a CPU 506, a communication I / F 507, an HDD 508, and the like, and each of them is connected to each other by a bus B. The input device 501 and the display device 502 may be connected and used when necessary.

The input device 501 includes a keyboard, a mouse, a touch panel, and the like, and is used for the user to input each operation signal. The display device 502 includes a display and the like, and displays the processing result by the computer 500.

The communication I / F 507 is an interface for connecting the computer 500 to various networks. As a result, the computer 500 can perform data communication via the communication I / F 507.

The HDD 508 is an example of a non-volatile storage device that stores programs and data. The stored programs and data include an OS, which is basic software that controls the entire computer 500, and an application that provides various functions on the OS. The computer 500 may use a drive device (for example, a solid state drive: SSD) that uses a flash memory as a storage medium instead of the HDD 508.

The external I / F 503 is an interface with an external device. The external device includes a recording medium 503a and the like. As a result, the computer 500 can read and / or write to the recording medium 503a via the external I / F 503. The recording medium 503a includes a flexible disk, a CD, a DVD, an SD memory card, a USB memory, a SIM card, and the like.

The ROM 505 is an example of a non-volatile semiconductor memory (storage device) capable of holding programs and data even when the power is turned off. The ROM 505 stores programs and data such as BIOS, OS settings, and network settings that are executed when the computer 500 is started. The RAM 504 is an example of a volatile semiconductor memory (storage device) that temporarily holds programs and data.

The CPU 506 is an arithmetic unit that realizes control and functions of the entire computer 500 by reading a program or data from a storage device such as a ROM 505 or an HDD 508 onto the RAM 504 and executing processing. The CPU 506 may be realized by one processor or a plurality of processors.

In the present embodiment, various processes as shown in FIG. 2 can be realized by executing the dialog display program and the dialog monitoring control program described later on the computer 500 shown in FIG.

<Software configuration>
FIG. 2 is a processing block diagram of an example of a computer according to the present embodiment. Note that the processing block diagram of FIG. 2 omits configurations that are not necessary for the description of the present embodiment. By executing the dialog monitoring control program 10, the computer 500 shown in FIG. 2 has a dialog hook unit 11, a dialog display detection unit 12, an automatic recording unit for all dialog history, a dialog database editing UI unit 14 for monitoring control, and a dialog deletion. The detection unit 15, the key press & button click detection unit 16, the key press & button click valid / invalid determination unit 17, and the timer unit 18 are realized.

Further, the computer 500 shown in FIG. 2 realizes the dialog display unit 31 by executing the dialog display program 30. The dialog display program 30 is an OS, an application, or the like. When the dialog display unit 31 detects an unexpected event, it displays a dialog such as the event notification dialog 1000 to notify the user of the occurrence of the event. Unpredictable events include, for example, email reception and error occurrence.

The dialog hook unit 11 of the dialog monitoring control program 10 hooks the dialog display API (application program interface) of the OS, and monitors the display of a dialog such as the event notification dialog 1000 by the dialog display unit 31. The dialog display detection unit 12 detects that the event notification dialog 1000 has been displayed, and notifies the all dialog history automatic recording unit 13.

The all dialog history automatic recording unit 13 records the history of all the displayed dialogs in the all dialog history database 21. The monitoring control target dialog database editing UI unit 14 displays, for example, the icon of the dialog monitoring control program 10 in the task tray at the lower right of the screen. The task tray is an example of an area for displaying the icon of the running program.

When the user determines that there is a possibility of performing an unintended operation on a button of a certain dialog, he / she right-clicks the icon in the task tray and selects "Register dialog" from the menu. In response to the user's selection of "register dialog", the monitoring control target dialog database editing UI unit 14 displays the dialog selection screen and allows the user to select the dialog to be registered in the monitoring control target dialog database 22. Details of the dialog selection screen will be described later. When the user right-clicks the icon in the task tray and selects "Edit Dialog Database" from the menu, the monitoring control target dialog database editing UI unit 14 displays the dialog editing screen, and the user displays the monitoring control target dialog database 22. Allows you to edit. Details of the dialog edit screen will be described later.

When the dialog display detection unit 12 detects that the dialog has been displayed, the dialog display detection unit 12 notifies the key press & button click valid / invalid determination unit 17 following the notification to the all dialog history automatic recording unit 13. The key press & button click valid / invalid determination unit 17 refers to the monitoring control target dialog database 22 and determines whether or not the displayed dialog is the monitoring control target. When it is determined that the target is the monitoring control target, the key press & button click valid / invalid determination unit 17 performs processing according to the contents of the monitoring control target dialog database 22.

For example, if a key press & button click valid / invalid determination unit 17 describes an automatic execution action, the action is automatically executed. Further, the key press & button click valid / invalid determination unit 17 notifies the timer unit 18 if a suppression time other than "0 seconds" is described in the suppression time after the dialog is displayed, and activates a timer for measuring the suppression time.

The dialog deletion detection unit 15 detects that the dialog such as the event notification dialog 1000 has been deleted, and notifies the key press & button click validity / invalidity determination unit 17. When the deletion of the dialog is notified, the key press & button click valid / invalid determination unit 17 refers to the monitoring control target dialog database 22. If the suppression time after clearing the dialog is described as something other than "0 seconds", the key press & button click valid / invalid determination unit 17 notifies the timer unit 18 and activates a timer for timing the suppression time.

The key press & button click detection unit 16 detects a key press or mouse click operation by the user, and notifies the key press & button click valid / invalid determination unit 17. When the key press & button click valid / invalid determination unit 17 is notified of the key press or mouse click operation by the user, the user presses the key or mouse by referring to the description of the monitoring control target dialog database 22 and the status of the timer unit 18. Determine whether to disable the click operation of.

If it is determined to invalidate, the key press & button click valid / invalid determination unit 17 invalidates the key press or mouse click by the user. There are two types of invalidation of key presses and mouse clicks: invalidation after the dialog is displayed and invalidation after the dialog is deleted.

As described above, the dialog monitoring control program 10 which is a resident program has the following functions. First, the dialog monitoring control program 10 has a function of hooking the dialog display API of the OS and monitoring the dialog display by the OS or the application. The dialog monitoring control program 10 has a function of recording in the entire dialog history database 21 every time the OS or application displays a dialog.

Further, the dialog monitoring control program 10 has a function of referencing and updating the monitoring control target dialog database 22 for managing a dialog that does not accept a key press or a mouse click operation by a user for a predetermined time after display. The dialog monitoring control program 10 has a GUI (graphical user interface) for registering the dialog in the monitoring control target dialog database 22 when the user finds a dialog to be monitored and controlled.

When a dialog matching the registration of the dialog database 22 to be monitored and controlled is displayed, the dialog monitoring control program 10 does not accept key presses or mouse click operations until a predetermined time elapses after the dialog is displayed. Has a function. Further, the dialog monitoring control program 10 has a function of automatically executing the action if the action to be automatically executed is registered in the monitoring control target dialog database 22.

Further, when the OS or the application deletes the dialog matching the registration of the monitoring control target dialog database 22, the dialog monitoring control program 10 processes the same as the display of the dialog matching the registration of the monitoring control target dialog database 22. The dialog monitoring control program 10 has a function of not accepting a key press or a mouse click operation until a predetermined time elapses after the dialog is cleared.

When the OS is Windows (registered trademark), the dialog display API includes, for example, MessageBox (), MessageBoxEx (), DialogBox (), and the like. A technique for changing the operation of the API by hooking the API of the OS is known. For example, when the OS is Windows (registered trademark), it is conceivable to execute the global hook using the SetWindowsHookEx () API.

<Processing>
<< Registration of monitoring control target dialog >>
FIG. 3 is a sequence diagram of an example of the process of registering the monitoring control target dialog. In step S11, the dialog hook unit 11 hooks the dialog display API of the OS and monitors the display of a dialog such as the event notification dialog 1000 by the dialog display unit 31.

In step S12, the dialog display detection unit 12 detects that the event notification dialog 1000 has been displayed, and notifies all dialog history automatic recording units 13. Proceeding to step S13, the all dialog history automatic recording unit 13 transmits the information of the displayed dialog to the all dialog history database 21. In step S14, the all dialog history database 21 records the information of all the displayed dialogs as shown in FIG. 4, for example.

FIG. 4 is a configuration diagram of an example of the entire dialog history database. The full dialog history database 21 has items such as a display date and time, an application name, an API, dialog identification data, the first user action after display, and a pointer to image data of the dialog.

The display date and time represents the date and time when the dialog was displayed. The application name is the name of the dialog display program 30 that displayed the dialog. The API indicates a hooked dialog display API. The dialog identification data is an example of information for identifying a dialog, and is determined by the dialog monitoring control program 10 depending on, for example, the type of the dialog display API. In the example of FIG. 4, when the type of the dialog display API is MessageBox () or MessageBoxEx (), the character string displayed in the dialog is used as the dialog identification data. Further, in the example of FIG. 4, when the type of the dialog display API is DialogBox (), the combination of the parameter values of the dialog display function is used as the dialog identification data.

The first user action after display indicates the first user action received from the user after the dialog is displayed. The pointer to the image data of the dialog is the pointer to the image data of the displayed dialog.

In the all dialog history database 21, for example, the maximum number of items to be registered (for example, 300 items) may be set, and the items exceeding the maximum number of items to be registered may be automatically deleted in chronological order.

Returning to FIG. 3, when the user determines that there is a possibility of accidentally pressing the button of the dialog by displaying or deleting the dialog, in step S15, the user right-clicks the icon of the task tray to display the menu. The menu displayed by right-clicking the icon in the task tray includes "Register dialog", "Edit dialog database", "Exit dialog monitoring control program" and so on. The user selects "Register dialog" from the displayed menu.

Upon receiving the selection of "register the dialog" by the user, the monitoring control target dialog database editing UI unit 14 proceeds to step S16, and instructs the entire dialog history database 21 to provide the information of the recently displayed dialog. In step S17, the monitoring control target dialog database editing UI unit 14 reads the information of the recently displayed dialog from the entire dialog history database 21.

Proceeding to step S18, the monitoring control target dialog database editing UI unit 14 displays the dialog selection screen 1100 as shown in FIG. FIG. 5 is an image diagram of an example of the dialog selection screen. The dialog selection screen 1100 displays a list of dialogs based on the recently displayed dialog information read from the all dialog history database 21 in step S17. The user can select the dialog to be registered in the monitoring control target dialog database 22 by checking the selection check box from the list of dialogs displayed on the dialog selection screen 1100.

In step S19, when the cancel button 1102 is pressed by the user, the monitoring control target dialog database editing UI unit 14 deletes the dialog selection screen 1100 and returns to the state before right-clicking the icon in the task tray. When the registration button 1101 is pressed by the user with the selection check box checked, the monitoring control target dialog database editing UI unit 14 displays the dialog registration screen 1200 as shown in FIG. 6 in step S21.

FIG. 6 is an image diagram of an example of the dialog registration screen. The dialog registration screen 1200 has a registration date, an application, an image, a suppression timing, a suppression time, a time until the action is automatically executed, an action to be automatically executed, and a description as items. The registration date represents the date when the dialog is registered. The application represents a dialog display program 30 that displays a dialog. The image represents the image of the dialog to be registered.

The suppression timing, suppression time, time until automatic action execution, action to be automatically executed, and description are items that can be edited by the user. The suppression timing indicates whether the user's key press or mouse click operation is suppressed after the dialog is displayed or after the dialog is cleared.

The suppression time represents the time for suppressing a key press or a mouse click operation by the user after the dialog is displayed or the dialog is deleted. The time until the action is automatically executed represents the time until the action to be automatically executed is automatically executed. The action to be automatically executed represents an action to be automatically executed after the dialog is displayed or the dialog is cleared.

In step S22, when the cancel button 1202 is pressed by the user, the monitoring control target dialog database editing UI unit 14 deletes the dialog registration screen 1200 and returns to the state before right-clicking the icon in the task tray.

When the registration button 1201 is pressed, the monitoring control target dialog database editing UI unit 14 proceeds to step S24, and registers the information of the dialog that is the monitoring control target of FIG. 6 in the monitoring control target dialog database 22. Further, the process proceeds to step S25, and the monitoring control target dialog database editing UI unit 14 displays the dialog editing screen 1300 as shown in FIG.

FIG. 7 is an image diagram of an example of the dialog editing screen. In the dialog edit screen 1300, the information of the dialog of the monitoring control target registered from the dialog registration screen 1200 of FIG. 6 is added to the first display. In the dialog editing screen 1300 of FIG. 7, the item "valid?" Is added to the dialog registration screen 1200 of FIG. The item "Enabled?" Is a check box for selecting whether to enable monitoring control for the dialog of the line.

In step S26, the user can instruct the addition of the information of the dialog of the monitoring control target to the monitoring control target dialog database 22 by pressing the add button 1301 of the dialog editing screen 1300 of FIG. The user can instruct the monitoring control target dialog database 22 to edit the information of the monitoring control target dialog by clicking the line of the dialog editing screen 1300 of FIG. 7 and pressing the edit button 1302. Further, the user can instruct to delete the information of the dialog of the monitoring control target from the monitoring control target dialog database 22 by clicking the line of the dialog editing screen 1300 of FIG. 7 and pressing the delete button 1303.

Proceeding to step S27, the monitoring control target dialog database editing UI unit 14 can add, edit, or delete information on the monitoring control target dialog from the monitoring control target dialog database 22 in response to an instruction from the user. When the cancel button 1304 is pressed by the user, the monitoring control target dialog database editing UI unit 14 deletes the dialog editing screen 1300 and returns to the state before right-clicking the icon in the task tray.

FIG. 8 is a configuration diagram of an example of a monitoring control target dialog database. Is the monitoring control target dialog database 22 valid? , Registration date, application name, API, dialog identification data, pointer to dialog image data, suppression timing, suppression time, time until action automatic execution, action to be automatically executed, and explanation are included as items.

The items of the dialog database 22 to be monitored and controlled in FIG. 8 are edited from the items of the entire dialog history database 21 of FIG. 4, the items registered from the dialog registration screen 1200 of FIG. 6, or the dialog edit screen 1300 of FIG. It can be generated by the items.

<< Editing the monitoring control target dialog >>
FIG. 9 is a sequence diagram of an example of the process of editing the monitoring control target dialog database. The user who wants to edit the contents of the monitoring control target dialog database 22 right-clicks the icon in the task tray and selects "Edit dialog database" from the menu in step S31 of FIG.

In response to the user's selection of "editing the dialog database", the monitoring and controlling target dialog database editing UI unit 14 proceeds from step S31 to step S32 to display the dialog editing screen 1300 of FIG. Steps S33 to S34 are the same as the processes of steps S26 to S27 of FIG.

《Display dialog》
FIG. 10 is a sequence diagram of an example of processing when a dialog is displayed. In step S41, the dialog display detection unit 12 detects that the event notification dialog 1000 has been displayed.

When the dialog display detection unit 12 detects that the dialog has been displayed, the dialog display detection unit 12 notifies the key press & button click validity / invalidity determination unit 17. The key press & button click valid / invalid determination unit 17 proceeds to step S42, and inquires of the monitoring control target dialog database 22 whether or not the dialog detected in step S41 is recorded as the monitoring control target.

If the dialog detected in step S41 is recorded as a monitoring control target, the key press & button click valid / invalid determination unit 17 reads the record of the dialog from the monitoring control target dialog database 22 in step S43.

Proceeding to step S44, the key press & button click valid / invalid determination unit 17 determines whether or not the dialog detected in step S41 is recorded in the monitoring control target dialog database 22 and is a monitoring control target dialog.

If the dialog detected in step S41 is not recorded in the monitoring control target dialog database 22 or is not the monitoring control target dialog, the dialog monitoring control program 10 performs the task tray after the processing of steps S13 to S14 of FIG. Returns to the state before right-clicking the icon.

If the dialog detected in step S41 is recorded in the monitoring control target dialog database 22 and the dialog is the monitoring control target dialog, the key press & button click valid / invalid determination unit 17 proceeds to step S45.

In step S45, the key press & button click valid / invalid determination unit 17 refers to the monitoring control target dialog database 22 and determines whether or not the automatic execution action is described in the detected dialog. If the auto-execution action is described in the detected dialog, the key press & button click valid / invalid determination unit 17 proceeds to step S46 and automatically executes the action. If the auto-execution action is not described in the detected dialog, the key press & button click valid / invalid determination unit 17 skips the process of step S46.

In step S47, the key press & button click valid / invalid determination unit 17 determines whether or not a suppression time other than "0 seconds" is described in the suppression time after the dialog is displayed. If a suppression time other than "0 seconds" is described in the suppression time after the dialog is displayed, the key press & button click valid / invalid determination unit 17 proceeds to step S48, notifies the timer unit 18, and sets a timer for timing the suppression time. to start.

In step S49, it is assumed that the key press & button click detection unit 16 detects a key press or a mouse click operation by the user. Proceeding to step S50, the key press & button click detection unit 16 notifies the key press & button click validity / invalidity determination unit 17 of the key press or mouse click operation by the user. When the key press & button click valid / invalid determination unit 17 is notified of the key press or mouse click operation by the user, it determines whether or not the timer for counting the suppression time has expired.

If the timer for counting the suppression time has not expired, the key press & button click valid / invalid determination unit 17 proceeds to step S51 to invalidate the key press and mouse click by the user. If the timer for counting the suppression time has expired, the key press & button click valid / invalid determination unit 17 does not invalidate the key press or mouse click by the user. Further, in step S47, if the key press & button click valid / invalid determination unit 17 describes "0 seconds" in the suppression time after the dialog is displayed, the timer unit 18 is not notified and a timer for measuring the suppression time is set. Do not start.

In this way, when the dialog of the monitoring control target is displayed, the dialog monitoring control program 10 can invalidate the key press and the mouse click by the user according to the description of the monitoring control target dialog database 22. Note that the process of invalidating key presses and mouse clicks by the user generally uses a hook in the same manner as the dialog monitoring process. The process of hooking a key press or a mouse click by a user is a known technique.

In step S51, the dialog monitoring control program 10 may have a function of displaying a message to that effect when the key press or mouse click by the user is invalidated. Further, the dialog monitoring control program 10 may visually indicate that the key presses and mouse clicks are disabled by reducing the brightness of the dialog while the key presses and mouse clicks are disabled. ..

《Clear Dialog》
FIG. 11 is a sequence diagram of an example of processing when the dialog is deleted. In step S61, the dialog deletion detection unit 15 detects that the event notification dialog 1000 has been deleted.

When the dialog deletion detection unit 15 detects that the dialog has been deleted, the dialog deletion detection unit 15 notifies the key press & button click validity / invalidity determination unit 17. The key press & button click valid / invalid determination unit 17 proceeds to step S62, and inquires of the monitoring control target dialog database 22 whether or not the dialog whose deletion is detected in step S61 is recorded as the monitoring control target.

If the dialog whose deletion is detected in step S61 is recorded as the monitoring control target, the key press & button click valid / invalid determination unit 17 reads the record of the dialog from the monitoring control target dialog database 22 in step S63.

Proceeding to step S64, the key press & button click valid / invalid determination unit 17 determines whether or not the dialog whose deletion is detected in step S61 is recorded in the monitoring control target dialog database 22 and is the monitoring control target dialog. To do.

If the dialog whose deletion is detected in step S61 is not recorded in the monitoring control target dialog database 22 or is not the monitoring control target dialog, the dialog monitoring control program 10 is in the state before right-clicking the icon in the task tray. Return to.

If the dialog whose deletion is detected in step S61 is recorded in the monitoring control target dialog database 22 and the dialog is the monitoring control target dialog, the key press & button click valid / invalid determination unit 17 proceeds to step S65.

In step S65, the key press & button click valid / invalid determination unit 17 determines whether or not a suppression time other than “0 seconds” is described in the suppression time after the dialog is deleted. If a suppression time other than "0 seconds" is described in the suppression time after the dialog is cleared, the key press & button click valid / invalid determination unit 17 proceeds to step S66, notifies the timer unit 18, and sets a timer for timing the suppression time. to start.

In step S67, it is assumed that the key press & button click detection unit 16 detects a key press or a mouse click operation by the user. Proceeding to step S68, the key press & button click detection unit 16 notifies the key press & button click validity / invalidity determination unit 17 of the key press or mouse click operation by the user. When the key press & button click valid / invalid determination unit 17 is notified of the key press or mouse click operation by the user, it determines whether or not the timer for counting the suppression time has expired.

If the timer for counting the suppression time has not expired, the key press & button click valid / invalid determination unit 17 proceeds to step S69 to invalidate the key press and mouse click by the user. If the timer for counting the suppression time has expired, the key press & button click valid / invalid determination unit 17 does not invalidate the key press or mouse click by the user. Further, in step S65, if the key press & button click valid / invalid determination unit 17 describes "0 seconds" in the suppression time after the dialog is displayed, the timer unit 18 is not notified and a timer for measuring the suppression time is set. Do not start.

In this way, when the dialog of the monitoring control target is deleted, the dialog monitoring control program 10 can invalidate the key press and the mouse click by the user according to the description of the monitoring control target dialog database 22.

<Summary>
According to the embodiment of the present invention, the dialog display program 30 does not implement a mechanism for suppressing the execution of an operation not intended by the user due to the display or deletion of the dialog at a timing not intended by the user. In addition, it can be realized for general purposes. Further, according to the embodiment of the present invention, the user can select the dialog to be monitored and controlled and set the suppression time for key presses and mouse clicks.

The present invention is not limited to the above-described embodiment disclosed specifically, and various modifications and modifications can be made without departing from the scope of claims. It goes without saying that the hardware configuration of FIG. 1 described in this embodiment is an example, and there are various system configuration examples depending on the application and purpose. For example, the present invention can be applied to an image forming apparatus such as a multifunction device having an operation panel or a production printer. Further, the dialog described in the present embodiment is an example of a screen temporarily displayed for the user to input something or confirm a message.

The monitoring control target dialog database editing UI unit 14 is an example of the monitoring control target screen registration receiving means described in the claims. The dialog display detection unit 12 is an example of the display detection means. The key press & button click detection unit 16 is an example of the operation detection means. The key press & button click valid / invalid determination unit 17 is an example of the determination means. The dialog erase detection unit 15 is an example of the erase detection means.

10 Dialog monitoring control program 11 Dialog hook part 12 Dialog display detection part 13 All dialog history automatic recording part 14 Monitoring control target dialog Database editing UI part 15 Dialog erasure detection part 16 Key press & button click detection part 17 Key press & button click valid Invalidity judgment unit 18 Timer unit 21 All dialog history database 22 Monitoring and control target dialog database 30 Dialog display program 31 Dialog display unit 500 Computer 501 Input device 502 Display device 503 External I / F
503a Recording medium 504 RAM
505 ROM
506 CPU
507 Communication I / F
508 HDD
1000 Event notification dialog 1100 Dialog selection screen 1200 Dialog registration screen 1300 Dialog edit screen B bus

Japanese Unexamined Patent Publication No. 2015-132888

Claims (5)

Computer,
A monitoring control target screen registration receiving means that accepts a user to select the screen to be monitored and controlled from the history of the screen displayed on the display unit.
Display detecting means for detecting the display of the screen on the display unit,
An operation detecting means for detecting an operation by the user,
If the screen whose display on the display unit is detected by the display detecting means is the screen selected by the user to be the monitoring control target, the operation detecting means detects the screen by the user for a predetermined time. Judgment means for invalidating the operation,
A program to function as. The computer,
It functions as an erasure detection means for detecting the erasure of the screen from the display unit.
If the screen on which the erasure from the display unit is detected by the erasure detecting means is the screen selected by the user to be the monitoring control target, the operation detecting means may use the operation detecting means for a predetermined time. The program according to claim 1, wherein the detected operation by the user is invalidated. The monitoring control target screen registration receiving means receives from the user for each of the screens to be monitored and controlled, a setting of the predetermined time for invalidating the operation by the user detected by the operation detecting means. The program according to claim 2. Whether the monitoring control target screen registration receiving means sets the predetermined time for invalidating the operation by the user detected by the operation detecting means after displaying or deleting the screen to be monitored and controlled. The program according to claim 2 or 3, wherein the program is received from the user for each screen to be monitored and controlled. A monitoring control target screen registration receiving means that accepts from the user the selection of the screen to be monitored and controlled from the history of the screen displayed on the display unit, and
Display detecting means for detecting the display of the screen on the display unit,
An operation detection means for detecting an operation by the user,
If the screen whose display on the display unit is detected by the display detecting means is the screen selected by the user to be the monitoring control target, the operation detecting means detects the screen by the user for a predetermined time. Judgment means to invalidate the operation and
Information processing device with.

Images