Image processing device, control method for image processing device, and program

Abstract

To allow for acceptance of an instruction for registering the setting of a job, corresponding to a selected setting history, as a frequently used setting, according to selection of the setting history of the job.SOLUTION: An image processing apparatus has display means capable of displaying a first button for setting the setting of a job stored as history as the setting of a new job, and a second button for setting the setting of a job registered according to registration instruction of a user as the setting of a new job, and control means for controlling to display a screen for accepting an instruction, registering the setting of the job being set by the selected first button, as the setting of a job being set by the second button, in the display means, according to selection of the first button displayed by the display means.SELECTED DRAWING: Figure 17

Description

[Technical Field]

[0001] The present invention relates to an image processing apparatus, a control method for an image processing apparatus, and a program. [Background technology]

[0002] Some image processing apparatuses allow frequently used job settings to be registered in advance, and display a custom button on the screen for calling up the settings.

[0003] Furthermore, Patent Document 1 describes an image processing apparatus that displays the settings of an executed job as a setting history on a touch panel and displays a job setting screen that reflects the job settings corresponding to a setting history selected by a user from the displayed setting history. By doing so, when executing a job with the same settings as a job that has been executed once, the settings of that job can be used without the user having to reconfigure the settings. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-146503 Summary of the Invention [Problem to be solved by the invention]

[0005] There is a limit to the number of job setting histories that an image processing device can read and set. When the number of job setting histories displayed on the image processing device reaches the upper limit, one of the displayed job setting histories must be hidden in order to display the setting history of a new job. As a result, when attempting to read and set frequently used settings from the setting history, the setting history may no longer be displayed. Therefore, by registering job settings stored as setting history to a custom button, it is possible to read and set the job settings set from the setting history even if the setting history is no longer displayed.

[0006] The setting history must be displayed appropriately so that the user can easily select it.

[0007] Therefore, an object of the present invention is to provide a method that allows a user to suitably select a setting history. [Means for solving the problem]

[0008] The image processing device according to the present invention has an image processing function and a display unit, and comprises: registration means for registering setting information related to the image processing function, which is set by a user; execution means for executing the image processing function using the setting information registered by the registration means; display control means for displaying on an operation screen a button corresponding to the setting information registered by the registration means, which is a button for opening a setting screen for the image processing function that reflects the registered setting information; and setting means for setting so that the display position of the button is fixed based on a user operation, wherein the display control means displays on the operation screen the buttons corresponding to the setting information registered by the registration means in the order in which the setting information was registered, and the buttons set by the setting means are displayed fixedly at a predetermined position on the operation screen. When new setting information is registered by the registration means, the button corresponding to the newly registered setting information is displayed below the button set by the setting means. It is characterized by: [Effects of the Invention]

[0009] The user can suitably select the setting history. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram showing a configuration of an image processing apparatus according to an embodiment of the present invention. [Figure 2] 1 is a diagram showing the appearance of an operation unit 12 of an image processing apparatus according to the present embodiment. [Figure 3] 10 is a flowchart showing a process from starting up the image processing apparatus to displaying a login user screen. [Figure 4] FIG. 2 is a diagram showing an example of an authentication screen displayed on the touch panel 200 in the present embodiment. [Figure 5] FIG. 2 is a diagram showing an example of a home screen displayed on a touch panel 200 of the image processing device according to the present embodiment. [Figure 6] 10 is a flowchart showing a process from starting an application to executing a job in this embodiment. [Figure 7] FIG. 2 is a schematic diagram showing an example of a copy screen in a copy function of the image processing apparatus according to the present embodiment. [Figure 8] 4 is a schematic diagram illustrating an example of a data table that stores default settings and job execution settings for each function in the present embodiment. FIG. [Figure 9] 10 is a flowchart showing a process for determining the content to be registered in a data table that manages an integrated history in the present embodiment. [Figure 10] 10 is a diagram showing an example of an integrated history data table stored in HDD 103 for displaying an integrated history in this embodiment. FIG. [Figure 11] 10 is a flowchart showing a process for generating text for a setting value to be displayed in the setting history of the integrated history in the first embodiment. [Figure 12] 10 is a flowchart illustrating a process for displaying a setting history on a home screen in the present embodiment. [Figure 13] 10 is a flowchart illustrating a process for launching an application from an integrated history in the present embodiment. [Figure 14] FIG. 10 is a diagram showing a data table for managing the order of setting histories to be displayed in the integrated history and the ON / OFF of pinning in the present embodiment. [Figure 15] 10 is a flowchart showing the processing performed when pinning is set for a setting history displayed in an integrated history and when the pinning setting is released in the present embodiment. [Figure 16] FIG. 10 is a diagram showing an example of a screen displayed when registering a custom button from the setting history displayed in the integrated history in this embodiment. [Figure 17] 10 is a flowchart illustrating a process for registering a setting history displayed in an integrated history to a custom button in the present embodiment. [Figure 18] FIG. 10 is a diagram illustrating an example of a data table for managing custom buttons in the present embodiment. [Figure 19] 10 is a flowchart showing a process for registering a setting history displayed in the integrated history to a custom button in the second embodiment. [Figure 20] FIG. 11 is a diagram showing an example of a screen displayed when a setting history displayed in an integrated history is registered in a custom menu in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the present invention. Furthermore, not all of the combinations of features described in the embodiments are necessarily essential to the solution of the present invention.

[0012] (First embodiment) FIG. 1 is a block diagram showing the configuration of an image processing device 1 according to an embodiment of the present invention.

[0013] The control unit 10 controls the operation of each unit of the image processing device 1. The control unit 10 includes a CPU 100, a communication unit 101, a RAM 102, a HDD 103, a ROM 104, a timer 105, and a FAX unit 106. The CPU 100 controls the entire control unit 10. The image processing device 1 is connected to the Internet via a LAN 11. The communication unit 101 transmits and receives data via the LAN 11. The RAM 102 provides system work memory for the operation of the CPU 100. The HDD 103 is a hard disk drive that stores programs, document data, and setting data for operating the image processing device 1. The HDD 103 may be a storage medium such as a magnetic disk, optical media, or flash memory. The HDD 103 does not have to be located within the image processing device 1. For example, the image processing device 1 may use an external server, PC, or the like connected via the communication unit 101 as a storage medium. The ROM 104 is a boot ROM that stores a system boot program. The CPU 100 loads a program installed in the HDD 103 into the RAM 102 and performs various controls based on the program. The timer 105 measures time according to instructions from the CPU 100 and notifies the CPU 100 when the specified time has elapsed. The FAX unit 106 sends and receives fax data via the telephone line 14.

[0014] The operation unit 12 is controlled by the control unit 10 and is composed of a display unit 120 and an input unit 121. The display unit 120 is a display for displaying information of the image processing device 1 to the user. The input unit 121 accepts input from the user via an interface such as a touch panel, a mouse, a camera, a voice input, or a keyboard.

[0015] The image processing unit 13 is controlled by the control unit 10 and is composed of an image analysis unit 130, an image generation unit 131, and an image output unit 132. The image analysis unit 130 analyzes the structure of an original image and extracts necessary information from the analysis results. The image generation unit 131 reads (e.g., scans) an original document, digitizes the image of the original document, generates image data, and stores the image data in the HDD 103. The image generation unit 131 can also generate original image data in a different format using information analyzed by the image analysis unit 130. The image output unit 132 outputs image data stored in the HDD 103 or the like. The image output unit 132, for example, prints the image data on paper, transmits the image data to an external device or server connected via the communication unit 101, or saves the image data in a storage medium connected to the image processing device 1.

[0016] FIG. 2 is a schematic view of the operation unit 12 according to this embodiment.

[0017] The touch panel 200 is a liquid crystal display unit with a touch panel sheet attached to the liquid crystal display unit. The touch panel 200 displays an operation screen and soft keys, and when a displayed key is pressed, transmits position information of the key to the CPU 100. Therefore, the touch panel 200 in this embodiment functions as the display unit 120 in FIG. 1 and also as the input unit 121.

[0018] Next, we will explain the various keys and buttons operated by the user. The start key 201 is used to instruct the start of a document scanning operation, etc. A two-color LED 202, green and red, is located in the center of the start key 201, and its color indicates whether the start key 201 is available for use. When the green LED 202 is lit, the image processing device 1 can start a job in response to detecting that the start key 201 has been pressed. On the other hand, while the red LED 202 is lit, the image processing device 1 cannot start a job. The stop key 203 is a key for stopping a process currently being executed by the image processing device 1. The numeric keypad 204 is composed of number and letter buttons and is used to set the number of copies, switch the screen on the touch panel 200, etc. The user mode key 205 is pressed when configuring the image processing device 1.

[0019] In this specification, the act of CPU 100 calling the corresponding screen data and screen control program from HDD 103 or RAM 102 and displaying the screen data on display unit 120 is referred to as "displaying a screen."

[0020] First, the home screen and integrated history displaying the job setting history displayed on the display unit 120 of the image processing device 1 will be described with reference to Fig. 5. Furthermore, a data table that manages the display content and display order of the setting history displayed in the integrated history 509 on the home screen will be described with reference to Figs.

[0021] 5A shows a home screen that is displayed when user A logs in to the image processing device 1. In an area 508, the user name of the currently logged-in user is displayed.

[0022] The home screen displays a menu 500 that displays buttons for launching each application. Menu 500 displays application buttons 501 to 503 that launch applications with default setting values ​​set. Menu 500 also displays custom buttons 504 and 505 that launch applications with setting values ​​registered in advance by the user set. Custom buttons 504 and 505 include a "my button" that is displayed only on the home screen of the logged-in user, and a "shared button" that is displayed on the home screen even when other users log in. The user can set each custom button as either a "my button" or a "shared button" using a method not shown.

[0023] The layout of the application buttons 501 to 503 and the custom buttons 504 and 505 is set by the logged-in user using a method not shown.

[0024] Slider bar 507 is used to slide menu 500 left and right to change the area displayed on display unit 120. When the user performs an operation such as moving slider bar 507 left and right, pressing arrow button 530, or performing a flick operation within the display area of ​​menu 500, a hidden area of ​​menu 500 is displayed on display unit 120.

[0025] The integrated history 509 is an area that displays the setting history of jobs executed by the image processing device 1. The integrated history 509 displays the setting history of executed jobs in reverse chronological order, regardless of the type of job. FIG. 5(A) shows a state in which the image processing device 1 is not executing any jobs, or a state in which all setting histories of jobs displayed in the integrated history 509 have been deleted. If the authentication function of the image processing device 1 is turned on, the integrated history 509 displays only the setting histories of jobs previously executed by the logged-in user. Furthermore, the number of setting histories that can be displayed in the integrated history 509 is predetermined. When the setting histories reach the upper limit of the number of setting histories that can be displayed in the integrated history 509, the setting history of the job with the oldest execution date and time will no longer be displayed, and instead the setting history of the job with the most recent execution date and time will be displayed.

[0026] 5(B) shows the home screen after user A executes a copy job in the state shown in FIG. 5(A). In FIG. 5(B), setting history 510 is displayed. Setting history 510 is composed of an application icon 511 indicating the type of job, text 512 indicating the execution date and time of the job, and text 513 indicating the setting values ​​of setting items whose settings have been changed from the default settings. For example, setting history 510 is the setting history of a copy application, and indicates that the job was executed after the settings for the number of copies (2), color printing, and double-sided printing were changed from the default settings. Image processing device 1 detects that setting history 510 has been pressed, and launches the application with the setting values ​​stored in association with setting history 510 set.

[0027] 5(C) shows the home screen after a copy job has been executed with settings different from those in setting history 510 in the state shown in FIG. 5(B). Setting history 510 and 514 are displayed sorted in descending order of job execution date and time. In this example, setting history 510 is older than setting history 514, so setting history 510 is displayed below setting history 514.

[0028] Fig. 5(D) shows the home screen after a transmission job has been executed in the state of Fig. 5(C). Since setting history 515 is a different application from setting histories 510 and 514, it is displayed with a different application icon from setting histories 510 and 514.

[0029] 5(E) shows the home screen after the user presses setting history 510 in the state of FIG. 5(D), calls up the settings, and executes a job without changing the settings. When a job is executed with the same settings, setting history 510 with the oldest execution date and time is not displayed, and only new setting history 516 is displayed. By preventing multiple setting histories showing the same settings from being displayed in this way, it is possible to display setting histories of various settings in integrated history 509.

[0030] FIG. 5(F) is a screen that is displayed when the user presses and holds setting history 514 in FIG. 5(E). A long press means that the user continues to press setting history for a predetermined period of time. When a long press of setting history 514 is detected, image processing device 1 pops up context menu 517 on the home screen. Context menu 517 is a menu screen for configuring settings for the selected setting history. Context menu 517 is composed of a "Pin" button 518, a "Register in menu" button 519, and a "Delete" button 520. After the user presses and holds setting history to display context menu 517, the user can release their finger from touch panel 200 and press any of buttons 518 to 520 to execute the process corresponding to each button. "Pin" button 518 is a button that prevents the display of the selected setting history from disappearing from integrated history 509. "Register in menu" button 519 is a button that displays a custom button having the same settings as the selected setting history in menu 500. Upon detecting that the "Register to Menu" button 519 has been pressed, the image processing device 1 displays on the touch panel 200 a name and comment registration screen 1701 for setting the name of the custom menu and the comment to be displayed on the custom button. Then, the user sets whether the custom button will be a "My Button" or a "Shared Button." This allows a custom button for calling up the setting values ​​displayed as the setting history to be displayed on the menu 500. The "Delete" button 520 is a button for preventing the selected setting history from being displayed in the integrated history 509.

[0031] Fig. 5(G) is the home screen after the "Pin" button 518 is pressed in Fig. 5(F). The setting history for which pinning has been specified is displayed at the top of the integrated history 509. Furthermore, a pin icon 521 is added to indicate that the setting history is pinned. If the user executes a job while the pinned setting history is displayed in the integrated history 509, the setting history with the most recent execution date and time is displayed below the pinned setting history.

[0032] The image processing device 1 according to this embodiment can pin setting histories displayed in the integrated history 509. By pinning setting histories that the user frequently calls up and uses from the setting history, it is possible to prevent the setting histories from disappearing from the integrated history 509. Pinning does not require any settings such as setting a name or entering a comment. Therefore, the user can easily display the setting histories as frequently used settings in the integrated history 509. Furthermore, by displaying pinned setting histories above other setting histories, it is possible to easily find the setting histories in the integrated history 509.

[0033] 5(H) is a screen displayed when unpinning a setting history that has been pinned in FIG. 5(G). When a pinned setting history is pressed and held, the image processing device 1 displays a context menu 517. The context menu 517 is composed of an "Unpin" button 522, a "Add to menu" button 519, and a "Delete" button 520. When the user presses the "Unpin" button 522, the image processing device 1 unpins the button ID corresponding to the setting history, and displays the setting history in integrated history 509 sorted in order of most recent job execution time.

[0034] Here, using Fig. 16, a screen displayed on touch panel 200 when the setting history displayed in integrated history 509 is registered to a custom button will be described. Fig. 16(A) shows a screen displayed when, from the state of Fig. 5(G), pinned setting history 514 is pressed and held to display context menu 517. When CPU 100 detects that "Register to menu" button 519 has been pressed, it displays custom button name and comment registration screen 1701 shown in Fig. 16(B) on touch panel 200. Fig. 16(B) shows name and comment registration screen 1701 after the user has entered "Regular" in name input field 1702 and "5 copies, color, double-sided" in comment input field 1703.

[0035] Upon detecting that the "OK" button 1704 has been pressed, the CPU 100 displays the home screen 1730 shown in FIG. 16(C) on the touch panel 200. At this time, the newly registered custom button 1711 is displayed on the home screen 1730. Furthermore, the pinning setting for the setting history 514 of the integrated history 509 is canceled. Therefore, the pinned icon 521 for the setting history 514 is no longer displayed. Furthermore, with the pinning canceled, the histories 514 to 516 are sorted and displayed in order of job execution time. When the user presses the created custom button, a job setting screen in which the setting values ​​stored in association with the custom button are set is displayed on the touch panel 200.

[0036] As shown in FIG. 16 , when a pinned setting history is registered as a custom button in the menu, the pinning setting for that setting history is unpinned. A user may temporarily select a frequently used setting from the setting history in the integrated history 509 and pin it. If the setting is subsequently used permanently, the user assigns a name and a comment to the custom button so that the user knows when the setting is used. At this time, if a custom button and a pinned setting history showing the same setting are displayed, the user may become confused as to which button to use to call up the setting. Therefore, when the pinned setting history is registered in a custom button, the pinning setting for that setting history is unpinned. In this way, after registering the pinned setting history in a custom button, the pinning setting for that setting history can be unpinned without the user having to perform an operation to unpin the pinned setting for that setting history.

[0037] Fig. 10 is an example of an integrated history data table 1000 for managing the setting history displayed in the integrated history 509. The data table shown in Fig. 10 is stored in the HDD 103. As noted in the table header, this table stores text data of button IDs, application IDs, data, the date and time to be displayed on the home screen, and setting values.

[0038] The button ID is a number for identifying a button that indicates the setting history displayed in the integrated history 509 .

[0039] The application ID is a number that indicates which application the setting history pertains to. The correspondence between application types and application IDs is predetermined. For example, the application ID for a copier is "101," and the application ID for a sender is "201."

[0040] The data is the name of the file in which the setting values ​​of the setting history are stored. This file is in a format that each application can read, and it stores all the setting values ​​used by that application. For example, for copying, this includes the number of copies, black and white / color settings when printing, paper size, etc.

[0041] The display text is text that indicates the date and time and setting content displayed in the setting history of the integrated history 509. The date and time is text data that indicates the date and time when the job in the setting history was executed. The setting value is text data of a setting that meets a predetermined condition among the settings stored as the setting history. For example, it is the setting value of a setting item that the user changed from the default setting. By displaying the date and time when the job was executed and the settings in the integrated history 509, the user can easily remember when the job in the setting history was executed and what settings it had.

[0042] FIG. 10(A) corresponds to FIG. 5(A), and no setting history has yet been registered in the integrated history data table 1000.

[0043] Figure 10(B) corresponds to Figure 5(B), and setting history 510 corresponds to the data of button ID 1001. Button ID 1001 is the setting history of a copy with application ID "101", the file name that stores the setting values ​​is "data1.xml", the date and time text is "2016 / 12 / 15 13:01:22", and the setting value text is "2 copies, color, double-sided".

[0044] FIG. 10C corresponds to FIG. 5C, and the setting history 514 corresponds to the data of the button ID 1002.

[0045] FIG. 10(D) corresponds to FIG. 5(D), and the setting history 515 corresponds to the data of the button ID 1003.

[0046] Figure 10(E) corresponds to Figure 5(E), and setting history 516 corresponds to the data of button ID 1001. In Figure 10(E), the date and time of the display text of button ID 1001 has been updated from "2016 / 12 / 15 13:01:22" to "2016 / 12 / 18 12:54:30".

[0047] 14 shows an example of a data table 1500 that manages the display order of the setting history and the ON / OFF of the pinning flag managed by the integrated history data table 1000. The data table is stored in the HDD 103.

[0048] The "Order" column indicates the order in which each setting history is displayed. The "Button ID" column stores the button ID of the setting history to be displayed in the integrated history 509. The "Pin" column stores information indicating whether the pin flag of the setting history for the button ID listed on the left is ON or OFF.

[0049] For example, Fig. 14(A) shows data table 1500 when displaying the home screen shown in Fig. 5(E). Integrated history 509 displays the setting histories in the order of button IDs 1001, 1003, and 1002 from the top. That is, integrated history 509 displays the setting histories in the order of setting histories 516, 515, and 514. Furthermore, the pinning flag for the setting history of any button ID is OFF, so no pinning setting has been made.

[0050] 14(B) shows the data table 1500 when the home screen shown in Fig. 5(G) is displayed. The setting history 514 of the button ID 1002, which has pinning set to ON, is displayed at the top, followed by the setting histories of the buttons IDs 1001 and 1003, which are displayed in order of execution date and time.

[0051] The processing executed by the image processing device 1 will be described below with reference to a flowchart.

[0052] First, the process of a user logging in to the image processing device 1 will be described with reference to Figures 3 and 4. Figure 3 is a flowchart showing the process from starting up the image processing device 1 according to this embodiment to displaying the login user screen. The process described in this flowchart is realized by the CPU 100 executing a program stored in the HDD 103 or ROM 104. The process described in Figure 3 is started when the image processing device 1 is powered on.

[0053] The CPU 100 displays an authentication screen on the touch panel 200 (S301). Fig. 4 shows an example of the authentication screen displayed on the touch panel 200. The authentication screen is made up of a user name input area 401, a password input area 402, and an "OK" button 403.

[0054] After displaying an authentication screen on touch panel 200, CPU 100 accepts input of a username and password (S302). Upon detecting that username input area 401 or password input area 402 has been pressed, CPU 100 displays a soft keyboard (not shown) on touch panel 200. The user inputs a username and password by pressing the soft keyboard. Upon detecting that "OK" button 403 has been pressed, CPU 100 advances the process to S303.

[0055] When CPU 100 detects that "OK" button 403 has been pressed, CPU 100 determines whether the input user name and password match the user name and password stored in HDD 103 (S303). If the input user name and password do not match the user name and password stored in HDD 103, CPU 100 displays an error message on touch panel 200 and then displays the authentication screen again (S304).

[0056] If the user name and password match, CPU 100 retrieves information associated with the user stored in HDD 103 (S305). Information associated with the user is, for example, information indicating the history of jobs executed by the logged-in user, or information regarding custom buttons to be displayed on the menu screen shown in Fig. 5. For example, this is integrated history data table 1000 shown in Fig. 10 or custom button data table 1900 shown in Fig. 18.

[0057] CPU 100 stores the authenticated user as the currently logged-in user in HDD 103 (S306). Thereafter, CPU 100 displays a home screen reflecting the information of the called logged-in user on touch panel 200 (S307).

[0058] Next, a process for a user who has logged in to the image processing apparatus 1 to execute a job will be described with reference to FIGS.

[0059] First, a series of operations until a user executes a job on the image processing device 1 will be described with reference to FIG.

[0060] After the user logs in to the image processing device 1, the home screen shown in Fig. 5 is displayed on the touch panel 200. The user selects an application to use from the menu 500 on the home screen. Here, an example will be described in which the user selects copy.

[0061] The user presses the application button 501 displayed on the menu 500 on the home screen. When the image processing device 1 detects that the user has pressed the application button 501, it displays the "Copy" screen 700 shown in FIG. 7A on the touch panel 200. FIG. 7A shows the "Copy" screen 700 in a state where default setting values ​​have been set. The "Copy" screen 700 is a setting screen for a job of the copy function.

[0062] The "Copy" screen 700 consists of an area 701 that displays the settings for color, magnification, paper size, and number of copies, and buttons for setting the settings. Button 702 is a button for confirming the currently set settings in a list. When the user presses button 702, details of the currently set settings are displayed on the touch panel 200. A "Color Selection" button 703 is a button for setting whether to print in black and white or color when making copies. A "Magnification" button 704 is a button for setting the magnification when making copies. A "Paper Selection" button 705 is a button for setting the size and type of paper to be used when printing. A "Finishing" button 706 is a button for setting whether to shift the paper ejection position for each copy or for each page when ejecting printed paper. A "Duplex" button 707 is a button for setting whether to print on both sides or one side when making copies. A "Density" button 708 is a button for setting the density when printing. A "Document Type" button 709 is a button for setting the type of document to be scanned by the scanner. The "ID Card Copy" button 710 is a button for making settings to print both the front and back of an original on one side of a single sheet of paper. The "Other Functions" button 711 is a button for making settings for items that cannot be set on the "Copy" screen 700, such as settings for assigning page numbers and control numbers to printed materials. The "Settings History" button 712 is a button for using settings from copy jobs previously performed by the user. The "Frequently Used Settings" button 713 is a button for setting settings that the user has registered in advance.

[0063] An icon 715 is a button for registering the settings currently displayed on the job setting screen to a custom button or registering the settings as frequently used settings.

[0064] 7(B) shows the "Copy" screen 700 when the user has set color printing, two copies to be printed, sorting to change the paper ejection position for each copy, and double-sided printing. After making the settings using the touch panel, the user presses the start key 201. When the image processing device 1 detects that the start key 201 has been pressed, it executes the job according to the settings set via the touch panel 200.

[0065] 7(C) shows a screen that is displayed on the touch panel 200 when the user presses the icon 715. The "Register to Custom Button" button 716 is a button for registering the settings configured on the displayed job setting screen to a custom button. The CPU 100 detects that the "Register to Custom Button" button 716 has been pressed, and generates a file that stores the currently configured setting values. The CPU 100 registers the application ID of the displayed application and the file name that stores the configured setting values ​​in a custom button data table 1900, which will be described later with reference to FIG. 18. Then, a name and comment registration screen 1701, shown in FIG. 16(B) and described later, is displayed on the touch panel 200. When the "OK" button 1704 on the name and comment registration screen 1701 is pressed, the CPU 100 registers the input name and comment in the custom button data table 1900, and displays the custom button on the menu screen.

[0066] The "Register as frequently used settings" button 717 is a button for registering the settings configured on the displayed job setting screen as settings that can be called up from the "frequently used settings" button 713. The "Close" button 718 is a button for closing the menu 719 that pops up when the icon 715 is pressed.

[0067] 6 is a flowchart showing the process from when the image processing apparatus 1 starts an application to when the image processing apparatus 1 executes a job. The process shown in FIG. 6 is realized by the CPU 100 executing a program stored in the HDD 103 or the ROM 104.

[0068] In FIG. 6, an example will be described in which the user selects a copy application on the menu 500.

[0069] Upon detecting a press of the application button 501 displayed on the menu 500, the CPU 100 displays the "Copy" screen 700, on which the default setting values ​​shown in Fig. 7A are set, on the touch panel 200 (S601). Thereafter, the CPU 100 accepts copy job settings from the user.

[0070] The CPU 100 determines whether the start key 201 has been pressed (S602). The CPU 100 continues to perform the process described in S602 until it detects that the start key 201 has been pressed.

[0071] In response to the determination that start key 201 has been pressed, CPU 100 stores the job settings that have been set in HDD 103 (S603). Fig. 8A is a schematic diagram of a data table for storing copy job settings. Copy data table 800 is stored in HDD 103. Default settings 802 in the first row of copy data table 800 indicate the default setting values ​​for the copy function, and current settings 803 in the second row indicate the job setting values ​​that were set when CPU 100 detected that start key 201 was pressed.

[0072] After storing the current settings in HDD 103, CPU 100 controls image processing unit 13 to execute the job (S604). CPU 100 controls image processing unit 13 to generate an output image that reflects the settings set on "Copy" screen 700. Image processing device 1 prints the generated output image on paper.

[0073] FIG. 6 has been described with reference to an example in which the image processing device 1 executes a copy job. The type of job executed by the image processing device 1 is not limited to a copy job, and similar processing is performed when executing a transmission job, fax job, print job, or scan job. For example, when a transmission job is executed, in S603, the CPU 100 stores the current setting values ​​in a transmission data table 1400 stored in the HDD 103. FIG. 8C is a diagram showing an example of a transmission data table related to a transmission job. Default settings 1402 are setting values ​​registered in advance in the image processing device 1, and current settings 1403 are setting values ​​set when the transmission job is executed.

[0074] 9, 11, and 12, a process for displaying the setting history in the integrated history 509 after a job is executed will be described.

[0075] FIG. 9 is a flowchart showing a process for determining the contents to be registered in the integrated history data table 1000 from the job settings stored by the image processing apparatus 1 as the current settings.

[0076] 9 is realized by the CPU 100 executing a program stored in the HDD 103 or the ROM 104. The process shown in FIG. 9 is executed after the process shown in FIG. 6 has ended.

[0077] The CPU 100 acquires information registered in the integrated history data table 1000 stored in the HDD 103 (S901). Here, the CPU 100 references the application ID of the executed job and acquires information on the data string of the setting history having the same application ID as the executed job from the integrated history data table 1000.

[0078] The CPU 100 compares the current setting 803 with the setting history data stored in the integrated history data table 1000 acquired in S901, and determines whether the same setting as the current setting is stored in the integrated history data table 1000 (S902).

[0079] If the integrated history data table 1000 does not contain any setting history with the same settings as the current setting, the CPU 100 executes processing to generate text data to be displayed in the integrated history 509 (S903). The processing executed by the CPU 100 in S903 will be described later with reference to FIG.

[0080] After generating the text to be displayed as the setting history, the CPU 100 stores the content to be registered in the integrated history data table 1000 in the HDD 103 (S904). The content to be registered in the integrated history data table 1000 is the application ID, the file name of the setting data, text data indicating the setting value and execution date and time, and a flag indicating whether or not there is existing data. The flag indicating whether or not there is existing data is determined based on the determination result in S902, and indicates whether or not there is setting history with the same settings as the settings of the executed job stored in the HDD 103. In S904, a new setting history is generated, so the existing data flag indicates no.

[0081] In S902, if a setting history having the same settings as the settings of the currently executed job is stored in the integrated history data table 1000, the CPU 100 executes the following process. The CPU 100 generates text data indicating the date and time the job was executed (S905). Thereafter, the CPU 100 stores in the HDD 103 the button ID of the setting history showing the same settings as the executed job, the text data indicating the execution date and time of the job generated in S905, and an existing data presence / absence flag (S906). In S906, since the settings of the executed job are the same as the settings stored in the integrated history data table 1000, the existing data presence / absence flag indicates presence.

[0082] After completing the process described in S904 or S906, the CPU 100 ends the process shown in FIG.

[0083] Fig. 11 is a flowchart showing the process in which CPU 100 generates text for the setting values ​​in S903 of Fig. 9. The process shown in Fig. 11 is realized by CPU 100 executing a program stored in HDD 103 or ROM 104.

[0084] First, the CPU 100 compares the current settings 802 in the copy data table 800 stored in the HDD 103 with the default settings 802 to determine whether any setting items have had their setting values ​​changed (S1101). If the comparison shows that the setting values ​​have been changed for one or more setting items, the CPU 100 determines that there are setting items whose settings have been changed from the default settings. If the setting values ​​have not been changed from the default settings, the CPU 100 ends the processing described in this flowchart.

[0085] If there is a setting item whose setting value has been changed from the default setting, the CPU 100 initializes a character number counter T for counting the number of characters in the text data of the setting value to 0 (S1102).

[0086] CPU 100 acquires text data (X characters) from copy data table 800 for the setting item whose setting value has been changed and that is located at the leftmost position in copy data table 800 (S1103). In this case, since there is a difference in the number of copies, CPU 100 acquires the text data "2 copies."

[0087] Next, the CPU 100 calculates the length of the entire text data acquired from the copy data table 800 up to this point (S1104). The CPU 100 executes a process of adding the number of characters X of the text data acquired in S1103 to the current value of the character counter T.

[0088] CPU 100 determines whether character counter T calculated in S1104 has reached a predetermined upper limit of the length of text that can be displayed (S1105). There is a limit to the size of the area for displaying one setting history in integrated history 509. Therefore, there is a limit to the length of text that can be displayed in one setting history, and in S1105 CPU 100 determines whether the length of the acquired text data exceeds the display area.

[0089] If it is determined in S1105 that the length of the acquired text data exceeds the display upper limit, CPU 100 discards the text data acquired for the setting item for which text data was last acquired, and ends the processing of this flowchart.

[0090] In S1105, if the character counter T has not reached the upper limit of the characters that can be displayed, the CPU 100 stores the text data acquired in S1103 as text data of the setting value to be displayed in the integrated history 509 (S1106).

[0091] CPU 100 determines whether any setting items whose setting values ​​have been changed from the default settings remain (S1107). If any setting items whose setting values ​​have been changed remain, CPU 100 repeats the processes of S1103 to S1107. At this time, in S1103, CPU 100 acquires text data for the setting item located at the leftmost position in copy data table 800 among the setting items for which text data has not yet been acquired. When processing has been performed for all setting items whose setting values ​​have been changed from the default settings, CPU 100 ends the processing described in this flowchart. In the copy data table shown in FIG. 8(A), up to "2 copies, color, double-sided" are generated as text data.

[0092] In Figure 11, if there are many setting items whose settings have been changed and it is not possible to display all of the changed setting items in the setting history, setting items whose number of characters exceeds the number that can be displayed in the setting history will not be displayed. However, if the changed setting values ​​for all setting items are not displayed, an indicator such as "..." may be added to the end of the text indicating the setting values ​​in the setting history. Alternatively, instead of an indicator, the character string "Other" may be displayed to indicate that there are other setting items whose settings have been changed in addition to the displayed setting items.

[0093] 12 is a flowchart showing the processing performed by the image processing device 1 up to the point where the current settings are displayed as a setting history in the integrated history 509. The processing shown in FIG. 12 is realized by the CPU 100 executing a program stored in the HDD 103 or the ROM 104. The processing shown in FIG. 12 is executed by the CPU 100 when the touch panel 200 displays the home screen after the user has executed a job.

[0094] The CPU 100 reads the information stored in the HDD 103 in S904 or S906 of FIG. 9 (S1201).

[0095] Next, the CPU 100 checks the existing data presence / absence flag of the data read in S1201 (S1202). If there is no existing data, the CPU 100 determines whether there is free space in the integrated history data table 1000 (S1203). If there is free space in the integrated history data table, the CPU 100 executes the process of S1205, which will be described later.

[0096] If there is no free space in the integrated history data table, the CPU 100 deletes the setting history with the oldest execution date and time among the non-pinned setting history from the integrated history data table 1000 (S1204). In S1204, the CPU 100 references the data table 1500 and acquires the setting history for the button ID for which pinning is set to OFF from the setting history data table. The CPU 100 identifies the setting history with the oldest job date and time from the display text of the acquired setting history, and deletes that setting history from the integrated history data table 1000.

[0097] Thereafter, the CPU 100 registers the information read in S1201 in the integrated history data table 1000 (S1205). In S1205, the CPU 100 assigns a button ID when registering the information related to the setting history in the integrated history data table 1000. Fig. 10(B) shows the data table after the data read from the HDD 103 has been added to the integrated history data table 1000.

[0098] If existing data is found in S1202, the CPU 100 identifies the button ID of the setting history having the same settings as the settings acquired in S1201 from the integrated history data table 1000. Thereafter, the CPU 100 updates the text data indicating the job execution date and time for the setting history of the identified button ID (S1206).

[0099] After the process of S1205 or S1206, the CPU 100 reads the setting history data table 1500 and determines whether there is any setting history in which pinning is set to ON (S1207).

[0100] If there is no setting history with pinning set to ON, the CPU 100 sorts the setting history stored in the integrated history data table 1000 by date and displays them on the touch panel 200 (S1208).

[0101] In S1207, if there is a setting history for which pinning has been set in the data table 1500, the CPU 100 sorts the setting history other than the setting history for which pinning has been set in order of execution date and time (S1209).

[0102] The CPU 100 displays the setting history sorted in S1207 on the touch panel 200 after the pinned setting history (S1210). In this embodiment, when there are multiple pinned setting history entries, the CPU 100 displays the setting history entries with the most recent pinned date and time at the top. When multiple setting history entries are pinned, the order in which the pinned setting history entries are arranged is not limited to the above order. For example, the user may set the display order of the pinned setting history entries. Furthermore, the pinned setting history entries may be arranged in the order in which jobs are executed.

[0103] Next, a process for calling up settings from the setting history displayed in integrated history 509 will be described. For example, assume that the home screen shown in FIG. 5B is displayed on touch panel 200. At this time, CPU 100 detects a tap on setting history 510, and displays "Copy" screen 700 shown in FIG. 7B on touch panel 200. A tap is when a user presses the touch panel and stops pressing it before a predetermined time has elapsed. When a setting history displayed in integrated history 509 is tapped, a screen for setting a job in which the setting value associated with the tapped setting history is set is displayed on touch panel 200.

[0104] 13, the process of calling a setting from the setting history displayed in the integrated history 509 will be described. The process shown in FIG. 13 is realized by the CPU 100 executing a program stored in the HDD 103 or the ROM 104. FIG. 13 is a flowchart showing the process of calling an application from the integrated history 509.

[0105] The CPU 100 determines whether a setting history displayed in the integrated history 509 has been tapped (S1301). The CPU 100 performs the process described in S1301 until a tap on the setting history is received.

[0106] In S1301, when a tap on the setting history is detected, the CPU 100 reads from the HDD 103 the setting in the setting history associated with the button ID of the button at the tapped position (S1302).

[0107] The CPU 100 displays a job setting screen that reflects the settings read out in S1302 on the touch panel 200, and ends the processing described in this flowchart (S1303).

[0108] 13, settings that have been set can be recalled with one touch, eliminating the need to set them again when the user wants to use the same settings as a job that was executed in the past. Also, even if the user wants to execute a job with some changes to the settings of a job that was executed in the past, reading out past settings from the setting history reduces the effort required for setting compared to setting from the default settings.

[0109] Next, pinning of the integrated history 509 will be described with reference to FIGS.

[0110] 5(F), when the user presses and holds the setting history, a context menu 517 for configuring settings related to the setting history is displayed. Although a long press has been used as an example of a user operation for displaying the context menu 517, the way to call up the context menu 517 is not limited to a long press, and may include a double tap or providing a call button.

[0111] 15(A) will be used to explain the process in which a user sets pinning of a setting history displayed in integrated history 509. The process described in FIG. 15(A) is realized by CPU 100 executing a program stored in HDD 103 or ROM 104. The flowchart described in FIG. 15(A) is started when CPU 100 detects that "Pin" button 518 of context menu 517 has been pressed. Here, an example will be explained in which the pinning setting of the setting history displayed in the Nth position in integrated history 509 has been set to ON.

[0112] The CPU 100 acquires the button ID of the setting history for which the pinning setting is set to ON (S1601).

[0113] The CPU 100 changes the button IDs and pinned flags currently stored in the data table 1500 from 1 to N-1 to 2 to N (S1602).

[0114] Finally, the CPU 100 stores the button ID acquired in S1601 as the first item in the data table 1500, turns on the pinned flag, and ends this flowchart (S1603).

[0115] When the user turns on the pin setting for the setting history displayed at the top of the integrated history 509, the CPU 100 turns on the pin flag for the button ID whose order in the data table 1500 is "1" and ends the processing.

[0116] The process of unpinning a pinned setting history in this embodiment will be described with reference to Fig. 15(B). The process shown in Fig. 15(B) is implemented by the CPU 100 executing a program stored in the HDD 103 or the ROM 104. The process shown in Fig. 15(B) is initiated when the CPU 100 detects that the "Unpin" button 522 has been pressed on the context menu 517 shown in Fig. 5(H).

[0117] The CPU 100 acquires the button ID of the setting history for which the pinning setting has been canceled from the data table 1500 (S1604). For example, when the "Unpin" button 522 is pressed on the screen shown in Fig. 5(H), the CPU 100 acquires the button ID "1002" corresponding to the setting history 514 from the data table 1500. Then, the CPU 100 sets the pinning flag for the setting history of the button ID 1002 in the data table 1500 to OFF.

[0118] Thereafter, the CPU 100 determines whether or not there is a setting history in which the pinning flag is set to ON in the data table 1500 (S1605).

[0119] If there is no setting history with the pinned flag set to ON, the CPU 100 sorts the setting history of the button IDs registered in the data table 1500 in order of job execution time and displays them on the touch panel 200 (S1606).

[0120] If the data table 1500 contains a setting history with the pinned flag set to ON, the CPU 100 executes a process to remove that setting history from the list of settings to be sorted (S1607). Then, the CPU 100 sorts the remaining setting history in order of job execution time and displays them on the touch panel 200 following the setting history with the pinned flag set to ON (S1608).

[0121] 17 and 18, the operation and process for registering the setting history displayed in the integrated history 509 in a custom button will be described.

[0122] The custom button data table 1900, which manages custom buttons, will be described with reference to FIG. 18. The custom button data table 1900 is composed of a button ID, an application ID, data, a name, and a comment. The button ID is an ID for identifying a custom button, and when registering a new custom button, the CPU 100 assigns a button ID to the custom button so that the button ID does not overlap with that of other custom buttons. The application ID and data are the same as those described for the integrated history data table 1000 shown in FIG. 10. The name and comment are text data displayed on the custom button. The name and comment are text set on the name and comment registration screen 1701 shown in FIG. 16(B), and indicate the type of settings for the custom button, the situation in which the button is used, and so on. The custom button data table 1900 is stored in the HDD 103, and is read and written by the CPU 100 via the RAM 102.

[0123] 17 shows the flow up to registering the setting history displayed in integrated history 509 as a custom button, and processing starts when CPU 100 detects pressing of "Register in menu" button 519. This processing is realized by CPU 100 executing a program stored in HDD 103 or ROM 104.

[0124] The CPU 100 identifies the button ID of the selected setting history and acquires necessary information such as the application ID and data from the integrated history data table 1000 (S1801). For example, when registering the setting history 514 as a custom button in Fig. 16(A), the CPU 100 acquires the application ID "101" and the data "data1.xml" from the integrated history data table 1000 shown in Fig. 10(E).

[0125] The CPU 100 registers the acquired data in the custom button data table 1900 stored in the HDD 103 (S1802). The CPU 100 registers the information acquired in S1801 in the custom button data table 1900 stored in the HDD 103. The custom button data table 1900 shown in FIG. 18(A) is the custom button data table 1900 after the processing of S1802 is completed. The CPU 100 sets the button ID to "1903" and registers the application ID "101" and data "data1.xml" in the data table. The name and comment of the custom button are not yet registered because they are information that does not exist in the integrated history.

[0126] Next, CPU 100 displays custom button name and comment registration screen 1701 on touch panel 200 (S1803). After detecting that "OK" button 1704 on button name and comment registration screen 1701 has been pressed, CPU 100 registers the name and comment in custom button data table 1900. Figure 18(B) shows custom button data table 1900 after the name "Regular" and comment "5 copies, color, double-sided" have been registered.

[0127] The CPU 100 determines whether the pinning setting corresponding to the button ID of the selected setting history is ON (S1805). The CPU 100 determines whether the pinning setting of the selected setting history is ON by referring to the data table 1500. If the pinning setting of the selected setting history is OFF, the CPU 100 executes the process of S1807, which will be described later.

[0128] If the pinning setting for the selected setting history is ON, the CPU 100 sets the pinning setting for the setting history to OFF in the data table 1500 (S1806).

[0129] The CPU 100 displays the integrated history 509, which is obtained by sorting the setting histories registered in the integrated history data table 1000 in the order of job execution, and the menu 500 on the touch panel 200 (S1807). Specifically, the CPU 100 executes the processes described in S1207 to S1210 in FIG.

[0130] In this embodiment, the pinning setting of the setting history registered to the custom button is turned off. In S1806, CPU 100 may display pinned status change confirmation screen 1740 shown in FIG. 16(D) on touch panel 200, allowing the user to select whether to unpin. In this way, it is possible to confirm with the user whether to unpin when registering to the custom button. It is possible to prevent the pinning setting from being unpinned for setting history that the user does not want to unpin.

[0131] Finally, the process of reading and setting job settings registered as a custom button from the home screen will be described. Upon detecting the press of a custom button displayed on the home screen, CPU 100 identifies the button ID of the pressed custom button. CPU 100 reads the data for the custom button corresponding to the pressed button ID from custom button data table 1900. For example, if the button ID of the pressed custom button is "1903," CPU 100 reads "data3.xml." CPU 100 displays a job setting screen on touch panel 200, on which the read setting values ​​have been set. By registering the setting history for a custom button, the job settings can be read and set from the home screen even if the setting history is no longer displayed in integrated history 509.

[0132] As described above, in this embodiment, a custom button registered in accordance with a registration instruction from a user and a setting history generated as a job is executed are displayed. Furthermore, when a setting history is selected, an instruction to register job settings that can be set using the setting history to a custom button can be input. This allows job settings that can be set using the setting history to be registered to a custom button without having to set the job. This reduces the user's effort when registering job settings that can be set from the setting history to a custom button.

[0133] Furthermore, in this embodiment, when a pinned history in integrated history 509 is registered as a custom button, the pinning setting is automatically turned OFF. It is expected that a user who registers a custom button from the setting history will use the created custom button rather than integrated history 509. Therefore, the pinning setting set in the setting history becomes unnecessary and the user is likely to unpin the setting. In this embodiment, after registering the pinned history as a custom button, the pinning setting is turned OFF without the user having to manually unpin the setting, improving convenience.

[0134] (Second embodiment) In the first embodiment, a method for turning off the pinning setting set in the setting history when registering the pinned setting history in the custom button has been described. In the first embodiment, even after the user registers the setting history in the custom button, the setting history is displayed in the integrated history 509.

[0135] On the other hand, if a setting history displayed in integrated history 509 is registered as a custom button, the user is likely to use the custom button from next time onwards, and is unlikely to read settings from the pinned setting history displayed in integrated history 509. Therefore, in the second embodiment, a case will be described in which, when registering a setting history displayed in integrated history 509 to a custom button, control is performed so that the pinned setting history is not displayed in the integrated history. Note that descriptions of the same configurations and processes as in the first embodiment will be omitted, and only differences will be clearly described.

[0136] 19 and 20, the processing and display when the setting history displayed in the integrated history 509 is registered in a custom button will be described.

[0137] 19 is a flowchart showing the processing up to registering a history in integrated history 509 as a custom button, and is started when pressing of "Register to Menu" button 519 is detected. This processing is realized by CPU 100 executing a program stored in HDD 103 or ROM 104. Note that this flow is the same as that in FIG. 17, with S1806 replaced by S2101.

[0138] If the pinning flag of the setting history registered in the custom button is ON, the CPU 100 deletes the setting history from the integrated history data table 1000 (S2101).

[0139] If the pinning flag of the selected setting history is OFF, the CPU 100 executes the process of S1807.

[0140] 16(A), when a setting history that has been pinned is registered in a custom button, a screen such as that shown in Fig. 20(A) is displayed on touch panel 200. In Fig. 20(A), setting history 514 displayed in integrated history 509 is hidden, and instead custom button 1711 that can read and set the same settings as setting history 514 is displayed.

[0141] In this embodiment, CPU 100 deletes data linked to the history button ID from the data table in S2101, but a history deletion confirmation screen 2110 shown in Fig. 20(B) may be displayed to allow the user to select whether to delete the history. CPU 100 detects that the "OK" button on history deletion confirmation screen 2110 has been pressed, and executes the processing described in S2106. In this way, setting history that the user does not want to hide can be displayed in integrated history 509.

[0142] In the present embodiment, a method has been described in which, when a setting history that has been pinned is set as a custom button, control is performed so that the selected setting history is not displayed in the integrated history 509. However, when a custom button is registered from a setting history that is displayed in the integrated history 509, control may be performed so that the setting history is not displayed in the integrated history 509, regardless of the pinning setting. In this case, in the processing shown in FIG. 19 , the CPU 100 executes the processing described in S2101 without executing S1805.

[0143] As described above, in the second embodiment, when a setting history that is set to be pinned and that is displayed in the integrated history 509 is registered to a custom button, the setting history is controlled so that the setting history is not displayed in the integrated history 509. According to this embodiment, after registering a setting history that is set to be pinned as a custom button, the user does not need to perform an operation to delete the history himself / herself, which reduces the effort required for the user to perform an operation and improves convenience.

[0144] (Other embodiments) In the first and second embodiments, it has been described that when registering setting history in a custom button, the user inputs a comment to be displayed on the custom button. The name and comment registration screen 1701 may be displayed with the date and time and setting values ​​to be displayed in the setting history pre-entered in the comment input area 1703. In this case, in S1801, the CPU 100 acquires text data indicating the date and time and setting values ​​of the display text from the integrated history data table 1000. In S1802, the CPU 100 displays the text data in the comment input area 1703 of the name and comment registration screen 1701.

[0145] In the first and second embodiments, CPU 100 detects the pressing of a custom button and displays a job setting screen that reflects the settings associated with the custom button and stored in custom button data table 1900. CPU 100 may also detect the pressing of a custom button and execute a job using the job settings stored in association with the custom button. In this way, the user can execute a job simply by pressing a custom button displayed on the home screen.

[0146] In the first and second embodiments, when a setting history is tapped, a job setting screen reflecting the setting history is displayed, and when a setting history is pressed and held, a context menu is displayed. However, the image processing apparatus 1 may detect a tap on a setting history and display a context menu 517. In this case, by displaying a "call settings" button (not shown) in the context menu 517, it is possible to select in the context menu whether to call and set the selected setting history or to register it as a custom button in the menu.

[0147] The present invention can also be realized by executing the following process: software (program) that realizes the functions of the above-described embodiments is supplied to a system or device via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or device reads and executes the program. In this case, the computer program and the storage medium storing the computer program constitute the present invention.

Claims

1. An image processing device having an image processing function and a display unit, a registration means for registering setting information relating to an image processing function, the setting information being set by a user; an execution means for executing an image processing function using the setting information registered by the registration means; a display control means for displaying on an operation screen a button corresponding to the setting information registered by the registration means, the button being for opening a setting screen for an image processing function that reflects the registered setting information; and a setting means for setting the display position of the button to be fixed based on a user operation, the display control means displays buttons corresponding to the setting information registered by the registration means on the operation screen in the order in which the setting information was registered, and the buttons set by the setting means are fixed and displayed at predetermined positions on the operation screen; When new setting information is registered by the registration means, the button corresponding to the newly registered setting information is displayed below the button set by the setting means.

1. An image processing device comprising:

2. An image processing device having an image processing function and a display unit, a registration means for registering setting information relating to an image processing function, the setting information being set by a user; an execution means for executing an image processing function using the setting information registered by the registration means; a display control means for displaying on an operation screen a button corresponding to the setting information registered by the registration means, the button being for opening a setting screen for an image processing function that reflects the registered setting information; and a setting means for setting the display position of the button to be fixed based on a user operation, the display control means displays the buttons that have not been set by the setting means on the operation screen in the order in which the setting information was registered by the registration means, and displays the buttons that have been set by the setting means in fixed positions on the operation screen; When new setting information is registered by the registration means, the button corresponding to the newly registered setting information is displayed below the button set by the setting means.

1. An image processing device comprising:

3. 3. The image processing device according to claim 1, wherein the setting means sets the button so that it is pinned.

4. 4. The image processing device according to claim 1, wherein the display control means displays the button set by the setting means in a manner that allows a user to recognize that the button is displayed in a fixed state.

5. 5. The image processing apparatus according to claim 1, wherein the setting of the button set by the setting unit is cancelled by a user operation.

6. 6. The image processing apparatus according to claim 1, wherein the button corresponding to a copy function and a button corresponding to a scan function are displayed on the operation screen.

7. 7. The image processing apparatus according to claim 1, wherein the setting unit performs the setting for the button selected by the user on the operation screen.

8. 8. The image processing device according to claim 1, further comprising a second display control means for displaying a menu screen including an item for deleting a button selected by a user from among the buttons displayed on the operation screen and an item for performing settings using the setting means.

9. A control method executed by an image processing device having an image processing function and a display unit, comprising: a registration step of registering setting information related to image processing functions, the setting information being set by a user; an execution step of executing an image processing function using the setting information registered in the registration step; a display control step of displaying on an operation screen a button corresponding to the setting information registered in the registration step, the button being for opening a setting screen for an image processing function that reflects the registered setting information; a setting step of setting the display position of the button to be fixed based on a user operation, In the display control step, buttons corresponding to the setting information registered in the registration step are displayed on the operation screen in an order in which the setting information was registered, and the buttons set in the setting step are displayed fixedly at predetermined positions on the operation screen; When new setting information is registered in the registration step, the button corresponding to the newly registered setting information is displayed below the button set in the setting step. A control method comprising:

10. A control method executed by an image processing device having an image processing function and a display unit, a registration step of registering setting information related to image processing functions, the setting information being set by a user; an execution step of executing an image processing function using the setting information registered in the registration step; a display control step of displaying on an operation screen a button corresponding to the setting information registered in the registration step, the button being for opening a setting screen for an image processing function that reflects the registered setting information; a setting step of setting the display position of the button to be fixed based on a user operation, In the display control step, the button that has not been set in the setting step is the setting information is displayed on the operation screen in the order in which it was registered in the setting step, and the button set in the setting step is fixed and displayed at a predetermined position on the operation screen; When new setting information is registered in the registration step, the button corresponding to the newly registered setting information is displayed below the button set in the setting step. A control method comprising:

11. A program for causing a computer to function as each of the means of the image processing apparatus according to any one of claims 1 to 8.

Images