Information processing systems and their control methods

Abstract

With conventional technology, a problem arose in that menu screens had many buttons displayed because only one action could be assigned to each button. [Solution] In the information processing system, the MFP has a menu display unit, and the menu screen displays buttons 511 to 516. When button 511 is pressed, the MFP controls whether to execute the process associated with the pressed button or open the settings screen for that process, based on areas 601 and 602 within the pressed button.

Description

Technical Field

[0001] The present invention relates to cooperation technology in a plurality of information processing apparatuses.

Background Art

[0002] In recent years, image processing apparatuses (e.g., MFPs) installed in offices generally have menu screens. The menu screen is a screen for allowing a user to select which application (hereinafter referred to as "app") to call from a plurality of applications installed in the MFP. In the menu screen, an app is called by pressing a button.

[0003] Also, a technique for displaying a button for calling an app by giving a specific setting value to the app on the menu screen has been disclosed (e.g., Patent Document 1). When the button is pressed, a setting screen of the app reflecting the setting value is displayed, or processing of the app reflecting the setting value is executed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, with conventional technology, only one action could be assigned to a single button. Therefore, in order to allow a user to choose between two actions—for example, executing an application process with predetermined settings when a button is pressed, and opening the application's settings screen when a button is pressed—two buttons corresponding to each action must be displayed on the menu screen. In other words, in a device where multiple types of applications can each perform multiple types of actions, in order for the user to select which application performs which action, a large number of buttons must be displayed on the menu screen. This makes it cumbersome for the user to find the desired button. [Means for solving the problem]

[0006] An image processing apparatus characterized by having a display means for displaying a button for executing a process, and a control means for controlling whether to execute a process associated with the pressed button or open a settings screen for the process, based on the area within the pressed button, when the button is pressed. [Effects of the Invention]

[0007] According to the present invention, without increasing the number of buttons displayed on the menu screen, when a button is pressed by the user, it is possible to switch between executing the application's process or opening the application's settings screen in response to the button press. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows the configuration of an information processing system in an embodiment of the present invention. [Figure 2] This is a block diagram showing the hardware configuration of an MFP in an embodiment of the present invention. [Figure 3] This is a block diagram showing the hardware configuration of a file server and a user PC in an embodiment of the present invention. [Figure 4] This is a block diagram showing the software configuration of an MFP in an embodiment of the present invention. [Figure 5] This is an example of a button management table in an embodiment of the present invention. [Figure 6] This is an example of a menu screen in an embodiment of the present invention. [Figure 7] This is a sequence diagram showing the flow of a series of processes in an MFP according to an embodiment of the present invention. [Figure 8] This is a flowchart showing the processing of the MFP in an embodiment of the present invention. [Figure 9] This is a flowchart showing the processing of the MFP in an embodiment of the present invention. [Figure 10] This is an example of a button to be displayed on the menu screen in the second embodiment of the present invention. [Figure 11] This is an example of a button management table in a second embodiment of the present invention. [Figure 12] This is a flowchart showing the processing of the MFP in a second embodiment of the present invention. [Figure 13] This is a flowchart showing the processing of the MFP in a second embodiment of the present invention. [Figure 14] This is a flowchart showing the processing of the MFP in the third embodiment of the present invention. [Figure 15] This is a block diagram showing the software configuration of an MFP in a fourth embodiment of the present invention. [Figure 16] This is an example of a user management table in a fourth embodiment of the present invention. [Figure 17] This is an example of a menu screen in the fourth embodiment of the present invention. [Figure 18] This is a flowchart showing the processing of the MFP in the fourth embodiment of the present invention. [Figure 19] This is a flowchart showing the processing of the MFP in the fourth embodiment of the present invention. [Figure 20] This is an example of an application settings screen in an embodiment of the present invention. [Figure 21] This is an example of a button to be displayed on a menu screen in an embodiment of the present invention.

Mode for Carrying Out the Invention

[0009] Hereinafter, the best mode for implementing the present embodiment will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential for the solution means of the invention.

[0010] (First Embodiment) FIG. 1 is a diagram showing an example of the system configuration of the information processing system of the present embodiment. This system is composed of an MFP 101, a file server 102, and a user PC 103 connected via a LAN (Local Area Network) 110. Devices on the LAN 110 can communicate with each other through their respective networks. FIG. 1 is an example of a typical network configuration, and each device may be located either on the LAN 110 or a WAN (not shown). Also, the number of each device may increase or decrease.

[0011] The MFP 101 is an example of an image processing device having a scanner and a printer. The file server 102 is a server having a network folder accessible from the MFP 101 and the user PC 103. For example, the image data scanned by the MFP 101 is transmitted to the file server 102, and the file server 102 stores the image data in a folder. The user PC 103 is a PC used by the user to perform business, and can transmit print data to the MFP 101 using a printer driver or the like by the operation of the user.

[0012] FIG. 2 is a block diagram showing the hardware configuration of the MFP 101. A control unit 210 including a CPU 211 controls the operation of the entire MFP 101. The CPU 211 reads out control programs stored in the ROM 212 and the HDD 214 and executes various control processes such as read control and transmission control. The RAM 213 is used as a temporary storage area such as the main memory and work area of the CPU 211. The HDD 214 stores image data and various programs.

[0013] The control unit interface (I / F) 215 connects the control unit (219) and the control unit (210). The control unit (219) is equipped with a liquid crystal display with touch panel functionality and a keyboard. The printer interface (I / F) 216 connects the printer (220) and the control unit (210). Image data to be printed by the printer (220) is transferred from the control unit (210) to the printer (220) via the printer interface (I / F) 216 and printed onto the recording medium by the printer (220). The scanner interface (I / F) 217 ​​connects the scanner (221) and the control unit (210). The scanner (221) reads the image on the document, generates image data, and inputs it to the control unit (210) via the scanner interface (I / F) 217. The network interface (I / F) 218 ​​connects the control unit (MFP101) to the LAN (LAN) 110. The network interface (I / F) 218 ​​sends and receives various information with other devices on the LAN 110.

[0014] Figure 3 is a block diagram showing the hardware configuration of the file server 102 and the user PC 103. The control unit 310, which includes the CPU 311, controls the operation of the entire device. The CPU 311 reads control programs stored in the ROM 312 and HDD 314 and executes various control processes. The RAM 313 is used as the main memory and temporary storage area for the CPU 311, such as the work area. The HDD 314 stores various programs and data. The display interface 315 connects the display unit 318 to the control unit 310. The keyboard interface 316 connects the keyboard 319 to the control unit 310. The CPU 311 recognizes instructions from the user via the keyboard 319 and displays a screen corresponding to the recognized instructions on the display unit 318. The network interface 317 connects the control unit 310 to the LAN 110. The network interface 317 sends and receives various information with other devices on the LAN 110.

[0015] Figure 4 is a software configuration diagram for the MFP101 of this embodiment. The CPU211 reads the programs stored in the HDD214 and ROM212 of the MFP101 into the RAM213 and executes them, thereby realizing the processing described later.

[0016] The button management unit 401 manages the buttons to be displayed on the MFP101's menu screen. The button management table 402 is a table that holds information about the buttons to be displayed on the MFP101's menu screen and is recorded in RAM 213 or HDD 214. The menu display unit 403 displays the menu screen on the operation unit 219. The menu display unit 403 displays the buttons held by the button management table 402 on the menu screen. The copy application 404 is an application that provides copy functionality. The print application 405 is an application that provides functionality to print (hereinafter referred to as held print) print jobs accumulated in the MFP101. The print application 405 temporarily saves print data received from an external device such as a user PC 103 to HDD 214 and prints it separately upon instruction from the user. The send application 406 is an application that provides functionality to send scanned image data to a destination specified by the user. One of the destinations can be a network folder on the file server 102. The fax application 407 is an application that provides fax functionality. Applications 404 through 407 are examples, and the MFP101 may have other applications.

[0017] Figure 5 shows an example of a button management table 402 according to this embodiment. Each row contains button information for one button, and in the button management table 402 in Figure 5, six buttons are defined in rows 511 to 516 as an example.

[0018] The button management table 402 has four columns: 501 to 504. Column 501, Button ID, defines an identifier to uniquely identify the button. Column 502, Button Name, defines the name of the button. Column 503, Called Application, defines the application (app) that is called when the button is selected by the user. Column 504, Setting Value, defines the setting value to be added as a parameter when calling the app. Here, the setting value is a value indicating the settings related to the app's functionality, and the parameter is a variable added when calling the app, containing information indicating the setting value and flags. Buttons with a value set in column 504 (for example, row 511) can call the app or execute a process with the setting value associated with the button reflected. Buttons with such associated setting values ​​will be referred to as custom buttons from now on. On the other hand, buttons with no value set in column 504 (for example, row 514) are buttons that call the app without adding any setting values ​​(hereinafter referred to as app buttons).

[0019] Figure 6 shows an example of the menu screen of the MFP101 according to this embodiment. Figure 6 displays six buttons, from button 511 to button 516, as defined in the button management table 402. As defined in the button management table 402, buttons 511, 512, and 513 are custom buttons, and buttons 514, 515, and 516 are application buttons.

[0020] The display of custom buttons will be explained using button 511 as an example. A custom button consists of two areas: area 601 and area 602. The behavior differs depending on whether the user presses area 601 or area 602. If the user presses area 601, the settings screen of the application defined in column 503 (called application) is called, reflecting the settings defined in column 504 (settings value). On the other hand, if the user presses area 602, the job of the application defined in column 503 (called application) is executed with the settings defined in column 504 (settings value). In other words, when area 602 is pressed, the process is executed immediately without opening a confirmation screen or settings screen.

[0021] Label 603 displays the button name defined in column 502. Label 604 displays the setting value defined in column 504, converted into a string according to certain rules. For example, only important setting values ​​for the app can be displayed, or only the difference from the standard setting value can be displayed. Here, the copy setting values ​​"partial," "black and white," and "single-sided" are shown. Label 605 displays a string to indicate to the user that pressing area 602 will execute the app's job. Icon 606 displays an image to indicate to the user that pressing area 601 will bring up the app's settings screen. Icon 607 displays an image to indicate to the user that pressing area 602 will execute the app's job. Button 511 is an example of a custom button display, and other displays are possible. For example, the area can be divided left and right, or only a part of the button can be used as the execution area.

[0022] The display of app buttons will be explained using button 514 as an example. An app button consists of a single area, and when the user presses the button, the app defined in the Called App 503 column is called. The label 608 displays the button name defined in the Button Name 502 column.

[0023] The page display area 609 shows the total number of pages in the menu screen and the currently displayed page. In the example in Figure 6, it shows that there are 3 pages in the menu screen and that page 1 is currently displayed. You can navigate between menu screens using flick gestures, etc.

[0024] In this embodiment, a button is used to call the application, but other forms, such as a list, may also be used for display.

[0025] The display format of custom buttons is not limited to the above format. Figure 21 shows another example of the display format of custom buttons. Buttons 2100, 2110, 2120, and 2130 in Figure 21 all refer to button 511. Buttons with the same function and properties are given the same number. Buttons 2100 and 2110 consist of two areas, area 2101 and area 2102. When the user presses area 2101, the job is executed with the defined settings, and when the user presses area 2102, the settings screen is opened with the defined settings reflected. As shown in the figure, the display formats of area 2101 and area 2102 may be different from each other. Label 2103 displays the button name. Label 2104 displays the setting value, which is a string representation of the setting value defined in column 504, based on certain rules. The label 2104 for button 2101 is "1 copy / black and white / double-sided," and the label 2104 for button 2102 is "1 copy." If the user presses area 2102 of button 2101, a settings screen can be opened that allows the user to change the number of copies, color settings, and single-sided / double-sided settings. If the user presses area 2102 of button 2102, a settings screen can be opened that allows the user to change only the number of copies.

[0026] Icon 2105 displays an image indicating the process corresponding to the button. Icon 2106 displays an image to show the user that pressing area 2101 will execute the application's job.

[0027] For button 2120, pressing icon 2107 opens a settings screen with the settings applied, while pressing area 2108 (other than icon 2107) executes the process with the defined settings. Icon 2106 indicates that pressing area 2108 will immediately execute the process. For users who don't frequently open the settings screen to change settings, a larger area 2108 for immediate execution is more convenient. Icon 2107 displays an image to indicate to the user that pressing it will open the settings screen.

[0028] In the case of button 2130, when the user presses icon 2106, the process is executed with the defined setting value, and when the user presses any area 2109 other than icon 2107, a settings screen with the setting value reflected opens. Unless the narrow area of ​​icon 2106 is pressed, the process will not be executed, thus preventing accidental execution due to misoperation.

[0029] Icons 2106 and 2107 may be hidden until the button is executed for the first time. For example, when a user presses the button for the first time, if the user is informed that pressing the button will immediately execute the process, icons 2106 and 2107 may be displayed on the button for the first time. Then, from the next time onward, pressing a specific area of ​​the button will immediately execute the process. These custom button display methods may also be applied to app buttons.

[0030] Figure 20 shows an example of the application settings screen that is called up when the user presses area 601 of button 511 on the menu screen. Since the application called by button 511, 503, is defined as "copy application 404", the application being called is copy application 404. Figure 20 also reflects the settings defined in column 504 of the settings for button 511.

[0031] Label 2001 displays the name of the called application. Areas 2002-2006 display the current settings of copy application 404. The settings for button 511, defined in column 504, are "1 copy," "black and white," and "single-sided," so area 2005 displays "1 copy," area 2002 displays "black and white," and area 2006 displays "single-sided." Default values ​​are displayed for settings not defined in column 504 (areas 2003, 2004).

[0032] Areas 2002-2006 are represented by double lines when the settings have been changed from the default values. In Figure 20, area 2002 (the default value for color selection is "Color") is represented by double lines because it has a setting different from the default value. Note that although the setting value in column 504 of button 511 is set to "1 copy", the default value for the number of copies is "1 copy", and since it is the same as the default value, area 2005 is represented by a single line.

[0033] Note that for areas 2002 to 2006, clicking on each area will display a dialog box for changing the respective settings, allowing the user to modify those settings.

[0034] Button 2007 is used to reset each setting to its default value. Button 2008 is used to start the job with the currently set settings.

[0035] Figure 7 is a sequence diagram showing the flow of a series of processes in this embodiment. It shows an example from button registration to the display of the menu screen (button) and application call by pressing the button. The CPU 211 reads the program stored in the HDD 214 of the MFP 101 into the RAM 213, analyzes it, and executes it, thereby executing the processing of the sequence in Figure 7 and each step of the flowchart described later.

[0036] First, in step S701, each application (404-407) instructs the button management unit 401 to register a button when the application is launched. In this sequence, the timing of button registration is set to when the application is launched, but this is just an example, and it may be done at a different time. The button registration instruction includes information from each column of the button management table 402 (button name, called application, setting value).

[0037] In step S702, the button management unit 401, having received the button registration instruction, saves the received button information to the button management table 402.

[0038] In step S703, the menu display unit 403 receives a command from the user to display the menu screen. In step S704, the menu display unit 403 requests the button management unit 401 to acquire button information. In step S705, the button management unit 401 returns the button information to the menu display unit 403 as a response to step S704. In step S706, the menu display unit 403 displays the menu screen on the operation unit 219 based on the button information received in step S705.

[0039] In step S707, the menu display unit 403 receives the user's operation (button press). In step S708, the menu display unit 403 determines the application to call and the parameters to be added to the call based on the user's operation received in step S707. In step S709, the menu display unit calls the application according to the decision made in step S708. In step S710, the called application processes according to the parameters added to the call.

[0040] Figure 8 is a flowchart illustrating the processing of the MFP101 in this embodiment. It describes the process from receiving a request from the user to display the menu screen to displaying the menu screen on the operation unit 219. The flowchart in Figure 8 corresponds to steps S703 to S706 in the sequence diagram in Figure 7.

[0041] In step S801, the menu display unit 403 receives a request to display the menu screen. A request to display the menu screen may be an operation by the user to transition to the menu screen, or a system notification (for example, displaying the menu screen if there is no user operation for a certain period of time). In step S802, the menu display unit 403 reads the button information of the buttons to be displayed on the menu screen from the button management table 402 via the button management unit 401. In this embodiment, since the buttons to be displayed are the same for all users, all button information stored in the button management table 402 is read. On the other hand, different buttons may be displayed for each user, or buttons may have expiration dates. In that case, a column can be added to the button management table 402 to manage the necessary information for each button. In the following description, the group of button information obtained in step S802 will be called the "button list".

[0042] Steps S803 to S807 are steps for retrieving and processing button information one by one from the button list. In step S803, the menu display unit 403 retrieves one piece of button information from the button list for processing in the following steps. In step S804, it is determined whether or not button information was retrieved in the previous step. If button information was retrieved, the menu display unit 403 proceeds to step S805; otherwise, it terminates the process. In the following description, when simply referred to as "button information," it refers to the button information retrieved in step S803.

[0043] In step S805, the menu display unit 403 determines whether or not there is a setting value in the setting value column 504 of the button information. If there is a setting value, the menu display unit 403 proceeds to step S807; otherwise, it proceeds to step S806. In step S806, the menu display unit 403 displays the application button corresponding to the button information. The application button is a button where each button consists of a single area (i.e., a button that is not divided into multiple areas), as shown for buttons 514 to 516 in Figure 6, and the button name 502 is displayed in the center of the button. Also, to identify which button it is when the user presses it, a button ID 501 is associated as button data. After step S806, the process returns to step S803.

[0044] In step S807, the menu display unit 403 displays custom buttons corresponding to the button information. As shown for buttons 511 to 513 in Figure 6, each custom button is composed of multiple areas (i.e., a single button divided into multiple areas), and information such as the button name 502 and setting value 504 is displayed on the button. In addition, a button ID 501 is associated with the button as data to identify which button it is when the user presses it. After step S807, the process returns to step S803.

[0045] Figure 9 is a flowchart illustrating the processing of the MFP101 in this embodiment. It describes the process of detecting user operations on the menu screen shown in the flowchart of Figure 8 and calling an application in response to those operations. The flowchart in Figure 9 corresponds to the processes from steps S707 to S710 in the sequence diagram of Figure 7.

[0046] In step S901, the menu display unit 403 detects user operation on the menu screen. In step S902, the menu display unit 403 determines whether the user operation detected in the previous step corresponds to a button press. If the menu display unit 403 determines that the user operation is a button press, it proceeds to step S903; otherwise, it terminates the process. In the following description, the button pressed by the user in step S901 will be referred to as the "pressed button". In step S903, the menu display unit 403 uniquely identifies the button from the button ID 501 associated with the pressed button and obtains the button information from the button management table 402. In the following description, when simply referred to as "button information," it refers to the button information obtained in step S903.

[0047] In step S904, the menu display unit 403 determines whether the button to be pressed is a divided-area button (i.e., a custom button). Whether or not it is a divided-area button is determined by whether or not a value is defined in the setting value column 504 of the button information. If the button to be pressed is a divided-area button, the menu display unit 403 proceeds to step S906; otherwise, it proceeds to step S905.

[0048] In step S905, the menu display unit 403 calls the application corresponding to the pressed button without assigning any settings. The application called is the application defined in the button information call application column 503. After that, the menu display unit 403 proceeds to step S909. The processing in step S909 will be described later.

[0049] In step S906, the menu display unit 403 determines which area of ​​the button the user pressed in step S901. As an example of this determination, we will use button 511 in Figure 6. If the area pressed by the user is the "setting area" (i.e., area 601), the menu display unit 403 proceeds to step S907, and if the area pressed by the user is the "execution area" (i.e., area 602), it proceeds to step S908.

[0050] In step S907, the menu display unit 403 calls the application corresponding to the pressed button, adding parameters including the setting value. The application to be called is the application defined in the button information call application column 503. The parameters to be added are the setting value defined in the button information setting value column 504 and an instruction to display the setting screen without executing the job when called (execution flag OFF). After that, the menu display unit 403 proceeds to step S909.

[0051] In step S908, the menu display unit 403 calls the application corresponding to the pressed button with parameters attached. The application to be called is the application defined in the button information call application column 503. The parameters to be attached are the setting value defined in the button information setting value column 504 and an instruction to start the execution of the job when called (execution flag ON). After that, the menu display unit 403 proceeds to step S909.

[0052] In step S909, the called application processes according to the parameters provided at the time of the call. For example, if the parameters do not contain any settings, the application is displayed in its initial state. If the parameters contain both a setting and the execution flag OFF, the application displays a settings screen reflecting the settings. If the parameters contain both a setting and the execution flag ON, the application starts executing the job with the provided settings.

[0053] As described above, the procedure in this embodiment allows for two processes to be performed depending on the area where a button is pressed: either calling up the settings screen or executing a process. This improves user convenience.

[0054] Furthermore, in this embodiment, the decision to divide the button area was made based on whether or not the button had a configurable value, but this is not limited to this. For example, the decision to divide the button area could also be made based on the type of application that is called when the button is pressed. Moreover, even if the button does not have a configurable value, the button area could be divided, and different processes could be assigned to each area, such as opening the application's initial settings screen or executing the application with its initial settings.

[0055] (Second embodiment) In the first embodiment, an example was described in which a button with a set value is divided into two areas. Dividing the area into two is just one example; it may be divided into three or more areas. Furthermore, the area to which it is divided may be changed for each button. Therefore, in the second embodiment, an embodiment is described in which the number of areas to which it is divided is changed for each button. Since the second embodiment is a modification of the first embodiment, only the differences will be described.

[0056] Figure 10 illustrates an example of a button displayed on the menu screen in the second embodiment. Figure 10(a) shows an example where the button is divided into three areas. Button 1000 is defined in the button management table 402 in Figure 11, which will be described later. Button 1000 has three areas: areas 1001, 1002, and 1003. Area 1001 is equivalent to area 601 in Figure 6, and when the user presses area 1001, the application's settings screen is called up with the settings reflected. Area 1002 is equivalent to area 602 in Figure 6, and when the user presses area 1002, the application's job is executed. Area 1003 is an area that did not exist in Figure 6, and when the user presses area 1003, the application's settings screen is called up in its initial state without reflecting the settings.

[0057] Figure 10(b) shows an example where, in addition to the two areas shown by the custom button in Figure 6, areas for each setting value item are provided. Button 1010 is defined in the button management table 402 in Figure 11, which will be described later. Area 1011 is equivalent to area 601 in Figure 6, and when the user presses area 1011, the application's settings screen is called up with the settings values ​​reflected. Area 1012 is equivalent to area 602 in Figure 6, and when the user presses area 1012, the application's job is executed. Areas 1013, 1014, and 1015 each show the setting values ​​defined in setting value column 504 independently, and when the user presses these areas, a screen is displayed that changes only the setting value corresponding to the pressed area. For example, when the user presses area 1015, a screen is displayed that changes the resolution setting.

[0058] Figure 11 shows an example of a button management table 402 according to the second embodiment. A display format column 1101 has been added to the button management table 402 described in Figure 5. In the button management table 402 of Figure 11, six buttons are defined in rows 1111 to 1116, but since the contents of columns 501 to 504 are the same as in Figure 5, only the display format column 1101 will be explained.

[0059] Display format column 1101 defines the shape in which buttons are displayed on the menu screen. In this embodiment, three display methods are set as an example. "Type A" is a method that divides the display into two areas, as described in the first embodiment for custom buttons. "Type B" is a method that divides the display into three areas, as shown in Figure 10(a). "Type C" is a method that provides areas for each setting value, as shown in Figure 10(b). These display methods are just examples, and other display methods may be provided.

[0060] Figure 12 illustrates the menu screen display process in the second embodiment. Figure 12 is a flowchart derived from Figure 8. Only the differences from Figure 8 will be explained. The difference from Figure 8 is that steps S1201 to S1204 are processed instead of step S807.

[0061] In step S1201, the menu display unit 403 refers to the display format column 1101 of the button management table 402 to determine the subsequent processing. If the display format column 1101 is "Type A", the menu display unit 403 proceeds to step S1202; if it is "Type B", it proceeds to step S1203; and if it is "Type C", it proceeds to step S1204.

[0062] In step S1202, the menu display unit 403 displays the custom buttons corresponding to the button information, dividing them into two areas as shown in Figure 6, 511. After step S1202, the process returns to step S803.

[0063] In step S1202, the menu display unit 403 displays the custom buttons corresponding to the button information, dividing them into two areas as shown in Figure 6, 511. After step S1202, the process returns to step S803.

[0064] In step S1203, the menu display unit 403 displays the custom buttons corresponding to the button information, divided into three areas as shown in Figure 10(a). After step S1203, the process returns to step S803.

[0065] In step S1204, the menu display unit 403 displays the custom buttons corresponding to the button information, divided into areas for each set value as shown in Figure 10(b). After step S1204, the process returns to step S803.

[0066] Figure 13 illustrates the process of calling an application from the menu screen in the second embodiment. Figure 13 is a flowchart that is a modified version of Figure 9. Only the differences from Figure 9 will be explained.

[0067] Instead of step S906, a conditional branch is performed in step S1301. In step S1301, the menu display unit 403 determines which area of ​​the button the user pressed in step S901. As an example of this determination, button 511 in Figure 6 and buttons 1000 and 1010 in Figure 10 will be used for explanation. If the area pressed by the user is one of the "setting value areas" (i.e., any of areas 1013, 1014, or 1015), the menu display unit 403 proceeds to step S1302. If the area pressed by the user is one of the "setting areas" (i.e., any of areas 601, 1001, or 1011), the menu display unit 403 proceeds to step S907. If the area pressed by the user is one of the "execution areas" (i.e., any of areas 602, 1002, or 1012), the menu display unit 403 proceeds to step S908. Furthermore, if the area pressed by the user is the "Set from the beginning" area (i.e., area 1003), the menu display unit 403 proceeds to step S905.

[0068] In step S1302, the menu display unit 403 calls the application corresponding to the pressed button with parameters attached. The application to be called is the application defined in the button information call application column 503. The parameters attached are instructions to display a settings screen that changes only the setting values ​​defined in the button information setting value column 504 and the setting items in the area determined in step S1301.

[0069] In step S1303, the called application processes according to the parameters provided at the time of the call. The processing when the previous step is steps S905, 907, or S908 is the same as in Figure 9, so the explanation is omitted, and the explanation for the case when the previous step is step S1302 is given. When the previous step is step S1302, the application displays a settings screen, for example, as a pop-up, which allows the user to change only the notified settings. The settings screen may also display only the setting value to be changed, or it may be displayed in a state where other settings cannot be changed by disabling them. Furthermore, the job may be executed immediately after the settings are changed, or a confirmation screen may be displayed before the job is executed.

[0070] As described above, the procedure in this embodiment makes it possible to assign a wider variety of processes to each button, thereby improving user convenience.

[0071] (Third embodiment) The first and second embodiments described examples in which a button with a set value is divided into multiple areas. Dividing an area within a single button may result in each area becoming narrower depending on the design. In such cases, the user may press an area other than the one they intended. Therefore, the third embodiment describes an embodiment configured to prevent user errors by prompting the user for further action if there are multiple areas near the pressed location. The third embodiment is a modification of the second embodiment, so only the differences will be described.

[0072] Figure 14 illustrates the process of calling an application from the menu screen in the third embodiment. Since Figure 14 is a flowchart that is a modified version of Figure 13, only the differences from Figure 13 will be explained. The difference from Figure 13 is that the processes of steps S1401 to S1404 have been added between steps S904 and S1301.

[0073] In step S1401, the menu display unit 403 searches for an area that is within a certain distance from the position pressed by the user in step S901 (that is, an area that is at least partially contained within a circle with a radius of a certain distance centered on the position pressed by the user). For example, if the lower left corner of area 1014 is pressed in Figure 10(b), three areas are obtained: area 1014 and the adjacent areas 1012 and 1013. The certain distance used when searching for areas can be a value that is approximately the same as the size of a typical user's finger.

[0074] In step S1402, the menu display unit 403 determines whether there is only one region obtained in step S1401. If there is only one region obtained in step S1401, the menu display unit 403 proceeds to step S1301; otherwise, it proceeds to step S1403.

[0075] In step S1403, the menu display unit 403 displays a dialog box on the operation unit 219 with the multiple areas obtained in step S1401 as options, and waits for the user's selection. For example, if the areas obtained in step S1401 are areas 1012, 1013, and 1014, then "Start Execution," "Color Settings," and "Duplex Scan Settings" are presented as options.

[0076] In step S1404, the menu display unit 403 receives the selection made by the user in the dialog box and proceeds to step S1301, treating that selection as the user's clickable area. For example, if the user selects "Color Settings," in the determination in step S1301, it is determined that the user has clicked area 1013.

[0077] As described above, by following the procedure in this embodiment, when a user presses a button with divided areas, it becomes possible to prevent unintended processing from being executed even if the user presses a position where each area touches, thereby improving user convenience.

[0078] In this embodiment, a dialog box is displayed when the adjacent areas are pressed, but other methods may be used. For example, if there are multiple areas obtained in step S1402, the process may be terminated as if nothing was pressed. The user can then press the desired area again.

[0079] As another example, if there are multiple areas obtained in step S1402, the system may be configured to select one area based on a predetermined rule. For example, if there are two candidates, an area to open a settings screen and an area to issue an execution command, the area to open the settings screen may be prioritized to prevent unintended execution by the user. Also, if there are multiple setting areas as candidates, the one that the user changes most frequently may be prioritized.

[0080] (Fourth embodiment) In the first to third embodiments, an example was described in which multiple processes are assigned to a single button by dividing the custom button into multiple areas. In the fourth embodiment, an example is described in which multiple processes are switched for a single custom button using operation methods such as two-finger tap, double tap, and pinch-out. Furthermore, since operation methods are a matter of personal preference, an example is described in which the operation method applied can be changed for each user. Since the fourth embodiment is a modification of the second embodiment, only the differences will be described.

[0081] Figure 15 is a software configuration diagram for the MFP101 of this embodiment. Since Figure 15 is a modified version of Figure 4, only the differences will be explained. The difference from Figure 4 is that a user management unit 1501 and a user management table 1502 have been added.

[0082] The user management unit 1501 manages user information. It authenticates users who use the MFP101 and manages information for each user. The user management table 1502 is a table that holds information for each user and is recorded in RAM213 or HDD214.

[0083] Figure 16 shows an example of the user management table 1502 in this embodiment. In the user management table 1502 in Figure 16, six user information entries are defined in rows 1611 to 1616 as an example.

[0084] The user management table 1502 has three columns: 1601 to 1603. Column 1601, User ID, defines an identifier to uniquely identify a user. Column 1602, Settings Call Operation, defines the method for calling the settings screen using a custom button displayed on the menu screen. Column 1603, Execution Call Operation, defines the method for instructing an execution action using a custom button displayed on the menu screen. For example, a user in row 1611 would tap the custom button to call the settings screen, or use a two-finger tap to instruct execution.

[0085] The user management table 1502 defines the assignment of processing based on the operation method, but it may also define the assignment of processing based on the division of button areas, as described in the first to third embodiments. For example, the user in row 1615 is defined to have different processing assigned to buttons based on the "Type A" area division (dividing the area into two) described in the second embodiment.

[0086] Figure 17 shows an example of the menu screen of the MFP101 according to this embodiment. Figure 17(a) is an example of the menu screen displayed when the user in row 1611 of the user management table 1502 logs into the MFP101. Image 1701 is an image to show that execution calls can be instructed by a two-finger tap operation. Label 1702 shows the user ID of the logged-in user. Button 1703 is a button for the user to log out.

[0087] Figure 17(b) is an example of the menu screen displayed when a user with row 1612 in the user management table 1502 logs into the MFP101. Image 1711 is an image to show that execution calls can be instructed by pressing and holding a button.

[0088] Although Figure 17 only shows images illustrating execution call operations, it may be configured to display images illustrating configuration call operations. Alternatively, the system may be configured to use labels instead of images for explanation.

[0089] Figure 18 illustrates the display process of the menu screen in the fourth embodiment. Figure 18 is a flowchart derived from Figure 12. Only the differences from Figure 12 will be explained. The differences from Figure 12 are that the user is identified by logging in before the operation (steps S1801 to S1802), and the display of the buttons is changed according to the user's operation method defined in the user management table 1502 (steps S1803 to S1805).

[0090] In step S1801, the user management unit 1501 performs user authentication based on the user's login operation. In the following description, the user who logged in in step S1801 will be referred to as the "logged-in user". In step S1802, the menu display unit 403 obtains the login user's operation method on the menu screen (setting call operation column 1602, execution call operation column 1603) from the user management table 1502.

[0091] In step S1803, the menu display unit 403 determines whether the assignment of settings call and execution call processing is defined by "area division" of buttons in the menu screen of the logged-in user obtained in the previous step. If it is defined as "area division", the menu display unit 403 proceeds to step S1804; otherwise, it proceeds to step S1805.

[0092] In step S1804, the menu display unit 403 distributes subsequent processing based on the type of area division defined in the login user's settings call operation column 1602 and the execution call operation column 1603. If the type of area division is "Type A", the menu display unit 403 proceeds to step S1202; if it is "Type B", it proceeds to step S1203; and if it is "Type C", it proceeds to step S1204.

[0093] In step S1805, the menu display unit 403 displays custom buttons corresponding to the button information. At that time, images showing the operation method are attached to the buttons, as shown in images 1701 and 1711 in Figure 17.

[0094] Figure 19 illustrates the process of calling an application from the menu screen in the fourth embodiment. Since Figure 19 is a flowchart that is a modified version of Figure 13, only the differences from Figure 13 will be explained. Note that the processing from step S1301 onwards in Figure 13 is the same in this embodiment as well, so it is omitted from the diagram.

[0095] In step S1901, the menu display unit 403 determines whether the user operation detected in the previous step is an operation on a button, based on whether it is an operation on the area where the button is drawn. If the menu display unit 403 determines that the user operation is an operation on a button, it proceeds to step S1902; otherwise, it terminates the process. In the following description, the button operated by the user in step S901 will be referred to as the "operation button".

[0096] In step S1902, the menu display unit 403 determines whether the operation method on the menu screen for the logged-in user (setting call operation column 1602 and execution call operation column 1603 of the user management table 1502) is defined as "area division". If the operation method on the menu screen for the logged-in user is defined as "area division", the menu display unit 403 proceeds to step S1301 in the flowchart of Figure 13; otherwise, it proceeds to step S1903.

[0097] In step S1903, the menu display unit 403 determines whether the operation button is an application button. If the operation button is an application button, the menu display unit 403 proceeds to step S905; otherwise, it proceeds to step S1904.

[0098] In step S1904, the menu display unit 403 determines whether the operation performed by the user in step S901 matches an operation defined in the setting call operation column 1602. If the operations match, the menu display unit 403 proceeds to step S1904; otherwise, it proceeds to step S1905.

[0099] In step S1905, the menu display unit 403 determines whether the operation performed by the user in step S901 matches an operation defined in the execution call operation column 1603. If the operations match, the menu display unit 403 proceeds to step S908; otherwise, it terminates the process.

[0100] As described above, the procedure in this embodiment makes it possible to perform multiple processes depending on the user's operation on a single custom button, thereby improving user convenience. In this embodiment, a configuration was shown where the user logs in and setting call operations and execution call operations are defined for each user. However, this is not the only configuration; default settings for setting call operations and execution call operations can be maintained and applied to users who are not logged in.

[0101] (Other embodiments) The present invention can also be realized by performing the following information processing. This processing involves supplying software (programs) that realize the functions of the embodiments described above to a system or device via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or device reading and executing the program.

Claims

[Claim 1] A display means that displays a button for executing a process, When a button is pressed, a control means controls whether to execute a process associated with that button or open a settings screen for that process, based on the area within the pressed button. An image processing apparatus characterized by having

Images