JP5533382B2 - Printer driver, information processing apparatus, and computer-readable recording medium recording printer driver - Google Patents

Description

  The present invention relates to a printer driver, an information processing apparatus, and a computer-readable recording medium that records the printer driver.

  The printer driver executes printing in response to an instruction from the application. At this time, a print instruction from the application is transmitted to the printer driver by using a data structure called a DEVMODE structure in, for example, an MS Windows (registered trademark) environment. This DEVMODE structure can hold the setting information without leaving the printing function of the printer driver.

  By the way, the function of a printer may be expanded by upgrading or adding options. For example, the number of functions that can be used increases or decreases when a finisher or the like is attached to or removed from the printer body. When the function increases or decreases, information such as setting values that the printer driver must hold also changes.

  In response to such a situation, a technique has been proposed in which data that can be processed by the printing apparatus can be generated without depending on the function expansion of the printing apparatus. For example, in the technique disclosed in Patent Document 1, first, a print setting value set based on function setting information regarding the function of the printing apparatus is stored in a data structure (for example, DEVMODE structure) for storing print settings. An area for allocation is secured, and print setting values are allocated to this area. Then, by referring to the function setting information, data that can be processed by the printing apparatus is generated from the print setting value assigned to the data structure. In the technique of Patent Document 1, by adopting such a configuration, it is possible to generate data that can be processed by the printing apparatus without depending on the function expansion of the printing apparatus.

  As described above, in the conventional printer driver, as is the case with Patent Document 1, the setting value is generally stored in the form of a data structure such as a DEVMODE structure.

  Incidentally, the DEVMODE structure is a format for storing data on a program, and the data structure is statically determined at the time of coding. Therefore, when a version upgrade that expands the functions of the printer driver is performed and the functions increase or decrease, this data structure is updated (redesigned) so that the increased functions can be used from the application, especially when the functions increase. )Must. In other words, the data structure that stores the print settings must be extended by coding and compiling again.

  On the other hand, in the DEVMODE structure, setting information of a plurality of functions (each setting information is basically independent) can be stored as a value. There may be a need for exclusive control between functions, such as another function must be disabled. It is known that the number of exclusive controls increases at the same time when the function is expanded by upgrading the printer driver version or the like. Therefore, at the same time as the expansion of the DEVMODE structure for storing the setting value, the process for performing exclusive control of the setting value stored in the DEVMODE structure must be expanded at the same time.

  However, the printer driver may receive an old DEVMODE structure before upgrading (before function expansion) from an application and receive a print instruction. This is because the application itself can hold the DEVMODE structure (for example, the DEVMODE structure is held in the file created by the application, and the DEVMODE structure held when the file is opened is used. May be.)

  In that case, the printer driver must receive an old-format DEVMODE structure and perform validation processing for performing appropriate exclusive control and validity verification of the set value on the received DEVMODE structure. However, in the conventional method, there is a problem that inconsistency occurs between the old DEVMODE structure and the new validation process, and accurate exclusive control cannot be performed.

  The present invention has been made in view of the above, and a data structure in which various setting values (print setting information) related to printing are set even when the function is changed due to a version upgrade of a printer driver, and the like. A printer driver, an information processing apparatus, and an information processing apparatus, which are capable of performing an appropriate print setting value optimization process by eliminating inconsistencies that occur with a print setting value optimization program for optimizing print setting information An object of the present invention is to provide a computer-readable recording medium in which a printer driver is recorded.

  In order to solve the above-described problems and achieve the object, the present invention provides a printer driver capable of performing print settings via a data structure for exchanging print setting information with an external program. Using the storage means for storing print setting information and a print setting value optimization program in the data structure, and the print setting value optimization program stored in the data structure, It is characterized by functioning as set value suitability means for optimizing stored set value information.

  In addition, the present invention provides an information processing apparatus equipped with a printer driver capable of performing print settings via a data structure for transferring print setting information to and from an external program. Using the storage means for storing the print setting information and the print setting value optimization program and the print setting value optimization program stored in the data structure, the setting value information stored in the data structure is optimized. And a set value suitability means for performing.

  The present invention is also a computer-readable recording medium on which the printer driver is recorded.

  According to the present invention, even when the function of the printer driver is expanded (changed), the data structure in which various setting values related to printing are set, and the print setting value optimization processing for optimizing the various setting values are performed. It is possible to eliminate inconsistencies that occur between programs to be executed. As a result, an appropriate print setting value optimization process can be performed.

FIG. 1 is a diagram showing the overall configuration of a printer system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the configuration of the PC in the embodiment. FIG. 3 is a diagram illustrating the DEVMODE structure. FIG. 4 is a diagram for explaining the handling of the DEVMODE structure performed between the application and the printer driver. FIG. 5 is a diagram showing an example of layout information. 6 is a diagram showing an example of a print setting screen based on the layout information of FIG. 5 and the function information of FIG. FIG. 7 is a diagram illustrating an example of storage destination information. FIG. 8 is a diagram showing an example of the function information. FIG. 9 is a flowchart showing an outline of processing related to print setting using the DEVMODE structure between the application and the printer driver. FIG. 10 is a flowchart for explaining the details of the input DEVMODE process. FIG. 11 is a flowchart for explaining details of the output DEVMODE processing. FIG. 12 is a diagram illustrating an example of a validation program (script) stored in the program area of the input DEVMODE. FIG. 13 shows the validation program stored in the program area of the output DEVMODE by adding a new script to the validation program (script) stored in the program area of the input DEVMODE shown in FIG. It is a figure which shows an example. FIG. 14 is a schematic diagram for explaining the outline of the flow of processing between the programs related to the validation processing.

  Hereinafter, an embodiment of a printer system according to the present invention will be described in detail with reference to the accompanying drawings. In addition, the common code | symbol is attached | subjected to the common component.

(Overall configuration of printer system)
FIG. 1 is a diagram showing the overall configuration of a printer system according to an embodiment of the present invention. As shown in FIG. 1, in this embodiment, it is assumed that a PC 100 and a printer 150 are connected via a network 160. Then, in response to a print request from the PC 100, the printer 150 performs print processing.

(Configuration of PC100)
FIG. 2 is a block diagram showing the configuration of the PC 100. As illustrated in FIG. 2, the PC 100 includes a processing unit 101, a storage unit 102, and a communication unit 103. The processing unit 101 includes a CPU (Central Processing Unit) as a control unit (not shown) and a memory group having a ROM and a RAM as a main memory. When the PC 100 is started and executed, the application 104, the OS 105, and various drivers (only the printer driver 106 shown in FIG. 2) are loaded from the ROM and storage unit 102 and expanded on the main memory. Executed. The PC 100 has a hardware configuration using a normal computer including an input device such as a keyboard and a mouse, an output device such as a display, etc., but is omitted in FIG. 2 for simplicity of explanation.

  The functional blocks in the printer driver 106 shown in FIG. 2 are functions or means that are main parts for realizing control of the printer 150. In particular, the core driver 111 is a core part of the printer driver 106 and has a basic function as a printer driver. On the other hand, each plug-in (in FIG. 2, only plug-in A • 113 and plug-in B • 114 are illustrated) is a program for extending the function of the printer driver 106 including only the core driver 111. In combination with the core driver 111, the printer driver 106 (with expanded functions) is configured.

  The communication unit 103 transmits and receives information to and from the printer 150 connected via the network 160 illustrated in FIG.

  The application 104 is software that allows a user to issue a print instruction. When the user wants to print the data edited by the application 104, the application 104 receives a print instruction from the user. In this case, the application 104 does not generate print data for the printer 150 alone, and passes the print target information to the OS 105 together with the print request corresponding to the print instruction.

  The OS 105 is a program that manages the hardware and software of the PC 100. The OS 105 performs control such as program activation, information reading and storage. As a representative OS, MS Windows (registered trademark) and the like are known. In addition, the OS 105 passes information to be printed (document data, image data, etc.) to the printer driver 106 together with the print request passed from the application 104.

  The storage unit 102 is a storage unit that stores various information. Specifically, it is an HDD or the like. The stored information includes information related to processing for realizing a predetermined function of the core driver 111 and each plug-in (setting values used for processing, display information for changing setting values, and the like necessary for processing) There is setting information that defines all kinds of information. Examples of the setting information include layout information, storage destination information, function information, plug-in information, and the like (described below).

  In addition, a DEVMODE structure provided by the OS 105, a registry, etc., a validation program for performing validation processing on the initial standard functions, a validation program for upgrading that is added when the printer driver 106 is upgraded, and a plug-in An additional function validation program that is added as a result of the addition is also stored in the storage unit 102. In the present specification, each of the above validation programs is collectively referred to as a validation program (print setting value optimization program).

  The layout information is information describing the layout of the GUI component displayed on the setting screen. The storage destination information is information describing information about the storage location of each setting value. The function information is information describing information on the function (specification) of the connected printer. The plug-in information is information described about the added plug-in.

  The printer driver 106 includes a core driver 111, an interface unit 112, and plug-ins A and 113 and plug-ins B and 114 as plug-ins as a module group for performing the functions of the driver. Of course, the example of FIG. 2 is an example, and plug-ins can be arbitrarily added and deleted.

  The core driver 111 has a standard function as the printer driver 106. In addition, the core driver 111 includes a print setting unit 120 that controls UI, a drawing unit 130 that controls drawing, and each program (script) for validation as a module group for performing the function as the printer driver 106. A Validation program execution environment 140, which is an interpreter to be executed, is provided. The print setting unit 120 and the drawing unit 130 refer to the plug-in information when confirming the installed plug-in. Thereby, the core driver 111 can confirm the installed plug-in.

  The module group included in the core driver 111 performs not only the standard printing process but also the partial processing that cannot be performed by the module included in the installed plug-in. , Function information, plug-in information). Then, the setting information stored in the storage unit 102 is written by the plug-in installer, and the print setting unit 120 and the drawing unit 130 of the core driver 111 perform substitution by referring to the written setting information. It is possible. Regarding layout information, storage destination information, and plug-in information, each piece of information about each plug-in is added to the layout information, storage destination information, and plug-in information of the core driver 111. Functional information for each plug-in is stored in the storage unit 102 as an independent file.

  The print setting unit 120 includes a setting screen display unit 121, a distribution unit 122, a character string conversion unit 123, a compression unit 124, a compressed data storage unit 125, a compressed data acquisition unit 126, and a decompression unit 127.

  The setting screen display unit 121 controls display of a GUI (print setting screen) displayed on the monitor screen as a UI. The setting screen display unit 121 according to the present embodiment displays a print setting screen based on the layout information and function information stored in the storage unit 102. In addition, when the print setting screen is displayed, the processing result of the validation program executed in the validation program execution environment 140 is received, and usable functions and settings that can be set (setting range and setting value) are prohibited. Only display GUI components.

  The validation program is a program for verifying and managing the validity of various setting values used in the printing process and the prohibition between the settings as described above. In the present embodiment, the setting set in the DEVMODE structure is executed by the validation program execution environment (setting value suiting means) 140, which is an interpreter, of a validation program composed of, for example, an LUA script. It manages the value and the prohibition between each setting. In this embodiment, the use of an LUA script as a validation program eliminates the need for program compilation. In addition, when this script is converted into a byte code, the processing speed can be increased. Details of the structure of the DEVMODE structure that is characteristic in the present embodiment will be described later.

  The distribution unit 122 refers to the storage destination information and performs a process of distributing each set value for each storage destination specified by the storage destination information.

  The character string converting unit 123 converts the setting values distributed by the distribution unit 122 into character strings that are variable-length character strings each including a set name and a setting value for each storage destination. For example, a character string such as {“Duplex”: “on”, “Orientation”: “portrait”,. In this character string, the setting name functions as an identifier for identifying each setting value or an address of the setting value. By making the setting information into a character string in this way, it is possible to flexibly cope with the increase / decrease of the setting value.

  The compression unit 124 performs compression processing such as Zip compression on each character string generated by the character string converting unit 123 for each storage destination, and generates compressed data for each storage destination. By reducing the data size by this compression processing, even if the set value increases, the amount of increase in the compressed data stored in the DEVMODE structure that is a fixed-size data structure can be suppressed. Note that the compression method used here is arbitrary. The compression unit 124 also compresses the validation program.

  The compressed data storage unit (storage unit) 125 stores each compressed data generated by the compression unit 124 in each storage destination (setting value storage area of the registry or DEVMODE structure), and the compressed validation program is DEVMODE. Store and save in the program area of the structure. As shown in FIG. 3, the DEVMODE structure includes a public area that is a fixed area whose use is determined by the OS 105, and a private area that is a free area where the driver creator can freely manage information. . In the present embodiment, the compressed data stored in the DEVMODE structure is stored in the private area of the DEVMODE structure (details will be described later).

  The compressed data acquisition unit 126 reads the compressed data stored from the registry and the DEVMODE structure.

  The decompression unit 127 decompresses the compressed data acquired from the registry and the DEVMODE structure by the compressed data acquisition unit 126 and expands the compressed data in the internal memory.

  On the other hand, the drawing unit 130 includes a compressed data acquisition unit 131, a decompression unit 132, and a print data generation unit 133.

  The compressed data acquisition unit 131 reads the compressed data stored from the registry and the DEVMODE structure.

  The decompression unit 132 decompresses the compressed data acquired from the registry and the DEVMODE structure by the compressed data acquisition unit 131 and expands the compressed data in the internal memory.

  The print data generation unit 133 receives the processing result by the validation program after decompression executed in the validation program execution environment 140 with respect to the print setting (current value) after decompression, The validity of the print settings is confirmed, and print data that can be interpreted by the printer 150 is generated from the print settings whose validity has been confirmed and the drawing data requested to be printed by the application 104. Then, the generated print data is transmitted to the printer 150 via the communication unit 103.

  The interface (I / F) unit 112 is an interface that accepts addition of a plug-in. When a plug-in is added to the printer driver 106, the core driver 111 can call each module of the added plug-in via the interface unit 112. The added plug-in can also call each module of the core driver 111 via the interface unit 112.

  Plug-ins A and 113 and plug-ins B and 114 surrounded by broken lines in the figure are plug-ins configured as a dynamic link library that adds functions to the core driver 111. These plug-ins are composed of one or more modules in order to realize a predetermined function. The plug-in shown in the figure includes a print setting unit and a drawing unit, but generally the configuration is arbitrary.

  Then, the print setting unit of each plug-in displays a setting screen for the function of each plug-in in accordance with a display command from the print setting unit 120 of the core driver 111 performed via the interface unit 112. On the other hand, the drawing unit of each plug-in executes a drawing function performed using the function of the plug-in according to a drawing command from the drawing unit 130 of the core driver 111 performed through the interface unit 112.

  That is, the extended part of the print setting unit 120 of the core driver 111 is a plug-in print setting unit. An extended portion of the drawing unit 130 of the core driver 111 is a plug-in drawing unit.

  In addition, depending on the plug-in to be added, all the modules are included in the plug-in by using the functions of the modules (print setting unit 120 and drawing unit 130) of the core driver 111, that is, the core driver 111 performs the function substitution. No longer need to be created. This can reduce the development burden of plug-ins.

  In order to substitute a part of the functions necessary for the plug-in by the module of the core driver 111, it is necessary to update the external file referred to by each module of the core driver 111. In other words, the plug-in can operate as a plug-in simply by adding a module specific to the plug-in having a function that the core driver 111 does not have and updating the setting information referred to by each module of the core driver 111. it can.

  The addition of the plug-in to the printer driver 106 according to the present embodiment includes the addition of the plug-in's own dynamic link library and the validation program for the additional function, and further includes layout information, storage destination information, and plug-in information. This is done by adding descriptions to one or more and adding function information. Accordingly, it is possible to easily add a plug-in to the printer driver 106 already installed in the PC 100. That is, the user need not reinstall the printer driver itself.

  Here, the DEVMODE structure used in the present embodiment will be described with reference to FIGS. FIG. 3 is a diagram for explaining the DEVMODE structure, and FIG. 4 is a diagram for explaining the handling of the DEVMODE structure performed between the application 104 and the printer driver 106.

  The application 104 and the printer driver 106 exchange print settings with a data structure called a DEVMODE structure. This DEVMODE structure is a data format common to all printer drivers. However, the functions of the printer driver are usually different. Therefore, in the DEVMODE structure, two areas (Public area 301 and Private area 302) for storing setting values related to functions common to all printer drivers and setting values related to functions different for each printer driver are stored. Exists.

  The Public area 301 is an area for storing setting values related to functions common to all printer drivers. On the other hand, the private area 302 is an area for storing setting values related to different functions for each printer driver. The printer driver vendor can freely define and use the private area 302.

  The application 104 can acquire the setting value of the Public area 301 and set the setting value. However, the setting value of the private area 302 cannot be acquired or set. The private area 302 can be referred to only by the printer driver 106.

  When instructing print settings from the application 104 to the printer driver 106, the application 104 changes the print settings in the public area 301 described above, and inputs the changed DEVMODE structure (input DEVMODE) to the printer driver 106. To do.

  However, there are few functions that can be set in the Public area 301, and the application user cannot sufficiently set the functions of the printer driver 106 unless the setting value existing in the Private area 302 is changed. Therefore, in general, the printer driver provides the application 104 with a function of performing GUI display that enables the setting value existing in the private area 302 to be changed. This GUI is designed for the convenience of the application user so that all setting values existing in the Public area 301 and the Private area 302 can be set.

  Although the application 104 can access only the public area 301 as described above, the application 104 can acquire the entire DEVMODE structure (the public area 301 and the private area 302) and hold it. In the present embodiment, not only the setting value but also a validation program (script) is stored in the private area 302, and stored in this DEVMODE structure even if the printer driver 106 is upgraded or a function is expanded by a plug-in. The validation process can be performed using the validation program. In the private area 302, the setting value is stored in the setting value storage area 303, and the validation program is stored in the program area 304.

  As described above, the print settings are exchanged between the application 104 and the printer driver 106 using the DEVMODE structure. The application 104 can request the printer driver 106 to acquire a DEVMODE structure specific to the printer driver. The output DEVMODE 402 is obtained by this acquisition request.

  The output DEVMODE 402 acquired by the application 104 can be used as the input DEVMODE 401 for transmitting the print settings to the printer driver 106 again by the following three methods. The operation on the application 104 side for changing the output DEVMODE 402 to the input DEVMODE 401 is the following three operations.

(1) The output DEVMODE 402 obtained by the acquisition request made to the printer driver 106 is used as the input DEVMODE 401 as it is.

(2) By displaying the GUI provided in the printer driver 106 with the output DEVMODE 402 obtained by the acquisition request made to the printer driver 106, settings relating to all functions existing in the Public area and the Private area are performed. The changed output DEVMODE 402 is defined as an input DEVMODE 401.

(3) Only the setting value of the public area of the output DEVMODE 402 obtained by the acquisition request made to the printer driver 106 is changed to be the input DEVMODE 401.

  In any case, the application 104 makes an acquisition request for the DEVMODE structure to the printer driver 106 and changes the contents of the obtained DEVMODE structure to transmit any print setting to the printer driver 106.

  As described above, the application 104 can hold the DEVMODE structure (output DEVMODE 402) obtained from the printer driver 106. Therefore, only the printer driver 106 is often upgraded while the application 104 holds the DEVMODE structure. In this case, since the application 104 cannot know the version upgrade of the printer driver 106, there is a problem in that the old incompatible DEVMODE structure (input DEVMODE 401) is transmitted to the upgraded printer driver 106.

  The printer driver 106 verifies each setting value stored in the input DEVMODE 401 serving as the input information in consideration of such a situation in which the DEVMODE structure is inconsistent, and outputs the output DEVMODE 402 as an output DEVMODE 402. A DEVMODE structure reflecting the current correct setting status must be passed to the application 104. For this purpose, validation processing is performed.

  In the validation process, if a mismatch occurs between each setting value set in the Public area and each setting value set in the Private area, the responsibility for solving the inconsistency and the validity verification of the set value itself (For example, when the input range is 0 to 100, -1 and 101 are incorrect values and must be corrected). In this validation process, in the input DEVMODE 401, the setting value in the Public area acts on the setting value in the Private area. In the output DEVMODE 402, the setting value in the Private area acts on the setting value in the Public area. This is the description of the method for handling the DEVMODE structure provided in a general printer driver including the printer driver 106.

  Subsequently, the configuration of the DEVMODE structure in the present embodiment will be further described with reference to FIG.

  In the present embodiment, a validation program (validation program 403, version upgrade validation program 404, validation program group for additional functions (405, 406, etc.)) is stored in the DEVMODE structure, and the printer driver 106 executes it. The validation program is a program (script) that can realize two validation functions for input DEVMODE and output DEVMODE.

  The printer driver 106 acquires a validation program from the program area stored in the input DEVMODE 401, and executes validation processing on the input DEVMODE 401. Normally, the validation process is performed by executing the validation program stored in the input DEVMODE 401 on the output DEVMODE 402 in the same manner.

  If the input DEVMODE is not received from the application 104 as an exceptional operation or when the application 104 requests the printer driver 106 to acquire a DEVMODE structure, the input DEVMODE 401 does not exist. Therefore, when the output driver DEVMODE 402 is transferred to the application 104, the printer driver 106 compresses and stores the stored validation programs 403 to 406 in the program area of the output DEVMODE 402. Validation processing is performed. The same applies when the validation program is changed due to version upgrade or the like.

  When the printer driver 106 is upgraded, the difference of the upgrade validation program 404 is also executed for the output DEVMODE 402. The upgrade validation program 404 complements the validation program stored in the input DEVMODE 401. That is, when available functions increase due to version upgrade, the increase (difference) does not exist in the validation program stored in the input DEVMODE 401. The version upgrade validation program 404 is called when validation needs to be performed between the extended function and the existing function. If it is not necessary to extend Validation due to version upgrade, the version upgrade Validation program 404 may not exist.

  Besides the version upgrade, the function of the printer driver 106 may be expanded. Specifically, function expansion can occur in a printer driver such as the printer driver 106 that includes a mechanism for adding functions to an existing printer driver such as plug-in expansion. Since plug-in extension is a dynamic function addition, the function is detached. Also, there may be a plurality of plug-ins instead of a single plug-in. Therefore, there is a possibility that the validation process changes following the extended function. The additional function validation programs 1 and 405 and the additional function validation programs 2 and 406 are programs that complement the validation processing that follows such dynamic function expansion. In the present embodiment, the validation program is configured using a Lua script, but the form is not limited as long as the printer driver 106 can execute the program. When the print setting unit 120 and the drawing unit 130 of the printer driver 106 directly execute a validation program, these become setting value suitability means.

  Next, a specific example of the setting information (layout information, storage destination information, and function information) will be described.

(Layout information)
FIG. 5 is a diagram showing an example of layout information. In FIG. 5, only a part is illustrated. Further, the layout information shown in FIG. 5 is described in the JSON format, but may be in other formats.

  As shown in FIG. 5, the layout information describes the layout data for each GUI component displayed on the print setting screen. This layout data has type, name, and axis as attributes.

  “type” represents the type of GUI component. CheckBox, which is the value of type, indicates that the check box component is used for display. ComboBox indicates that a combo box component is used for display. Also, SpinBox indicates that display is performed by a spin box component. Although not shown, a GUI component can also be displayed by an edit box component, a list box component, or the like by describing EditBox, ListBox, or the like.

  name represents the name of the setting. Of the value of name, “duplex” indicates that duplex printing is set. Orientation indicates that the print orientation is set. “Copies” indicates that the number of copies is set. Although not shown, paper size setting, aggregation setting, and the like can also be specified by describing papersize, layout, and the like.

  Axis represents the coordinates of the display position of the GUI component. The attribute of axis, x indicates the horizontal coordinate from the upper left origin of the dialog box, and y indicates the vertical coordinate from the upper left origin of the dialog box. For example, the double-sided print setting (duplex) axis shown in FIG. 5 describes that the check box component specified by the attribute type is displayed at the horizontal position 25 and the vertical position 30.

  The setting screen display unit 121 reads layout information from the storage unit 102, generates a setting screen according to the read layout information, and displays the generated print setting screen on a display device (not shown) of the PC 100. At this time, the print setting unit 120 displays only items that can be set based on function information to be described later among the GUI components described in the layout information.

  6 is a diagram showing an example of a print setting screen displayed by the setting screen display unit 121 of the printer driver 106 when the layout information of FIG. 5 and the function information shown in FIG. As shown in FIG. 6, a check box component is arranged together with a display name “Duplex” for duplex printing setting, a combo box component is arranged together with a display name “Orientation” for setting the print orientation, and a display name for setting the number of copies. A spin box box component is arranged together with “Copies” (default setting values for the print orientation setting and the number of copies setting are based on function information described later). The OK button shown in FIG. 6 is a button for saving the changed print setting, and the Cancel button is a button for canceling the change.

(Save destination information)
In the storage destination information, information for specifying the storage location of each setting value is described. FIG. 7 illustrates only a part of the storage destination information. In the example shown in FIG. 7, the storage destination information is described in the JSON format, but may be in another format.

  Each setting name described in the portion specified by the registry and devmode keys of the storage destination information has a corresponding relationship with each setting name described in the layout information and function information. Then, the setting values corresponding to the setting names described in the key “registry” (finisher, hdd, fold... In the example of FIG. 7) are stored in the registry. On the other hand, the setting value corresponding to each setting name (duplex, orientation,... In the example of FIG. 7) described in the key “devmode” is stored in the DEVMODE structure. Note that finisher, hdd, and fold respectively represent a finisher, a hard disk, and a paper folding machine that have the functions of the printer 150.

(Function information)
FIG. 8 is a diagram showing an example of the function information. In FIG. 8, only duplex printing setting (duplex), printing orientation setting (orientation), and number of copies setting (copies) are illustrated for simplicity of explanation. Describes the setting of. The function information shown in FIG. 8 is described in the XML format, but may be in another format (for example, JSON).

  In the example of the function information illustrated in FIG. 8, information on each setting is defined for each feature tag. This feature tag has attributes of name, default, and type. Of course, the example shown in FIG. 8 is an example, and other attributes can be defined and used.

  The attribute name is the name of the setting and corresponds to the name of the layout information. In the example of FIG. 8, “duplex” as the value of the attribute name specifies that the duplex printing setting is set, “orientation” indicates the print orientation setting, and “copyes” specifies the number of copies setting. The attribute default represents the initial value of the option. The attribute type represents the format of the input set value. The value of type, pickone, specifies an option format. In addition to this pickone, there are a string for specifying a character string input format, a number for specifying a numeric input format, and the like.

  The pickone tag represents a selectable set value, and the set value is set by the attribute name in the pickone tag. The value of name, which is an attribute of pickone, indicates that portrait is vertical and landscape is horizontal in the print orientation setting. In the duplex printing setting, off represents function off and on represents function on. In setting the number of copies, min represents the minimum number of copies and max represents the maximum number of copies.

  Although not shown, a constraint tag can be described in a portion surrounded by the feature tag. The portion described using the constraint tag represents prohibition information regarding the setting of the feature tag that is the parent tag (example: <constant fixvalue = “off”>). Also, a fix value that is an attribute in the constraint tag can be used to set a setting value ("off" in the above example) that is forcibly changed when the prohibition condition is met.

  The prohibition condition can be described by using a condition tag in a portion surrounded by the constraint tag (example: <condition expression = “AAAAA! =“ On ”>). This condition tag is a prohibition of the constraint tag that is a parent tag. It represents the condition and can specify the condition using the expression expression (in the above example, the condition is satisfied when the setting AAAA is other than on) This also applies to the pickone tag A constraint tag can be described in a portion surrounded by the tags, and the pickone tag itself, that is, the option itself can also have prohibition information.

  As described above, the function information describes all functions provided in each printer including the option, and is prepared for each supported printer model.

(Processing related to print settings)
Next, processing related to print setting using the DEVMODE structure between the application and the printer driver will be described with reference to the flowchart of FIG. FIG. 9 is a flowchart showing an outline of processing related to print setting using the DEVMODE structure between the application and the printer driver.

  When the printer driver 106 receives the input DEVMODE from the application 104, the input DEVMODE process (step S901) verifies whether the input DEVMODE is appropriate setting information by the validation process, and there is a problem in inconsistency or validity. If so, solve it.

  Thereafter, the printer driver 106 executes print setting change processing (step S902) according to an instruction from the application 104. Specifically, as described above, by displaying a GUI (print setting screen) included in the printer driver 106, a print setting changing unit is provided to the end user, and the setting input is accepted. In the GUI displayed at this time, a GUI reflecting the setting status of the input DEVMODE after the input DEVMODE processing is displayed. The end user operates the GUI, and the determined print setting can be obtained as output DEVMODE.

  Next, as an output DEVMODE process (step S903), the output DEVMODE is verified by the validation process to determine whether the output DEVMODE is appropriate setting information, and if there is a problem with inconsistency or validity, it is resolved. Then, the output DEVMODE after the output DEVMODE process is passed to the application 104.

(Input DEVMODE processing)
Next, details of the input DEVMODE process shown in FIG. 9 will be described using the flowchart of FIG. FIG. 10 is a flowchart for explaining the details of the input DEVMODE process. The following processing is processing when the input DEVMODE structure is passed from the application 104. When the input DEVMODE structure is not passed from the application 104, the following series of processing is omitted.

  The printer driver 106 receives a DEVMODE structure (input DEVMODE) from the application 104 (step S1001).

  Next, a validation program is acquired from the program area of the DEVMODE structure (step S1002).

  Since the Validation program is stored in a compressed format, the compressed data is decompressed and restored (step S1003). At this time, a validation program for performing validation processing on the standard function, a validation program for upgrading, and a validation program for additional functions are expanded in the internal memory. However, the version upgrade validation program and the additional function validation program are expanded only when they exist.

  Then, the validation program is executed for the standard function to perform validation processing on the input DEVMODE (step S1004).

  Next, if the printer driver 106 has been upgraded, a version-up validation program exists, so the presence or absence of the program is checked (step S1005). If there is an upgrade validation program, each upgrade validation program is stored in a predetermined directory area of the internal memory when the compressed data is restored in step S1003. Therefore, by confirming this directory area, it is possible to confirm the presence or absence of a version upgrade validation program.

  If there is an upgrade validation program (Yes in step S1005), an additional validation process for upgrade is required, so the upgrade validation program is called and executed (step S1006). On the other hand, if there is no version upgrade validation program (No in step S1005), the process proceeds to step S1007.

  Next, when a dynamic function expansion such as a plug-in is performed, since there is a validation program for an additional function, the presence or absence is confirmed (step S1007). It is assumed that each additional function validation program is also stored in a predetermined directory area of the internal memory at the time of restoration in step S1003. Therefore, by confirming this directory area, it is possible to confirm whether or not the validation program for the additional function exists.

  If there is an additional function validation program (Yes in step S1007), additional validation processing according to the additional function is required, and each additional function validation program is called and executed (step S1008). On the other hand, if there is no validation program for additional functions (No in step S1007), the series of processing ends.

(Output DEVMODE processing)
Next, details of the output DEVMODE process shown in FIG. 9 will be described with reference to the flowchart shown in FIG. FIG. 11 is a flowchart for explaining details of the output DEVMODE processing.

  In the output DEVMODE processing, when the output DEVMODE is returned to the application 104 as a response to the input DEVMODE input from the application 104, the application 104 responds to the printer driver 106 to obtain a printer driver-specific DEVMODE structure request. There are two possible cases for returning the output DEVMODE. The following processing flow corresponds to these two cases.

  First, the printer driver 106 checks whether there is an input DEVMODE, that is, whether the input DEVMODE has been received from the application 104 (step S1101).

  If the input DEVMODE does not exist (No in step S1101), refer to a validation program (a validation program for standard functions, a validation program for upgrading, and a validation program for additional functions) stored in the storage unit 102. These are expanded in the internal memory (step S1102).

  Next, the validation program is compressed and stored in the program area of the output DEVMODE (step S1103). Here, the amount of use of the program area can be reduced by compressing the validation program. Prior to this, for example, when a function has been deleted by further upgrading or adding a plug-in or deleting a function by deleting a plug-in, a validation program (script), part of which is shown in FIG. The validation program shown in FIG. 13 to which the additional script (difference) is added is overwritten and stored in the program area (in FIG. 12 and FIG. 13, an example of a program for verifying the validity of the set value) In the functions shown in these figures, the default value is used when a value other than the value set in the table (tbl) is passed as a parameter or when a value outside the specified range is passed. Otherwise, the corresponding value on the table is returned). As described above, when the validation program is changed due to version upgrade or the like, the change (difference) is also reflected in the output DEVMODE structure.

  On the other hand, if the input DEVMODE exists (Yes in step S1101), the validation program in the program area of the held input DEVMODE is referred to (step S1104). The validation program is expanded in the internal memory in step S1003 described above.

  Next, the validation program stored in the storage unit 102 is referred to (step S1105).

  Next, it is confirmed whether there is a change in the validation program (step S1106). Specifically, the validation program stored in the program area of the input DEVMODE expanded in the internal memory is compared with the validation program stored in the storage unit 102. It is determined that there is no change in the program for use (No in step S1106), and the process proceeds to step S1107. On the other hand, if they are different as a result of the comparison, it is determined that the validation program has been changed (Yes in step S1106), and the process of step S1103 is executed. As a result, the change of the validation program is reflected in the output DEVMODE.

  Next, the validation program developed in the internal memory is executed, and validation processing is executed on the output DEVMODE after the print setting change processing executed in step S902 in FIG. 9 (step S1107).

  Next, if the printer driver 106 has been upgraded, the upgrade validation program is also expanded in the internal memory, and the presence or absence is confirmed (step S1008). The processing here is performed in the same manner as in step S1005 of FIG.

  If an upgrade validation program exists (Yes in step S1008), an additional validation process for upgrade is necessary, so the upgrade validation program is executed (step S1109). On the other hand, if there is no version upgrade validation program (No in step S1008), the process proceeds to step S1110.

  Next, when dynamic function expansion such as plug-in is performed, since the validation program for additional functions is also expanded and present in the internal memory, the presence or absence is confirmed (step S1110). The confirmation here is performed in the same manner as in step S1007 in FIG.

  If there is an additional function validation program (Yes in step S1110), the additional function validation program is executed because the additional validation process corresponding to the additional function is required (step S1111). On the other hand, when the validation program for additional functions does not exist (No in step S1110), the process proceeds to step S1112.

  After the above processing, the output DEVMODE is passed to the application 104 (step S1112).

(Processing flow between programs)
Next, the process flow between the programs related to the validation process shown in steps S1004 to S1008 in FIG. 10 and steps S1107 to S1111 in FIG. 11 will be outlined with reference to FIG. FIG. 14 is a schematic diagram for explaining the outline of the flow of processing between the programs related to the validation processing.

  As described above, the core driver 111 of the printer driver 106 includes the main program 1401 including the print setting unit 120 and the drawing unit 130, and the validation program execution environment 140 for operating the program executed in the validation process. In this embodiment, the validation program employs a Lua script, and the validation program execution environment 140 is a Lua script execution environment.

  The validation program 403 for the standard function is either a program stored in the program area of the input DEVMODE passed from the application 104 or a program provided in the printer driver 106, and is executed in the validation program execution environment 140 and executed. The result is notified to the main program 1401.

  The validation program 403 searches for a directory 1402 that stores a version-up validation program (404 that is expanded in the internal memory if it exists), and stores the version-up validation program (404) in the directory 1402. Check for existence and call multiple programs recursively. The called program is executed in the Validation program execution environment 140. With this operation, even when there are a plurality of version upgrade validation programs (for example, when there are multiple version upgrades), the program can be executed.

  The version upgrade validation program (404), if present, is executed after validation processing by the validation program 403, and the execution results are combined and notified to the main program 701.

  Furthermore, in order to cope with the case where the printer driver 106 is added by a dynamic function addition function such as a plug-in mechanism, an additional function validation program (405) (stored in the internal memory if it exists) is stored. The directory 1403 to be searched is searched, and processing is executed in the same manner as the version-up validation program.

  The details of the present embodiment have been described above. As described above, in this embodiment, setting information related to print settings and a validation program are set and stored in the DEVMODE structure, and the validation program stored or stored in the DEVMODE structure is used. Thus, the validation process for the setting information is executed, so that it is possible to eliminate the inconsistency between the setting value that could occur in the past and the program that performs the validation process for the setting value.

  The printer driver 106 according to the above-described embodiment is an installable or executable file and can be read by a computer such as a CD-ROM, flexible disk (FD), CD-R, or DVD (Digital Versatile Disk). Recorded on a simple recording medium.

  These programs may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network.

100 ... PC
101 ... Processing unit 102 ... Storage unit 103 ... Communication unit 104 ... Application 105 ... OS
106: Printer driver 111 ... Core driver 112 ... I / F unit 113 ... Plug-in A
114 ... Plug-in B
DESCRIPTION OF SYMBOLS 120 ... Print setting part 121 ... Setting screen display part 122 ... Sorting part 123 ... Character string conversion part 124 ... Compression part 125 ... Compressed data storage part 126 ... Compressed data acquisition part 127 ... Decompression part 130 ... Drawing part 131 ... Compressed data Acquisition unit 132 ... decompression unit 133 ... print data generation unit 140 ... validation program execution environment 150 ... printer 160 ... network 301 ... public area 302 ... private area 303 ... set value storage area 304 ... program area 401 ... input DEVMODE
402: Output DEVMODE
403 ... Validation program 404 ... Version upgrade validation program 405 ... Additional function validation program 1
406 ... Validation program 2 for additional functions

JP 2008-097574 A

Claims (15)

In a printer driver that can perform print settings via a data structure for exchanging print setting information with an external program,
Computer

Storage means for storing print setting information and a print setting value optimization program in the data structure;
A printer driver that functions as a setting value optimization unit that optimizes setting value information stored in the data structure using a print setting value optimization program stored in the data structure.   The printer driver according to claim 1, wherein the setting value suitability program is in a script language.   3. The printer driver according to claim 1, wherein the print setting information stored in the data structure is based on a format composed of a character string including a set name and a set value. .   The printer driver according to claim 2, wherein the setting value optimization program stored in the data structure is a byte-coded script.   The printer driver according to claim 1, wherein the setting value optimization program stored in the data structure is compressed.   6. The printer driver according to claim 1, wherein the print setting information stored in the data structure is compressed.   When the print setting value optimization program stored in the data structure has a change in the print setting value optimization program included in the printer driver, the storage means stores the change in the data structure. The printer driver according to claim 1, wherein the printer driver is reflected in a stored print setting value optimization program. In an information processing apparatus that implements a printer driver capable of performing print settings via a data structure for transferring print setting information to and from an external program,
Storage means for storing print setting information and a print setting value optimization program in the data structure;
Setting value optimization means for optimizing setting value information stored in the data structure using a print setting value optimization program stored in the data structure;
An information processing apparatus comprising:   9. The information processing apparatus according to claim 8, wherein the setting value suitability program is in a script language.   10. The information processing according to claim 8, wherein the print setting information stored in the data structure is based on a format composed of a character string composed of a set of a setting name and a setting value. apparatus.   The information processing apparatus according to claim 9, wherein the setting value suitability program stored in the data structure is a byte-coded script.   The information processing apparatus according to claim 8, wherein the setting value suitability program stored in the data structure is compressed.   The information processing apparatus according to claim 8, wherein the print setting information stored in the data structure is compressed.   When the print setting value optimization program stored in the data structure has a change in the print setting value optimization program included in the printer driver, the storage means stores the change in the data structure. The information processing apparatus according to claim 8, wherein the information processing apparatus is reflected in a stored print setting value optimization program.   The computer-readable recording medium which recorded the printer driver of any one of Claims 1-7.

Images