Image processing device

Abstract

To solve the problem in which, in an image processing device, when the same user executes an application, it is common for differences to arise in some setting values depending on the purpose of use, however, generating buttons corresponding to setting values for each purpose of use results in an enormous number of buttons being displayed on the screen.SOLUTION: According to the image processing device of the present invention, when a call button for executing an application is selected, a setting button generated on the basis of the history of setting information changes is displayed. This allows a user to select setting values with fewer steps without increasing the number of call buttons displayed on the screen.SELECTED DRAWING: Figure 14

Description

Technical Field

[0001] The present invention relates to an image processing apparatus.

Background Art

[0002] In recent years, image forming apparatuses such as multifunction printers installed in offices and the like have become more multifunctional and highly functional, and are equipped with a number of convenient functions. Generally, in a multifunction printer, a plurality of installed applications (apps) such as copy and fax are selected from a portal screen to call up the setting screen of the app. Then, within the setting screen of the app (for example, copy), a set value (for example, 1 copy) is selected for each of the various setting items (for example, number of copies) when executing the app, and the app is executed.

[0003] However, the set values to be set when executing each app vary depending on the user. Therefore, in order to reduce the number of steps for repeating the settings for the app, there is known a multifunction printer that provides a button or the like on the portal screen for calling up the set values set for each user (for example, Patent Document 1). Such buttons include a button (custom button) for calling up the set values preset for each user, a button (history button) for calling up specific set values used in the past, a button (business specialization button) for calling up set values specialized for specific business, and the like.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] By the way, for example, it can be easily assumed that differences in some setting information occur depending on the purpose of use.

[0006] Therefore, the present disclosure aims to improve usability in response to differences in some setting information.

Means for Solving the Problem

[0007] The present disclosure includes display control means for displaying a predetermined soft key indicating a copy function in which setting information is registered, reception means for receiving a user operation, and execution means for executing processing of the copy function. When the reception means receives a user operation for changing a part of the setting information and a user operation for executing the processing of the copy function, the execution means executes the processing of the copy function using the changed setting information. Based on the execution means executing the processing of the copy function using the changed setting information, the display control means displays an area different from the predetermined soft key and for receiving a user operation reflecting the setting information of the copy function. When the reception means receives a user operation for reflecting the changed setting information in the copy function in the area for receiving a user operation for reflecting the setting information of the copy function and a user operation for displaying the setting screen of the copy function, the display control means displays the setting screen reflecting the changed setting information.

Effect of the Invention

[0008] According to the present invention, usability can be improved in response to differences in some setting information.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9A

Figure 9B

Figure 9C

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15A

Figure 15B

Figure 15C

Figure 16

Figure 17

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. However, each of the embodiments described below is merely an example and is not intended to limit the scope of the present invention. Also, not all combinations of the features described in the following embodiments are essential for the solution means of the present invention.

[0011] <Embodiment 1> <Internal Configuration of an Image Processing Apparatus> FIG. 1(a) is a block diagram showing an example of the internal configuration of an image processing apparatus according to an embodiment of the present invention. The image processing apparatus 1 is composed of, for example, an image forming apparatus such as a multi-function peripheral (MFP). As a basic configuration, the image processing apparatus 1 includes, for example, a controller unit 100 that controls each part within the image processing apparatus 1, an operation unit 112, a scanner unit 123, and a printer unit 125.

[0012] The operation unit 112 is composed of, for example, hard keys such as a numeric keypad for inputting numbers and a start key for executing processing, or a liquid crystal touch panel, and provides a user interface for the user to operate the image processing apparatus 1. The user can input information or perform settings on the image processing apparatus 1 by pressing the hard keys of the operation unit 112 or touching icons or buttons representing each setting item displayed on the touch panel.

[0013] The scanner unit 123 reads an image such as a document as image data. The printer unit 125 transports recording paper and prints the image data on the recording paper as a visible image. The controller unit 100 is connected to the scanner unit 123 via a bus 122 and is also connected to the printer unit 125 via a bus 124. In addition, the controller unit 100 is connected to other devices via a LAN 113, a public line (WAN) 114, or a wireless 115 to perform input / output control of image information and device information.

[0014] Next, each hardware inside the controller unit 100 will be described. The CPU 101 is a controller that controls the entire system. The RAM 102 is a system work memory for the CPU 101 to operate and is also an image memory for temporarily storing image data. The ROM 103 is a boot ROM that stores the system boot program. The HDD 104 is a hard disk drive that stores system software, image data, and all information related to wireless communication (wireless communication specifications) of the communication unit 111 described later. In the image processing apparatus 1, functions can be added by installing an application (hereinafter referred to as "app") that implements the desired function. By installing the app, application programs for running various functions on the image processing apparatus 1 are stored in the RAM 102 and the HDD 104.

[0015] The operation unit I / F 106 is an interface unit between the operation unit 112, which is a user interface (UI), and the controller unit 100, and outputs data to be displayed on the operation unit 112 to the operation unit 112. Also, it plays a role of transmitting information input by the user from the operation unit 112 to the CPU 101. The network unit 109 is connected to the LAN 113 and performs input / output of information. The MODEM 110 is connected to the WAN 114 and performs input / output of information. The communication unit 111 is connected to the wireless 115 via an antenna (not shown) and performs input / output of information. Also, the communication unit 111 can perform multiple types of wireless communication. Each of the above hardware components is arranged on the system bus 107.

[0016] The image bus I / F 105 is a bus bridge that connects the system bus 107 and the image bus 108 for transferring image data at high speed, and converts the data structure. The image bus 108 is defined by a PCI bus or IEEE 1394 or the like. For each device arranged on the image bus 108, the raster image processor (RIP) 116 expands the PDL code into a bitmap image. The device I / F 117 connects the scanner unit 123 or the printer unit 125 to the controller unit 100 and performs synchronous / asynchronous conversion of image data. The scanner image processing unit 118 corrects, processes, edits, etc. the input image data. The printer image processing unit 119 performs corrections, resolution conversion, etc. suitable for the printer unit 125 on the print output image data. The image rotation unit 120 rotates the image data. The image processing unit 121 performs compression / expansion processing such as JPEG, JBIG, MMR, MH on the image data, and format conversion processing such as PDF, TIFF, OCR, encryption.

[0017] Figure 1(b) is a configuration example of a system including the image processing apparatus 1. The image processing apparatus 1 is connected to the server 2, which is an external device, via the network 3 through the LAN 113, WAN 114, wireless 115, etc.

[0018] <Software Configuration of Image Processing Apparatus> Next, with reference to FIG. 2, the software configuration such as applications installed in the image processing apparatus 1 will be described. Examples of applications installed in the image processing apparatus 1 include a copy application 211, a fax application 212, a portal application 213, etc. The copy application 211 has functions related to the copy operation, and the fax application 212 has functions related to the fax operation for transmitting / receiving document data. Also, the portal application 213 has functions related to the portal. These applications are directly installed in the image processing apparatus 1 by the user, but may also be installed in the image processing apparatus 1 via the network unit 109, the communication unit 111, etc. The installed applications are stored in the RAM 102 and the HDD 104 as application programs.

[0019] In addition, each application such as the copy application 211, the fax application 212, and the portal application 213 installed in the image processing apparatus of FIG. 1 operates independently according to the instructions of the CPU 101. Therefore, the data used in each application is grouped for each application and stored in the HDD 104. Note that the data shared by each application is stored as common data in the common data section 220 set in the HDD 104. In addition, an application ID is assigned to each application installed in the image processing apparatus 1 as an identifier for identifying each application. The application ID is stored as common data in the common data section 220. In the following description, the application ID of the copy application 211 is "1000", the application ID of the fax application 212 is "1001", and the application ID of the portal application 213 is "1002".

[0020] The window control unit 201 determines which application to display on the operation unit 112 for a plurality of applications installed in the image processing apparatus 1. Each application such as the copy application 211 installed in the image processing apparatus 1 acquires data such as screen resources and setting values from the HDD 104 in response to a command from the window control unit 201 and performs display. For example, when the window control unit 201 receives a display request for the copy application 211 (application ID "1000"), it determines whether display by the function of the copy application 211 is possible. If display is possible, it notifies the copy application 211 of a display command. If there is setting information or the like for display, it is notified together with the display command. The copy application 211 that has received the display command acquires screen resources and setting values from the copy data section 221 set in the HDD 104 and performs display on the operation unit 112.

[0021] On the other hand, when displaying data not present in the copy data section 221, the copy application 211 notifies the window control unit 201 of a data request. The window control unit 201 that has received this acquires the corresponding data from the common data section 220 set in the HDD 104 and notifies the copy application 211. Then, the copy application 211 performs display of this data.

[0022] The fax application 212 can transmit and receive fax-related data to and from the fax data section 222 set in the HDD 104. Similarly, the portal application 213 can transmit and receive portal-related data to and from the portal data section 223 set in the HDD 104. In FIG. 2, the image processing apparatus 1 has been described as including three types of applications, namely, the copy application 211, the fax application 212, and the portal application 213. However, it may be configured to include other applications.

[0023] <Appearance of the operation unit equipped with a touch panel> FIG. 3 is an external view of the operation unit 112 provided in the image processing apparatus 1. The operation unit 112 is provided with a touch panel 300. The touch panel 300 is composed of, for example, a liquid crystal display unit, and a touch panel sheet is attached on the liquid crystal display unit. An operation screen and soft keys are displayed on the touch panel 300, and when a displayed soft key is touched, its position information is transmitted to the CPU 101.

[0024] In addition, the operation unit 112 is provided with various keys and buttons operated by the user. The start key 301 is used when instructing the start of the document reading operation. In the center of the start key 301, two-color LEDs 302 of green and red are provided, and the color indicates whether the start key 301 is in a usable state. The stop key 303 is used when stopping an operating operation. The numeric keypad 304 is composed of number and character buttons and is used to instruct the setting of the copy number of copies and the switching of the screen of the touch panel 300. The user mode key 305 is pressed when setting the device.

[0025] In the following description, the phrase "display a screen" means that the CPU 101 calls the corresponding screen display data and the screen control program from the HDD 104 or the RAM 102 and displays the screen display data on the operation unit 112. Similarly, when referring to operations on a touch panel such as "the user presses ○○" or various keys, it means that when the user presses a button, list, various keys, etc. displayed on the screen, the CPU 101 acquires position information from the operation unit 112 and executes the process instructed based on the screen control program.

[0026] In this embodiment, it is assumed that all information (coordinates, fonts, image resources, default setting values, etc.) displayed on each screen by each application is stored in either the RAM 102, ROM 103, or HDD 104. And the information stored in the RAM 102, ROM 103, HDD 104, etc. is displayed on the touch panel 300 of the operation unit 112 through the operation unit I / F 106 under the control of the CPU 101.

[0027] <User Authentication Process> FIG. 4 is a flowchart showing the user authentication process from when the image processing apparatus 1 is started until the screen of the logged-in user is displayed. The processes in the flowchart shown in FIG. 4 are realized by the CPU 101 executing a program recorded in the HDD 104 or the like. First, when the setting for identifying the user in the image processing apparatus 1 is ON, after the main body is started, the CPU 101 displays an authentication screen on the touch panel 300 (S401). FIG. 5 shows an example of the authentication screen 500 displayed on the touch panel 300. The authentication screen 500 has areas for inputting the user name 501 and password 502.

[0028] After the image processing apparatus 1 displays the authentication screen 500, it enters a state of waiting for the input of the user name and password (S402). When the user inputs the pre-registered user name and password respectively and presses the OK button 503, the CPU 101 compares whether the user name and password stored in the HDD 104 match the input user name and password (S403).

[0029] If the username and password do not match (NO in S404), the CPU 101 displays an error message on the touch panel 300 and displays the authentication screen 500 again (S405). On the other hand, if the username and password match (YES in S404), the CPU 101 calls the information associated with the user stored in the HDD 104 (S406). When the call is completed, the CPU 101 permits the user to log in (S407), saves the user whose login has been permitted as the logged-in user in the HDD 104 (S408). Thereafter, the CPU 101 displays on the touch panel 300 a portal screen reflecting the information of the called logged-in user (S409).

[0030] <Portal screen> Figure 6(1) is an example of a portal screen reflecting the settings of the logged-in user. On the portal screen of the logged-in user, a menu 600 for starting each application is displayed. On the portal screen, buttons such as application buttons 601 to 603 and custom buttons 604 to 606 are displayed as display objects. Note that the application buttons 601 to 603 are call buttons for instructing the execution of the application with default setting values, and the custom buttons 604 to 606 are call buttons for instructing the execution of the application with preset setting values. Note that objects such as buttons displayed on the screen for instructing the execution of such an application are called display objects. Also, for example, for the custom button 606, an icon 607, a button name 608, and a comment 609 for this button are displayed, but the displayed content is not limited to these.

[0031] The information for displaying the custom buttons 604 to 606 is managed as a button information table as shown in FIG. 10 and stored in the HDD 104. In the button information table shown in FIG. 10, an application ID, an action ID, icon information, display information, and user information are associated with and stored in the custom button No. assigned to the custom button. The icon information includes image data such as bitmap format to be displayed as an icon or a path to the image data. The display information includes a button name and a comment. The button name is the name of the button displayed on the icon. The comment is the content to be displayed as a comment on the icon. The user information includes a user name and a password. A custom button with user information is displayed on the portal screen of the logged-in user but not on the portal screens of other users. On the other hand, a custom button without user information is not limited to the logged-in user and is commonly displayed on the portal screens of all users. Note that the action ID will be described later.

[0032] Returning to the description of Fig. 6(1), the slider bar 610 indicates that the menu 600 can slide and move. By sliding the slider bar 610, pressing the arrow 611, or flicking within the menu 600, the CPU 101 receives the input and calls and displays the application buttons and custom buttons registered in the next area from the HDD 104. The name of the current logged-in user is displayed in the user name display area 612 at the upper right. In the example of Fig. 6(1), it represents that the current logged-in user is "User A". In the menu 600 of the portal screen (Fig. 6(1)), for example, when the copy button 601 is pressed by the user, the display of the touch panel 300 switches to the copy setting screen.

[0033] <Copy Setting Screen> Fig. 7(1) shows an example of the copy setting screen 700. On the copy setting screen 700, as setting information regarding the copy function, the set values for various setting items are displayed. In the example of Fig. 7(1), the copy setting screen 700 is composed of an area 701 for displaying the set values for each setting item such as color selection, magnification, paper size, and number of copies, and various buttons for displaying the set values for other setting items in rows. The preview button 702 is a button that previews the image data output according to the current set values. When the preview button 702 is pressed, a screen that details the current set values is displayed. Also, as buttons for setting the basic setting items of the copy function, there are a color selection button 703, a magnification setting button 704, a paper selection button 705, a finishing button 706, a duplex button 707, a density button 708, a document type button 709, and an ID card copy button 710. The other function button 711 is used to set the other setting items of the copy function.

[0034] The setting history button 712 is a button for displaying the history of the set values used in the past for the copy function. The frequently used setting button 713 is a button for displaying a screen for registering, editing, and calling frequently used set values. The home button 714 is a button for returning to the portal screen (Fig. 6(1)). The gear button 715 is a button for displaying the setting items related to the entire application.

[0035] In the example of Fig. 7(1), it can be seen from the area 701 for displaying the set values that the current set values are black and white for color, 100% for magnification, automatic for paper size, and 1 copy for the number of copies. Also, since the finishing button 706 is displayed in an inverted state, it can be seen that sorting is set. When the user places the document to be copied in this state on the scanner and presses the start key 301, the CPU 101 transmits an instruction to execute the copy with these set values to the image processing unit 121. Then, when the user presses the start key 301, the CPU 101 receives the start instruction and causes the image processing unit 121 to read the document by the scanner. After the reading is completed, the image processing unit 121 generates an output image. At that time, the image processing unit 121 reflects the functions related to the image set for the copy in the output image and outputs a copy of the input document.

[0036] <Button registration process> Next, the button registration process for registering a custom button will be described using the flowchart of FIG. 8. Here, an example of registering a custom button in the copy app 211 will be described. In FIG. 8, to distinguish the processes performed by the copy app 211 and the processes performed by the portal app 213, the processes performed by the copy app 211 are described on the left side and the processes performed by the portal app 213 are described on the right side. Note that all the processes in this embodiment are performed by the portal app 213 acquiring information previously stored in the HDD 104 and user input, and issuing various execution commands using the CPU 101 based on this information. Also, all the processes performed by the copy app 211 and the portal app 213 are performed by the CPU 101.

[0037] Here, as an example, in the copy app 211, as shown in FIG. 6(2), the case of registering a setting of copying 2 copies, double-sided from both sides, sorted as a custom button 613 in the menu 600 will be described. First, as shown in FIG. 7(2), on the copy settings screen 700, when the user selects setting values for various setting items such as the number of copies, double-sided, and sorting, the copy app 211 detects these setting values and stores them in the HDD 104 as setting information (S801). Next, when the copy app 211 detects the pressing of the gear button 715 within the copy settings screen 700, it displays a menu list 901 on the copy settings screen 700 as shown in FIG. 9A(1). Then, when it detects the pressing of the registration button 902 within the menu list 901, the copy app 211 enters the registration mode for registering the custom button on the portal screen (S802).

[0038] When entering the registration mode, the copy app 211 pops up and displays a setting confirmation screen 903 on the copy settings screen 700 as shown in FIG. 9A(2) (S803). The setting confirmation screen 903 displays the setting values (2 copies, double-sided from both sides, etc.) for the setting items (number of copies, double-sided setting, etc.) set by the user, a cancel button 904, and a next button 905.

[0039] When the copy app 211 detects the pressing of the Next button 905 on the setting confirmation screen (Fig. 9A(2)) (YES in S804), it sends a registration request to the portal app 213 (S805). When sending the registration request, the copy app 211 obtains its own app ID (1000) and the icon information to be displayed as a custom button from the HDD 104, and sends them to the portal app 213. Note that information regarding setting values such as the number of copies is not sent. As specific processing for S805, the copy app 211 obtains the app ID and the icon information from the storage area of the copy app 211 (including the common data section 220 and the copy data section 221) set in the HDD 104. Then, it notifies these pieces of information to the window control unit 201. Then, the window control unit 201 sends these pieces of information to the portal app 213. The portal app 213 stores the received information in its own storage area (including the common data section 220 and the portal data section 223).

[0040] When a registration request is sent from the copy app 211 to the portal app 213, button creation processing by the portal app is executed (S806). When the button creation processing starts, first, the portal app 213 displays a custom button registration screen (S807). Fig. 9B(3) shows an example of the custom button registration screen 906 that is pop-up displayed on the copy setting screen 700. On the custom button registration screen 906 in Fig. 9B(3), soft buttons for selecting / inputting the button display position are displayed. When the pressing of the Next button 907 is detected on the custom button registration screen 906, the portal app 213 changes the custom button registration screen 906 to the custom button display setting screen 908.

[0041] FIG. 9B(4) shows an example of a custom button display setting screen 908 that is pop-up displayed on the copy setting screen 700. On the custom button display setting screen 908, an input box for entering a button name and an input box for entering a comment are displayed. Then, when it detects the pressing of an OK button 909 indicating that the input is completed on the custom button display setting screen 908, the portal app 213 creates a custom button based on the content input on the custom button display setting screen 908 (S808).

[0042] In the process of creating a custom button, first, the portal app 213 generates an action ID that can uniquely identify each registration request (in this embodiment, as the action ID, a serial number is assigned starting from "1"). Next, the portal app 213 creates a custom button based on the app ID, action ID, icon information, and display information. Specifically, in the storage area of the portal app 213 in the HDD 104, as a button information table (FIG. 10), the app ID, action ID, icon information, and display information of the copy app 211 are associated and stored regarding the custom button. It is shown that a custom button NO. 4 is added by this registration process in the button information table shown in FIG. 10. When the creation of the custom button is completed, the portal app 213 sends the generated action ID to the copy app 211 together with a completion notification (S809). Then, the button creation process by the portal app ends.

[0043] When the button creation process by the portal app 213 ends, the copy app 211 associates the received action ID with the setting information stored in S801 and stores it in the storage area of the copy app 211 in the HDD 104 (S810). Then, it ends the registration mode for registering the custom button on the portal screen.

[0044] <Action Information Table> FIG. 11 shows an example of an action information table stored in the storage area of the copy application 211 in the HDD 104. In the action information table shown in FIG. 11, for each action ID, icon information and setting information are stored in association as action information. Note that when the copy application 211 always uses the same icon, it is not necessary to store the action ID and the icon information in association as shown in FIG. 11.

[0045] When the button registration process of FIG. 8 described above is performed, the setting information of the button registered on the portal screen is stored only in the copy application 211, and the portal application 213 stores only the action ID. When executing the setting information stored in the copy application 211 from the portal application 213, it is only necessary to notify the copy application 211 of an execution command of the action ID. Therefore, regardless of the data format in which the portal application 213 manages the setting information, it can be registered on the portal screen in the same procedure. In the present embodiment, the processing in the copy application 211 is described as an example of an application, but the same processing can be performed in the fax application 212 and other applications.

[0046] <Execution Process> Next, with reference to the flowchart of FIG. 12, the process of calling the custom button displayed in the menu 600 and executing the application will be described. In the present embodiment, an example in which the custom button 613 is pressed in the menu 600 shown in FIG. 6(2) will be described. In FIG. 12, the button call process performed by the portal application 213 is shown on the left side, and the action ID process performed by the copy application 211 is shown on the right side.

[0047] When detecting the pressing of the custom button 613 on the menu 600, the portal application 213 searches the button information table (FIG. 10) for the custom button No. corresponding to the pressed custom button (S1201). Next, the portal app 213 acquires the app ID and action ID corresponding to the custom button No. from the button information table, and notifies the app corresponding to the app ID of the action ID (S1202). Here, from the custom button No. 4 corresponding to the custom button 613 in the button information table (FIG. 10), the app ID "1000" and the action ID "2" are acquired, and the acquired action ID is notified to the copy app 211.

[0048] When the action ID is notified to the copy app 211, the action ID process is executed (S1203). The copy app 211 that has received the action ID acquires the setting information corresponding to the received action ID from the action information (FIG. 11) (S1204). Next, the copy app 211 pops up and displays a setting content confirmation screen related to the app on the touch panel 300 (S1205).

[0049] FIG. 9C(5) is an example of the setting content confirmation screen 910 that is popped up and displayed on the copy setting screen 700. The app-specific setting values included in the acquired action information are displayed on the setting content confirmation screen 910. Next, when it is detected that the OK button 911 displayed on the setting content confirmation screen 910 is pressed (YES in S1206), the copy app 211 displays a copy setting screen in which the setting information corresponding to the received action ID is reflected (S1207). FIG. 7(2) is an example of the copy setting screen in which the setting information is reflected. The user can give an execution instruction with the setting information associated with the custom button 613 as it is on the copy setting screen of FIG. 7(2), or can also give an execution instruction after changing any of the setting values.

[0050] Next, the copy app 211 waits for the start key 301 of the operation unit 112 to be pressed by the user (S1208), and then executes the process (S1209). The process in this case is executed based on the set value information set on the copy setting screen (FIG. 7(2)) displayed in S1207. Next, the copy application 211 compares the setting information at the time of execution with the setting information acquired in S1204, and determines whether the setting information has been changed (S1210). If it has been changed, the different setting values are saved in the setting information difference table shown in FIG. 13 (S1211). Then, the action ID process ends.

[0051] As a specific process of S1210, the case where, in the copy setting screen (FIG. 7(2)) displayed in S1207, after the user sets black-and-white and single-sided, the start key 301 of the operation unit 112 is pressed and the process of S1209 is executed will be described. In this case, the copy application 211 compares the setting information at the time of execution with the setting information corresponding to the received action ID ("2") in the action information table (FIG. 11). As a result, the different setting information (setting information difference) is black-and-white and single-sided. Therefore, the copy application 211 stores the setting information difference for each custom button related to the application in the setting information difference table (FIG. 13) in the storage area of the copy application 211 in the HDD 104. The setting count is incremented by 1 each time it is extracted as the setting information difference in S1210. FIG. 13(1) shows that for the action ID "2", the setting counts for the black-and-white and single-sided setting values are both "1".

[0052] <Button setting change process> Next, using the flowchart of FIG. 14, the process of executing the application after giving a setting change instruction to the custom button displayed in the menu 600 will be described. When the user has changed a part of the settings associated with the custom button that is the display object in the past and then executed the process, the history information that is the changed setting value is stored for each display object. Then, based on the stored history information, the setting with the most change times is recommended and displayed to the user. When the number of times the user has changed the settings associated with the custom button and executed the process exceeds a predetermined number of times, that is, when the number of records recorded in the setting information difference table (FIG. 13) exceeds a predetermined value, the process shown in FIG. 14 may be performed. Here, an example will be described in which a setting change instruction is given to the custom button 604 in the menu 600 shown in FIG. 6(1). In FIG. 14, the button setting change process performed by the portal app 213 is described on the left side, and the action ID process performed by the called copy app 211 is described on the right side.

[0053] When a setting change instruction for the custom button 604 on the portal screen (FIG. 6(1)) is detected, the portal app 213 searches for the custom button No. corresponding to the custom button for which the setting change instruction was given from the button information table (FIG. 10) (S1401). The instruction in this case may be anything as long as it can be distinguished from the instruction (S1201) for starting the button call process shown in FIG. 12. In this embodiment, since the start of the button call process of S1201 is a press operation, the setting change instruction may be any other operation. For example, a long press operation, a continuous press operation two or more times, or separating the button reaction area for starting the button call process and the button reaction area for the setting change instruction may be used.

[0054] Next, the portal app 213 acquires the app ID and the action ID corresponding to the custom button No. from the button information table (FIG. 10), and notifies the app corresponding to the app ID of the action ID (S1402). Here, from the custom button No. 1 corresponding to the custom button 604 in the button information table (FIG. 10), "1000" is acquired as the app ID and "1" is acquired as the action ID, and the acquired action ID is notified to the copy app 211.

[0055] When the action ID is notified to the copy app 211, the action ID process is executed (S1403). Note that the content of the action ID process in S1403 is different from the action ID process in S1203, as will be described later. First, the copy app 211 that has received the action ID acquires the setting information difference corresponding to the received action ID from the setting information difference table (FIG. 13) (S1404). Next, the copy application 211 pops up and displays a list of setting change options for the custom button 604 on the touch panel 300 based on the acquired setting information difference (S1405).

[0056] FIG. 15A(1) shows an example of a list of setting change options 1500 for the custom button 604. In the list of setting change options 1500, setting change candidate buttons 1501 and 1502 and other setting buttons 1503 are displayed as setting buttons. Here, the setting buttons 1501, 1502, and 1503 are displayed on the portal screen where the custom button is displayed. That is, an example is shown in which when a setting change instruction for the custom button is detected, the screen does not transition and the setting buttons are displayed on the same screen as the custom button, but this is not limited to this. When a setting change instruction for the custom button is detected, the screen may transition and the setting buttons 1501, 1502, and 1503 may be displayed. The setting change candidate buttons 1501 and 1502 are buttons that preferentially display setting values in descending order of the number of settings from the setting information difference table (FIG. 13). The other setting button 1503 is a setting button for accessing all available setting items from the application. In the example of FIG. 15A(1), based on the setting information difference table of FIG. 13(1), the upper right stapler with a setting count of "7" and the double-sided with a setting count of "5" are displayed as the setting change candidate buttons 1501 and 1502.

[0057] Note that the upper limit number of setting change option buttons that can be displayed within the menu 600 area of the touch panel 300 is two in the example of FIG. 15A(1), but it is variable depending on the layout of the menu 600 and is not limited to a specific value. Also, if there is no setting information difference corresponding to the received action ID in the setting information difference table (Fig. 13), the setting change option button is not displayed, and only the other setting button 1503 for accessing all the setting items available from the app is displayed. Alternatively, in addition to the other setting button 1503, one or more setting values that are commonly set in the app may be displayed as the initial values of the setting change candidate buttons.

[0058] Next, the copy app 211 determines whether any of the setting change candidate buttons displayed in the setting change option list 1500 has been pressed (S1406). For example, when detecting the pressing of the upper right staple button 1501 which is a setting change candidate button (YES in S1406), the copy app 211 reverses the color of the upper right staple button 1501 (Fig. 15A(2)). At the same time, the setting of the upper right staple is stored in the HDD 104 linked to the setting information corresponding to the action ID "1" in the action information table (Fig. 11) (S1407).

[0059] On the other hand, when detecting the pressing of a button other than the setting change candidate buttons (NO in S1406), the copy app 211 determines whether the pressed button is the other setting button 1503 (S1408). If the pressed button is the other setting button 1503, the copy app 211 displays the setting information corresponding to the received action ID on the setting change screen that can access all the setting items that can be set in the copy app 211 (S1409). Also, if either of the setting change candidate buttons 1501, 1502 has been pressed before the other setting button 1503 is pressed, the setting value is reflected and displayed.

[0060] FIG. 15B(4) shows an example of a setting change screen 1504 that can access all the setting items available in the copy application 211 when the other setting button 1503 is pressed. The user can change any setting value on the setting change screen 1504. The content displayed on the setting change screen 1504 in FIG. 15B(4) may be the same as the copy setting screen 700 shown in FIG. 7(1). Also, in order to make it easier to operate, for example, a separate setting change screen different from the copy setting screen 700 may be provided, such as displaying the setting items in a list format. However, on the setting change screen 1504 that can access all the setting items available in the copy application 211, a BACK 1505 button that was not present on the copy setting screen 700 in FIG. 7(1) is displayed.

[0061] Next, the copy application 211 determines whether the BACK button displayed on the setting change screen 1504 (FIG. 15B(4)) has been pressed (S1410). When it detects the pressing of the BACK 1505 button (YES in S1410), the copy application 211 associates the setting value changed on the setting change screen 1504 with the setting information corresponding to the action ID "1" in the action information table (FIG. 11) and stores it in the HDD 104. Also, as shown in FIG. 15B(3), the color of the other setting button 1503 is inverted and displayed (S1411). On the other hand, when it detects that an area other than the setting change option list 1500 (FIG. 15A(1)) has been pressed in S1406 (NO in S1406 and NO in S1408), the copy application 211 ends the action ID process.

[0062] Note that in the setting change candidate buttons 1501 and 1502 (FIG. 15A(1)), buttons related to setting values that cannot be combined with the previously set setting values are made non-selectable. Similarly, on the setting change screen 1504 (FIG. 15B(4)), buttons related to setting values that cannot be combined with the previously set setting values are also made non-selectable. For example, the color of the button is changed to gray, which is different from the inverted color during pressing, or it is changed to a non-operable shaded state. In addition, when there is a set value that cannot be combined with the previously set content, it is not necessarily required to prioritize the previously set set value. For example, the later set set value may be prioritized, and the previously set set value may be automatically changed to a set value that can be combined with the later set set value.

[0063] Next, when the start key 301 of the operation unit 112 is pressed by the user (YES in S1412), the copy application 211 executes the process (S1413). The process in this case is executed based on the setting information stored in the HDD 104 in S1407 or S1411. Here, as a method of notifying the user of the set value that cannot be combined, it is not limited to making the button non-selectable at the timing when the non-combinable setting is made. For example, a message such as "The setting that cannot be combined has been automatically changed" may be displayed at the timing of S1412. In the latter case, in S1413, the copy application 211 changes the setting information stored in the HDD 104 in S1407 or S1411 to the automatically corrected setting information and then executes the process.

[0064] Thereafter, the copy application 211 compares the setting information at the time of execution with the setting information corresponding to the action ID in the action information table (FIG. 11) acquired in S1402, and determines whether the setting information has been changed (S1414). If the setting information has not been changed (NO in S1414), the copy application 211 simply ends the action ID process.

[0065] On the other hand, if the setting information has been changed, the copy application 211 stores the setting information difference, which is the difference in the set value, in the setting information difference table (FIG. 13) (S1415). Thereafter, the action ID process ends. As a specific process of S1415, for example, the case where the upper right stapler setting and the color setting are made in S1407 or S1411 will be described. In this case, the copy application 211 extracts the upper right stapler setting and the color setting as setting information differences at S1414, and counts up the setting times of the upper right stapler in the setting information difference table (Fig. 13(2)) from 7 to 8. Also, the color setting is newly stored as a setting information difference.

[0066] As described above, according to Embodiment 1, for a custom button to which specific setting information is assigned, when the setting information is changed, the setting information difference is saved for each custom button. Thereby, for each custom button, as a setting change candidate button, the difference in detailed setting values for each usage purpose can be presented to the user, so that the desired setting value can be selected in a short operation sequence. Also, when changing the setting of a custom button, a change candidate button can be displayed, and when changing the setting of an app button, it is also possible to switch to display a setting change screen that can access all setting items.

[0067] <Embodiment 2> In Embodiment 1, in the action ID process (Fig. 12), the copy setting screen 700 (Fig. 7(2)) reflecting the setting information is displayed (S1207), and after the start key 301 of the operation unit 112 is pressed (S1208), the process is executed (S1209). In contrast, in Embodiment 2, in the setting content confirmation screen 910 (Fig. 9C(5)) that is pop-up displayed on the copy setting screen 700, when the OK button 911 is pressed by the user (YES in S1206), the process is executed. That is, in Embodiment 2, in the flowchart of Fig. 12 described in Embodiment 1, the processes of S1207 to S1208 are skipped, and the process of S1209 is started immediately after S1206.

[0068] Also in Embodiment 2, in the flowchart of the button setting change process (FIG. 14), a setting change screen 1504 (FIG. 15B(4)) that can access all setting items available in the copy application 211 is displayed. Then, on the setting change screen 1504, the setting items registered in the custom button can be changed (S1409). Also, the setting information difference can be saved for each custom button (S1415).

[0069] In this way, also in Embodiment 2, for each custom button, as a setting change candidate button, since the difference in detailed setting values for each usage purpose can be presented to the user, the desired setting value can be selected in a short operation.

[0070] <Embodiment 3> In Embodiment 1, as the setting change candidate buttons 1501 and 1502 in the setting change option list 1500 (FIG. 15A(1)), for example, the setting values were configured to be displayed, such as top right stapler, double-sided, etc. On the other hand, in Embodiment 3, the setting items are configured to be displayed as the setting change candidate buttons.

[0071] Accordingly, in Embodiment 3, in the setting information difference table (FIG. 13), as the setting information difference, the setting items are stored instead of the setting values. For example, as shown in the setting information difference table in FIG. 13(2), for the setting information difference regarding the action ID "1", instead of each setting value of double-sided, top right stapler, color, each setting item of double-sided, finish, color selection is saved.

[0072] Also, in S1405 of the flowchart of the button setting change process in FIG. 14, as the setting change candidate buttons 1501 and 1502 in the setting change option list 1500 (FIG. 15A(1)), various setting items such as finishing, duplex setting, and color selection are displayed. When it is detected that any of the setting items displayed as the setting change candidate buttons 1501 and 1502 is pressed, a setting change screen related to the pressed setting item is displayed, and when it is detected that either the setting value button or the OK button on the setting change screen is pressed, the process returns to S1406.

[0073] For example, when a setting item such as color selection is displayed as the setting change candidate button and the pressing of the button is detected, a color setting screen 1506 related to the color selection setting item as shown in FIG. 15C(5) is displayed. Then, on the color setting screen 1506, when any of the setting value buttons 1507 to 1511 is selected and the pressing of the OK 1512 button is detected, the process returns to the process of S1406. Note that the color setting screen 1506 shown in FIG. 15C(5) may have the same configuration as the selection screen displayed when the color selection button 703 is selected in the copy setting screen 700 (FIG. 7(1)). Also, in order to enable easier operation, for example, it may be a screen in which various setting values are displayed in a list format.

[0074] In this way, according to Embodiment 3, setting items are displayed as the setting change candidate buttons to be displayed for each custom button, and when any of the setting items is selected, a setting change screen for selecting the setting value related to the selected setting item is displayed. Thereby, even when the upper limit number of setting change candidate buttons that can be displayed is limited, it is possible to handle differences in more setting values.

[0075] <Embodiment 4> In Embodiment 1, among the setting value candidates stored as the setting information difference in the setting information difference table (Fig. 13), the setting change candidate buttons displayed as the setting change option list 1500 (Fig. 15A(1)) are configured to be preferentially displayed in descending order of the number of setting times.

[0076] However, among the setting values to be displayed in the setting change candidate buttons, there are some that should always be displayed regardless of the number of setting times, such as the setting values related to charging like the number of copies and duplex setting in the case of copying, or the setting values related to the destination in the case of fax. Therefore, in Embodiment 4, for the setting values and setting items that should always be displayed as the setting change candidate buttons, they are configured to be fixedly displayed.

[0077] Accordingly, in Embodiment 4, in the setting information difference table (Fig. 13), in addition to the action ID and the setting information difference, information on "fixed display / non-fixed display" is also stored. For the setting values stored as "fixed display" in the setting information difference table, regardless of the number of setting times of other setting values, they are always displayed as the setting change candidate buttons 1501 and 1502 in the setting change option list 1500 (Fig. 15A(1)).

[0078] Thus, according to Embodiment 4, for specific setting values and setting items, regardless of the number of setting times, by always displaying them as the setting change candidate buttons, the desired setting value can be selected in a short operation sequence.

[0079] <Embodiment 5> In Embodiment 1, the setting change candidate buttons 1501 and 1502 displayed in the setting change option list 1500 (Fig. 15A(1)) are configured to display the setting values. In contrast, in Embodiment 5, the setting change candidate buttons are configured to display combinations of setting values.

[0080] Accordingly, in Embodiment 5, as shown in FIG. 13(3), in the setting information difference table, the combination of setting values and the number of setting times are associated and stored as setting information differences. For example, in the setting information difference table of FIG. 13(3), in the setting information difference regarding the action ID "1", combinations of changed setting values such as "double-sided, upper right stapler" and "color, 2in1" are stored collectively.

[0081] Also, in S1404 of the flowchart of the button setting change process in FIG. 14, combinations of setting values such as "double-sided, upper right stapler" and "color, 2in1" are displayed as setting change candidate buttons 1501 and 1502. Note that the selection of the setting change candidate buttons 1501 and 1502 where combinations of setting values are displayed is exclusive, and it is assumed that multiple setting change candidate buttons cannot be selected simultaneously. Therefore, when there is a previously set setting change candidate button, all other setting change candidate buttons except the other setting button 1503 cannot be pressed (selected). For example, the color of the button is changed to gray different from the inverted color during pressing, or it is changed to a non-operable shaded state.

[0082] Thus, according to Embodiment 5, since combinations of setting values are displayed as setting change candidate buttons, desired setting values can be selected in a shorter operation sequence.

[0083] <Embodiment 6> In Embodiment 1, the buttons targeted for the button setting change process shown in FIG. 14 are configured as the custom buttons 604 to 606 of the menu 600 (FIG. 6(1)). In contrast, in Embodiment 6, the buttons targeted for the button setting change process are configured as app buttons 601 to 603. Accordingly, in Embodiment 6, the button call process shown in the flowchart of FIG. 12 is changed as shown in the flowchart of FIG. 16.

[0084] Regarding the flowchart of FIG. 16, in menu 600 (FIG. 6(1)), it will be described as if copy button 601 is pressed as an app button. When detecting the pressing of copy button 601 on menu 600, copy app 211 acquires setting values etc. from HDD 104 and displays copy setting screen 700 (FIG. 7(1)) (S1601). On copy setting screen 700, the user selects setting values using buttons for setting various copy functions. When the start key on operation unit 112 is pressed (S1602), copy app 211 executes processing (S1603). The processing in this case is executed based on the setting information set on the screen displayed in S1601.

[0085] Next, copy app 211 compares the setting information at the time of execution with the setting information acquired in S1601 and determines whether the setting information has been changed (S1604). If the setting information has been changed (YES in S1604), the setting information difference, which is the setting value difference, is stored in the storage area of copy app 211 in HDD 104, associating the setting value and the number of settings as shown in the setting information difference table of FIG. 13(4) (S1605). Note that the number of settings is incremented by 1 each time it is extracted as the setting information difference in S1604. Then, the button call processing ends. On the other hand, if the setting information has not been changed (NO in S1604), the button call processing ends as it is.

[0086] Also, when executing button setting change processing for app buttons 601 to 603, in the flowchart of FIG. 14 described in Embodiment 1, the start point and the end point are on the application side, and the processing of S1401 and S1402 is omitted.

[0087] Thus, according to Embodiment 6, even for an app button that executes an app with default setting values, when the setting information is changed, the setting information difference is saved. For app buttons, compared with custom buttons, the purposes of use are diverse, but since a large number of setting difference information is collected, it is possible to present the user with the differences in detailed setting values for each actual purpose of use.

[0088] <Embodiment 7> In Embodiment 1, among the set values included in the setting information difference of the setting information difference table (FIG. 13), the setting change candidate buttons 1501 and 1502 in the setting change option list 1500 (FIG. 15A(1)) were configured to be displayed up to the display upper limit number in descending order of the number of setting times. In contrast, in Embodiment 7, each time a setting change candidate button is selected, the setting change candidate button is configured to be updated to a set value having a high degree of relevance to the selected set value.

[0089] Accordingly, in Embodiment 7, like the setting information difference table shown in FIG. 13(5), in addition to the setting information difference, the set values set simultaneously with the selected setting candidate button are stored as related setting information. For example, in S1210 of the button call processing shown in FIG. 12, it is assumed that setting information differences such as double-sided, upper right stapler, and 2-in-1 are extracted. In this case, as shown in FIG. 13(5), the set values of the setting information difference, namely double-sided, upper right stapler, and 2-in-1, are stored by incrementing the count of each setting time by 1. Further, for each set value, the set values extracted simultaneously are stored as the set values of the related setting information by incrementing the count of each setting time by 1. For example, when taking double-sided as a set value, here, since upper right stapler and 2-in-1 were set simultaneously with double-sided, upper right stapler and 2-in-1 are stored in the table information as the set values of the related setting information, and the count of each setting time is incremented by "1".

[0090] In addition, the flowchart showing the button setting change process is as shown in FIG. 17 instead of FIG. 14 described in Embodiment 1. In the flowchart of FIG. 17, the processes from S1701 to S1707 are the same as the processes from S1401 to S1407 in the flowchart of FIG. 14. Also, the processes from S1709 to S1716 are the same as the processes from S1401 to S1407 in the flowchart of FIG. 14. However, it is different in that the step of S1708 is added as compared with the flowchart of FIG. 14. However, the flowchart of FIG. 17 is different in that the step of S1708 is added as compared with the flowchart of FIG. 14.

[0091] In the flowchart of FIG. 17, the copy app 211, following the process of S1406, acquires the related setting information of the set value pressed in S1406 from the setting information difference table shown in FIG. 13(5). Then, from the acquired related setting information, set values are extracted up to the upper limit number in the order of the highest relevance (the most frequent setting times), and the setting change candidate buttons 1501 and 1502 are updated and displayed (S1708). For example, if double-sided is selected as the setting change candidate button in S1406, the setting information difference table (FIG. 13(5)) is searched, and set values (here, black and white, three copies) are updated and displayed as the setting change candidate buttons up to the upper limit number in the order of the highest relevance.

[0092] As described above, according to Embodiment 7, related setting information related to the selected set value is collected, and based on this, the setting change candidate buttons are updated and displayed. As a result, set values with a high relevance to the selected set value can be selected in a shorter order.

[0093] <Embodiment 8> In Embodiment 1, the setting information difference table (FIG. 13) for recording the setting information difference is configured to be stored in the storage area of each app in the HDD 104 of the image processing apparatus 1. In contrast, in Embodiment 8, the setting information difference table is configured to be stored not in the image processing apparatus 1 but in the server 2 which is an external device connected by the network 3 via the LAN 113, WAN 114, wireless 115, etc.

[0094] Accordingly, in Embodiment 8, the CPU 101 acquires the setting information difference stored in the server 2 via the network 3 based on the instruction of the copy application 211 and notifies the copy application 211. Note that it is conceivable that a problem may occur in the connection to the server 2 and the stored setting information difference cannot be acquired from the server 2. In such a case, the setting change candidate buttons 1501 and 1502 in the setting change option list 1500 (FIG. 15A(1)) display up to the upper limit number of the setting values of the copy application 211 in descending order of the number of times of use.

[0095] As described above, according to Embodiment 8, the setting information difference table is stored in the server 2 which is an external device connected to the image processing apparatus 1. Further, when a problem occurs in the connection to the server 2, as the setting change candidate buttons 1501 and 1502, the setting values are displayed based on the number of times of use regardless of the setting information difference.

[0096] <Other Embodiments> The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and causing one or more processors in a computer of the system or apparatus to read and execute the program. Further, it can also be realized by a circuit (for example, ASIC) that realizes one or more functions. The present invention may be applied to a system composed of a plurality of devices or to an apparatus composed of a single device. The present invention is not limited to the above-described embodiments, and various modifications are possible based on the gist of the present invention, and they are not excluded from the scope of the present invention. That is, all configurations combining the above-described configuration examples and their modified examples are also included in the present invention.

Explanation of Symbols

[0097] 1 Image processing apparatus 112 Operation unit 700 Copy setting screen 1500 Setting change option list 1501, 1502 Setting change candidate buttons

Claims

1. a display control means for displaying a predetermined soft key indicating a copy function for which setting information is registered; A receiving means for receiving a user operation; An execution unit for executing the process of the copy function; Equipped with When the accepting unit accepts a user operation to change a part of the setting information and also accepts a user operation to execute the process of the copy function, the executing unit executes the process of the copy function using the changed setting information, The display control means displays an area for receiving a user operation that reflects the setting information of the copy function, which is an area different from the predetermined softkey, based on the execution means having executed processing of the copy function using the changed setting information, and when the acceptance means accepts a user operation that reflects the changed setting information in the copy function in the area for accepting a user operation that reflects the setting information of the copy function and accepts a user operation that displays a setting screen for the copy function, the display control means displays the setting screen that reflects the changed setting information.

13. An image processing device comprising:

Images