JP2015060337A - Information processing device, device driver, and customization program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a set value before customization to be taken over and referenced even when the functional objects of a device driver are recombined.SOLUTION: A customization tool 30 for customizing a device driver by recombining the functional objects incorporated into the device driver has: a functional object alteration unit 31 for recombining, on the basis of instruction operation by a user, at least one functional object incorporated into the device driver into a new functional object; and a takeover processing unit 32 which, following the recombination of functional objects, reads out, from management information 10 pre-generated by the device driver, a set value at a preservation destination designated in the functional object before being recombined and preserves the set value at a preservation destination designated in the recombined functional object.

Description

  The present invention relates to an information processing apparatus, a device driver, and a customization program, and more particularly to a technique for customizing a function of a device driver installed in the information processing apparatus.

  2. Description of the Related Art Conventionally, a technique is known in which a user can customize an initial value setting of a device driver such as a printer driver or a setting item display / non-display switching setting using a customization tool (for example, Patent Document 1). . In this prior art, various settings such as print settings can be edited by using a customization tool. Information customized by the customization tool is stored in a file. When the installer updates the device driver, it determines whether the installer is a customized device driver, and if it is a customized device driver, writes the information stored in the file to the updated device driver. By doing so, the customized information is taken over. That is, according to the conventional technology, when the installer reinstalls for updating the device driver, the information customized before the update is taken over after the update.

JP 2006-309726 A

  By the way, in recent years, in order to improve the development efficiency of device drivers such as printer drivers, for example, only basic function parts common to various devices are created as driver common parts, and settings corresponding to functions unique to individual devices are created. A development method is adopted in which a part such as an item is created as a function object that is incorporated in the driver common part. Therefore, a recent device driver is configured by a driver common unit and a plurality of functional objects incorporated in the driver common unit. A function object is provided for each function, and defines the setting items for each function, the display / non-display of the setting items, the display position when displaying the setting items, the options that the user can select for the setting items, and the like. is there. Such a function object designates a DEVMODE structure or a registry address as a storage destination of default setting values and setting values set by the user for each setting item. Therefore, the driver common unit can display setting items for each function on a display screen serving as a user interface by referring to various types of information defined by each function object incorporated in the device driver. Further, at this time, the driver common unit reads the setting value for each setting item of each function from the storage location specified by each function object, so that the default setting value or the user can set the setting value to be displayed on the display screen. Displays the setting values that have been set in the past. Therefore, the user can perform setting operations such as print output while referring to the default setting value and the current setting value for each setting item for each function.

  In the case of a device driver in which a function object is embedded as described above, when a user performs a customization operation for each function, the function object embedded in the device driver may be reconfigured to a new function object specified by customization. is there. At this time, the range that can be customized by the user is not only the part that can be visually recognized on the display screen, such as adding or deleting setting items for each function, changing the display position, and switching between display / non-display, but also each setting. It is possible to customize and change the storage location of setting values for items. Therefore, for example, even though the function object before recombination specified the DEVMODE structure as the setting value storage destination, the new function object recombined with it specifies the registry as the setting value storage destination. Can happen.

  However, if the storage location of the setting value changes due to the rearrangement of the function object, the reference destination when the driver common unit reads the setting value before and after customization changes. As a result, the device driver starts after customization, and even if the driver common unit tries to read the setting value from the storage location specified in the new function object, the setting value saved before customization cannot be read. The display screen cannot be displayed normally. To prevent this, if the function object is reconfigured to a new function object, the default setting values are stored in the storage location specified by the new function object by reinstalling the device driver. It is necessary to do this, and there is a problem that convenience is bad.

  Accordingly, the present invention has been made to solve the above-described problems, and provides an information processing apparatus, a device driver, and a customization program that can refer to setting values before customization even if functional objects are rearranged. It is intended.

  In order to achieve the above object, the invention according to claim 1 is an information processing apparatus, which is provided for each function that can be set by a user, and incorporates a plurality of function objects that specify storage destinations of setting values of the respective functions. And a customization tool for customizing a function object incorporated in the device driver, wherein the device driver obtains a setting value of each function from a storage destination specified in each of the plurality of function objects. A user interface unit that reads out and displays and changes a setting value of a storage destination specified in a function object corresponding to the function for which the setting operation is performed based on a setting operation for each function by the user; Setting the storage location specified by each function object And a setting value management unit that manages the information as management information, and the customization tool converts at least one function object incorporated in the device driver into a new function object based on an instruction operation by a user. When the storage destination specified in the functional object after the rearrangement is changed by the functional object changing unit to be rearranged and the functional object changing by the functional object changing unit, the function before the rearrangement from the management information And a takeover processing unit that reads the setting value of the storage destination specified in the object and stores the setting value in the storage destination specified in the functional object after the rearrangement.

  According to a second aspect of the present invention, in the information processing apparatus according to the first aspect, the setting value management unit stores the setting value in a storage destination specified in the functional object after the rearrangement by the handover processing unit. The management information is updated later.

  The invention according to claim 3 is the information processing apparatus according to claim 1 or 2, further comprising a plurality of the device drivers provided for each device, wherein the function object changing unit includes the plurality of device drivers. The function objects incorporated in each of the device drivers can be rearranged, and the takeover processing unit is the set value management unit of the device driver in which the functional object is rearranged by the functional object change unit among the plurality of device drivers. The setting value of the storage destination specified in the functional object before the rearrangement is read out from the management information managed by.

  According to a fourth aspect of the present invention, in the information processing apparatus according to any one of the first to third aspects, the setting value management unit records and manages information related to each of the plurality of functional objects in the management information. When the function object changing unit performs the rearrangement of the functional objects, the information regarding the functional objects after the rearrangement is different from the information regarding the functional objects before the rearrangement recorded in the management information. In addition, the configuration is characterized in that it is detected that the storage destination specified in the functional object after the rearrangement is changed.

  According to a fifth aspect of the present invention, in the information processing apparatus according to the fourth aspect, the setting value management unit is a functional object in which at least one functional object incorporated in the device driver by the functional object changing unit is a new functional object. The information related to the functional object recorded in the management information is updated with the rearrangement.

  The invention according to claim 6 is the information processing apparatus according to any one of claims 1 to 5, wherein the function object changing unit corresponds to at least one function object incorporated in the device driver. A function definition data acquisition unit that acquires definition data, a function definition data editing unit that edits the function definition data acquired by the function definition data acquisition unit based on an instruction operation by a user, and an edit by the function definition data editing unit And a function object generation unit that generates a new function object based on the function definition data.

  The invention according to claim 7 is the information processing apparatus according to any one of claims 1 to 6, wherein the setting management unit changes a setting value of a storage destination specified in each functional object by the user interface unit. Each time, the management information is updated by mirroring the setting value of the storage destination.

  The invention according to claim 8 incorporates a plurality of function objects provided for each function that can be set by a user, and specifies a storage location of a setting value for each function in each function object. A device driver that can be customized by recombining any of the functional objects, and the information processing apparatus reads the setting value of each function from the storage destination specified in each of the plurality of functional objects A user interface unit for displaying and changing a setting value of a storage destination specified in a function object corresponding to the function for which the setting operation has been performed based on a setting operation for each function by the user, and the plurality of functions The storage location specified by each object A configuration for causing the function setting value management unit mirroring a value is managed as management information, as.

  The invention according to claim 9 is a customization program for customizing a function object incorporated in a device driver installed in an information processing apparatus, wherein the information processing apparatus is connected to the device based on an instruction operation by a user. It is specified in the functional object after recombination in accordance with the functional object changing unit that rearranges at least one functional object incorporated in the driver into a new functional object, and the functional object changing by the functional object changing unit. When the storage destination is changed, the setting value of the storage destination specified in the function object before the rearrangement is read from the management information managed in the device driver, and the function object after the rearrangement is read out. A construction which is characterized in that to function as the takeover processing unit, which stores the destination specified in the transfected.

  According to the present invention, even when the device driver is customized by rearranging the functional objects, the setting value before customization can be taken over and referenced, so that the device driver can be normally operated even after customization. Can be started.

It is a figure which shows an example of the hardware constitutions of information processing apparatus. It is a figure which shows an example of a detailed functional structure in case CPU functions as a device driver. It is a figure which shows an example of the data structure of a registry and a DEVMODE structure. 6 is a diagram illustrating an example of a print setting screen displayed by a UI processing unit. FIG. It is a figure which shows an example of the management information managed by the setting value management part. It is a figure which shows an example of the functional object information, registry management information, and DEVMODE structure management information contained in management information. It is a flowchart which shows an example of the process sequence performed by a device driver. It is a figure which shows an example of a detailed functional structure in case CPU functions as a customization tool. It is a figure explaining the concept of the process in each of a function definition data acquisition part, a function definition data edit part, a function object production | generation part, and a rearrangement process part. It is a figure which shows the example of 1 structure of the device driver by which the rearrangement of the functional object was performed. It is a figure which shows an example of the data structure of the registry and DEVMODE structure which were updated by the data structure update part. It is a flowchart which shows an example of the process sequence performed by the customization tool. It is a flowchart which shows an example of the detailed process sequence of a data transfer process.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings. In the embodiments described below, members that are common to each other are denoted by the same reference numerals, and redundant descriptions thereof are omitted.

  FIG. 1 is a diagram illustrating an example of a hardware configuration of an information processing apparatus 1 according to an embodiment of the present invention. The information processing apparatus 1 includes a CPU 2, a memory 3, a display unit 4, an operation input unit 5, a communication interface 6, and a storage device 7. For example, the information processing device 1 is configured by a general personal computer (PC). Is done.

  The CPU 2 executes various programs installed in advance in the storage device 7. The memory 3 stores temporary data and the like when the CPU 2 executes various programs. The display unit 4 is configured by a color liquid crystal display, for example, and displays various types of information to the user. The operation input unit 5 includes a keyboard and a mouse, receives various input operations by the user, and outputs operation information to the CPU 2. The communication interface 6 communicates with an external device by connecting the information processing apparatus 1 to a network such as a LAN (Local Area Network). The storage device 7 is a nonvolatile storage unit configured by a hard disk drive (HDD) or a solid state drive (SSD), and stores programs executed by the CPU 2 and various data.

  For example, the programs installed in advance in the storage device 7 include an operating system 8 that is basic software of the information processing apparatus 1, and a device driver 9a that is a driver program for outputting a print job to a printer that is an external device. There is a customization program 9b for customizing the device driver 9a. In addition to this, the storage device 7 stores various application programs for the user to perform document editing and the like. Further, the storage device 7 stores management information 10, a registry 11, and a DEVMODE structure 12 as shown in FIG. The management information 10 is information generated when the CPU 2 activates the device driver 9a. The registry 11 is information that is managed by the operating system 8 activated in the CPU 2 and stores setting values of the operating system 8, the device driver 9a, and other various applications. The DEVMODE structure 12 is a database for storing setting values related to print settings.

  In the information processing apparatus 1 as described above, the CPU 2 automatically starts the operating system 8 when the power is turned on. Thereafter, various application programs for performing document editing and the like are started based on an instruction for starting the application by the user. For example, when the user issues a print instruction while the application program is activated in the information processing apparatus 1, the CPU 2 reads the device driver 9 a from the storage device 7 and executes it. As a result, the information processing apparatus 1 displays a display screen for the user to perform a print setting operation on the display unit 4. Therefore, the user can perform a print setting operation while viewing the display screen. When the user instructs activation of the customization program 9b while the operating system 8 is activated, the CPU 2 reads the customization program 9b from the storage device 7 and activates it. Thereby, the user can perform the customization operation of the device driver 9a.

  FIG. 2 is a diagram illustrating an example of a detailed functional configuration when the CPU 2 functions as the device driver 20 by executing the device driver 9a. The device driver 20 includes a driver common unit 21 and a plurality of functional objects 27a, 27b, and 27c, and a plurality of functional objects 27a, 27b, and 27c are incorporated in the driver common unit 21. The driver common unit 21 is a processing unit that executes processing related to common functions that can be used in common for a plurality of types of printers, for example. That is, the driver common unit 21 performs processing independent of the printer model. The driver common unit 21 includes a setting value management unit 22, a user interface processing unit 23 (hereinafter simply referred to as “UI processing unit 23”), a drawing processing unit 24, and a common interface unit 25.

  Each of the plurality of function objects 27a, 27b, and 27c manages information related to individual functions installed in a printer of a specific model connected to the network, for example. For example, setting items corresponding to the individual functions Manage etc. That is, the function objects 27a, 27b, and 27c manage information related to settings for each function depending on the printer model. Such functional objects 27a, 27b, and 27c are constructed as program modules incorporated in the driver common unit 21, for example. Therefore, each functional object 27a, 27b, and 27c does not function independently, but functions by being incorporated in the driver common unit 21, and the driver common information necessary according to the request from the driver common unit 21 is shared. It is comprised so that it may output to the part 21.

  There are various functions managed in these function objects 27a, 27b, and 27c. For example, if the printer can print out by switching the document orientation between portrait and landscape, the function to set the document orientation at the time of print output or the paper size when the printer outputs various document sizes A function that sets the document size, paper size, etc. when printing is possible by enlarging or reducing the image, a function that switches between color printing and monochrome printing when the printer is capable of color printing, and various printers When the paper type is supported, the function to set the paper type at the time of printing is set. When the printer has the function to perform secure printing (confidential printing), the security printing setting and the security printing are set. There is a function for setting identification information such as an ID and a password. In addition to this, various functions related to settings at the time of print output are assigned to the function objects 27a, 27b, and 27c. In this embodiment, the case where three functional objects 27a, 27b, and 27c are incorporated in the driver common unit 21 is illustrated, but the number of functional objects is not limited to three, and is four or more. It doesn't matter. Each of these functional objects 27a, 27b, and 27c holds functional information 28a, 28b, and 28c and storage destination information 29a, 29b, and 29c.

  The function information 28a, 28b, 28c is information that defines a display mode or the like related to the function of each function object 27a, 27b, 27c. For example, each function information 28a, 28b, 28c includes information defining at least one setting item corresponding to the function assigned to each function object 27a, 27b, 27c, and display or non-display of the setting item. Information that defines display settings, display positions of the setting items, choices that the user can select and operate on the setting items, and the like is included. The storage destination information 29a, 29b, and 29c is information that specifies a default setting value for each setting item defined in each function information 28a, 28b, and 28c or a storage destination of a setting value set by the user. This is information for designating either the registry 11 or the DEVMODE structure 12 as a storage destination, and designating an address for storing the setting value in the registry 11 or the DEVMODE structure 12. Each function object 27 a, 27 b, 27 c outputs function information 28 a, 28 b, 28 c and storage destination information 29 a, 29 b, 29 c to the driver common unit 21 in response to a request from the driver common unit 21.

  FIG. 3 is a diagram illustrating an example of the data structure of the registry 11 and the DEVMODE structure 12. As shown in FIG. 3A, the registry 11 has an address part 11a and a data part 11b. The address part 11a indicates a storage address of data (set value) stored in the data part 11b. Therefore, when each functional object 27a, 27b, 27c designates the registry 11 as a setting value storage destination, the address of the registry 11 in which the setting value is stored in the storage destination information 29a, 29b, 29c. Contains information. Note that FIG. 3A illustrates a case where setting values related to the function of one functional object 27a among the three functional objects 27a, 27b, and 27c are stored in the registry 11. Since the registry 11 is information managed by the operating system 8 as described above, the setting values stored in the registry 11 are information used only in the information processing apparatus 1 as shown in FIG. Become.

  On the other hand, as shown in FIG. 3B, the DEVMODE structure 12 also has an address part 12a and a data part 12b. The address part 12a indicates a storage address of data (set value) stored in the data part 12b. Therefore, when each functional object 27a, 27b, 27c designates the DEVMODE structure 12 as a setting value storage destination, the storage device information 29a, 29b, 29c stores the setting value in the DEVMODE structure. The address information of the body 12 is included. FIG. 3B illustrates a case where setting values related to the functions of the two function objects 27b and 27c among the three function objects 27a, 27b, and 27c are stored in the DEVMODE structure 12.

  Such a DEVMODE structure 12 can be associated with, for example, an application that performs document editing or a document file generated by the application. By associating the DEVMODE structure 12 with an application or document file, it is possible to perform printing by taking over the previous print settings when performing print output again after performing print setting operations once and performing print output. There is an advantage that the second and subsequent print setting operations can be simplified. On the other hand, when the DEVMODE structure 12 is associated with the document file, when the document file is viewed by another user, the setting value included in the DEVMODE structure 12 associated with the document file is also different from the other setting values. Will be viewed by the user. Therefore, for example, identification information such as ID and password for security printing is preferably stored in the registry 11 instead of being stored in the DEVMODE structure 12.

  Returning to FIG. 2, the UI processing unit 23 of the driver common unit 21 displays a print setting screen on the display unit 4 as the device driver 20 functions, and the user's operation performed on the operation input unit 5. Accept setting operations. When displaying the print setting screen on the display unit 4, the UI processing unit 23 generates a screen frame of the print setting screen. The UI processing unit 23 refers to the function information 28a, 28b, 28c of each function object 27a, 27b, 27c, and displays various setting items in the display mode defined by the function information 28a, 28b, 28c. By arranging inside the screen frame and reading the setting value of each setting item from the registry 11 or the DEVMODE structure 12 based on the storage destination information 29a, 29b, 29c, and reflecting the current setting value to each setting item Generate print setting screen. The UI processing unit 23 outputs the print setting screen generated in this way to the display unit 4, thereby displaying a print setting screen on which the user can perform various print settings. It becomes like this.

  FIG. 4 is a diagram illustrating an example of the print setting screen G1 displayed by the UI processing unit 23. The UI processing unit 23 generates a screen frame of the print setting screen G1, and displays setting items, current setting values, and the like that allow the user to perform print setting operations on the setting region R1 at the center of the screen frame. . That is, the UI processing unit 23 arranges each setting item in the setting area R1 based on the function information 28a, 28b, 28c of each function object 27a, 27b, 27c, and saves each function object 27a, 27b, 27c. Based on the previous information 29a, 29b, 29c, the current setting value of each setting item is acquired from the registry 11 or the DEVMODE structure 12, and is displayed as the current setting value of each setting item. As a result, the setting items displayed in the setting area R1 are displayed in the display mode defined by the function objects 27a, 27b, and 27c. The user can change the current setting value to a desired setting value by performing a desired setting operation on each setting item included in the setting area R1.

  Further, the print setting screen G1 shown in FIG. 4 includes an area R2 for the user to make settings related to security printing. In security printing, identification information including an ID and a password is set in advance in a print job, and the user moves to the printer installation location and inputs identification information that matches the ID and password to the printer. Thus, the printing method starts printing output in the printer. For this reason, the area R2 includes setting items for presetting identification information including an ID and a password to be input by the user in order to perform security printing.

  When the setting value of each setting item is changed by the user's print setting operation in the state where the print setting screen G1 as described above is displayed, the UI processing unit 23 stores the storage location of the setting value of the setting item. It is specified based on the previous information 29a, 29b, and 29c, and the setting value stored in the specified storage location is rewritten to the setting value specified by the user. Thereby, the setting value of each setting item is changed. That is, the UI processing unit 23 is configured to update the setting value stored in the registry 11 or the DEVMODE structure 12 based on a setting operation by the user. The UI processing unit 23 also updates the print setting screen G1 displayed on the display unit 4 when the setting values stored in the registry 11 and the DEVMODE structure 12 are updated. Thereby, the setting value on the print setting screen G1 displayed on the display unit 4 is updated to the setting value designated by the user.

  The UI processing unit 23 causes the drawing processing unit 24 to function when detecting a print instruction by the user while the print setting screen G1 is displayed on the display unit 4. The drawing processing unit 24 obtains a document (image data) designated by the user, and performs a drawing process corresponding to the document, so that it can be printed out by a printer of a specific model connected to the network. Print data is generated. The drawing processing unit 24 generates a print job including the print data generated by the drawing process and various print commands, and transmits the print job to a specific model printer via the communication interface 6. At this time, the drawing processing unit 24 reads the setting values of the setting items for each function from the registry 11 or the DEVMODE structure 12 based on the storage destination information 29a, 29b, and 29c of the function objects 27a, 27b, and 27c. In addition to performing drawing processing corresponding to, a print command corresponding to these set values is generated. Therefore, the print job output to the printer of the specific model is a print job that reflects the print settings set by the user on the print setting screen G1. Note that the drawing processing unit 24 may acquire the setting values from the UI processing unit 23 instead of reading the setting values from the registry 11 or the DEVMODE structure 12.

  The setting value management unit 22 reads setting values stored in the registry 11 and the DEVMODE structure 12, and stores and manages these setting values in management information 10 different from the registry 11 and the DEVMODE structure 12. It is. That is, the setting value management unit 22 manages the setting values stored in the registry 11 and the DEVMODE structure 12 by mirroring them in the management information 10. For example, when the setting value stored in the registry 11 or the DEVMODE structure 12 is changed by the UI processing unit 23, the setting value management unit 22 manages the setting value stored in the registry 11 or the DEVMODE structure 12. The information 10 is mirrored, and the change of the setting value by the UI processing unit 23 is reflected in the management information 10 as well. As a result, the management information 10 stores the same setting values as the setting values related to the print settings stored in the registry 11 and the DEVMODE structure 12 respectively.

  FIG. 5 is a diagram illustrating an example of the management information 10 managed by the setting value management unit 22. As shown in FIG. 5, the management information 10 includes functional object information 16 in which information related to the functional objects 27a, 27b, and 27c is recorded, and setting values of the setting items defined in the functional objects 27a, 27b, and 27c. And setting value management information 17 for managing the. The setting value management information 17 includes registry management information 18 that holds the same information as the setting values stored in the registry 11 and DEVMODE structure management that holds the same information as the setting values stored in the DEVMODE structure 12. Information 19.

  FIG. 6 is a diagram illustrating an example of the functional object information 16, the registry management information 18, and the DEVMODE structure management information 19 included in the management information 10. As shown in FIG. 6A, the functional object information 16 includes functional object identification information 16a for identifying the functional objects 27a, 27b, and 27c, and version information 16b of the functional objects 27a, 27b, and 27c. In addition, the identification information and the version of each functional object 27a, 27b, 27c are recorded. That is, by referring to this functional object information 16, it is possible to determine whether or not the version of each functional object 27a, 27b, 27c incorporated in the driver common unit 21 has been updated. Therefore, for example, the setting value management unit 22 acquires version information from each functional object 27a, 27b, 27c at the timing when the device driver 20 is activated in the CPU 2, and the version information and the version recorded in the functional object information 16 are obtained. By comparing with the information 16b, it is possible to determine whether or not each functional object 27a, 27b, 27c has been updated before the device driver 20 is activated. When the version information acquired from the function objects 27a, 27b, and 27c is different from the version information 16b recorded in the function object information 16, the setting value management unit 22 acquires the information from the function objects 27a, 27b, and 27c. The latest version information is written in the version information 16b field of the functional object information 16, and the management information 10 is updated.

  The registry management information 18 is information in which setting items 18a, address information 18b, size information 18c, and setting values 18d are recorded for each function of the function objects 27a, 27b, and 27c. The setting item 18a is a setting item defined in the function information 28a, 28b, and 28c of each function object 27a, 27b, and 27c, and the address information 18b is stored in the registry 11 in which the setting value of the setting item is stored. This is information indicating an address. The size information 18c is information indicating the data size of the setting value stored in the registry 11, and the setting value 18d is a value stored by mirroring the setting value stored in the registry 11. Therefore, by referring to the registry management information 18, it is possible to identify the setting item whose storage destination is specified as the registry 11 in each functional object 27 a, 27 b, 27 c and the setting value of the setting item.

  Further, as with the registry management information 18, the DEVMODE structure management information 19 records setting items 19a, address information 19b, size information 19c, and setting values 19d for each function of each functional object 27a, 27b, 27c. Information. The setting item 19a is a setting item defined in the function information 28a, 28b, 28c of each function object 27a, 27b, 27c, and the address information 19b is a DEVMODE structure in which the setting value of the setting item is stored. Information indicating 12 addresses. The size information 19c is information indicating the data size of the setting value stored in the DEVMODE structure 12, and the setting value 18d is stored by mirroring the setting value stored in the DEVMODE structure 12. Value. Therefore, by referring to the DEVMODE structure management information 19, the setting item in which the storage destination is specified as the DEVMODE structure 12 in each function object 27a, 27b, and 27c and the setting value of the setting item are specified. Can do.

  Then, each time the setting value stored in the registry 11 or the DEVMODE structure 12 is rewritten by the UI processing unit 23, the setting value management unit 22 sets the column of the setting value 18d of the registry management information 18 or the DEVMODE structure management. The management information 10 is updated by rewriting the column of the setting value 19 d of the information 19.

  The common interface unit 25 is an interface for incorporating each of the plurality of functional objects 27a, 27b, and 27c into the driver common unit 21. The common interface unit 25 includes, for example, a setting value management unit 22, a UI processing unit 23, and a drawing processing unit 24, which function information 28a, 28b, 28c and storage destination information 29a, 29b, from the function objects 27a, 27b, 27c, respectively. When reading 29c, the common command can be used for reading. For this reason, the setting value management unit 22, the UI processing unit 23, and the drawing processing unit 24 do not need to switch commands for each functional object, so that the processing efficiency is improved.

  Next, the operation of the device driver 20 configured as described above will be described. FIG. 7 is a flowchart illustrating an example of a processing procedure performed by the device driver 20. This process is a process performed by the driver common unit 21 of the device driver 20, and is a processing procedure that proceeds by the cooperative operation of the setting value management unit 22, the UI processing unit 23, and the drawing processing unit 24 described above. ing. When the device driver 20 functions in the CPU 2, the driver common unit 21 reads the function information 28a, 28b, and 28c from the function objects 27a, 27b, and 27c incorporated in the driver common unit 21 (step S10). Then, the set value management unit 22 functions and performs version comparison with the version information 16b recorded in the function object information 16 (step S11), and determines whether the function objects 27a, 27b, and 27c have been changed. (Step S12). As a result, when at least one of the plurality of functional objects 27a, 27b, and 27c has been changed (YES in step S12), the setting value management unit 22 sets the version information 16b of the functional object information 16 included in the management information 10 It is rewritten and updated to the latest state (step S13). If no change has occurred in the plurality of functional objects 27a, 27b, and 27c (NO in step S12), the process in step S13 is skipped.

  Subsequently, the UI processing unit 23 functions in the driver common unit 21. The UI processing unit 23 acquires storage destination information 29a, 29b, and 29c from the functional objects 27a, 27b, and 27c, and sets the setting values of the setting items based on the storage destination information 29a, 29b, and 29c in the registry. 11 or DEVMODE structure 12 is read (step S14). The UI processing unit 23 generates a print setting screen G1 to be displayed on the display unit 4 based on the read setting value, and outputs and displays the print setting screen G1 on the display unit 4 (step S15). .

  Then, the UI processing unit 23 determines whether or not a print instruction has been given by the user (step S16). If no print instruction has been given (NO in step S16), the user performs a print setting setting change operation. It is determined whether or not it has been received (step S17). If the setting change operation has not been performed (NO in step S17), the process by the UI processing unit 23 returns to step S16, and the above determination is repeated until the user performs an operation. If the user performs a print setting change operation (YES in step S17), the UI processing unit 23 changes the setting based on the storage destination information 29a, 29b, and 29c of the function objects 27a, 27b, and 27c. Reference is made to the storage location of the set value that has been performed (step S18), and the storage location setting value is updated to the setting value designated by the user (step S19). Then, the UI processing unit 23 updates the print setting screen G1 displayed on the display unit 4 to a display screen reflecting the user's operation (Step S20). Accordingly, the set value management unit 22 functions. Then, the setting value management unit 22 reads the setting value of the registry 11 or the DEVMODE structure 12 updated by the UI processing unit 23, and the registry management information 18 or the DEVMODE structure management information 19 of the management information 10 based on the setting value. The management information 10 is updated to the latest state by rewriting the setting value stored in (step S21). And it returns to step S16 and will be in the state which waits for the next operation by a user.

  When a print instruction is issued by the user (YES in step S16), the UI processing unit 23 causes the drawing processing unit 24 to function. The drawing processing unit 24 generates a print job by performing drawing processing based on the print settings designated by the user (step S22), and outputs the print job to the printer via the communication interface 6 (step S23). ). Thus, a series of processing by the device driver 20 is completed.

  Next, a case where the customization program 9b is activated in the CPU 2 will be described. FIG. 8 is a diagram showing an example of a detailed functional configuration when the CPU 2 functions as the customization tool 30 by executing the customization program 9b. When the CPU 2 executes the customization program 9b based on the activation instruction from the user, the CPU 2 causes the customization tool 30 to function as shown in FIG. The customization tool 30 is a tool for updating the device driver 20 by adding, deleting, or changing a function object with respect to the device driver 20 based on a customization operation by the user. That is, the customization tool 30 updates the device driver 20 by changing the function object for the driver common unit 21 without changing the driver common unit 21 of the device driver 20. Therefore, the user activates the customization tool 30 in the information processing apparatus 1 to change the display or non-display of the setting items displayed in the setting region R1 of the print setting screen G1 described above and the display mode of the setting items, for example. Can be customized. The customization tool 30 not only changes the display mode of the print setting screen G1, but also stores the setting value storage location of each setting item from the registry 11 to the DEVMODE structure 12 based on an instruction operation by the user. It is also possible to change from the DEVMODE structure 12 to the registry 11. Hereinafter, the customization tool 30 will be described in detail.

  As illustrated in FIG. 8, the customization tool 30 includes a function object changing unit 31 and a takeover processing unit 32. The functional object changing unit 31 is a processing unit that updates the device driver 20 by rearranging the functional objects of the device driver 20 based on a user's customization operation. Further, the takeover processing unit 32 sets the setting before customization when the storage location of the setting value of each setting item is changed from the registry 11 to the DEVMODE structure 12 or from the DEVMODE structure 12 to the registry 11 by the customization operation by the user. It is a processing unit that allows data before customization (setting values) to be normally referred to even after customization by writing values to a storage location after customization.

  The function object changing unit 31 includes a function definition data acquiring unit 33, a function definition data editing unit 34, a function object generating unit 35, and a reassignment processing unit 36, and by making these function in order, a device driver 20 is updated. FIG. 9 is a diagram illustrating the concept of processing in each of the function definition data acquisition unit 33, the function definition data editing unit 34, the function object generation unit 35, and the reassignment processing unit 36. FIG. 9 exemplifies a processing concept when the three functional objects 27a, 27b, and 27c shown in FIG. 2 are rearranged into new functional objects 27d, 27e, and 27f.

  As shown in FIG. 9, first, the function definition data acquisition unit 33 acquires function definition data 51a, 51b, 51c corresponding to each of the three function objects 27a, 27b, 27c to be rearranged. The function definition data is original data from which a function object is generated. For example, setting items corresponding to individual functions installed in a printer of a specific model, a display mode of setting items, and a storage location of setting values related to each setting item Is described in script format. For example, in FIG. 9, the function definition data 51a is the original data of the function object 27a, the function definition data 51b is the original data of the function object 27b, and the function definition data 51c is the original data of the function object 27c. When the function definition data acquisition unit 33 designates that each of the three function objects 27a, 27b, and 27c incorporated in the device driver 20 is to be rearranged by the user, the three function objects 27a and 27b. , 27c corresponding to the function definition data 51a, 51b, 51c. Such function definition data 51a, 51b, 51c is stored in the storage device 7 in advance.

  The function definition data editing unit 34 displays a function definition data editing screen on the display unit 4 based on the function definition data 51 a, 51 b, 51 c acquired by the function definition data acquisition unit 33. Based on the editing operation by the user, the setting items corresponding to the individual functions installed in the printer of the specific model, the display mode of the setting items, the storage location of the setting values for each setting item, etc. are changed to create new function definition data. 51d, 51e, and 51f are generated. That is, the function definition data editing unit 34 rewrites the script format description in each function definition data 51a, 51b, 51c based on the customization operation by the user to generate new function definition data 51d, 51e, 51f. The new function definition data 51d, 51e, 51f generated in this way is stored in the storage device 7.

  Next, the function object generation unit 35 functions. The function object generation unit 35 generates new function objects 27d, 27e, and 27f based on the new function definition data 51d, 51e, and 51f generated by the customization operation by the user. That is, the function object generation unit 35 converts the function definition data 51d, 51e, 51f described in the script format into binary format data that can be incorporated into the common interface unit 25 of the driver common unit 21, thereby creating new data. Function objects 27d, 27e, and 27f are generated. These function objects 27d, 27e, and 27f include function information 28d, 28e, and 28f reflecting the user's customization operation and storage destination information 29d, 29e, and 29f. The function objects 27d, 27e, and 27f newly generated in this way are function objects having different versions from the existing function objects 27a, 27b, and 27c. However, since the newly generated function objects 27d, 27e, and 27f have the same functions as the existing function objects 27a, 27b, and 27c, the identification information of the newly generated function objects 27d, 27e, and 27f is This is the same as the identification information of the existing function objects 27a, 27b, and 27c.

  The reassignment processing unit 36 functions. The reassignment processing unit 36 selects the device driver 20 designated by the user as a change target, and performs a process of reassigning the functional object of the selected device driver 20 based on the reassignment setting operation by the user. For example, as shown in FIG. 9, three new function objects 27d, 27e, and 27f are generated by the function object generation unit 35, and these three function objects 27d, 27e, and 27f are already incorporated into the device driver 20 by the user. When it is specified that the three functional objects 27a, 27b, and 27c are to be recombined, the reassignment processing unit 36 replaces each of the three functional objects 27a, 27b, and 27c already incorporated in the device driver 20 with the common interface unit. The device driver 20 is updated by incorporating each of the three newly generated functional objects 27d, 27e, and 27f into the common interface unit 25. As a result, the configuration of the device driver 20 shown in FIG. 2 is updated to a state in which new functional objects 27d, 27e, and 27f are incorporated in the driver common unit 21 as shown in FIG.

  As described above, the function object changing unit 31 causes the function definition data acquisition unit 33, the function definition data editing unit 34, the function object generation unit 35, and the reassignment processing unit 36 to function sequentially, thereby enabling the device based on the user's customization operation. The driver 20 is updated. In the above, the case where an existing functional object is changed to a new functional object has been exemplified. However, the present invention is not limited to this, and the functional object changing unit 31 assigns a new functional object to the device driver 20. Customization to be added or customization to delete an existing function object incorporated in the device driver 20 can also be performed. Then, when the device driver 20 is updated by the functional object changing unit 31, the takeover processing unit 32 functions next.

  The takeover processing unit 32 includes a version comparison unit 37 and a data structure update unit 38. The version comparison unit 37 acquires the version information of each functional object 27d, 27e, 27f incorporated in the device driver 20 updated by the functional object changing unit 31, and is recorded in the functional object information 16 of the management information 10. The version information 16b is read, and it is determined whether or not there is a functional object whose version information has been changed before and after the device driver 20 is updated. As a result, when there is a functional object whose version information has been changed, the version comparison unit 37 causes the data structure update unit 38 to function.

  The data structure update unit 38 stores the storage destination information 29a, 29b, and 29c of the function objects 27a, 27b, and 27c incorporated in the device driver 20 before the device driver 20 is updated, and the device driver after the device driver 20 is updated. 20 is compared with the storage destination information 29d, 29e, 29f of each functional object 27d, 27e, 27f, and when the storage destination of the setting value is changed before and after the update of the device driver 20, the registry 11 and The storage state of the setting value in the DEVMODE structure 12 is updated. That is, the data structure update unit 38 reads the registry management information 18 and the DEVMODE structure management information 19 included in the management information 10, and the device driver 20 is updated from the registry management information 18 and the DEVMODE structure management information 19. The setting value of the storage destination specified in each of the previous function objects 27a, 27b, and 27c is acquired. Then, the data structure update unit 38 stores the setting value read from the management information 10 in the storage destination specified in each of the function objects 27d, 27e, and 27f after the device driver 20 is updated.

  For example, as shown in FIG. 3, the function object 27a before the update of the device driver 20 designates the registry 11 as a storage destination, and a new function object 27d recombined with the function object 27a by the update of the device driver 20 exists. When the DEVMODE structure 12 is specified as the storage destination, the data structure update unit 38 reads the setting value of the registry 11 specified by the function object 27a from the registry management information 18 of the management information 10, and sets the setting value. And stored in the designated address of the DEVMODE structure 12 designated by the new function object 27d.

  Further, for example, as shown in FIG. 3, the function object 27c before the update of the device driver 20 designates the DEVMODE structure 12 as the storage destination, and a new function recombined with the function object 27c by the update of the device driver 20 When the object 27f designates the registry 11 as the storage destination, the data structure update unit 38 reads the setting value of the DEVMODE structure 12 designated by the function object 27c from the DEVMODE structure management information 19 of the management information 10. The set value is stored in the designated address of the registry 11 designated by the new function object 27f.

  As described above, the data structure update unit 38 changes the setting value storage location from the registry 11 to the DEVMODE structure 12 due to the update of the device driver 20, or when the DEVMODE structure 12 changes to the registry 11. Based on the registry management information 18 or the DEVMODE structure management information 19 of the management information 10, the storage state of the setting value of the DEVMODE structure 12 or the registry 11 is updated. If the storage location of the setting value is not changed by updating the device driver 20, the update process by the data structure update unit 38 may not be performed. However, even when the registry 11 or the DEVMODE structure 12 specified as the storage destination does not change before and after the update of the device driver 20, the address for storing the setting value may change. Therefore, when the address for saving the setting value has changed before and after the update of the device driver 20, the data structure update unit 38 determines that the DEVMODE structure 12 is based on the registry management information 18 or the DEVMODE structure management information 19 of the management information 10. Alternatively, the storage state of the setting value of the registry 11 is updated.

  FIG. 11 is a diagram illustrating an example of the data structure of the registry 11 and the DEVMODE structure 12 that are rewritten by the data structure update unit 38. FIG. 11 illustrates a state where the data structure shown in FIG. 3 is rewritten. As described above, the functional object 27c before the update of the device driver 20 designates the DEVMODE structure 12 as the storage destination, and the new functional object 27f recombined with the functional object 27c by the update of the device driver 20 is the registry 11. Is specified as the storage destination, the data structure update unit 38 reads the setting value stored in the registry 11 from the management information 10, writes the setting value in the DEVMODE structure 12, and sets the DEVMODE structure 12 Update the value storage state. In addition, the functional object 27c before the update of the device driver 20 designates the DEVMODE structure 12 as the storage destination, and the new functional object 27f recombined with the functional object 27c by the update of the device driver 20 stores the registry 11 therein. Is specified, the data structure update unit 38 reads the setting value stored in the DEVMODE structure 12 from the management information 10, writes the setting value in the registry 11, and sets the storage state of the setting value in the registry 11 Update. Thereby, the setting value stored in the registry 11 is rewritten from the state shown in FIG. 3A to the state shown in FIG. Further, the setting value stored in the DEVMODE structure 12 is rewritten from the state shown in FIG. 3B to the state shown in FIG. As a result, the setting value before the update of the device driver 20 is stored in the storage destination of the setting value designated by each of the plurality of functional objects 27d, 27e, and 27f after the device driver 20 is updated. . Therefore, when the device driver 20 is activated after the device driver 20 is updated, the setting value of each setting item can be normally read from the storage destination designated by each of the plurality of functional objects 27d, 27e, and 27f. Thus, the print setting screen G1 after the customization operation by the user can be normally displayed.

  Next, the operation of the customization tool 30 configured as described above will be described. 12 and 13 are flowcharts illustrating an example of a processing procedure performed by the customization tool 30. FIG. This processing is a processing procedure performed by the function object changing unit 31 and the takeover processing unit 32 of the customization tool 30 functioning in order. When the customization tool 30 functions in the CPU 2, first, the function object changing unit 31 operates. The function object changing unit 31 reads and acquires the existing function definition data 51a, 51b, 51c stored in the storage device 7, for example, based on an instruction operation by the user (step S30). The function object changing unit 31 may acquire the function definition data 51a, 51b, 51c from an external server via the communication interface 6. When the function object changing unit 31 acquires the function definition data 51a, 51b, 51c designated by the user, the function object changing unit 31 displays the editing screen of the function definition data 51a, 51b, 51c on the display unit 4, and the editing operation by the user. Based on the above, the function definition data editing process is executed (step S31). Thereby, the function definition data 51a, 51b, 51c acquired in step S30 is modified based on the editing operation by the user. Such editing processing continues until the editing operation by the user is completed (step S32). When the editing operation by the user is completed (YES in step S32), the function object changing unit 31 stores the function definition data 51d, 51e, 51f newly generated by the modification based on the editing operation in the storage device 7 (step S31). S33), new function objects 27d, 27e, 27f are generated based on the function definition data 51d, 51e, 51f (step S34). At this time, the function object changing unit 31 updates the version of the newly generated function objects 27d, 27e, and 27f to the latest version. For example, the function object changing unit 31 adds the version to the function information 28d, 28e, and 28f of the function objects 27d, 27e, and 27f. Information is written (step S35). Functional objects 27d, 27e, and 27f to be newly incorporated into the device driver 20 are generated by the processing as described above.

  Subsequently, the functional object changing unit 31 selects the device driver 20 to be changed based on an instruction operation by the user (step S36). For example, when a plurality of device drivers 20 are installed in the information processing apparatus 1, one device driver 20 to be customized is selected in this step S36. When the function object changing unit 31 selects one device driver 20 to be customized, the function object changing unit 31 displays the current function object configuration in the device driver 20 on the display unit 4 and accepts the reconfiguration setting of the function object by the user ( Step S37). That is, a setting operation for recombining each of the existing functional objects 27a, 27b, and 27c with new functional objects 27d, 27e, and 27f is received. At this time, the user can also set deletion of an existing function object or addition of a new function object. When a setting operation is performed by the user, the functional object changing unit 31 executes a functional object recombination process (step S38) and updates the device driver 20 (step S39). As a result, the existing function objects 27a, 27b, and 27c incorporated in the device driver 20 are rearranged to new function objects 27d, 27e, and 27f, and the configuration of the function object in the device driver 20 is updated.

  Next, the takeover processing unit 32 operates in the customization tool 30 and executes data takeover processing (step S40). FIG. 13 is a flowchart showing an example of a detailed processing procedure of this data transfer processing (step S40). The takeover processing unit 32 reads the functional object information 16 from the management information 10 (step S50), and performs version comparison processing of each functional object before and after the update of the device driver 20 (step S51). By this version comparison process, it is possible to specify whether or not there is a functional object rearranged by updating the device driver 20. When the function object is rearranged, the setting value storage destination may be changed. Therefore, the handover processing unit 32 performs recombination when the version information related to the functional objects 27d, 27e, and 27f after recombination is different from the version information 16b related to the functional objects 27a, 27b, and 27c before recombination recorded in the management information 10. It is detected that there is a possibility that the storage destination specified in the subsequent functional objects 27d, 27e, and 27f has been changed. Then, the takeover processing unit 32 specifies the function objects 27a, 27b, and 27c separated from the device driver 20 by updating the device driver 20 (step S52), and the function objects 27d and 27d newly incorporated into the device driver 20 are included. It is determined whether or not the save destination of the setting value specified in 27e and 27f has been changed (step S53). As a result, when the setting value storage destination has not been changed (NO in step S53), the takeover processing unit 32 ends the process without particularly changing the setting value storage state of the registry 11 and the DEVMODE structure 12. To do.

  On the other hand, when the storage destination of the setting value is changed with the update of the device driver 20 (YES in step S53), the takeover processing unit 32 sets the settings related to the functional objects 27a, 27b, and 27c before the reorganization from the management information 10. A value is acquired (step S54). Then, the takeover processing unit 32 stores the setting value acquired from the management information 10 in the storage destination designated by the updated function objects 27d, 27e, and 27f of the device driver 20 (step S55).

  Thus, a series of processing by the customization tool 30 is completed. Then, by performing the above-described series of processing by the customization tool 30, the device driver 20 can be updated based on the user's customization operation, and the updated device driver 20 is saved in the registry 11 and the DEVMODE structure 12. It is possible to refer to the set value normally. For this reason, even when the device driver 20 is updated, the device driver 20 can be normally activated without reinstalling the device driver 20.

  On the other hand, when the device driver 20 is activated after being updated based on the customization operation, the device driver 20 causes the setting value management unit 22 to function, rewrites the version information 16b included in the functional object information 16 of the management information 10, and the registry 11 and By mirroring and rewriting the setting values stored in each of the DEVMODE structures 12 to each of the registry management information 18 and the DEVMODE structure management information 19, the management information 10 corresponds to the updated device driver 20. Update.

  Therefore, the user reinstalls the device driver 20 even when the user performs a customization operation for changing the storage destination of identification information such as an ID and password set for security printing from the DEVMODE structure 12 to the registry 11. In addition, since the updated device driver 20 can be activated promptly, the operability when customizing the device driver 20 is improved.

  As described above, the information processing apparatus 1 according to the present embodiment includes the device driver 20 and the customization tool 30 that customizes the device driver 20. The device driver 20 has a configuration in which a plurality of function objects 27a, 27b, and 27c provided for each function that can be set by the user are incorporated in the driver common unit 21, and the function objects 27a, 27b, and 27c have functions. The save destination for each setting value is specified. The customization tool 30 updates the device driver 20 by rearranging the functional objects 27a, 27b, and 27c incorporated in the device driver 20 based on the user's customization operation.

  The device driver 20 reads out and displays the setting values of each function from the storage destination specified in each of the plurality of function objects 27a, 27b, and 27c, and performs the setting operation based on the setting operation for each function by the user. The UI processing unit 23 that changes the setting value of the storage destination specified in the function objects 27a, 27b, and 27c corresponding to the performed function, and the storage that is specified by each of the plurality of function objects 27a, 27b, and 27c. A setting value management unit 22 that mirrors the previous setting value and manages it as management information 10 is provided. In addition, the customization tool 30 is a functional object changing unit that rearranges at least one of the functional objects 27a, 27b, and 27c incorporated in the device driver 20 into new functional objects 27d, 27e, and 27f based on a user's instruction operation. 31 and when the functional object changing unit 31 performs the rearrangement of the functional objects, when the storage destination of the set values designated in the rearranged functional objects 27d, 27e, and 27f is changed, the management information 10 A take-over processing unit that reads the setting value of the storage destination specified in the functional objects 27a, 27b, and 27c before the rearrangement and stores the setting value in the storage destination specified in the functional objects 27d, 27e, and 27f after the rearrangement. 32 and There.

  According to the information processing apparatus 1 having the above configuration, as the customization tool 30 updates the device driver 20 based on a user's instruction operation, the function objects 27d, 27e, and 27f newly incorporated in the device driver 20 are updated. The setting value before update is stored in the storage location specified in each. Therefore, even when the device driver 20 is updated, the device driver 20 can normally take over and refer to the setting value before the update, and can normally display the display screen such as the print setting screen G1. it can.

  When the information processing apparatus 1 includes a plurality of device drivers 20 provided for each device, the function object changing unit 31 can rearrange the function objects incorporated in each of the plurality of device drivers 20 and takes over. The processing unit 32 is a functional object before recombination from the management information 10 managed by the setting value management unit 22 of the device driver 20 in which the functional object is rearranged by the functional object changing unit 31 among the plurality of device drivers 20. The setting value of the storage destination specified in is read, and the setting value is stored in the storage destination specified in the rearranged functional object. According to such a configuration, even if any of the plurality of device drivers 20 is updated, the updated device driver 20 can normally take over and refer to the setting value before the update.

  As mentioned above, although one embodiment related to the present invention was described, the present invention is not limited to the contents described in the above embodiment, and various modifications can be applied.

  For example, in the above-described embodiment, the case where the device driver 20 is configured as a printer driver for the user to perform various print settings when the print job is output to the printer is illustrated. However, the device driver 20 is not limited to a printer driver. For example, when a facsimile apparatus is provided as an external device of the information processing apparatus 1, the device driver 20 may be a facsimile driver that outputs a job to the facsimile apparatus.

  In the above-described embodiment, the case where the device driver 9a and the customization program 9b are installed in the information processing apparatus 1 in advance has been described. Each of these programs, that is, the device driver 9a and the customization program 9b may be provided in a state recorded in a computer-readable recording medium such as a CD-ROM, or may be downloaded via a network. It may be provided by doing. Therefore, the installation on the information processing apparatus 1 may be performed by reading a recording medium, or may be performed by downloading via a network.

  In the above-described embodiment, the case where either the registry 11 or the DEVMODE structure 12 is specified as the setting value storage destination is illustrated. However, the save destination of the setting value is not necessarily limited to the registry 11 or the DEVMODE structure 12, and any storage means may be designated as the save destination.

1 Information processing device 9a Device driver (driver program)
9b Customized program 10 Management information 11 Registry 12 DEVMODE structure 20 Device driver 21 Driver common part 22 Setting value management part 23 UI processing part (user interface part)
24 drawing processing unit 27a, 27b, 27c functional object 27d, 27e, 27f functional object 30 customization tool 31 functional object change unit 32 takeover processing unit 33 function definition data acquisition unit 34 function definition data editing unit 35 function object generation unit 36 reclassification Processing unit 37 Version comparison unit 38 Data structure update unit

Claims (9)

A device driver that is provided for each function that can be set by the user and that includes a plurality of function objects that specify the storage destination of the setting value of each function;
A customization tool for customizing functional objects incorporated in the device driver;
With
The device driver is
In the function object corresponding to the function for which the setting operation is performed based on the setting operation for each function by the user, while reading the setting value of each function from the storage destination specified in each of the plurality of function objects A user interface part for changing the setting value of the specified storage destination;
A setting value management unit that mirrors the setting value of the storage destination designated by each of the plurality of functional objects and manages it as management information;
Have
The customization tool is
A functional object changing unit that rearranges at least one functional object incorporated in the device driver into a new functional object based on an instruction operation by a user;
When the storage destination specified in the functional object after the rearrangement is changed due to the rearrangement of the functional object by the functional object changing unit, the storage specified in the functional object before the rearrangement from the management information A take-over processing unit that reads the previous set value and saves the set value in the save destination specified in the functional object after the rearrangement;
An information processing apparatus comprising:   The said setting value management part updates the said management information, after a setting value is preserve | saved at the preservation | save destination designated in the functional object after recombination by the said inheritance process part. Information processing device. A plurality of the device drivers provided for each device;
The function object changing unit is capable of rearranging the function objects incorporated in each of the plurality of device drivers,
The takeover processing unit is a functional object before recombination from the management information managed by the setting value management unit of the device driver in which the functional object is recombined by the functional object changing unit among the plurality of device drivers. The information processing apparatus according to claim 1, wherein the setting value of the storage destination specified in step 1 is read out. The set value management unit records and manages information on each of the plurality of functional objects in the management information;
When the functional object changing unit performs the reassignment of the functional object, the takeover processing unit, when the information about the functional object after the rearrangement is different from the information about the functional object before the rearrangement recorded in the management information The information processing apparatus according to claim 1, wherein the information processing apparatus detects that the storage destination specified in the functional object after the rearrangement has been changed.   The set value management unit is information related to the functional object recorded in the management information when the functional object changing unit reassigns at least one functional object incorporated in the device driver to a new functional object. The information processing apparatus according to claim 4, wherein the information processing apparatus is updated. The function object changing unit
A function definition data acquisition unit that acquires existing function definition data corresponding to at least one function object incorporated in the device driver;
A function definition data editing unit for editing the function definition data acquired by the function definition data acquiring unit based on an instruction operation by a user;
A function object generation unit that generates a new function object based on the function definition data edited by the function definition data editing unit;
6. The information processing apparatus according to claim 1, further comprising:   The setting management unit updates the management information by mirroring the setting value of the storage destination every time the setting value of the storage destination specified in each functional object is changed by the user interface unit. The information processing apparatus according to any one of claims 1 to 6. A plurality of function objects provided for each function that can be set by the user are incorporated, a setting value storage destination for each function is designated in each function object, and an arbitrary function of the plurality of function objects A device driver that can be customized by rearranging objects.
In the function object corresponding to the function for which the setting operation is performed based on the setting operation for each function by the user, while reading the setting value of each function from the storage destination specified in each of the plurality of function objects A user interface part for changing the setting value of the designated storage destination, and
A setting value management unit that mirrors the setting value of the storage destination designated by each of the plurality of functional objects and manages it as management information;
Device driver characterized by functioning as A customization program for customizing a function object incorporated in a device driver installed in an information processing apparatus, the information processing apparatus comprising:
A function object changing unit that rearranges at least one function object incorporated in the device driver into a new function object based on an instruction operation by a user; and
The function before recombination from the management information managed in the device driver when the storage destination specified in the functional object after recombination is changed as the functional object is rearranged by the functional object changing unit A take-over processing unit that reads the setting value of the storage destination specified in the object and stores the setting value in the storage destination specified in the functional object after the rearrangement,
Customized program characterized by functioning as

Images