Aspects of the present invention generally relate to an image processing apparatus, a method for controlling the image processing apparatus, and a storage medium.
A certain image processing apparatus executes a plurality of applications to perform various kinds of data processing. Such an image processing apparatus is provided with a function of storing setting data corresponding to applications that have been executed by a user. Japanese Patent Application Laid-Open No. 8-292864 discusses a user interface for automatically setting default values for each application and application customization processing.
A large majority of users of image processing apparatuses uses a small number of setting patterns for applications to be executed. Particularly for each application, a user needs to reset patterns each time although the user uses less number of setting patterns.
Although setting registration functions (default value change, custom menu, mode memory, etc.) are proposed to avoid pattern setting each time, the user does not bother to register settings.
Meanwhile, Japanese Patent Application Laid-Open No. 8-292864 discusses a method for predicting a user's intention to save the user the trouble of registering settings for applications. With this method, however, the user may not grasp settings registered to an image processing apparatus.
Aspects of the present invention are generally directed to providing a mechanism for simultaneously displaying setting data automatically registered in the course of execution of each application and setting data set for each application by a user. This enables the user to conveniently select setting data to be executed.
According to an aspect of the present invention, an image processing apparatus for executing a plurality of applications associated with specific functions to perform image processing includes a first registration unit configured to, when executing any one of the plurality of applications, automatically register first setting data set for the any one of the plurality of applications in a storage unit in association with the application, a second registration unit configured to, according to a registration instruction, register second setting data set for any one of the plurality of applications in association with the any one of the plurality of applications, and a display control unit configured to display on a display unit a calling-up and setting screen including a first button group for calling up the first setting data automatically registered in the storage unit and a second button group for calling up the second setting data registered in the storage unit.
According to the present disclosure, it is possible to display setting data automatically registered in the course of execution of each application and setting data set for each application by a user in an identical calling-up and setting screen, enabling the user to conveniently select setting data to be executed.
Further features of the present disclosure will become apparent from the following description of exemplary embodiments with reference to the attached drawings.
Various exemplary embodiments will be described in detail below with reference to the drawings.
Referring to
The communication unit 12 transmits and receives data via the LAN 11. The RAM 13 provides a system work memory necessary for operations of the CPU 10. The HDD 14 may be a storage medium such as a magnetic disk, an optical medium, and a flash memory.
The HDD 14 is configured to store in a table format (described below) document data and setting data associated with each application. The HDD 14 does not need to be included in the MFP 100. An external server or a personal computer (PC) may be used as a storage apparatus via the communication unit 12. The ROM 15 is a boot ROM which stores a boot program of a system. The CPU 10 loads a program installed in the HDD 14 into the RAM 13 by using the boot program in the boot ROM (ROM 15), and performs various control based on the loaded program. The HDD 14 further includes a specific area for managing a button group (an automatically registered button group) displayed in a specific area in a recall portal screen 300 (described below). The relevant specific area is used as a first-in first-out (FIFO) area.
A timer 16 performs timing processing according to an instruction of the CPU 10. When a specified time interval has elapsed, the timer 16 notifies the CPU 10 of the relevant passage of time as an interruption.
An operation unit 20 is controlled by the control unit 1, and includes a display unit 21 and an input unit 22. The display unit 21 is used to display information about the MFP 100 to a user. The input unit 22 receives an input from the user via an interface, such as a touch panel, a mouse, a camera, an audio input, and a keyboard.
The display unit 21 displays a user interface (UI) screen (described below) to receive settings from the user.
An image processing unit 30 is controlled by the control unit 1, and includes an image analysis unit 31, an image generation unit 32, and an image output unit 33. The image analysis unit 31 analyzes the structure of a document image, and extracts necessary information from an analysis result. The image generation unit 32 reads a document (for example, by scanning the document), converts an image of the document into image data in digital form, and stores the image data in the HDD 14.
The image generation unit 32 can also generate document image data in another format by using the information analyzed by the image analysis unit 31. The image output unit 33 outputs the image data stored in the HDD 14. The image data can be output, for example, by printing the document image data on paper, by transmitting via the communication unit 12 the document image data to an external device, a server, a facsimile, etc. connected to the network, or by storing the document image data in a storage medium connected to the MFP 100.
Referring to
Various keys and buttons operated by the user will be described below.
A start key 201 is used to instruct to start a document read operation. Two (green and red) light emitting diodes (LEDs) 202 are provided at the center of the start key 201 to indicate whether the start key 201 is usable or not. A stop key 203 is used to stop the current operation. A numeric keypad 204 includes numeric and character buttons, and is used to instruct to set the number of copies or to change the screen of the display unit 21. A user mode key 205 is pressed to set the MFP 100.
A recall portal screen according to the present exemplary embodiment will be described below.
Referring to
In the present exemplary embodiment, the CPU 10 performs control to display fixed settings in the fixed setting area 301 and display recall settings in the recall settings display area 302, allowing the user to easily identify each area. Buttons 303 to 307 are pressed to call up setting data to be fixedly preset by the user in setting screens (described below) illustrated in
The button 310 is pressed to select monochrome printing and 2in1 in setting data associated with the copy application 402. Processing (registration and deletion) for setting data subjected to automatic registration will be described below. In the present exemplary embodiment, buttons are displayed in different areas, and shapes of buttons to be displayed are differentiated to allow the user operating the relevant UI screen to perform button operations with sufficient visibility.
When the recall portal screen 300 is activated, the recall portal screen 300 first reads a fixed registration data management table 1201 illustrated in
Then, the CPU 10 performs control to search for an entry having the same application ID stored in an application icon table 1211 illustrated in
In the recall portal screen 300, the CPU 10 processes the entire fixed registration data management table 1201 illustrated in
The recall portal screen 300 sequentially reads entry 1102 and subsequent entries. Each time the recall portal screen 300 calls up an entry, the CPU 10 refers to the application ID. When the application ID is “0000”, the CPU 10 performs control not to display the corresponding button. On the other hand, when the application ID is not “0000”, the CPU 10 performs control to display a display TXT on the corresponding button.
Then, the CPU 10 performs control to search for an entry having the same application ID stored in the application icon table 1211 illustrated in
Thus, the CPU 10 can display the UI screen illustrated in
Hereinafter, to simplify descriptions, all of the fixed settings are collectively referred to as fixed settings 301S in connection with the fixed setting area 301. Similarly, all of the recall settings are collectively referred to as recall settings 302S in connection with the recall settings display area 302.
In the present exemplary embodiment, button shapes for the fixed settings 301S are differentiated from button shapes for the recall settings 302S to allow the user to visually identify each area based on button shapes.
Each of the buttons for the fixed settings 301S displays the icon of an application to be activated by pressing the relevant button, and a button name input by the user. The button name is input to a button specified in a user setting registration screen (described below) by the user. Unregistered buttons are not displayed.
Meanwhile, for each of the buttons for the recall settings 302S, the CPU 10 performs control to display the icon for an application to be activated by pressing the relevant button, and a text expressing the summary of the setting generated by display TXT generation (refer to step S606 in
Referring to
Each application can be identified by the application ID, and stores data described in a recall data registration configuration and a setting data management table (described below).
When a button displayed on the operation unit 20 is pressed, the recall portal 401 calls up recall data according to the button, and transmits a relevant action ID to the application ID (refer to a notification 406). An application specified by the application ID reads setting data according to the received action ID, and sets the setting data. Needless to say, any kind of application can be specified as long as it is capable of exchanging the above-described setting data.
Referring to
A Cancel button 506 is used to cancel data registration, and a Next button 507 is used to display the following fixed setting registration screen 508.
The fixed setting registration screen 508 illustrated in
The fixed setting registration screen 508 includes an area 509 for confirming the contents of an input text, and a keyboard (software keyboard) 510 for inputting characters. Pressing a Back button 511 displays the fixed setting registration screen 501 illustrated in
An example case where the following new job is executed by the copy application 402 illustrated in
A job setting is a setting of {3 copies, color copy, one-sided printing, 4in1}.
The image output unit 33 illustrated in
Although the present exemplary embodiment will be described below based on the copy application 402 as an example, the copy application 402 may be replaced with the E-mail application 403, the Fax application 404, or any other applications capable of exchanging data illustrated in
More specifically, the flowchart illustrated in
In step S601, when the copy application 402 completes job execution, the recall portal 401 starts job completion processing. In step S602, when the recall portal 401 starts the job completion processing, the recall portal 401 first acquires an application ID. In this case, the recall portal 401 starts processing corresponding to step S701 in
More specifically, in step S703, the copy application 402 transmits the application ID to a registered ID list acquisition routine of the recall portal 401 (refer to a request 407 illustrated in
To be more precise, when the recall portal 401 starts processing in step S701 illustrated in
In step S604, the recall portal 401 reads setting data corresponding to the action ID acquired from the copy application 402, and searches for the setting data registered in the HDD 14 to determine whether the read setting data is identical to the currently executed setting data. When the recall portal 401 determines that the read setting data is identical to the currently executed setting data (YES in step S604), then in step S608, the recall portal 401 ends the job completion processing without performing the recall data registration processing.
In the present exemplary embodiment, on the other hand, when the recall portal 401 determines that the read setting data is not identical to the currently executed setting data (NO in step S604), then in step S605, the recall portal 401 invokes a setting data storage processing routine (refer to
Upon reception of a registered ID list acquisition request 407 from the copy application 402 as illustrated in
Referring to the registered ID list acquisition started in step S701 illustrated in
In the present exemplary embodiment, the registered ID list is a list of {0001, 0002, 0003, 0004}.
Referring to the job completion processing started in step 5601 illustrated in
More specifically, in step S801, the recall portal 401 starts the setting data storage processing. In step S802, the recall portal 401 determines whether an upper limit of settings is reached. The recall portal 401 makes such determination, for example, based on whether there is any unused entry.
In this case, the recall portal 401 determines whether there is any unused entry based on whether the first item of an entry is “0”. When the recall portal 401 determines that there is no unused entry (Upper Limit Reached in step S802), then in step S806, the recall portal 401 exits this processing routine.
For example, in the case of the example illustrated in
When a job completion processing routine of the copy application 402 requests to register recall data in step S607 illustrated in
Referring to the recall data registration processing, in step S902, the recall portal 401 reads registration data from the recall data management table 1101 illustrated in
Upon reception of the notification 405, the E-mail application 403 deletes the entry 1012 corresponding to “action ID=0003” in the setting data management table 1008 illustrated in
Referring to the recall data registration processing illustrated in
In the second exemplary embodiment, instead of user setting buttons, application activation buttons are arranged on a recall portal screen.
Referring to
According to the present exemplary embodiment, a user can arbitrarily select whether to use automatically registered setting data or to execute a user-selected application on the recall portal screen 1300.
Each process of the present exemplary embodiment can be implemented also by executing software (program) acquired via a network or various storage media on a processing apparatus (CPU or processor), such as a personal computer.
The above-described exemplary embodiments are not seen to be limiting and can be modified in diverse ways (including organic combinations of these exemplary embodiments) without departing from the spirit and scope thereof. These modifications are not excluded from the scope of the present disclosure.
While the present disclosure has been described with reference to exemplary embodiments, it is to be understood that these exemplary embodiments are not seen to be limiting. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.
Number | Date | Country | Kind |
---|---|---|---|
2014-018268 | Feb 2014 | JP | national |
This application is a Continuation of U.S. patent application Ser. No. 17/173,675, filed Feb. 11, 2021, which is a Continuation of U.S. patent application Ser. No. 15/907,091, filed Feb. 27, 2018, now U.S. Pat. No. 10,951,782, which is a Continuation of U.S. patent application Ser. No. 14/610,943, filed Jan. 30, 2015, now U.S. Pat. No. 9,936,088, which claims the benefit of Japanese Patent Application No. 2014-018268, filed Feb. 3, 2014, all of which are hereby incorporated by reference herein in their entirety.
Number | Date | Country | |
---|---|---|---|
Parent | 17173675 | Feb 2021 | US |
Child | 18303416 | US | |
Parent | 15907091 | Feb 2018 | US |
Child | 17173675 | US | |
Parent | 14610943 | Jan 2015 | US |
Child | 15907091 | US |