Image processing device, method for controlling the image processing device, and program

JP7899418B2Active Publication Date: 2026-08-03CANON KK
View PDF 4 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
CANON KK
Filing Date
2025-07-25
Publication Date
2026-08-03

AI Technical Summary

Benefits of technology

【0009】 ユーザが好適に設定履歴を選択可能となる。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007899418000001
    Figure 0007899418000001
  • Figure 0007899418000002
    Figure 0007899418000002
  • Figure 0007899418000003
    Figure 0007899418000003
Patent Text Reader

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
Need to check novelty before this filing date? Find Prior Art

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 Art

[0002] Some image processing apparatuses register settings of frequently used jobs in advance and display a custom button for calling those settings on the screen.

[0003] Also, Patent Document 1 describes an image processing apparatus that displays the settings of executed jobs as a setting history on a touch panel and displays a job setting screen that reflects the job settings corresponding to the user's selected setting history 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 user can use the settings of the job without having to make new settings.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems 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 configure. If the number of job setting histories displayed on the image processing device reaches its limit, one of the displayed job setting histories must be hidden in order to display a new job setting histories. As a result, when trying to read and configure frequently used settings from the setting histories, the setting histories may no longer be displayed. Therefore, by registering the job settings stored in the setting histories to a custom button, it is possible to read and configure the job settings from those setting histories even if the setting histories are no longer displayed.

[0006] The settings history needs to be displayed appropriately so that users can easily make selections.

[0007] Therefore, the objective is to provide a method that allows users to select their preferred settings history. [Means for solving the problem]

[0008] The image processing apparatus according to the present invention provides a first for displaying the copy function settings screen. button and scanning function Corresponding Second button An image processing device that displays a home screen including, a first execution means that executes the copy function using the setting value set by the user in the copy function setting screen, vinegar A second execution means that performs the cancellation function, and the job performed by the first execution means setting History and jobs executed by the second execution means setting Jobs sorted by execution order, regardless of the history and the type of function performed. Settings A list of history, which shows the jobs executed by the first execution means based on the fact that the first execution means executed a job. setting The history is added, and based on the fact that the second execution means executed the job, the job executed by the second execution means setting The aforementioned job to which the history is added Settings List of history On the home screenDisplay control means for displaying, and the job setting From the history list By the user The job executed by the selected first execution means setting A third step to display the copy function settings screen, which reflects the settings corresponding to the history. button Display it on the home screen User operations for The system includes a reception means for receiving the job, and the display control means controls the job Settings The job executed by the first execution means selected from the list of history setting The settings screen for the copy function, which reflects the settings corresponding to the history, is displayed, and the receiving means User operation Based on the fact that it has been accepted, An input screen is displayed that accepts text input from the user on the third button, and the text entered via the input screen includes The third of the above button The feature is to display a home screen that includes [this element]. [Effects of the Invention]

[0009] The user will be able to select their preferred settings from the settings history. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows the configuration of the image processing apparatus according to this embodiment. [Figure 2] This figure shows the external appearance of the operation unit 12 of the image processing apparatus according to this embodiment. [Figure 3] This flowchart shows the process from starting the image processing device to displaying the logged-in user's screen. [Figure 4] This figure shows an example of an authentication screen displayed on the touch panel 200 in this embodiment. [Figure 5] This figure shows an example of a home screen displayed on the touch panel 200 of the image processing device according to this embodiment. [Figure 6] This flowchart shows the process from launching the application to executing a job in this embodiment. [Figure 7] This is a schematic diagram showing an example of a copy screen in the copy function of the image processing device in this embodiment. [Figure 8] A schematic diagram showing an example of a data table that stores default settings and settings at the time of job execution for each function in this embodiment. [Figure 9] A flowchart showing a process for determining what to register in a data table that manages an integration history in this embodiment. [Figure 10] A diagram showing an example of an integration history data table stored in the HDD 103 for displaying the integration history in this embodiment. [Figure 11] A flowchart showing a process for generating text of setting values displayed in the setting history of the integration history in the first embodiment. [Figure 12] A flowchart showing a process for displaying the setting history on the home screen in this embodiment. [Figure 13] A flowchart showing a process for starting an application from the integration history in this embodiment. [Figure 14] A diagram showing a data table for managing the order of the setting history displayed in the integration history and the ON / OFF of pinning in this embodiment. [Figure 15] A flowchart showing a process when the setting history displayed in the integration history is pinned and when the pinning setting is canceled in this embodiment. [Figure 16] A diagram showing an example of a screen displayed when registering a custom button from the setting history displayed in the integration history in this embodiment. [Figure 17] A flowchart showing a process for registering the setting history displayed in the integration history in a custom button in this embodiment. [Figure 18] A diagram showing an example of a data table for managing custom buttons in this embodiment. [Figure 19] A flowchart showing a process when registering the setting history displayed in the integration history in a custom button in the second embodiment. [Figure 20]In the second embodiment, this figure shows an example of a screen that appears when the settings history displayed in the integrated history is registered to a custom menu. [Modes for carrying out the invention]

[0011] Embodiments of the present invention will be described in detail below with reference to the attached drawings. Note that the following embodiments do not limit the scope of the present invention as defined in the claims. Furthermore, not all combinations of features described in these embodiments are necessarily essential to the solutions of the present invention.

[0012] (First embodiment) Figure 1 is a block diagram showing the configuration of an image processing apparatus 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, RAM 102, HDD 103, 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 LAN 11. The communication unit 101 sends and receives data via LAN 11. RAM 102 provides system work memory for the operation of the CPU 100. HDD 103 is a hard disk drive that stores programs, document data, and setting data for operating the image processing device 1. HDD 103 may be a storage medium such as a magnetic disk, optical media, or flash memory. Also, HDD 103 does not have to be located inside the image processing device 1. For example, the image processing device 1 may use an external server or PC connected via the communication unit 101 as a storage medium. ROM 104 is a boot ROM that stores the system's boot program. The CPU 100 loads the programs installed on the HDD 103 into the RAM 102 and performs various controls based on those programs. The timer 105 measures time according to the instructions of the CPU 100 and notifies the CPU 100 when the instructed time has elapsed. The fax unit 106 sends and receives fax data through the telephone line 14.

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

[0015] The image processing unit 13 is controlled by the control unit 10 and consists 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 the original image and extracts necessary information from the analysis results. The image generation unit 131 reads the original document (for example, by scanning), digitizes the image of the document, generates image data, and stores it in the HDD 103. The image generation unit 131 can also generate original image data in a different format using the information analyzed by the image analysis unit 130. The image output unit 132 outputs the image data stored in the HDD 103 or the like. For example, the image output unit 132 can print the image data on paper, transmit the image data to an external device or server connected via the communication unit 101, or save the image data to a storage medium connected to the image processing device 1.

[0016] Figure 2 is an overview view of the operation unit 12 according to this embodiment.

[0017] The touch panel 200 is a liquid crystal display unit, on which a touch panel sheet is attached. The touch panel 200 displays an operation screen and soft keys, and when a displayed key is pressed, it transmits its position information to the CPU 100. Therefore, in this embodiment, the touch panel 200 functions as both the display unit 120 in Figure 1 and 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 the document scanning operation. In the center of the start key 201 is a two-color LED 202, green and red, which indicates whether the start key 201 is ready to use. When the green LED 202 is lit, the image processing device 1 can start the job in accordance with the detection of the press of the start key 201. On the other hand, while the red LED 202 is lit, the image processing device 1 cannot start the job. The stop key 203 is used to stop the process that the image processing device 1 is currently running. The numeric keypad 204 consists of number and letter buttons and is used to instruct settings such as the number of copies and switching screens on the touch panel 200. The user mode key 205 is pressed when configuring settings for the image processing device 1.

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

[0020] First, using Figure 5, we will explain the home screen and the integrated history that displays the job setting history on the display unit 120 of the image processing device 1. Furthermore, using Figures 10 and 14, we will explain the data table that manages the display content and display order of the setting history displayed in the integrated history 509 of the home screen.

[0021] Figure 5(A) shows the home screen displayed when user A logs into the image processing device 1. Area 508 displays the username of the currently logged-in user.

[0022] The home screen displays a menu 500 showing buttons for launching various applications. Menu 500 displays application buttons 501-503 that launch applications with default settings. Furthermore, menu 500 displays custom buttons 504 and 505 that launch applications with settings pre-registered by the user. Custom buttons 504 and 505 include a "My" button that is only displayed on the logged-in user's home screen and a "Share" button that is displayed on the home screen even when other users log in. Users can configure whether each custom button is a "My" button or a "Share" button using a method not shown in the illustration.

[0023] The layouts of application buttons 501-503 and custom buttons 504 and 505 are configured by the logged-in user in a manner not shown.

[0024] The slider bar 507 is used to change the area displayed on the display unit 120 by sliding the menu 500 left or right. By moving the slider bar 507 left or right, pressing the arrow button 530, or performing a flick operation within the display area of ​​the menu 500, the hidden area of ​​the menu 500 will be displayed on the display unit 120.

[0025] The Integrated History 509 is an area that displays the configuration history of jobs executed by the Image Processing Device 1. Regardless of the job type, the configuration history of executed jobs is displayed in chronological order, from newest to oldest. Figure 5(A) shows a state where the Image Processing Device 1 has not executed any jobs, or where all job configuration history entries displayed in the Integrated History 509 have been deleted. If the Image Processing Device 1 has the authentication function turned ON, the Integrated History 509 will only display the configuration history of jobs previously executed by the logged-in user. In addition, the number of configuration histories that can be displayed in the Integrated History 509 is predetermined. When the number of configuration histories reaches the upper limit of the number of configuration histories that can be displayed in the Integrated History 509, the oldest configuration history entry will no longer be displayed, and instead, the configuration history of the most recent job entry will be displayed.

[0026] Figure 5(B) shows the home screen after user A has executed a copy job in the state shown in Figure 5(A). In Figure 5(B), the settings history 510 is displayed. The settings history 510 consists of an application icon 511 indicating the type of job, text 512 indicating the date and time the job was executed, and text 513 indicating the setting values ​​of the setting items whose settings have been changed from the default settings. For example, the settings history 510 is the settings history of a copy application, and it indicates that the job was executed after the settings for the number of copies to print (2 copies), color printing, and duplex printing were changed from the default settings. The image processing device 1 detects that the settings history 510 has been pressed and starts the application with the setting values ​​stored in association with the settings history 510 set.

[0027] Figure 5(C) shows the home screen after running a copy job with different settings than those in setting history 510, in the state shown in Figure 5(B). Setting histories 510 and 514 are displayed sorted in descending order of job execution date and time. Here, since setting history 510 is older than setting history 514, setting history 510 is displayed below setting history 514.

[0028] Figure 5(D) shows the home screen after executing another send job in the state shown in Figure 5(C). Since setting history 515 is a different application from setting history 510 and 514, it is displayed with a different application icon.

[0029] Figure 5(E) shows the home screen after the user presses the setting history 510 in the state shown in Figure 5(D), retrieves the settings, and executes a job without changing the settings. If a job is executed with the same settings, the older setting history 510 with the execution date and time will not be displayed, and only the newer setting history 516 will be displayed. By preventing multiple setting histories showing the same settings from being displayed in this way, the integrated history 509 can display setting histories for various settings.

[0030] Figure 5(F) is the screen displayed when the user long-presses the setting history 514 in Figure 5(E). Long-pressing means that the user continues to press the setting history for a predetermined period of time. When the image processing device 1 detects a long-press of the setting history 514, it pops up a context menu 517 on the home screen. The context menu 517 is a menu screen for making settings for the selected setting history. The context menu 517 consists of a "pin" button 518, a "register to menu" button 519, and a "delete" button 520. After the user long-presses the setting history to display the context menu 517, they release their finger from the touch panel 200 once and then press one of the buttons 518 to 520 to execute the process corresponding to each button. The "pin" button 518 is a button to prevent the display of the selected setting history from disappearing from the integrated history 509. The "register to menu" button 519 is a button to display a custom button with the same settings as the selected setting history in the menu 500. The image processing device 1 detects that the "Register to Menu" button 519 has been pressed and displays a name / comment registration screen 1701 on the touch panel 200 to set the name of the custom menu and the comment to be displayed on the custom button. After that, it sets whether the custom button should be a "My Button" or a "Share Button". This makes it possible to display a custom button in the menu 500 for recalling the setting values ​​displayed as setting history. The "Delete" button 520 is used to prevent the selected setting history from being displayed in the integrated history 509.

[0031] Figure 5(G) shows the home screen after the "Pin" button 518 is pressed in Figure 5(F). The setting history that has been instructed to be pinned is displayed at the top of the integrated history 509. Furthermore, a pin icon 521 is added to indicate that the setting history has been pinned. When a user executes a job while a 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 allows users to pin settings displayed in the integrated history 509. By pinning settings that users frequently access and use, it is possible to prevent those settings from disappearing from the integrated history 509. Pinning does not require setting a name or entering comments. Therefore, users can easily display frequently used settings in the integrated history 509. In addition, by displaying pinned settings above other settings, it becomes easier to find those settings in the integrated history 509.

[0033] Figure 5(H) is the screen displayed when the pinning setting in Figure 5(G) is removed from the setting history. The image processing device 1 displays a context menu 517 when the pinned setting history is long-pressed. The context menu 517 consists 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 removes the pinning setting for the button ID corresponding to that setting history and displays the setting history sorted in descending order of job execution time in the integrated history 509.

[0034] Here, using Figure 16, we will explain the screen displayed on the touch panel 200 when the setting history displayed in the integrated history 509 is registered to a custom button. Figure 16(A) is the screen displayed when the setting history 514, which has been set to pin, is long-pressed from the state in Figure 5(G) to display the context menu 517. When the CPU 100 detects that the "Register to Menu" button 519 has been pressed, it displays the custom button name / comment registration screen 1701 shown in Figure 16(B) on the touch panel 200. Figure 16(B) is the name / comment registration screen 1701 after the user has entered "For Regular Use" in the name input area 1702 and "5 copies, color, double-sided" in the comment input area 1703.

[0035] Upon detecting the press of the "OK" button 1704, the CPU 100 displays the home screen 1730 shown in Figure 16(C) on the touch panel 200. At this time, the newly registered custom button 1711 is displayed on the home screen 1730. In addition, the setting history 514 of the integrated history 509 is unpinned. Consequently, the pinned icon 521 for setting history 514 is no longer displayed. Furthermore, because the pinning has been removed, histories 514 to 516 are sorted and displayed in order of job execution time. When a user presses a custom button they have created, the settings screen for the job with the setting value stored in association with the custom button is displayed on the touch panel 200.

[0036] As shown in Figure 16, when a setting history entry that has been pinned is registered as a custom button in the menu, the pinning setting for that setting history entry is removed. Users may temporarily select frequently used settings from the integrated history 509 setting history and pin them. Later, when they want to use that setting permanently, they add a name or comment to it and register it as a custom button so that it is clear when to use that setting. At this time, if a custom button representing the same setting and a pinned setting history entry are displayed, the user may not know which button to use to access the setting. Therefore, when a pinned setting history entry is registered as a custom button, the pinning setting for that setting history entry is removed. In this way, the pinning setting for a setting history entry can be removed without the user having to perform an operation to remove the pinning setting after registering the pinned setting history entry as a custom button.

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

[0038] The button ID is a number used to identify the button that indicates the settings history displayed in the integrated history 509.

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

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

[0041] The displayed text is the date, time, and settings shown in the configuration history of Integrated History 509. The date and time is text data indicating the date and time the job in that configuration history was executed. The setting value is text data of the settings that meet certain conditions among the settings stored in the configuration history. For example, it is the setting value of a setting item that the user changed from the default setting. By displaying the job execution date, time, and settings in Integrated History 509, users can easily remember when and what kind of job that configuration history was performed.

[0042] Figure 10(A) corresponds to Figure 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 for button ID 1001. Button ID 1001 is a copy of the setting history for application ID "101," the file name that stores the setting value 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] Figure 10(C) corresponds to Figure 5(C), and setting history 514 corresponds to the data for button ID 1002.

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

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

[0047] Figure 14 shows an example of a data table 1500 that manages the display order of the setting history and the ON / OFF status of the pinning flag, which are managed by the integrated history data table 1000. This data table is stored on 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 displayed in integrated history 509. The "Pinned" column stores information indicating whether the pinned flag for the setting history of the button ID listed on the left is ON or OFF.

[0049] For example, Figure 14(A) is the data table 1500 when displaying the home screen shown in Figure 5(E). The integrated history 509 displays the setting history in the order of button IDs 1001, 1003, and 1002 from highest to lowest. That is, the integrated history 509 displays the setting history in the order of setting history 516, 515, and 514. Also, since the pin flag is OFF for the setting history of any of the button IDs, no pinning setting has been made.

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

[0051] The following flowchart will explain the processes performed by the image processing device 1.

[0052] First, the process of a user logging into the image processing device 1 will be explained using 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 logged-in user's 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 starts when the power to the image processing device 1 is turned ON.

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

[0054] The CPU 100 displays an authentication screen on the touch panel 200 and then accepts input for a username and password (S302). The CPU 100 detects that the username input area 401 or the password input area 402 has been pressed and displays a soft keyboard (not shown) on the touch panel 200. The user enters the username and password by pressing the soft keyboard. The CPU 100 detects that the "OK" button 403 has been pressed and proceeds to S303.

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

[0056] If the username and password match, the CPU 100 retrieves the user-related information stored in the HDD 103 (S305). User-related information includes, for example, information showing the history of jobs performed by the logged-in user, and information about custom buttons to be displayed on the menu screen shown in Figure 5. Examples include the integrated history data table 1000 shown in Figure 10 and the custom button data table 1900 shown in Figure 18.

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

[0058] Next, using Figures 6 to 8, we will explain the process from when a user logs into the image processing device 1 until they execute a job.

[0059] First, Figure 7 will be used to explain the series of actions a user takes to execute a job on the image processing device 1.

[0060] After the user logs in to the image processing device 1, the home screen shown in Figure 5 is displayed on the touch panel 200. The user selects the application to use from the menu 500 on the home screen. Here, we will explain using the case where the user selects "copy" as an example.

[0061] The user presses the application button 501 displayed in 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 Figure 7(A) on the touch panel 200. Figure 7(A) shows the "Copy" screen 700 with default settings. The "Copy" screen 700 is the job setting screen for 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 making those settings. Button 702 is for viewing a list of the currently set settings. When the user presses button 702, the details of the currently set settings are displayed on the touch panel 200. The "Color Selection" button 703 is for setting whether to print in black and white or in color when making a copy. The "Magnification" button 704 is for setting the magnification when making a copy. The "Paper Selection" button 705 is for setting the size and type of paper to be used when printing. The "Finishing" button 706 is for setting whether to shift the output position after printing each copy or each page. The "Duplex" button 707 is for setting whether to print double-sided or single-sided when making a copy. The "Density" button 708 is for setting the density when printing. The "Document Type" button 709 is for setting the type of document to be scanned. The "ID Card Copy" button 710 is used to configure settings for printing both the front and back of the original document on one side of a single sheet of paper. The "Other Functions" button 711 is used to configure settings that cannot be configured on the "Copy" screen 700, such as adding page numbers or management numbers to the printed document. The "Setting History" button 712 is used to use settings from copy jobs previously performed by the user. The "Frequently Used Settings" button 713 is used to configure settings that the user has registered in advance.

[0063] Icon 715 is a button used to register the settings currently displayed on the job settings screen as a custom button, or to register frequently used settings.

[0064] Figure 7(B) shows the "Copy" screen 700 when the user has set the printer to color print, print 2 copies, sort the output position for each copy, and print double-sided. The user uses the touch panel to make the settings and then 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 configured via the touch panel 200.

[0065] Figure 7(C) shows the screen displayed on the touch panel 200 when the user presses icon 715. The "Register to Custom Button" button 716 is used to register the settings configured on the displayed job settings screen to a custom button. The CPU 100 detects that the "Register to Custom Button" button 716 has been pressed and generates a file to store the currently configured settings. The CPU 100 registers the application ID of the displayed application and the file name of the file that stores the configured settings in the custom button data table 1900, which will be described later in Figure 18. Then, the name / comment registration screen 1701 shown in Figure 16(B) is displayed on the touch panel 200. When the "OK" button 1704 on the name / comment registration screen 1701 is pressed, the CPU 100 registers the entered 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 setting" button 717 registers the settings currently displayed on the job settings screen as settings that can be recalled from the "Frequently Used Settings" button 713. The "Close" button 718 closes the menu 719 that pops up when you press the icon 715.

[0067] Figure 6 is a flowchart showing the process from when the image processing device 1 starts an application to when it executes a job. The process described in Figure 6 is achieved when the CPU 100 executes a program stored in the HDD 103 or ROM 104.

[0068] Figure 6 illustrates the case where the user selects the copy application in menu 500.

[0069] Upon detecting the press of the application button 501 displayed in the menu 500, the CPU 100 displays the "Copy" screen 700 with the default settings shown in Figure 7(A) on the touch panel 200 (S601). Subsequently, the CPU 100 accepts the copy job settings from the user.

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

[0071] Upon determining that the start key 201 has been pressed, the CPU 100 stores the settings of the configured job in the HDD 103 (S603). Figure 8(A) is a schematic diagram of the data table for storing the copy job settings. The copy data table 800 is stored in the HDD 103. The first row of the copy data table 800, default setting 802, shows the default setting value for the copy function, and the second row, current setting 803, shows the setting value for the job that was set when the CPU 100 detected that the start key 201 had been pressed.

[0072] The CPU 100 stores the current settings in the HDD 103 and then controls the image processing unit 13 to execute the job (S604). The CPU 100 controls the image processing unit 13 to generate an output image that reflects the settings set on the "Copy" screen 700. The image processing unit 1 prints the generated output image onto paper.

[0073] Figure 6 illustrates the case where the image processing device 1 executes a copy job. The type of job that the image processing device 1 executes is not limited to copy jobs; the same process is performed when executing transmission jobs, fax jobs, print jobs, and scan jobs. For example, when executing a transmission job, in S603, the CPU 100 stores the current settings in the transmission data table 1400 stored in the HDD 103. Figure 8(C) shows an example of a transmission data table related to a transmission job. The default setting 1402 is a setting value that has been registered in the image processing device 1 in advance, and the current setting 1403 is a setting value that is set when executing a transmission job.

[0074] Figures 9, 11, and 12 illustrate the process for displaying the configuration history in the integrated history 509 after job execution.

[0075] Figure 9 is a flowchart showing the process by which the image processing device 1 determines the contents to be registered in the integrated history data table 1000 based on the job settings stored as the current settings.

[0076] The process described in Figure 9 is achieved by the CPU 100 executing a program stored in the HDD 103 or ROM 104. The process described in Figure 9 is executed after the process described in Figure 6 has been completed.

[0077] The CPU 100 retrieves information registered in the integrated history data table 1000 stored in the HDD 103 (S901). Here, the CPU 100 refers to the application ID of the executed job and retrieves information from the integrated history data table 1000 about the data column of the configuration history that has the same application ID as the executed job.

[0078] The CPU 100 compares the current setting 803 with the setting history data stored in the integrated history data table 1000 obtained in S901 to determine if the same setting as the current setting is stored in the integrated history data table 1000 (S902).

[0079] If there is no configuration history for the same settings as the current settings in the integrated history data table 1000, the CPU 100 executes a process to generate text data to be displayed in the integrated history 509 (S903). The process executed by the CPU 100 in S903 will be described later using Figure 11.

[0080] After generating the text to be displayed as the setting history, the CPU 100 stores the contents to be registered in the integrated history data table 1000 in the HDD 103 (S904). The contents to be registered in the integrated history data table 1000 are 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 existing data exists. The flag indicating whether or not existing data exists is determined based on the judgment result in S902 and indicates whether or not a setting history with the same settings as the executed job is stored in the HDD 103. In S904, since a new setting history is to be generated, the flag indicating whether or not existing data exists is set to "none".

[0081] In S902, if a configuration history with the same settings as the currently executed job is stored in the integrated history data table 1000, the CPU 100 performs the following process: The CPU 100 generates text data indicating the date and time the job was executed (S905). Subsequently, the CPU 100 stores the button ID of the configuration 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 the existing data existence / absence flag in the HDD 103 (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 existence / absence flag indicates existence.

[0082] After completing the process described in S904 or S906, CPU 100 terminates the process shown in Figure 9.

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

[0084] First, the CPU 100 compares the current settings 802 and the default settings 802 of the copy data table 800 stored in the HDD 103 to determine if any setting items have had their values ​​changed (S1101). If the comparison reveals that one or more setting items have had their values ​​changed, the CPU 100 determines that there are setting items whose settings have been changed from the default settings. If no setting values ​​have been changed from the default settings, the CPU 100 terminates the process described in this flowchart.

[0085] If any setting item's value has been changed from its default setting, CPU100 initializes the character counter T, which counts the number of characters in the text data of the setting value, to 0 (S1102).

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

[0087] Next, CPU 100 calculates the total length of the text data obtained so far from the copy data table 800 (S1104). CPU 100 then adds the number of characters X of the text data obtained in S1103 to the current value of the character counter T.

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

[0089] In step S1105, if the CPU 100 determines that the length of the acquired text data exceeds the display limit, it discards the acquired text data for the last setting item for which text data was acquired, and terminates the processing of this flowchart.

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

[0091] CPU 100 determines if there are any setting items whose values ​​have been changed from the default settings (S1107). If there are any setting items whose values ​​have been changed, CPU 100 repeats the processes from S1103 to S1107. At this time, in S1103, CPU 100 obtains text data for the leftmost setting item in the copy data table 800 among the setting items for which text data has not yet been obtained. Once processing has been performed for all setting items whose values ​​have been changed from the default settings, CPU 100 terminates the process described in this flowchart. In the copy data table shown in Figure 8(A), text data is generated up to "2 copies, color, double-sided".

[0092] In Figure 11, if the number of changed settings is large and it is not possible to display all changed settings in the settings history, settings exceeding the character limit for display in the settings history will not be displayed. However, if the changed settings are not displayed for all settings, an indicator such as "..." may be added to the end of the text showing the setting values ​​in the settings history. Alternatively, instead of an indicator, the string "Other" may be displayed to indicate that there are other changed settings besides those displayed.

[0093] Figure 12 is a flowchart showing the process by which the image processing device 1 displays the current settings as a setting history in the integrated history 509. The process described in Figure 12 is achieved by the CPU 100 executing a program stored in the HDD 103 or ROM 104. The process shown in Figure 12 is the process that the CPU 100 executes 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 Figure 9 (S1201).

[0095] Next, CPU 100 checks for the existence or non-existence of existing data in the data read in S1201 (S1202). If there is no existing data, CPU 100 determines whether there is space available in the integrated history data table 1000 (S1203). If there is space available in the integrated history data table, CPU 100 executes the process in S1205, which will be described later.

[0096] If there is no space left in the integrated history data table, CPU 100 deletes the oldest unpinned setting history from the integrated history data table 1000 (S1204). In S1204, CPU 100 refers to data table 1500 and retrieves the setting history for button IDs that have pinning set to OFF from the setting history data table. CPU 100 identifies the setting history with the oldest job date and time from the displayed text of the retrieved setting history and deletes that setting history from the integrated history data table 1000.

[0097] Subsequently, the CPU 100 registers the information read in S1201 into the integrated history data table 1000 (S1205). In S1205, when the CPU 100 registers the setting history information into the integrated history data table 1000, it assigns a button ID. Figure 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 exists in S1202, CPU 100 identifies the button ID of the setting history that has the same settings as the settings obtained in S1201 from the integrated history data table 1000. Then, 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 processing S1205 or S1206, the CPU 100 reads the setting history data table 1500 and determines if there is a setting history in which pinning is set to ON (S1207).

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

[0101] In S1207, if there is a setting history entry in data table 1500 that has been pinned, CPU 100 sorts the setting histories other than the one that has been pinned 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, if there are multiple setting histories that have been pinned, the CPU 100 displays them so that the setting history with the most recent pinning date and time is at the top. When multiple setting histories have been pinned, the order in which the pinned setting histories are sorted is not limited to the above order. For example, the user may set the display order of the pinned setting histories. Alternatively, the pinned setting histories may be sorted in the order of job execution.

[0103] Next, we will explain the process of retrieving a setting from the setting history displayed in the integrated history 509. For example, suppose the home screen shown in Figure 5(B) is displayed on the touch panel 200. At this time, the CPU 100 detects a tap on the setting history 510 and displays the "Copy" screen 700 shown in Figure 7(B) on the touch panel 200. A tap is when the user presses the touch panel and ends the press before a predetermined time has elapsed. When a setting history displayed in the integrated history 509 is tapped, the screen for the job settings with the setting value associated with the tapped setting history is displayed on the touch panel 200.

[0104] Figure 13 illustrates the process of retrieving a setting from the setting history displayed in the integrated history 509. The process described in Figure 13 is achieved by the CPU 100 executing a program stored in the HDD 103 or ROM 104. Figure 13 is a flowchart showing the process of retrieving an application from the integrated history 509.

[0105] CPU 100 determines whether a setting history item displayed in the integrated history 509 has been pressed (S1301). CPU 100 continues the process described in S1301 until it receives confirmation that a setting history item has been tapped.

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

[0107] The CPU 100 displays the job settings screen, which reflects the settings read in S1302, on the touch panel 200, and terminates the process described in this flowchart (S1303).

[0108] By executing the process shown in Figure 13, previously set settings can be recalled with a single touch, eliminating the need to reconfigure settings when using the same settings as a job previously executed. Furthermore, if a user wants to run a job with slightly modified settings from a previously executed job, retrieving past settings from the settings history reduces the effort required compared to configuring from the default settings.

[0109] Next, we will explain the pinning of integration history 509 using Figures 15(A) and 15(B).

[0110] As shown in Figure 5(F), when a user long-presses the settings history, a context menu 517 for configuring settings related to the settings history is displayed. While long-pressing is given as an example of a user operation to display the context menu 517, the method of accessing the context menu 517 is not limited to long-pressing; double-tapping or a dedicated button for calling it can also be used.

[0111] The process of a user setting a pin for a setting history item displayed in the integrated history 509 is explained using Figure 15(A). The process described in Figure 15(A) is implemented by the CPU 100 executing a program stored in the HDD 103 or ROM 104. The flowchart shown in Figure 15(A) is initiated when the CPU 100 detects that the "Pin" button 518 in the context menu 517 has been pressed. Here, the example is given where the pin setting for the Nth setting history item displayed in the integrated history 509 is set to ON.

[0112] CPU100 retrieves the button ID of the setting history for which the pinning setting was turned ON (S1601).

[0113] CPU100 changes the button IDs and pinning flags currently stored in the 1st to N-1th positions of data table 1500 to the 2nd to Nth positions (S1602).

[0114] Finally, CPU 100 stores the button ID obtained in S1601 in the first entry of data table 1500, turns on the pinning flag, and terminates this flowchart (S1603).

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

[0116] In this embodiment, the process for unpinning a setting history item that has been pinned will be explained using Figure 15(B). The process shown in Figure 15(B) is implemented by the CPU 100 executing a program stored in the HDD 103 or ROM 104. The process shown in Figure 15(B) is initiated when the CPU 100 detects that the "Unpin" button 522 has been pressed from the context menu 517 shown in Figure 5(H).

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

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

[0119] If there is no setting history where the pinning flag is 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 it on the touch panel 200 (S1606).

[0120] If there is a setting history in data table 1500 with the pinning flag set to ON, CPU 100 executes a process to remove that setting history from the sorting target (S1607). Then, CPU 100 sorts the remaining setting history in order of job execution time and displays it on touch panel 200 after the setting history with the pinning flag set to ON (S1608).

[0121] Figures 17 and 18 illustrate the operations and processes for registering the settings history displayed in the integrated history 509 to a custom button.

[0122] Figure 18 illustrates the custom button data table 1900, which manages custom buttons. The custom button data table 1900 consists of a button ID, application ID, data, name, and comment. The button ID is an ID used to identify a custom button, and when the CPU 100 registers a new custom button, it assigns a button ID that does not overlap with other custom buttons. The application ID and data are the same as those described in the integrated history data table 1000 shown in Figure 10. The name and comment are text data displayed on the custom button. The name and comment are text set on the name / comment registration screen 1701 shown in Figure 16(B), and indicate what kind of settings the custom button has, what situations it is used in, etc. The custom button data table 1900 is stored in the HDD 103 and read and written by the CPU 100 via the RAM 102.

[0123] Figure 17 shows the flow from registering the settings history displayed in the integrated history 509 as a custom button. Processing begins when the CPU 100 detects the pressing of the "Register to Menu" button 519. This process is achieved by the CPU 100 executing a program stored in the HDD 103 or ROM 104.

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

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

[0126] Next, the CPU 100 displays the custom button name and comment registration screen 1701 on the touch panel 200 (S1803). After detecting that the "OK" button 1704 on the button name and comment registration screen 1701 has been pressed, the CPU 100 registers the name and comment in the custom button data table 1900. Figure 18(B) shows the custom button data table 1900 after the name "For regular use" and the 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 refers to the data table 1500 to determine whether the pinning setting of the selected setting history is ON. If the pinning setting of the selected setting history is OFF, the CPU 100 executes the process in S1807 described below.

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

[0129] The CPU 100 displays the integrated history 509, which is the configuration history registered in the integrated history data table 1000 sorted 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 Figure 12.

[0130] In this embodiment, the pinning setting for the setting history registered to the custom button is turned OFF. In S1806, the CPU 100 may display the pinning status change confirmation screen 1740 shown in Figure 16(D) on the touch panel 200, allowing the user to select whether or not to unpin the setting. In this way, the user can be confirmed whether or not to unpin the setting when registering to the custom button. This prevents the pinning setting from being removed for setting history that the user does not want to be unpinned.

[0131] Finally, we will explain the process of reading and configuring job settings registered as a custom button from the home screen. The CPU 100 detects that a custom button displayed on the home screen has been pressed and identifies the button ID of the pressed custom button. The CPU 100 reads the data for the custom button with the pressed button ID from the custom button data table 1900. For example, if the button ID of the pressed custom button is "1903", the CPU 100 reads "data3.xml". The CPU 100 displays the job settings screen with the read settings on the touch panel 200. By registering the setting history to the custom button, even if the setting history is no longer displayed in the integrated history 509, the settings for that job can be read and configured from the home screen.

[0132] In this embodiment, the custom button registered according to the user's registration instructions and the setting history generated during job execution are displayed. Furthermore, if the setting history is selected, the user can input instructions to register the job settings that can be set from that setting history to the custom button. This allows the user to register job settings that can be set from the setting history to the custom button without having to configure the job itself. Consequently, the user's effort is reduced when registering job settings that can be set from the setting history to the custom button.

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

[0134] (Second Embodiment) In the first embodiment, a method was described for turning off the pinning setting in a setting history when registering the setting history with pinning enabled to a custom button. In the first embodiment, even after the user registers the setting history to a custom button, the setting history is displayed in the integrated history 509.

[0135] On the other hand, if the setting history displayed in the integrated history 509 is registered as a custom button, the user is likely to use the custom button on subsequent occasions, and the setting is unlikely to be read from the pinned setting history displayed in the integrated history 509. Therefore, in the second embodiment, we will describe a case in which, when registering the setting history displayed in the integrated history 509 as a custom button, the pinned setting history is not displayed in the integrated history. Note that descriptions of the same configuration and processing as in the first embodiment are omitted, and only differences are specified.

[0136] Using Figures 19 and 20, we will explain the process and display when the settings history displayed in the integrated history 509 is registered to a custom button.

[0137] Figure 19 is a flowchart showing the process up to registering the history of the integrated history 509 as a custom button, and it starts when the "Register to Menu" button 519 is detected to be pressed. This process is achieved by the CPU 100 executing a program stored in the HDD 103 or ROM 104. Note that this flowchart is the same as in Figure 17, but with S1806 replaced by S2101.

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

[0139] If the pinning flag for the selected setting history is OFF, CPU100 executes process S1807.

[0140] As shown in Figure 16(A), when a setting history with pinned items is registered to a custom button, the touch panel 200 displays a screen as shown in Figure 20(A). In Figure 20(A), the setting history 514 displayed in the integrated history 509 is hidden, and instead, a custom button 1711 is displayed that allows you to read and set the same settings as the setting history 514.

[0141] In this embodiment, the CPU 100 deleted the data associated with the history button ID from the data table in S2101. However, as shown in Figure 20(B), a history deletion confirmation screen 2110 may be displayed, allowing the user to select whether or not to delete the history. The CPU 100 detects that the "OK" button on the history deletion confirmation screen 2110 has been pressed and executes the process described in S2106. In this way, setting history that the user does not want to hide can be displayed in the integrated history 509.

[0142] In this embodiment, a method was described for controlling the display of a selected setting history in the integrated history 509 when a setting history that has been set to be pinned is set as a custom button. However, when a custom button is registered from a setting history displayed in the integrated history 509, the system may be controlled so that the setting history is not displayed in the integrated history 509 regardless of the pinning setting. In this case, in the process shown in Figure 19, the CPU 100 executes the process described in S2101 without executing S1805.

[0143] As described above, in the second embodiment, when registering a setting history with pinned items displayed in the integrated history 509 to a custom button, control was implemented to prevent the setting history from being displayed in the integrated history 509. According to this embodiment, after registering a setting history with pinned items as a custom button, the user does not need to delete the history themselves, thus reducing the effort required from the user and improving convenience.

[0144] (Other embodiments) In the first and second embodiments, it was explained that when registering the setting history to a custom button, the user enters a comment to be displayed on the custom button. Alternatively, the name / comment registration screen 1701 may be displayed, in which the date, time, and setting values ​​to be displayed in the setting history are pre-entered in the comment input area 1703. In that case, in S1801, the CPU 100 obtains text data indicating the date, time, and setting values ​​of the display text in the integrated history data table 1000. In S1802, the CPU 100 displays the text data in the comment input area 1703 of the name / comment registration screen 1701.

[0145] In the first and second embodiments, the CPU 100 detects the press of a custom button and displays a job setting screen that reflects the settings stored in the custom button data table 1900 associated with the custom button. Alternatively, the CPU 100 may detect the press of a custom button and execute a job using the job settings stored associated 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 settings screen reflecting that setting history is displayed, and when a setting history is long-pressed, a context menu is displayed. However, the image processing device 1 may also detect a tap on the setting history and display a context menu 517. In this case, by displaying an "Recall Settings" button (not shown) in the context menu 517, the user can choose from the context menu whether to recall and set the selected setting history or register it as a custom button in the menu.

[0147] Furthermore, the present invention can also be realized by performing the following process: that is, supplying software (program) that realizes the functions of the above-described embodiment to a system or device via a network or various storage media, and having the computer (or CPU, MPU, etc.) of that system or device read and execute 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 that displays a home screen including a first button for displaying the settings screen for the copy function and a second button corresponding to the scan function, A first execution means that executes the copy function using the settings set by the user on the copy function settings screen, A second execution means for performing a scanning function, A display control means for displaying a list of job setting histories on the home screen, which is a list of job setting histories arranged in the order of job execution regardless of the type of function performed, wherein the job setting histories of jobs executed by the first execution means and the job setting histories of jobs executed by the second execution means are added based on the execution of a job by the first execution means, and the job setting histories of jobs executed by the second execution means are added based on the execution of a job by the second execution means, A reception means for receiving user input to display a third button on the home screen that displays a copy function settings screen reflecting the settings values ​​corresponding to the settings history of a job executed by the first execution means, selected by the user from the list of job settings history, It has, The display control means is The settings screen for the copy function is displayed, which reflects the setting values ​​corresponding to the setting history of the job executed by the first execution means selected from the list of job setting history. Based on the fact that the user operation has been received by the reception means, an input screen is displayed that accepts text input from the user on the third button. An image processing apparatus characterized by displaying a home screen that includes a third button containing text entered via the input screen.

2. The image processing apparatus according to claim 1, characterized in that the display control means displays a copy function setting screen that reflects the setting values ​​corresponding to the setting history of a job executed by the first execution means selected from the list of job setting history, based on the selection of the third button.

3. The image processing apparatus according to claim 1, further comprising setting means for setting text corresponding to the third button.

4. The image processing apparatus according to claim 3, characterized in that the text set by the setting means is at least one of a name and a comment.

5. The image processing apparatus according to claim 1, characterized in that the list of job setting history displays the setting history of jobs executed by the first execution means along with the execution date and time of the job on the home screen.

6. The number of job configuration histories displayed in the job configuration history list has an upper limit. The image processing apparatus according to claim 1, characterized in that if the number of job setting histories included in the list of job setting histories reaches the upper limit when the first execution means executes a job, at least one of the job setting histories included in the list of job setting histories is deleted.

7. The image processing apparatus according to claim 6, characterized in that the job setting history to be deleted is the job setting history of the job with the oldest execution date and time among the job setting histories displayed in the list of job setting histories.

8. The image processing apparatus according to claim 1, further comprising setting means for setting the setting history of a job selected by the user from the list of job setting history to be fixed and displayed in a predetermined position in the list of job setting history.

9. The image processing apparatus according to claim 8, characterized in that the predetermined position is the starting position of the list of job setting history.

10. The display control means, based on the acceptance of the user operation, when a job setting history that has been set by the setting means to be fixed and displayed in the predetermined position in the list of job setting histories has been selected, displays the third button on the home screen that is associated with the job setting history that has been fixed and displayed in the predetermined position in the list of job setting histories. The image processing apparatus according to claim 9, wherein the setting means is characterized by releasing the setting.

11. A control method for an image processing device that displays a home screen including a first button for displaying the settings screen for the copy function and a second button corresponding to the scan function, The first execution step involves executing the copy function using the settings set by the user on the copy function settings screen, A second execution step in which the scanning function is performed, A first display control step to display on the home screen a list of job setting histories, which is arranged in the order of job execution regardless of the type of function performed, including the job setting histories of jobs performed in the first execution step and the job setting histories of jobs performed in the second execution step, wherein the job setting histories of the copy function jobs performed based on the execution of the copy function jobs are added, and the job setting histories of the scan function jobs performed based on the execution of the scan function jobs are added. A second display control step involves displaying the settings screen for the copy function, which reflects the setting values ​​corresponding to the settings history of the copy function job selected from the list of job settings history, A reception step for receiving user input to display a third button on the home screen that displays a copy function settings screen reflecting the settings values ​​corresponding to the job settings history of the copy function selected by the user from the list of job settings history, Based on the acceptance of the user operation in the reception process, a third display control step is performed to display an input screen that accepts text input from the user on the third button, A control method for an image processing apparatus, characterized by comprising: a fourth display control step of displaying a home screen including a third button containing text entered via the input screen.

12. A computer program for causing a computer to function as each means of an image processing apparatus according to any one of claims 1 to 10.