JP2002328757A - User interface controller and user interface control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a user interface controller and a user interface control method capable of reducing the work man-hours or artificial mistake of a developer by realizing a function for displaying a reason why the setting of a specific item is made impossible without occurring the omission of the detection of the reason. SOLUTION: A rule for preventing any mismatching generated between set data is described in a conflict processing rule description file (301). An instruction to make it impossible to directly change the state of a prescribed set item after applying the specific conflict processing rule and an identifier indicating a reason why the direct change is made impossible according to the instruction can be described in the conflict processing rule description file (301). An inference engine (302) refers to the conflict processing rule description file (301), and when the input set value is turned into an object to which any conflict processing rule should be applied, the inference engine (302) applies this rule.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a user interface control apparatus and method for avoiding inconsistency occurring between setting data for a predetermined control object input via a user interface.

[0002]

2. Description of the Related Art A user interface (hereinafter referred to as "UI")
Also called. ) Receives input of a plurality of setting values from a user via the device, and a device controlled based on those setting values,
There are many. An image forming system (printer system) that is connected to a host computer and performs an image forming process based on information set in the host computer is one example. In general, a host computer of a printer system generally includes a so-called printer driver for controlling a printing operation and a UI for receiving print settings from a user.
And a print processing-related program including

Each time a print processing-related program receives an input of a set value from a user via a UI, the program evaluates a relation between the set value and a related set value among a plurality of set values set up to that time. It is determined whether there is any inconsistency (conflict) between the set values. Examples of conflicts include settings that are expected to be inconvenient for the user, such as settings for performing double-sided printing on OHP sheets set as recording media, and settings that cause the printer to perform operations that are not possible. There is.

When there is a conflict, it is necessary to perform a conflict process for avoiding the conflict.

Conventionally, a plurality of setting value conditions (conflict processing rules) that require conflict processing are stored as a list in a file or the like, and this file is read into a conflict processing program, thereby causing a conflict. Some perform processing. This method is superior in that the conflict processing program can be used for general purposes without depending on a specific set value.

By the way, depending on the conflict processing,
In addition to changing the setting values in the data structure, changing the setting values on the UI controls (hereinafter, also simply referred to as "controls") and graying out the controls (displaying the setting items in light gray) In some cases, the item performs processing to inform the user that the item cannot be directly changed (by a mouse or the like).

[0007] As a result of the conflict processing including such processing, a control that cannot be used depending on other items cannot be directly changed by being grayed out as described above. When the cause that cannot be changed directly (that is, another item having a dependency) is in another sheet or dialog box among a plurality of sheets or dialog boxes, it is difficult for the user to understand the cause. To solve this problem, some display a message near the grayed-out control, including a reason why the control cannot be changed directly.

[0008]

Conventionally, in order to display the reason why the control is grayed out and cannot be directly changed as described above, a program dedicated to reason detection has been created separately from the description of the conflict processing. I needed to. In order to perform the reason detection accurately, a program code for the reason detection process corresponding to each of the processes for grayout is required. Further, not only is it troublesome to create this program code, but also there is a problem that the reason detection processing is likely to be omitted or discrepant due to the addition / change of the grayout processing.

Further, for example, if a specific device option (for example, a staple finisher) is not installed, the control cannot be used, and the control is grayed out such that the control is in an exclusive relationship with other items. There may be more than one reason. In such a case, the reason detection process becomes more complicated, and the above-mentioned problem concerning the creation of the program becomes more prominent.

The present invention has been made in view of such a problem, and realizes a function of displaying the reason why a specific item cannot be set on a user interface without causing omission or discrepancy in reason detection. It is another object of the present invention to provide a user interface control device and method capable of reducing the number of work steps and human error of a developer.

[0011]

To achieve the above object, for example, a user interface control device of the present invention comprises:
The following configuration is provided. That is, a user interface control device for avoiding inconsistency that occurs between setting information for a predetermined control target input via a user interface and / or environment information of the control target, wherein the setting information and / or Or, holding means for holding a conflict processing rule indicating a conflict avoidance strategy applied in accordance with the environment information, and controlling whether or not the state of a predetermined setting item in the user interface can be directly changed according to the conflict processing rule. State control means, notification control means for notifying via the user interface a message including a reason that the state of the predetermined setting item is directly unchangeable by the state control means,
The conflict processing rule includes an instruction for directly disabling the state of a predetermined setting item, and reason information indicating a reason for disabling the direct change by the instruction.
It is characterized by including.

[0012]

FIG. 1 is a block diagram of a print processing system according to an embodiment of the present invention. The print processing system includes a host computer 3
000 and a printer 1500.

In the host computer 3000, 1
Reference numeral 2 denotes a CPU that controls each device connected to the system bus 4 as a whole; and 2, a RAM that functions as a main memory, a work area, and the like of the CPU 1. 3 is various programs,
A ROM for storing data, a font ROM 3a for storing various fonts, a boot program and a BIOS.
And the like, and a data ROM 3c for storing various data.

5 is a keyboard controller (KBC)
Controls the key input from the keyboard 9 or a pointing device (mouse) not shown. Reference numeral 6 denotes a CRT controller (CRTC), and a CRT display (CRT display).
RT) 10 is controlled.

The external memory 11 (whose access is controlled by the disk controller (DKC) 7) includes a hard disk (HD) or a floppy (registered trademark) disk (F
D) and the like, as shown in the figure, an operating system program (hereinafter referred to as OS) 205, various applications (for example, a document processing application program for performing document processing in which graphics, images, characters, tables, and the like are mixed) 201, print processing-related In addition to storing the program 204, it also stores user files, editing files, and the like. The print processing related program 204 is a program for generating print data described using a page description language,
It can be commonly used for a plurality of printers of the same series.
In addition, a printer control command generation module (hereinafter referred to as “printer driver”) 2041 and a printer driver UI control module 2042 are included.

Reference numeral 8 denotes a printer controller (PRTC) which controls the printer 1 via a bidirectional interface 21.
500, and performs communication control processing with the printer 1500.

The application stored in the external memory 11 is loaded into the RAM 2 and executed by the CPU 1. Further, the CPU 1 executes, for example, rasterization of the outline font on the RAM 2, and executes WYSIWYG (What you see is W
hat you get). Furthermore, CPU1
Opens various registered windows based on a command specified by a mouse cursor or the like (not shown) on the CRT 10 and executes various data processing. When executing printing, the user opens a print setting setting screen (controlled by the printer driver UI control module 2042), and can set a printer and a print process for the printer driver 2041 including selection of a print mode. it can.

In the printer 1500, a CPU 12 controls the entire printer 1500. 19 is CP
U12 functions as a main memory, work area, etc., as well as an output information development area, an environment data storage area, and an NVR.
This RAM is used for AM and the like, and is configured so that the memory capacity can be expanded by an optional RAM connected to an extension port (not shown). 13 is RO
M, a font ROM 13 for storing various fonts
a, Program ROM 13 for storing control programs and the like
b and a data ROM 13c for storing various data.

The external memory 14 (memory controller (M
C) The access is controlled by 20) is a hard disk (HD), floppy disk (FD), IC card, or the like that is connected as an option, and stores font data, emulation programs, form data, and the like. When the external memory 14 such as a hard disk is not connected, the data ROM 13c of the ROM 13
Then, information used by the host computer 3000 is stored. The external memory 14 is not limited to one, and may include a plurality of external memories. For example, an external memory storing an optional font card, a program for interpreting a printer control language of a different language system, and the like in addition to the built-in fonts may be provided. It may be configured so that a plurality of connections can be made.

An operation panel 1501 is provided with an operation panel for receiving an operation from a user, and the operation panel is provided with switches for operation and an LED display (not shown). Further, an NVRAM (not shown) may be provided to store the printer mode setting information from the operation panel 1501.

The printer CPU 12 sends an image signal as output information to a printing unit (printer engine) 17 connected to the system bus 15 via a printing unit interface 16 based on a control program stored in a program ROM 13b of the ROM 13. Output. The CPU 12
Can communicate with the host computer 3000 via the input unit 18 and can notify the host computer 3000 of information and the like in the printer 1500.

(Software Configuration) FIG. 2 shows a state in which a predetermined application and a print processing-related program to be controlled by the printer 1500 are started, and the RAM 2 is loaded into the RAM 2 on the host computer 3000.
3 shows a memory map of the first embodiment. As shown in the figure, an application 201, a print processing related program 204, and related data 203, as well as a BIOS 206 and an OS 205, are loaded into the RAM 2, and a free memory area 202 is also secured. As a result, the application 201 and the print processing related program 204 are in an executable state.

A printer driver UI control module 2042 in the print processing related program 204 displays a print setting screen on the CRT 10 in response to a print setting command from the user, and allows the user to make settings.

FIG. 8 shows a display example of a print setting screen as a UI. In the figure, a [Print Style] column 80 is a column for designating a print layout. For example, the user can select one-sided printing (1-Sided Printing) 801 and two-sided printing (2-Side).
d Printing) 802, and Booklet Printi
ng) The user can designate a radio button corresponding to any of the controls 803 by clicking with a mouse.

The [Finishing] column 81 is a column for specifying the output order and finishing of the printed recording medium, and the user can specify one of the following, for example.

[Collate] 811 Copies. When printing M copies of an N-page document, the first page, the second page,..., The N-th page are output one by one, and this is repeated M times.

[Group] 812 Printing in page units. When printing M copies of an N-page document, the first page is output as M sheets, the second page is output as M sheets,..., And the N-th page is output as M sheets.

[Staple] 813 Staple finish. As in the case of the above [Collate] 811, the output is performed in units of copies, and the stapling is performed for each copy as finishing.

In this specification, the above-mentioned user-settable items are referred to as “printer functions” or simply “functions”.
Also called. It has many other printer functions,
Omitted for simplicity.

Here, a combination of settings considered to be inconvenient for the user and a combination of meaningless settings, that is, an inconsistency (conflict) between the set values are performed by the printer driver UI control module 2042 in a conflict process described in detail below. Designed to be avoided as.

FIG. 3 shows a schematic configuration of the printer driver UI control module 2042 of the print processing related program 204 in the embodiment. Reference numeral 303 denotes a conflict manager that manages data transfer between modules, updates of data, and the like, and controls conflict processing. A printer driver UI 306 performs the above-described print setting screen display control, and executes a printer driver UI as a main program in the printer driver UI control module 2042.
It is. Reference numeral 301 denotes a conflict processing rule description file in which conflict processing rules indicating inconsistency avoidance strategies described in a description format described later are listed. 302 is
An inference engine that loads the conflict processing rule description file 301, applies the conflict processing rules to the input setting values, and infers the state of each function;
Reference numeral 4 denotes a status variable list for displaying the status of each printer function in a list format, which can be updated based on the input from the user and the content of the conflict processing rule description file 301. Reference numeral 305 denotes an internal structure as a form on which a screen display provided by the printer driver UI 306 is based, and displays the status of each printer function in a predetermined format in conjunction with the status variable list 304.

After that, the conflict manager 303, which has received the setting information from the user via the printer driver UI 306, refers to the conflict processing rule description file 301. This is indicated as “R (Read)” by an arrow from the conflict processing rule description file 301 to the conflict manager 303 as shown in the figure. If the setting information matches the conflict processing rule as a result of the reference, the conflict processing is applied. Then, the conflict manager 303 updates the state variable list 304 and the internal structure 305 and reflects them on the printer driver UI 306. As shown in the figure, the conflict manager 303 is connected to the state variable list 304 and the internal structure 305 by a two-way arrow, and is displayed as "R / W (Read / Write)".

FIG. 4 is a schematic diagram for explaining the relationship between data handled in each module shown in FIG. In FIG. 4, the conflict processing rule description file 301 is referred to in a form included (loaded) by the inference engine 302. The conflict processing rule description file 301 is also referred to by the conflict manager 303, and the state variable list 304 has contents according to the conflict processing rules. The internal structure 30
5 and the state variable list 304 are displayed in conjunction with each other as described above, and are in a relationship of being mapped to each other. This state is the printer driver UI 306
Is expressed in a form that can be seen by the user.

The state variable list 304 will be described in detail. As shown in the figure, a state value is firstly set for each printer function (columns A, B, C,... For example, information on whether the corresponding control can be used, information on the reason (invalidity reason) when the control cannot be used, information on the necessity of updating the UI, and the like are described.

The internal structure 305 indicates the status of each printer function by, for example, the syntax of data type, function name member, and status member, and stores the function name members corresponding to the printer function names A, B, and C as cA, cB, and cC, respectively. Express as: The status members for each function are in the status variable list 3
The state value at 04 is mapped.

(Description Format of Conflict Processing Rule) Next, the conflict processing rule description file 301 will be described.

Each rule is formalized mathematically using logic. The predicate is described in the form of a printer function name (argument). As an argument, a numerical value may be entered in addition to ON / OFF (for example, the number of print copies). On the left side, “printer function name (argument)” is described, and on the right side, a logical condition for establishing the left side is described. For example, A (ON) ← B (ON). Is a rule meaning that “when the status of the printer function B is ON, the status of the printer function A is ON”.

The symbol "," in the expression is a logical "and (AN
D) ”. For example, "When the status of printer function B is ON and the status of printer function C is OFF,
The rule of “turn printer function A on” is described as A (ON) ← B (ON), C (OFF).

Further, in the conflict processing rule description file 301, processing for updating the printer driver UI 306 can be described. When the inference engine 302 interprets the description, via the state variable list 304 of the conflict manager 303,
The update processing of the printer driver UI 306 can be directly performed.

For example, {disable} is used as UI update processing.
By adding the description of the set, it is possible to instruct a process of disabling the control of the corresponding item (a process of graying out the display and making it unsettable).

After the {disable} set, {Reason (X)}
When the description of the set is added, it becomes possible to display a message corresponding to the reason identifier X for displaying the reason for being disabled (details will be described later).

Next, a specific example of a function name described in a conflict processing rule will be shown, taking the printer function displayed in FIG. 8 as an example. The function names of the collate printing function corresponding to [Collate] 811, the page printing function corresponding to [Group] 812, and the staple finishing function corresponding to [Staple] 813 shown in FIG. Group (),
And Staple (), and the argument is ON or OFF.
The print layout function corresponding to the [PrintStyle] column 80 is indicated by Layout (), and the arguments are 1-Sided, 2-Sided,
One of Booklet.

In addition, it is possible to define a function not directly related to the UI (for example, environment information indicating attributes such as a mounting state of a specific option and a type of a set recording sheet). For example, in connection with the staple finishing function, Finisher () indicating whether or not a staple finisher as a device option is mounted can be used. The argument is ON or OFF. When ON, the finisher is attached, and when OFF, the finisher is not attached.

Also, a StaplablePaper () indicating whether or not the set recording paper is a stapleable paper can be used. The argument is ON or OFF. When ON, it indicates that stapleable paper is set and OFF.
Indicates that no stapleable paper is set.

It should be noted that the above-described function names are merely examples for a control target called a printer, and it goes without saying that other function names can be defined according to the control target.

FIG. 6 shows an example of the conflict processing rule description file 301 described according to the above example.

(1) is a rule that when the finisher is not mounted, Staple (OFF), that is, staple finishing is not possible. Since {disable} is described in the subsequent continuation, when this rule is applied, the control [Staple] 813 is grayed out.
In the next line, {Reason (NO_FINISHER)} is described. Here, the reason identifier NO_FINISHER indicates that the finisher is not mounted.

(2) is a rule that sets Staple (OFF) when no stapleable recording paper is set. Here, as in (1), since {disable} is described in the subsequent continuation, the control [Staple] 813 is grayed out when this rule is applied. Also, the next line has INVALID_PAPER as the reason identifier indicating that non-staplable paper is set.
{Reason (INVALID_PAPER)} set is described.

(3) When [Booklet Printing] 803 is checked and Layout (BOOKLET) is set,
This is a rule that sets ple (OFF). Similarly, when this rule is applied, the control [Staple] 813 is grayed out by the description of {disable}. In addition, the next line indicates that an incompatible print style (layout) is specified INVALID_LA
A {Reason (INVALID_LAYOUT)} set having YOUT as a reason identifier is described.

(4) is a rule that when an OHP sheet is set as a recording medium, it is Staple (OFF).
When this rule is applied, the control [Staple] 813 is grayed out according to the description of {disable}. Also, the next line has INVALID_PAPERTYPE as the reason identifier indicating that an incompatible paper type is specified.
{Reason (INVALID_PAPERTYPE)} set is described.

The rule (5) is a rule that sets the Staple (OFF) when the Collate (ON) is turned on by checking the [Collate] 811. The rule (6) is a rule that the [Group] 812 is checked. This is a rule that makes it Staple (OFF) when it becomes Group (ON).

(7) Colla is displayed when [Booklet Printing] 803 is checked and Layout (BOOKLET) is displayed.
This rule is te (ON), and when this rule is applied, control [co
llate] 811 is grayed out.

(8) indicates that when [Booklet Printing] 803 is checked and the layout becomes BOOKLET,
(OFF). When this rule is applied, control [Gr.
oup] 812 is grayed out.

As described above, the rules applied according to the state of each function are described.

(Printer Driver UI Control Module 2)
Hereinafter, the process of the printer driver UI control module 2042 including the conflict process will be described in detail with reference to the flowchart of FIG.

Printer driver UI control module 20
The process of 42 is performed by the user using the keyboard controller KBC.
The process starts by giving an instruction to open a print setting screen by using 5 or the like. When the user instructs to open the print setting screen, the print processing related program 204 is loaded into the RAM 2 under the management of the OS 205 as described above.

The print processing related program 204 is stored in the RAM 2
First, as initialization processing for opening the print setting screen, the inference engine 302 reads the conflict processing rule description file 301 into the RAM 2 via the conflict manager 303 (step S5).
01).

Subsequently, a state variable list 304 used by the conflict manager 303 is created (step S).
503).

[0059] Conflict processing rule description file 30
All the printer function names described in No. 1 have status variables in a status variable list 304 included inside the conflict manager 303. The value of this state variable is linked to the value of the corresponding member of the internal structure 305 used in the printer driver UI 306. The initial value of the state variable of each printer function name is the value of the member of the internal structure 305.

For example, in FIG.
Since the initial value of int cA described in the above is 0, the printer function in the state variable list 304 corresponding to the initial value is 0.
The value of A is OFF. Therefore, the initial value of the status of the printer function A in the status variable list 304 is OFF. Similarly, the initial value of the printer function name B is ON, and the initial value of the printer function name C is OFF. That is, A OFF B ON C OFF.

After that, the inference engine 302 makes an inference of a conflict check by referring to the conflict processing rule description file 301. For example, as shown in FIG. 4, when A (ON) ← B (ON), C (OFF). Described in the conflict processing rule description file 301 is satisfied, the inference engine 302 sets the state variable list 304 Initialize the status variable value of printer function A
Change from to ON. That is, A ON B ON C OFF. Thus, the state variable list 304 is initialized. Further, other items (display / non-display information of the control, etc.) in the state variable list 304 are initialized similarly.

After the inference of the conflict check is completed, the conflict manager 303 stores the value of the changed state variable in the corresponding member int cA of the internal structure 305.
To reflect. That is, int cA is changed from 0 to 1 when the above rule is satisfied.

Specifically, an initialization process for opening the UI shown in FIG. 8 will be described as an example. FIG. 7 shows an example of an internal structure for the UI of FIG. As can be seen from the figure, for example, the function name members Layout, Collate, Group,
And the state members corresponding to Staple are 1Sided,
0, 1, and 0. From this state, a conflict check is performed with reference to the conflict processing rule description file 301 shown in FIG. When the content of the internal structure is in the state shown in FIG. 7, none of the rules in the conflict processing rule description file 301 shown in FIG. 6 is applied. That is, the state variable value of the function name is as follows as an initial value by the initialization in step S503. Collate OFF Group ON Staple OFF Layout 1-Sided

Subsequently, other initialization processing required for opening the UI is performed, and the UI as illustrated in FIG. 8 is opened (step S504). in this case,
By referring to the state variable list 304, a value corresponding to the set value is displayed, and a process (change of “able / disable”) according to control availability information is performed.

After the print setting screen as a UI is opened, an event sent from the OS is acquired, and processing for the event is performed (step S505).

Next, it is determined whether or not the event acquired in step S505 is an event in which the user has changed a setting item on the print setting screen (step S50).
6). Here, if the acquired event is a setting change request from the user, the process proceeds to step S507, and the conflict processing rule is applied with reference to the conflict processing rule description file 301.

FIG. 8 shows an example of a case where the acquired event is a setting change request by the user.
le] column 80, 1-Sided Printing 8
A case will be described in which the booklet printing (Booklet Printing) 803 is changed from 01. Here, it is assumed that a finisher capable of stapling is mounted, and a stapler capable of stapling the paper size and paper type is set.

Printer function names Collate, Group, Staple,
FIG. 7 shows the values of the layout state variables before the setting change request.
In other words, the state shown in FIG. Collate OFF Group ON Staple OFF Layout 1-Sided

Since the user's change request is to change the layout from 1-Sided to Booklet, the contents of the state variables of Layout are changed, and the values of the state variables of each printer function name are as follows. Collate OFF Group ON Staple OFF Layout Booklet

Then, the printer driver UI 306 calls the conflict manager 303, then the inference engine 302 is called, and the conflict check starting from Layout is started with reference to the conflict processing rule description file 301.

The inference engine 302 checks the application / non-application of each rule of the conflict processing rule description file 301. As described above, in this example, a finisher capable of stapling is mounted, and a paper size and a paper type capable of stapling are set, so that the rules (1) and (2) are not applied.

Since rule (3) will be applied, S
The control is disabled while taple is OFF, that is, the setting is disabled by graying-out display. Furthermore, as described above, the IN indicating that an incompatible print style has been specified as the reason for graying out.
VALID_LAYOUT is set.

Although the rules (4), (5) and (6) are not applied,
Rules (7) and (8) are applied, and the value of Collate changes from OFF to ON
And the value of Group is changed from ON to OFF, and each control is disabled as follows. Collate ON (disable) Group OFF (disable) Staple OFF (disable, Reason = INVALID_LAYOUT) Layout BOOKLET

In some cases, rules that gray out the same control but have different reasons may be applied redundantly. In this case, a reason having a predetermined high priority is adopted. In the embodiment, it is determined that the rule described earlier in the conflict processing rule description file 301 has a higher priority.

For example, suppose that, following the above example, a sheet of a size that cannot be stapled is set. In this case, the rule (2) is applied together with the rule (3). According to the embodiment, the rule (2) having a higher priority is adopted, and the reason why the grayout is performed is IN indicating that a nonconforming recording sheet is set.
VALID_PAPER will be set. That is, the state of each control is as follows. Collate ON (disable) Group OFF (disable) Staple OFF (disable, Reason = INVALID_PAPER) Layout BOOKLET

Thus, the application of the conflict processing rule in the inference engine 302 in step S507 is completed.

The conflict manager 303 updates the state variable list 304 based on the result of applying the conflict processing rule in step S507 (step S5).
08). That is, the state variable list is as shown in FIG. In FIG. 11, it can be seen that the state of the function Staple is OFF, the control is disabled, and the reason identifier INVALID_PAPER is recorded.

Subsequently, the internal structure 305 is updated (step S509). Specifically, the state variable list 304
The UI update processing is performed for the control in which the UI update information in the table is “required (yes)”, and thereafter the UI update information is changed to “unnecessary (no)”. In the example above,
Layout changed from 1-Sided Printing to Booklet Printing, Collate changed from OFF to ON, Group changed to O
N is changed to OFF, Collate, Group, and Staple are respectively disabled, and the UI in FIG. 8 is updated as shown in FIG.

Further, as shown in FIG. 9, when the control is grayed out, a conflict mark 91 for notifying the grayout is displayed (the details will be described later). After step S509, the process returns to step S505 to repeat the processing.

In step S506, step S5
If the event acquired in step S05 is not the event in which the user has changed the setting items on the print setting screen, the process advances to step S512 to determine whether the event is a grayout reason display event. This event occurs, for example, when the conflict mark 91 is clicked or when the mouse cursor is over the conflict mark 91.

If this event has occurred, the process proceeds to step S 513, where the printer driver UI 306 refers to the invalid reason information of the corresponding control from the state variable list 304 and performs processing corresponding to the identifier registered therein. For example, a comment message 92 as shown in FIG. 10 can be displayed. When the event is released by pressing any key or moving the mouse cursor, the message disappears and step S505 is executed.
Return to and repeat the process.

If the result of determination in step S512 is that the event is not a reason display event, the flow advances to step S514 to determine whether it is a printer driver UI close request. If the request is a close request, the internal structure is updated with the setting of the state variable (step S515), a predetermined end process is performed, the printer driver UI is closed, and all processes are ended (step S516). . On the other hand, if it is not a close request, step S5
Returning to step 05, the process is repeated.

The above processing is repeatedly executed until the printer driver UI is closed. When the printer driver UI is closed, the processing ends, the processing of the print processing related program 204 ends, and the RAM 2
It is deleted by the function of S205.

According to the embodiment described above, when the control is disabled by applying the conflict processing rule and the control is grayed out, the reason for the conflict processing rule description file can be described. Thus, the management of the grayed-out reason information can be facilitated. For this reason, it is free from the trouble of adding a dedicated program code for the reason detection and the case where the conditions are omitted or different, and high-quality reason display processing can be realized.

According to another aspect of the present invention, the reason display process is shifted from the printer driver UI to the conflict manager, thereby eliminating the need to synchronize reason identifiers between the two, thereby improving independence and improving productivity. This has the effect of being excellent in maintainability.

[0086]

[Other Embodiments] In the above embodiment, step S5
The display of the 13 reason comment is displayed in the printer driver UI 30.
6, the conflict manager 303
Can be performed. That is, a character string resource is provided inside the conflict manager 303, and when a reason display event occurs, the conflict manager 30
3, the corresponding message may be displayed by referring to the reason attribute of the state variable.

In step S507, only one reason having the highest priority is stored. However, all relevant reasons may be stored, and all the reasons may be displayed in step S513.

In step S507, the priorities are determined according to the description order of the rules. However, the present invention is not limited to this, and another standard may be provided. By applying only rules that change state values,
It is also possible to keep the latest reason and to improve efficiency.

In the above-described embodiment, an example has been described in which UI control including conflict processing is performed on a printer device. However, the present invention is not limited to a printer device, but may be a digital camera, a digital recorder, an image scanner, or the like. It goes without saying that the present invention can be applied to network-related devices such as modems and routers in addition to the peripheral devices and control devices. It is also possible to apply to a system composed of a plurality of these devices.

As described above, an object of the present invention is to supply a storage medium (or a recording medium) storing a program code of software for realizing the functions of the above-described embodiments to a system or an apparatus, and to provide the system or the apparatus. This is also achieved by a computer (or CPU or MPU) reading and executing a program code stored in a storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiment, and the storage medium storing the program code constitutes the present invention. When the computer executes the readout program code, not only the functions of the above-described embodiments are realized, but also an operating system (OS) running on the computer based on the instruction of the program code.
It goes without saying that a case where the functions of the above-described embodiments are implemented by performing some or all of the actual processing, and the processing performs the functions of the above-described embodiments.

Further, after the program code read from the storage medium is written into the memory provided in the function expansion card inserted into the computer or the function expansion unit connected to the computer, the program code is read based on the instruction of the program code. , The CPU provided in the function expansion card or the function expansion unit performs part or all of the actual processing,
It goes without saying that a case where the function of the above-described embodiment is realized by the processing is also included.

When the present invention is applied to the storage medium, the storage medium stores program codes corresponding to the flowchart of FIG. 5 described above.

[0093]

As described above, the function for displaying the reason why a specific item cannot be set on the user interface is realized without causing omission or discrepancy in the reason detection. It is possible to provide a user interface control device and a method capable of reducing a target error.

[Brief description of the drawings]

FIG. 1 is a block diagram of a print processing system according to an embodiment.

FIG. 2 is a diagram showing a memory map of a RAM 2 in the embodiment.

FIG. 3 is a schematic configuration diagram of a printer driver UI control module according to the embodiment.

FIG. 4 is a schematic diagram illustrating a relationship between data handled by a printer driver UI control module according to the embodiment.

FIG. 5 is a flowchart illustrating processing of a printer driver UI control module according to the embodiment.

FIG. 6 is a diagram illustrating an example of a conflict processing rule description file according to the embodiment.

FIG. 7 is a diagram illustrating an example of an internal structure according to the embodiment.

FIG. 8 is a diagram illustrating an example of a print setting screen by a printer driver UI according to the embodiment.

FIG. 9 is a diagram illustrating an example of a print setting screen by a printer driver UI according to the embodiment.

FIG. 10 is a diagram illustrating an example of a print setting screen by a printer driver UI according to the embodiment.

FIG. 11 is a diagram illustrating an example of a state variable list according to the embodiment.

Claims (9)

[Claims] 1. A user interface control device for avoiding inconsistency that occurs between setting information for a predetermined controlled device and / or environment information of the controlled device input via a user interface, Holding means for holding a conflict processing rule indicating a conflict avoidance strategy applied according to the setting information and / or the environment information; and directly changing a state of a predetermined setting item in the user interface according to the conflict processing rule State control means for controlling whether or not the state of the predetermined setting item is directly unchangeable by the state control means, notification control means for notifying via the user interface a message including the reason. The conflict processing rule makes it impossible to directly change the state of a predetermined setting item. Instruction and user interface control apparatus characterized by including a reason information indicating the reason for said direct changes allowed by the instruction for. 2. The method according to claim 1, wherein the state control unit directly changes a state of a predetermined setting item in the user interface according to the command included in the conflict processing rule applied according to the setting information and / or the environment information. 2. The user interface control device according to claim 1, wherein the user interface control device controls whether or not the user interface can be executed. 3. The notification control unit according to claim 1, wherein the message according to the reason information included in the applied conflict processing rule is notified via the user interface. User interface control device. 4. The conflict processing rule is described and stored in a conflict processing rule description file, and each conflict processing rule in the conflict processing rule description file has a predetermined priority. In a case where a plurality of the conflict processing rules are applied to the setting items in a redundant manner, the notification control unit may include the reason information included in the conflict processing rule having the highest priority among the conflict applied rules that have been repeatedly applied. The user interface control device according to claim 3, wherein a corresponding message is notified via the user interface. 5. The user interface control device according to claim 4, wherein the priority order is determined according to a description order of the conflict processing rules in the conflict processing rule description file. 6. The user interface control device according to claim 1, wherein the control target is an image forming device. 7. A user interface control method for avoiding inconsistency that occurs between setting information for a predetermined control target and / or environment information of the control target input via a user interface, wherein the setting is performed. Conflict processing rule indicating an inconsistency avoidance strategy applied in accordance with the information and / or the environmental information (the conflict processing rule includes an instruction for directly disabling the state of a predetermined setting item, and the instruction (Including reason information indicating the reason that direct change was not possible)
A state control step of controlling whether or not the state of a predetermined setting item in the user interface can be directly changed, and a message corresponding to the reason information included in the applied conflict processing rule, via the user interface. A user interface control method, comprising: a notification control step of performing notification. 8. A program executable by a computer device, wherein the computer device executing the program causes the computer device to function as the user interface control device according to any one of claims 1 to 6. program. 9. A storage medium storing the program according to claim 8.