JP5159974B2 - Information processing apparatus, method, and control program - Google Patents

Description

  The present invention relates to a print control program including a printer driver.

  When printing a file such as a document or a diagram created on a computer, which is an example of an information processing apparatus, from an application, drawing data is converted into a printer language using a printer driver and transmitted to the printer. Settings such as paper type, duplex, color, and paper feed stage are user interface print settings provided by an application or printer driver, and data set by the user is transmitted to the printer as a printer command.

  The functions of printer drivers are increasing year by year. Many printer drivers have hundreds of functions. In addition, the user interface for performing print settings of the printer driver has a plurality of dialog windows that are opened by pressing a button from the user interface. Thus, many users are wondering where they can make the desired settings. Therefore, the printer driver has a function prohibition process (conflict process) for the user. Function prohibition processing means that when a certain function is selected, other functions cannot be used or other setting values are changed. For example, many printer drivers cannot set “postcard” and “staple” at the same time. At this time, if “postcard” is selected, the “staple” item on the user interface of the printer driver is grayed out (Patent Document 1). In addition, the display of an item that cannot be set is hidden and cannot be selected, or an icon indicating that the item cannot be selected is displayed (Patent Document 2). In addition, a message is displayed as a warning about an item that cannot be set (Patent Document 3).

  In addition, the prohibition process of the printer driver is not only the display on the user interface. The print settings can also be changed by application software. However, settings that are in a prohibited state from the application may be passed to the printer driver as they are. In this case, if the printer driver converts the setting into a printer command, an error occurs in the printer. Therefore, the printer driver performs a function prohibition process even when printing, and changes the print setting to a printable value.

  On the other hand, there is a demand for fixing a specific function for print settings because of increased security awareness and cost reduction. For example, if monochrome printing is fixed on a color printer, the cost of toner and ink for printing can be reduced. In addition, paper can be saved by fixing 2Up printing for printing two pages at a reduced size or double-sided printing.

  However, the function of fixing the value is often incompatible with prohibition processing. For example, if double-sided printing is fixed, there arises a problem of how to prohibit when selecting paper that cannot be double-sided. Conventionally, a method of customizing the printer driver itself and creating a completely different dedicated driver has been common. However, a printer driver must be created for each user's request. For this reason, it has been considered to add a new prohibition processing rule from an external plug-in (Patent Document 4). Furthermore, there is a method of changing the print setting when the setting can be changed by prohibition processing after performing a fixed setting as much as possible (Patent Document 5). There is a technology that automatically complements the prohibition processing rule opposite to the current prohibition processing rule.

  Further, the developer can describe all the rules that are turned ON for a certain function name, and can omit the rules that are turned OFF as described above. Rules that are turned off are automatically generated by the inference engine 302. Conversely, the developer can describe all the rules that are turned OFF for a certain function name, and can omit the rules that are turned ON as described above. Rules that are turned ON are automatically generated by the inference engine 302. The developer can also describe all the rules that are turned ON and OFF for a certain function name. In this case, rules are not automatically generated. When an item is written on the right side of an item described in the format of function name (ON) and function name (OFF) on the left side, the same ON / OFF format as that on the left side is used. In this case, a rule is automatically generated (Patent Document 6).

JP 2003-99170 A JP 2000-227847 A JP 2000-225754 A JP 2005-190467 A JP2007-272779 JP2002-169669

  However, with the conventional method, it has been difficult to completely fix the value. That is, when inserting a prohibition processing rule from an external plug-in, the external plug-in must know all the prohibition processing rules (also referred to as conflict rules) of the printer driver in advance. Furthermore, when the functions of the printer driver main body are expanded and the prohibition process is expanded, the external plug-in must insert a newly changed prohibition process rule. In addition, when the change is allowed by the prohibition process, it is not always possible to fix the value depending on the fixed value. In the case of automatically complementing the reverse rule, the method of Patent Document 6 automatically complements only the setting value of ON / OFF. For example, when there is a prohibition processing rule that turns both sides on, the prohibition processing rule that turns both sides off is automatically complemented. In order to avoid any inconvenience in the forbidden processing rule when the set value is fixed, it is sufficient to complement the rule of changing the automatically complemented rule to a fixed value. However, if the value is changed by a prohibition processing rule evaluated before that, it may not be fixed as intended by the developer or user. Further, it cannot be applied to a case where there are two or more set values, for example, a paper size. In addition, when applying multiple preset values saved by the user, such as “Favorite”, different values that are not fixed setting values are included in “Favorites” along with the fixed setting values. The value was changed and could not be fixed reliably.

  The present application has been made in view of at least one of the above problems.

  First display means for displaying an acceptance screen for accepting an instruction as to whether or not the function for saving data in the printer is always valid, and an instruction for always validating the function for saving the data in the printer via the acceptance screen And a print setting screen that does not accept a change from valid to invalid for the function to save the data in the printer when receiving an instruction to always enable the function to save the data in the printer. Information indicating that the function for storing the data in the printer is always enabled when an instruction to always enable the function for storing the data in the printer is received. It is displayed on the screen.

  According to the present invention, it is possible to perform printing in accordance with the prohibition process of the printer while fixing the setting value, so that there is an effect that the administrator can surely manage the print setting.

1 is a block configuration diagram of hardware and software of a computer system as one embodiment of the present invention. FIG. 1 is a block configuration diagram of an XPSDrv printing system as an embodiment of the present invention. FIG. It is a block block diagram of the configuration module in Example 1 as one Embodiment of this invention. It is a part of format of the XML file contained in the model dependence file in Example 1 as one embodiment of this invention. It is a flowchart of the logic which performs the prohibition process of the prohibition engine in Example 1 as one Embodiment of this invention. It is a part of user interface screen which designates the lock function in Example 1 as one embodiment of the present invention. FIG. 5 is a print setting screen in which a lock function in Example 1 is designated as an embodiment of the present invention. FIG. In the XML file included in the model-dependent file in Example 1 as an embodiment of the present invention, a part of XML in which the lock function is enabled. It is a block block diagram of the configuration module in Example 2 as one Embodiment of this invention. It is a part of GPD file which is a model dependence file in Example 2 as one embodiment of the present invention. It is a flowchart of the prohibition process of the configuration module in Example 2 as one embodiment of the present invention. FIG. 14 shows some GPDs in which the lock function is enabled in the model-dependent file in Example 2 as an embodiment of the present invention. 3 is a binary DEVMODE structure of print settings according to an embodiment of the present invention. FIG. 4 is an XML of a print ticket for a print setting according to an exemplary embodiment of the present invention. It is a block diagram of an XPS spool file as one embodiment of the present invention.

(Example)
The best mode for carrying out the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram of a print processing system showing an embodiment of the present invention. Unless otherwise specified, as long as the functions of the present invention are executed, a single function or a system composed of a plurality of devices can be connected via a network such as a LAN or WAN. Needless to say, the present invention can be applied to a system in which processing is performed.

  FIG. 1 shows a block diagram of a system using a computer. The CPU 101 controls the entire apparatus according to a program stored in the ROM 102, the RAM 103, or the external storage device 105. The RAM 103 is also used as a work area when the CPU 101 performs various processes. The storage device 105 records an operating system (OS) 1054, application software 1051, and the like. Input devices such as a keyboard and a mouse are devices for the user to give various instructions to the computer through the input I / F 104. The output I / F 106 is an interface for outputting data to the outside, and outputs data to the monitor 110 and the printer 111. The printer 111 may be connected not only through a local I / O directly connected but also through a network such as a LAN or a WAN. Reference numeral 107 denotes a common data bus for exchanging data. 2, 3, and 9 are stored as the printer driver 1053 in the storage device 105 in FIG. 1, and the CPU 101 develops them in the RAM 103 and executes them.

  FIG. 2 shows a block diagram of the XPSDrv printing system. XPSDrv refers to a printer driver that performs printing using a document file format called XPS (XML Paper Specification) as spool data. The user uses the input device 104 such as a keyboard and a mouse to display a Win32 application program 201 (hereinafter abbreviated as “Win32 application”) or a Windows (registered trademark) Presentation Foundation application program 202 (hereinafter referred to as “Win32 application”) displayed on the monitor of the output device 105. , Abbreviated as WPF application). The printing process is executed by sequentially performing three processes: printer selection, print setting creation, drawing data conversion, and so on. 201 to 213 and 215 in FIG. 2 are stored in the external storage device 105 in FIG.

  First, the printer 214 to be printed is selected, which is the same as selecting a printer driver corresponding to the printer that executes printing. Next, print settings are created. The print setting is performed in such a manner that the application secures a memory for print setting, and the configuration module 204 of the application or the printer driver fills the setting data using the model-dependent file 205. The Win32 application 201 uses a binary DEVMODE structure 215 as print setting data, and the WPF application 202 uses a PrintTicket 203 described in markup language XML. The DEVMODE structure 215 has the structure shown in FIG. 13, and is a binary structure having a public area defined by the operating system and a private area defined by the printer driver. PrintTicket 203 is print setting information described in the XML format as shown in FIG. The DEVMODE structure 215 or the PrintTicket 203 holds the print setting, and the print setting is changed by directly rewriting the application. The dedicated setting depending on the printer 214 is performed by displaying the user interface of the printer driver included in the configuration module 204 and operating the user interface. The printer driver changes the setting depending on the printer 214 of the DEVMODE structure 215 or the PrintTicket 203 according to the setting of the user interface. Specifically, the print setting refers to settings such as setting the output paper size to “A4”, performing double-sided printing, switching between color and monochrome, and specifying a paper feed stage. Since PrintTicket 203 describes the print settings in XML format, it is easy for the WPF application 202 to directly change and rewrite all the setting values. However, even if the settings are changed using the user interface of the printer driver as before, It doesn't matter.

  Finally, drawing data is converted. When the print setting is confirmed, the user executes print processing from the application. When printing from the Win32 application 201, drawing data is sent to the GDI to XPS conversion module 206 in the form of a version 3 printer driver, and an XPS spool file 207 is created. The version 3 printer driver refers to a printer driver compatible with Windows (registered trademark) 2000 or later of Microsoft (registered trademark). At this time, the GDI to XPS conversion module 206 calls the configuration module 204 to convert the print setting from the DEVMODE structure 215 to the PrintTicket 203. When printing from the WPF application 202, there are two methods: an XPS file is generated by the WPF application itself, and an XPS file is generated by the operating system in response to a command from the WPF application. A spool file 207 is generated. As described above, the XPSDrv printing system is characterized in that the XPS spool file 207 is always generated at the time of printing.

  When the XPS spool file 207 is generated, processing is passed to the print filter pipeline process. The print filter pipeline process is a mechanism in which printing is performed by passing a plurality of filters, and the number and order of the filters are controlled by the filter configuration file 208. In this embodiment, the filter pipeline manager that operates in the print filter pipeline process performs processing in the order of the setting filter 209, the layout filter 210, and the renderer filter 211 in accordance with the filter configuration file 208. The processing is performed by passing the XPS spool file 207 to the filter, and the processing proceeds when the filter processes the XPS spool file 207 and passes it to the next filter. Finally, the data is output as a printer control language (hereinafter referred to as PDL (Page Description Language)) which is a data language understood by the printer. Of course, if the printer 214 can directly read the XPS spool file 207, it may be left as it is. The setting filter 209 reads the PrintTicket and writes data necessary for printing into the PrintTicket, and the layout filter 210 performs layout-related processing such as magnification change, bookbinding layout and stamp. Since the layout filter 210 operates in accordance with the print setting PrintTicket 203 included in the XPS spool file 207, for example, when the imposition setting does not exist in the PrintTicket 203, the layout filter 210 does not operate and passes through to the next filter. The XPS spool file 207 is passed as it is. The last renderer filter 211 renders the XPS spool file 207 and converts it into PDL. The PDL data is managed by a print manager 212 that manages a print processing schedule, and print jobs are successively registered in a queue (queue). When the printer 214 is ready for printing, the PDL data is transmitted through the I / O monitor 213 in the order registered in the queue. Thus, converting the print data from the application into the printer language is the main role of the printer driver, and actual print processing is performed.

  FIG. 3 is a block diagram of the configuration module 204 of the printer driver in this embodiment. The configuration module 301 operates by reading a model-dependent file 307 having information dependent on the model of each printer. By doing in this way, even if the configuration module 301 is a module common to all the printers, it is possible to perform an operation specialized for each model. The model-dependent file 307 has an XML data file 308 in which actual model data is described, and the configuration module 301 interprets and reads the XML data file 308 by the data file parser 305 of the conflict engine 304.

  Since the XML data file 308 is a huge data file including printer model data, the model-dependent file 307 reduces the file size by compressing the XML data file 308 using ZIP compression. The data file parser 305 creates a binary data file 309 once the XML data file 308 is read. After the binary data file 309 is created, if there is no change in the XML data file 308, the operation is performed using the binary data file 309 instead of the XML data file 308. As a result, the work of expanding the XML data file 308 from the model-dependent file 307 and the work of analyzing the XML data file 308 are reduced, and the performance is improved. If there is a change in the XML data file 308, the XML is read again to create a binary data file 309.

  The data file parser 305 of the conflict engine 304 reads the XML data file 308 or the binary data file 309 and creates an object instance of a state variable (also referred to as Status Variables, hereinafter abbreviated as SV) 310. The SV 310 is handled as an object for each function of the printer, and represents the state of print setting information. The SV 310 is an object developed on a memory having a name, a value or a value list, a property associated with the value, a current value, a default value, a status, a reason, and a lock flag.

  For example, the SV 310 relating to the function “paper size that can be used by the printer” is illustrated in the example of FIG. The paper size SV 310 has the name “MediaSize”, and the value list lists paper sizes that can be used by the printer, such as “A4”, “Letter”, “B5”, and “PostCard”. In FIG. 3, since the current value is represented by a black circle and the default value is represented by a white circle, the default is “A4”, but currently “Letter” is selected. In addition, the SV 310 has a status and can indicate whether or not the value is available at the current set value. The SV 310 itself has a status for each value in the value list, and in FIG. 3, “B5” is a sheet that cannot be used with the current settings, and therefore a strikethrough with an unusable status for the value of “B5”. Is drawn. In a situation where the paper size cannot be selected, “MediaSize” itself can be given an unusable status. Similarly, “Orientation” as the printing direction, “OutputColor” as the color, and “InputBin” as the paper feed stage are given as examples. Of course, there can be any number of other functions. Furthermore, the SV 310 can have a numerical value or a character string as a value instead of a value list. Even for a value list, an SV 310 in the form of multi-selection that can have a plurality of current values can also be created. Since the multi-selection SV 310 selects a plurality of values at the same time, a box storage function that stores a print job in a printer storage device or the like, and printing that stores data in a plurality of boxes at the same time with a single printing. You can make settings.

  The prohibition engine 306 performs prohibition processing using the SV 310. The prohibition is a rule for prohibiting a conflict in print settings. For example, if both sides are ON and OHP is ON, it is impossible to achieve both, so the rule definition is to correct one to be OFF. This will be described in detail later. The forbidden engine 306 changes the value of the SV 310 based on the forbidden processing rule described in the XML data file 308 or the binary data file 309. The prohibition process rule is described for each SV 310 and describes the relationship with the values of other SVs 310. For example, consider the prohibition processing rule of SV “Collate” that performs a sort by group. The copy sort must be used when performing bookbinding printing. If this logic is described as a prohibition processing rule of SV “Collate”, it will be described in the form of “turn on itself if SV“ Booklet ”of bookbinding is ON”. In addition, a reason can be set in the prohibition process rule. The reason is a mark attached to the SV 310 for distinguishing which prohibition processing rule has changed the value when the value is changed by the prohibition processing rule. Furthermore, in the prohibition process rule, as a result of the described condition, not only the value can be changed, but also the status can be changed, and a specific value can be deleted or added from the value list.

  The configuration module 301 can input and output print settings in the form of DEVMODE 311 and PrintTicket 312 with application software through an application program interface (hereinafter abbreviated as API). The configuration module 301 collects all the current values of the SV 310 and creates the DEVMODE 311 and the PrintTicket 312 as overall print settings, and outputs them to the application software. When DEVMODE 311 or PrintTicket 312 is received as an input, the value is set in SV 310 and the conflict engine 304 is used to perform prohibition processing.

  The configuration module 301 also has a user interface 303 for allowing the user to make print settings. On the user interface 303, the current value of the SV 310 is displayed. When the value is changed by the user, the value is set in the SV 310, and the conflict engine 304 is used to perform the prohibition process. As a result of the prohibition process, the SV 310 is changed to a new value, and the current value of the SV 310 is displayed on the user interface 303. The user interface 303 changes the control display according to the status of the SV 310. There are four SV310 statuses: available, not available, not supported, and not permitted, and the display of the controls is different. When it is available, the normal display is performed, but when it is unavailable or not authorized, the controls and options are grayed out so that they cannot be selected. When support is not possible, hide the control so that it is not visible to the user. When the button for returning to the standard is pressed, the SV 310 is changed to the default value, the prohibition process is performed, and the state of the SV 310 is displayed on the user interface. As described above, the configuration module 301 performs batch management of functions and prohibition processes by converting all the inputs and outputs into the SV 310 and performing the process.

  As a special function of the SV 310, it has a lock function for fixing values and value lists. When the lock flag of the SV 310 is turned ON, the SV 310 cannot change the value from the outside or change according to the prohibition process rule. In order to turn on the lock function, it is described in advance in the XML data file 308 or the binary data file 309 (FIG. 8), or designated from the API 302 or the user interface 303. FIG. 6 shows a display on the user interface 303 for turning on / off the lock function. The lock function allows only a user with administrator authority to specify, and FIG. 6 shows a display when both sides are locked. FIG. 7 shows a display on the user interface 303 when the lock function is turned on. In FIG. 7, since both sides are locked, the controls are grayed out so that both sides are always ON and the user cannot operate. In addition, a lock-only key mark is displayed next to the control to indicate that it is locked. When a locked control or a lock-only key mark is pointed with a pointing device, a tooltip is displayed to indicate that it is locked.

  FIG. 4 shows a part of the XML data file 308. In the XML data file 308, information on the SV 310 and prohibition processing rules are described in accordance with the function of the printer, and FIG. 4 shows the location of the SV 310 of “Collate”. The SV 310 is defined by an element “Status Variable”. Here, the name of the SV 310 is defined by the attribute “name”, and the type of the SV 310 is defined by the attribute “type”. In FIG. 4, “Collate” is described in the name, and “selection” is described in the type. The “selection” type indicates that the SV 310 uses a value list. Next, a PropertyTable element and a ConflictRules element are described as the definition of SV310. SV310 parameters are described in the PropertyTable element, and forbidden processing rules are described in the ConflictRule element. The PropertyTable element has two values, a ValueInfoTable element and a ReasonInfoTable element, which define a value and a reason, respectively. Each value of the value list is described in the ValueSet element in the ValueInfoTable element. Data added to a value as a Property element can be additionally written to each value of the ValueSet element. For example, the Property element is used when it is desired to add information such as width and height regarding the paper size “A4”. In the DefaultValue element, a default value in the value list is described. In FIG. 4, two values “Collated” and “Uncollated” and “Collated” are default values are described. In addition, the ReasonInfoTable element describes three Reasons as ReasonSet elements. In the ConflictRules element, one prohibition processing rule is described in the Conflict element. Each forbidden processing rule has a priority, which is described with an attribute called priority. Since the prohibition processing rule is evaluated from the smallest priority value, the smaller priority is higher. The priority is set for each SV 310 as described above in order to perform prohibition processing at the time of simultaneous input. When a value entered as a print setting is already in a prohibited state and one of the values must be changed, the print setting as desired by the user can be set by giving priority to the function value with a higher priority. It can be performed. If there is no priority, depending on the order in which the forbidden processing rules are evaluated, the function that has been evaluated first is given priority, so the result is not always constant. The Conflict element has a Value element and a Condition element, and the Value element describes a value that changes as a result of prohibition. Also, in the Conflict element, a status that changes as a result of the prohibition can be described with a status attribute. In the Condition element, the name and value of the prohibited SV 310 are described. In the name attribute, the name of the target SV 310 is described, and in the Value element, the value of the target SV 310 is described. When Condition elements are described in parallel, it means logical product (AND). In addition, there is a function such as arithmetic operation. When the result attribute is false, the result is negative (NOT), the Block element is in parentheses, and the AnyOneCondition element is logical sum (OR). In FIG. 4, there are three prohibition processing rules. If the value of “Booklet”, which is the SV 310 of the bookbinding, is other than “None”, the status of the SV 310 itself is set to “NotAvailable”, which is “Collated”. If the cover “CoverFront” and the back cover “CoverBack” are other than “NoCover”, that is, they are designated as “Collated”, the status of the SV 310 itself is set to “NotAvailable”. When the staple “Staple” is the saddle stitch “SaddleStitch”, there are three prohibition processing rules that “Collated” and the status of the SV 310 itself cannot be used “NotAvailable”.

  FIG. 5 starts when the user instructs setting to the printer driver. S501 is to be confirmed each time, but if processing is performed in advance and the user changes the print setting, the processing from S502 onward may be performed.

  Next, the logic of the prohibition process by the prohibition engine 306 of the conflict engine 304 is followed along the flowchart of FIG. First, information on the lock function of the SV 310 is obtained from the API 302 or the user interface 303. Based on the lock information, the prohibition engine 306 changes the value of the target SV 310 to a value to be locked, and sets a lock flag (step 501). Also, the default value is changed to a lock value.

  In step 502, the API 302 and the user interface 303 next receive print setting information designated by the user from print settings such as a DEVMODE structure and a PrintTicket, and control inputs from the user interface (step 502). The API 302 and the user interface 303 create a list of SV 310 values to be changed based on the received print setting information. This has a table in which combinations of SV310 name / value pairs and print setting information are described, and a list is created along the table. The table is described in the XML file and is included in the model-dependent file 307. The forbidden engine 306 changes the current value of the corresponding SV 310 to the print setting value based on the list of values (step 503). The forbidden engine 306 creates a list of SVs 310 whose values have been changed (step 504). A list has already been created with the print setting values, but here a list of SVs 310 whose values have been changed is created. Further, in the process of processing the prohibition process rule, a list including both the SV 310 whose value is actually changed and the SV 310 whose result value of the prohibition process rule is changed is created. All the prohibition processing rules of SV 310 included in the list created in step 504 are extracted and arranged in order of priority (step 505). Here, if any of the SVs 310 is locked, the prohibited processing rules of the locked SV 310 are first arranged in order of priority, and the other prohibited processing rules are arranged in order of priority after that. If there are still prohibition processing rules arranged in order of priority (step 506), one prohibition processing rule is extracted (step 508), and the prohibition processing rule is evaluated. With reference to the value or property of the SV 310 described in the prohibition process rule, it is determined whether the rule is satisfied in conformity with the Condition element in the prohibition process rule. If the prohibition process rule is established, it is determined whether or not the value of the SV 310 needs to be changed (step 509). When the value must be changed, it is determined whether or not the lock flag is set based on the lock information (step 510). When locked, the status is changed to unusable for the value of the SV 310 included in the Condition element in the forbidden processing rule (step 511). In other words, the value of the target SV 310 is normally changed according to the value of the target SV 310 described in the prohibition process rule, whereas the status of the target SV 310 is changed when locked. When it is not locked, it tries to change the value according to the prohibition process rule as a normal prohibition process. At this time, the flag of whether or not the value of the target SV 310 to be changed has been changed once by the prohibition process is determined (step 512). Forbidden processing starts with the value being changed and evaluates the forbidden processing rule, but if the value is changed many times, depending on the forbidden processing rule, the evaluation may loop and may not end. . Thus, the value of the SV 310 is changed by the prohibition process rule only once, thereby preventing an infinite loop. If it is confirmed that the value has never been changed, the value of the SV 310 is changed, and a flag is set that the value of the SV 310 has been changed by the prohibition process rule (step 513). Then, the next prohibition processing rule is evaluated. When all of the prohibition process rules are eliminated, it is determined whether there is an SV 310 whose value has been changed by the prohibition process (step 507). If no value has been changed, as a result of evaluating all the prohibition processing rules, it is determined that the value is in a stable state, and the process ends. If it has been changed, all the prohibited processing rules of the SV 310 whose values have been changed are taken out, arranged in order of priority, and evaluated again. At this time, the SV 310 that is locked increases the priority.

  As described above, the configuration module 301 can completely fix the function by using the lock function of the conflict engine 304 and the SV 310, and operates so as not to contradict the prohibition process.

(Example 2)
A system shown in the block diagram of FIG. 9 is given as an implementation method of the configuration module different from that of the first embodiment. The difference from the first embodiment is a forbidden processing rule. In the forbidden processing rule of the first embodiment, the value to be changed based on the target value is described, but in the forbidden processing rule of the second embodiment, it is set simultaneously. It is different to describe combinations that are impossible to do. Therefore, although the logic that the conflict engine performs forbidden processing is different, an equivalent lock function is realized by rearranging the priorities.

  In FIG. 9, a configuration module 903 is a common module that can use the same module even if the printers are different. The data depending on each printer is described in a text file called GPD (Generic Description Language), and the GPD parser 904 of the configuration module 903 interprets and operates the GPD file to realize the operation specific to the printer. ing. In FIG. 9, the operation of the printer A is performed when the GPD 901 corresponding to the printer A is read, and the operation of the printer B is performed when the GPD 902 corresponding to the printer B is read. Since it is inefficient for the GPD parser 904 to read the GPD file every time the printer driver is used, when the GPD file is read, a binary file is created and saved. After that, if there is no change in the description of the GPD file, speeding up is realized by operating using the binary file.

  In FIG. 9, binary data 906 is created when GPD 901 corresponding to printer A is read, and binary data 907 is created when GPD 902 corresponding to printer B is read. Based on the data described in the GPD, the configuration module 903 creates an object instance for each function and performs a prohibition process. The print setting data from the application 910 is COMPSTUI. It is passed to the configuration module 903 via the DLL 909. Also, print settings on the user interface are transferred from the COMMONUI 905 to the configuration module 903. The configuration module 903 reflects the print setting in the object instance for each function, performs prohibition processing, and returns the print setting on the application 910 or the user interface. The configuration module 903 can also use the user interface plug-in 908 to freely add new functions.

  FIG. 10 is a part of the description of GPD. * Feature describes the name of the function. In FIG. 10, it is defined as a Feature with the name InputBin in the paper feed stage of the printer. * Option is a value for the function. In FIG. 10, there are four options of AUTO, INPUTTRAY_MANUAL, INPUTTRAY_CASSETTE 1 and INPUTTRAY_CASSETTE 2, and one of them is selected as the current value of InputBin. * In DefaultOption, which of the options describes the default. Here, AUTO, that is, “automatic” of the paper feed stage is the default.

  There are two prohibition processing rules: * Constraints and * Invalid Combination. * Constrains describes a prohibition that must not be combined with your own Option and another Feature Option. * Invalid Combination is described in the root of the GPD file (at the beginning of the line), and the prohibition between the Option of Feature is described. * In Invalid Combination, two or more Option prohibitions can be described, which is a difference from * Constraints. Also, * ConflictPriority describes the priority of Feature. The smaller the numerical value, the higher the priority, and the prohibition process is evaluated first. By reading this GPD, the configuration module 903 creates a Feature object and performs a prohibition process.

  The Feature has a flag indicating whether the Option is locked in order to fix the Option, and the Option is not changed when the Option is locked. The lock can be described in advance in the GPD Feature (FIG. 12).

  The prohibition processing logic performed by the configuration module 903 is followed according to the flowchart of FIG. When the feature lock information is held by the application 910 or the user interface 905 of the CommonUI, the feature is changed to the specified Feature Option and a lock flag is set (step 1101).

  Also, the DefaultOption is changed to an Option that locks the DefaultOption. Next, print setting information designated by the user is received from the application 910 or the user interface 905 of the CommonUI (step 1102). At this time, Option is not set in Feature yet. All the features are listed as a list, and the list is arranged in the order of ConflictPriority (step 1103).

  Here, if there is a locked Feature, the locked Feature is arranged in the order of Conflict Priority, and then the normal Feature is arranged in the order of Conflict Priority. If a feature remains in the list (step 1104), a feature is extracted from the list (step 1105). Whether all the Option of the Feature corresponding to the designated print setting value, that is, the Option to be set, is the target of the Constraints or Invalid Combination is determined by looking at all the Constraints or Invalid Combination (Step 1106).

  If it is a target, the print setting cannot be set to Option as the current value of Feature because it is in a prohibited state, and the process proceeds to the next Feature. If it is not in the forbidden state, it is next checked whether or not the current Feature Option is locked (step 1107).

  If the current Option is locked, the print setting cannot be set as Option as well, and the process proceeds to the next Feature. If the Option to be changed is not in the prohibited state and the current Option is not in the locked state, Option is set as the print setting value in Feature (step 1108). Then, when the processing is completed for all the features, the process ends.

  Thus, the function can be fixed by locking the Feature. The second embodiment is simpler and easier to implement when fixing functions or performing prohibition processing. However, in the prohibition process of the second embodiment, it is not possible to change another value by changing the value. Therefore, when the print setting is in the prohibition state, the user changes the setting to cancel the prohibition state once. Then, again, the value must be set.

  In addition, as a print setting that can be instructed to be fixed, it is possible to fix a confidential print setting using a password, a user name / date / time print fixed, and the like. When these print settings are fixed, if secure print is fixed, storage (mailbox) and overtaking printing are turned off. If the user name or date / time printing is fixed, the poster is turned off. The printer memory is a printer memory. The user interface screen is a user interface screen.

  The technical principle of this embodiment will be summarized.

  A computer that processes print settings in a printer driver that generates data to be transmitted to a printer 214, which is an example of a printing apparatus, is disclosed. Then, the prohibition rule defining the prohibition of print setting is stored in the external storage device. Then, the print driver is instructed to be fixed using the user interface of the printer driver or the XML file. Further, the configuration module raises the priority of the prohibition rule related to the print setting instructed to be fixed higher than the previous priority. This is an example of rule priority setting.

  The print setting value is stored as an object in the external storage device.

  The configuration module changes the value of the object based on the prohibition processing rule, and evaluates the prohibition processing rule in order of priority. The print setting instructed to be fixed is not changed by input from the user interface or execution of the prohibition process rule. Furthermore, when processing a prohibition processing rule that changes a value for an object for which a value is instructed to be fixed, the configuration module cannot select the value of the object that caused the change from the user interface of the printer driver. Can be in a state.

  The user interface of the printer driver controls processing for displaying the print setting instructed to be fixed on the monitor 110 in an identifiable manner. For example, as shown in FIG.

  The priority of the prohibition processing is decided arbitrarily by the manufacturer. However, it is convenient that the prohibition process can be freely changed using this embodiment. It is preferable that the user interface or the XML file can be instructed to fix both sides, 2Up, monochrome and save (mailbox). A mail box is a box for transmitting print data and the like from a PC and storing them on the memory of a printer or multifunction peripheral. Depending on the setting, print output can be prohibited and always saved in a mailbox.

  In addition, when the print setting of a document received from another person is “postcard”, when printing is performed without being aware of “postcard”, “A4”, “ It is convenient to come out on both sides. Further, when the storage (mailbox) is fixed, the designated paper size is corrected from “user-defined paper (long)” to “A4”. In the case of the processing so far, printing has been performed on a long sheet of paper, so it is possible to prevent waste of paper resources by always storing it. In other words, long paper cannot be used in this environment. As another embodiment, if there is a setting that violates the setting for saving in the mailbox, printing may be canceled and the administrator notified without storing the print data in the mailbox. I think that the. Here, the mailbox setting is set to be related to printing.

  Moreover, when 2Up is fixed, a design in which bookbinding is corrected to OFF can be assumed. A semi-fixed mode can be assumed in which bookbinding is performed when bookbinding is possible, 2Up is given up, and bookbinding is fixed at 2Up when the bookbinding is not on the printer specifications.

(Other embodiments)
The processing shown in FIGS. 5 and 11 in this embodiment is performed by a computer by a program installed from the outside. In this case, the present invention is applied even when an information group including a program is supplied to a host computer from a storage medium such as a CD-ROM, a flash memory, or an FD, or from an external storage medium via a network. Is.

  As described above, the system or apparatus can be obtained by supplying the storage medium storing the program code of the software that implements the functions of the above-described embodiments to the system or apparatus, or downloading the storage medium from an external server (not shown). It goes without saying that the object of the present invention can also be achieved by the computer (or CPU or MPU) reading and executing the program code stored in the storage medium.

  In this case, the program code itself read from the storage medium realizes the novel function of the present invention, and the storage medium storing the program code constitutes the present invention. As a storage medium for supplying the program code, for example, a floppy disk, hard disk, optical disk, magneto-optical disk, DVD, CD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) or the like running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included. Further, after the program code read from the storage medium is written to a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

Claims (19)

First display means for displaying an acceptance screen for accepting an instruction as to whether or not to always enable the function of saving data in the printer;
An instruction means for receiving an instruction to always enable the function of saving the data in a printer via the reception screen;
And a second display means for displaying a print setting screen that does not accept a change from valid to invalid for the function of saving the data in the printer when an instruction to always validate the function of saving the data in the printer is received. And
When an instruction to always enable the function of storing the data in the printer is received, information indicating that the function of storing the data in the printer is always enabled is displayed on the print setting screen. Information processing apparatus. The information processing apparatus according to claim 1, wherein the printer is a multifunction peripheral . The print setting screen, the information processing apparatus according to claim 1 or 2, characterized in that a user interface provided by the printer driver. The information processing apparatus according to any one of claims 1 to 3, wherein the instruction unit receives an instruction to always enable a function of saving the data in a printer from a user having a predetermined authority. . The information processing apparatus according to any one of claims 1 to 4, characterized in that the display the previous SL data next to the item to specify the function to be stored in the printer. The information processing apparatus according to claim 1 , wherein the reception screen receives an instruction as to whether or not to enable another function at all times . The information processing apparatus according to claim 1, wherein an item for designating a function for storing the data in a printer is displayed in gray. The information is an information processing apparatus according to any one of claims 1 to 7, characterized in that a mark. If the mark is designated by the pointing device, the information processing apparatus according to claim 8, wherein you to view that they are immobilized. A first display step for displaying an acceptance screen for accepting an instruction as to whether or not to always enable the function of saving data in the printer;
An instruction step of receiving an instruction to always enable a function of storing the data in a printer via the reception screen;
A second display step of displaying a print setting screen that does not accept a change from valid to invalid for the function of saving the data in the printer when an instruction to always validate the function of saving the data in the printer is received; And
When an instruction to always enable the function of storing the data in the printer is received, information indicating that the function of storing the data in the printer is always enabled is displayed on the print setting screen. Control method. Computer
First display means for displaying an acceptance screen for accepting an instruction as to whether or not to always enable the function of saving data in the printer;
An instruction means for receiving an instruction to always enable the function of saving the data in a printer via the reception screen;
When an instruction to always enable the function to save the data in the printer is received, the function to save the data in the printer functions as a second display unit that displays a print setting screen that does not accept a change from valid to invalid. ,
When an instruction to always enable the function of storing the data in the printer is received, information indicating that the function of storing the data in the printer is always enabled is displayed on the print setting screen. Control program. The control program according to claim 11, wherein the printer is a multifunction peripheral . The print setting screen, the control program according to claim 11 or 12, characterized in that a user interface provided by the printer driver. The control program according to any one of claims 11 to 13, wherein the instruction unit receives an instruction to always enable a function of saving the data in a printer from a user having a predetermined authority. The information is, the control program according to any one of claims 11 to 14, characterized in that display the previous SL data next to the item to specify the function to be stored in the printer. The control program according to any one of claims 11 to 15, wherein the reception screen receives an instruction as to whether or not another function is always enabled . The control program according to any one of claims 11 to 16, wherein an item for designating a function of storing the data in a printer is displayed in gray out. The information is, the control program according to any one of claims 11 to 17, characterized in that a mark. If the mark is designated by the pointing device, the control program according to claim 18, characterized in you to view that they are immobilized.

Images