JP6639570B2 - Application program - Google Patents

Description

  The present invention relates to an information processing method and a program for a touch panel print setting user interface (UI).

  A conventional printer driver has a conflict process that prevents a combination of unprintable settings from being set on the printer driver UI. This conflict processing on the printer driver UI is performed every time the user changes any one of the setting items, confirms whether the setting is possible, and if the setting is not possible, notifies the user to that effect. Is changed, and invalid settings are made unselectable, so that the user can grasp at a glance the items that cannot be set (see Patent Document 1).

  However, some printer drivers in recent years have only rules for performing conflict processing, and the OS (operating system) performs the conflict processing (see Non-Patent Document 1).

  In the conflict processing of the OS, there is a pattern for performing the conflict processing at two timings. First, every time a user changes a setting item, the printer driver UI calls a conflict process of the OS and confirms it. The other is that the OS calls the conflict processing collectively after all the print setting changes are completed and confirms them. However, each of the two conflict processes of the OS has a problem. When the driver UI calls and confirms the conflict processing of the OS every time the former user changes the setting item, the execution speed of the conflict processing of the OS is slow, and the usability is greatly reduced. The latter has a problem in that it is difficult for the user to recognize how the change has been made because the user performs the conflict processing collectively. To solve these problems, it is common for the printer driver UI to have its own prohibition rules and to apply conflict processing independently in accordance with the rules (see Non-Patent Document 2).

JP-A-2003-99170

http: // msdn. Microsoft. com / en-us / library / windows / hardware / ff562603 (v = vs.85). aspx http: // msdn. Microsoft. com / en-us / library / windows / hardware / jj218731 (v = vs.85). aspx

  However, according to the above-described method, it is necessary to maintain a rule for conflict processing performed by the OS and a rule for real-time conflict processing performed independently by the printer driver. There is a problem that the man-hour increases.

An application program according to the present invention is an application program for causing a computer having an operating system to execute a display control step and a setting change step, and provided in the display control step by a program different from the application program. When a predetermined user operation is received via the first print setting screen, and the printer driver corresponding to the output destination printer specified by the operating system is the first printer driver, 2 is displayed, and the predetermined user operation is received on the first print setting screen provided by a program different from the application program. When the specified printer driver is the second printer driver, control is performed so as to display a third print setting screen different from the second print setting screen, and in the setting change step, the second print setting screen is displayed. As the print setting is changed via the print setting screen or the third print setting screen, control is performed to change the print setting used when printing is performed using the specified printer driver, and the specified print setting is controlled. When the printer driver is the first printer driver, each time a print setting is changed via the second print setting screen, a processing step of performing prohibition processing for eliminating print setting values that cannot be combined is included. Further, the computer is caused to execute the print setting values which are not combined by the processing steps. The computer further causes the computer to execute a second display control step of displaying a pop-up screen indicating at least that the printing has been performed, and the first printer driver and the second printer driver determine whether It is characterized by being common to each other.

  According to the present invention, the original conflict processing and the OS conflict processing use the same rule, so that the rule for the OS conflict processing and the maintenance of the original conflict processing rule can be performed collectively. Man-hours can be reduced.

FIG. 1 is a configuration diagram of a network to which a client, a server, and a printer are connected according to an embodiment of the present invention. Configuration diagram of a system including a computer as one embodiment of the present invention Software block diagram as one embodiment of the present invention Printing flowchart as one embodiment of the present invention An example of a print setting screen displayed when printing from the store application of the print processing system according to the embodiment of the present invention An example of a detailed setting screen of a device application according to an embodiment of the present invention An example of a device application conflict pop-up screen as one embodiment of the present invention Flowchart of a process of calling a device application according to an embodiment of the present invention Flowchart of calling processing of a prohibition processing module as one embodiment of the present invention Flowchart of a process for skipping the prohibition process module (320) calling process (step S809) when a conflict process is performed on the UI An example of a non-conflict screen as one embodiment of the present invention Flowchart of printing when displaying a non-conflict screen as one embodiment of the present invention Flowchart for displaying a non-conflict screen as one embodiment of the present invention Flowchart of processing of a graphics filter as one embodiment of the present invention A flowchart for using a device application prohibition processing module from a graphics filter as an embodiment of the present invention Example of GPD file prohibition rule as one embodiment of the present invention Example of setting item information of paper size of GPD file as one embodiment of the present invention Example of setting item information for double-sided printing of GPD file as one embodiment of the present invention

  A computer as an embodiment of the information processing device according to the present invention will be described.

  FIG. 1 is a diagram illustrating an example of an apparatus configuration to which a printing system according to the present invention can be applied. The printing system includes a PC (10) and a printer (20). The PC (10) and the printer (20) are connected via the LAN (1). LAN (1) corresponds to the Ethernet communication system. The PC (10) and the printer (20) may be connected by other connection forms such as a wired LAN, a wireless LAN, BlueTooth (registered trademark), and USB. A computer as an embodiment of the information processing device according to the present invention will be described. FIG. 2 is a block diagram illustrating a configuration of a printer control system including the computer according to the present embodiment.

  The PC (10) is a host computer and includes a CPU (101) for executing various programs stored in a program ROM of a ROM (102) or an external memory (109). Further, each device connected to the system bus (120) is generally controlled by the CPU (101). The ROM (102) or the external memory (109) stores an OS or the like which is a control program of the CPU (101). In this embodiment, the OS is Windows (registered trademark), but another OS may be used.

  A RAM 103 functions as a main memory, a work area, and the like for the CPU (101). A keyboard I / F 104 controls a key input from a keyboard (105) or a pointing device (113) such as a mouse / touch panel. Reference numeral 106 denotes a display I / F, which controls display on a display (107).

  An external memory I / F 108 controls access to an external memory (109) such as a hard disk (HD) or a floppy (registered trademark) disk (FD). The external memory (109) stores various programs such as an application (10901), a device application (10902), a printer driver (10903), and an OS (10904) which occupy important positions in the present invention. In this embodiment, Microsoft Windows is assumed, but the present invention is not limited to this.

  A printer I / F 110 connects to a printer (111). A pointing device I / F 112 is connected to a pointing device (113) including a touch panel and the like. Unless otherwise specified, it goes without saying that the present invention can be applied regardless of the configuration of the device as long as the functions of the present invention are executed. It may be a single device, a system including a plurality of devices, or a system in which connections are made and processing is performed via a network such as a LAN or WAN.

  FIG. 3 is a block diagram showing an example of a software module to which the present invention is applied. The basic configuration of the block diagram includes an application (10901), a printing system (109041), a printer driver (10903), a system spooler (109042), and a device application (10902). These software modules are stored in the external memory (109), and are loaded from the external memory (109) to the RAM (103) in response to a user's request or a request from another system, and are loaded into the CPU (101). Be executed. The application (10901) here is a general application such as a word processor or a browser.

  A UI is displayed on the display (107), and a print request from the user is received by an input device such as a pointing device (113) or a keyboard (105). Upon receiving the user's print request, the application (10901) issues a print request to the print system (109041). The printing system (109041) is a subsystem of the OS (10904).

  It is located between the application (10901) and the printer driver (10903), and executes common processing in print processing. Specific execution processing includes selection of a printer to be printed, generation of PrintTicket (311) and PrintCapabilities (310) of the selected printer driver (10903), conflict processing of PrintTicket (311), and XPS (XML Paper Specification) file. Is converted into Page Description Language (PDL). PrintCapabilities (310) is data of a list of items that can be executed by the printer (20), including the paper size.

  On the other hand, PrintTicket (311) is print setting information used at the time of printing, and is used at the time of printing and conflict processing. PrintCapabilities (310) and PrintTicket (311) are requested to be generated from the application (10901) to the printer driver (10903) via the printing system (109041).

  The printer driver (10903) requested to generate the PrintCapabilities (310) and the PrintTicket (311) generates them and passes them to the application (10901) via the printing system (109041), so that the application (10901) is selected. Printer driver (10903) related information can be used.

  The XPS file (312) is data to be printed passed from the application (10901), and information of the PrintTicket (311) is added by the application (10901). The printer (20) can perform printing by being passed from the application (10901) to the printer driver (10903) via the printing system (109041) and converting it into the PDL (314).

  Note that PrintCapabilities (310), PrintTicket (311), and XPS file (312) are each described in a markup language.

  The printer driver (10903) is a module that performs processing depending on the printer (20) that is the print output destination, and is roughly composed of two blocks.

  One is a print setting block (109030) that creates print setting-related information, and performs conflict processing of PrintTicket (311) and creation of PrintCapabilities (310). The print setting block (109030) includes a prohibition processing module (320), a GPD file (321), and Constraint Javascript (322). The prohibition processing module (320) is responsible for conflict processing of the PrintTicket (311) and creation of the PrintCapabilities (310). The GPD file (321) is data in which prohibition rules, items that can be set at the time of printing, and the like are described. The GPD file (321) will be described later in detail with reference to FIG. Constraint Javascript (322) is called in order to reflect settings and prohibition rules that cannot be described in the GPD file (321) in PrintTicket (311) and PrintCapabilities (310). However, in consideration of security, the module is written in the JavaScript language, which is an interprinter language. Unlike a native language, the module is not optimized in advance, so it takes a very long time to execute. When performing the conflict processing, the prohibition processing module (320) receives the PrintTicket (311) from the caller, and then reads information on the prohibition rules described in the GPD file (321). The prohibition processing module (320) performs the conflict processing of the PrintTicket (311) based on the information of the GPD file, then calls Constraint Javascript, and adapts the prohibition rules that cannot be described in the GPD file to the PrintTicket (311). A conflict process is performed by a series of these processes.

  Next, the graphics filter (10931) of another block constituting the printer driver (10903) will be described. The graphics filter (10931) is a part that converts the XPS file (312) into the PDL (314). The information of the PrintTicket (311) added to the XPS file (312) is extracted, and the PrintTicket (311) is generated from the information. The graphics filter (109031) converts the XPS file (312) into a PDL (314) based on the PrintTicket (311). Next, the device application (10902) will be described. The device application (10902) is an auxiliary application for the printer driver (10903). Similarly to the printer driver (10903), PrintCapabilities (310) and PrintTicket (311) can be interpreted by software corresponding to the printer (20). The device application (10902) includes a detailed setting screen, device metadata (330), and a prohibition processing module (307). The device metadata (330) associates the printer driver (10903) with the device application (10902). A printer driver (10903) that can be assisted by the device application (10902) is described. The device application (10902) assists the printer driver (10903) described in the device metadata (330) with the device. This can be performed by the application (10902).

  The device application (10902) can assist a plurality of types of printer drivers (10903).

  The prohibition processing module (307) is a module that can perform the same processing as the prohibition processing module (320) in the printer driver (10903). Here, the same applies to the case where the PrintTicket (311) and the GPD file are input and the PrintTicket (311) subjected to the conflict processing is output, and the prohibition processing module (307) of the printer driver (10903) and the device are output. The prohibition processing module (320) in the application (10902) means outputting the same output from the same input. The prohibition processing module (307) is passed the PrintTicket (311) from the caller, then reads the prohibition rules in the GPD file (315) in the driver property bag (331), and prints the PrintTicket (311) based on the information. ), And outputs a PrintTicket (311) as an output.

  The GPD file (315) is placed in the driver property bag (331) at the time of installation, and has the same contents as the GPD file (321). This is because the device application (10902) cannot access the GPD file (321) and thus places the GPD file (315) in an accessible location and uses it as an input during conflict processing. The driver property bag (331) is a storage area in which data to be defined before installation can be stored, and can be accessed from the printer driver (10903) or the device application (10902).

  Next, the GPD file (321) in the print setting block (109030) and the GPD file (315) in the driver property bag will be described with reference to FIGS. 16 (a), 16 (b) and 16 (c). . The GPD file is composed of data on choices of selection items such as an inappropriate combination of conflict processing and paper size.

  Reference numeral 1700 denotes an example of a combination for performing a conflict process. The conflict processing prohibition rule describes an invalid combination of settings. In this figure, the combination of the paper size “postcard” and the two-sided printing “long side both sides” is a combination of the MediaType. PostCard, DUPLEX. Expressed in VERTICAL. Reference numeral 1701 denotes that the setting of the paper size selection item is described, and similarly, reference numeral 1702 denotes that the setting of double-sided printing is described. Reference numeral 1703 denotes an option of a setting item, and is an example in which detailed data of “postcard” of the paper size is described in FIG. Reference numeral 1704 denotes the priority of the paper size prohibition process, and indicates that a setting item having a lower value has a higher priority. For example, in this drawing, the priority of the paper size is 1 in the prohibition processing, and 1705 indicates that the priority of the duplex printing is 15. Therefore, when the conflict processing of 1700 is performed, the setting of double-sided printing is changed without changing the postcard, which is the paper size.

  Here, the outline of the printing process will be described with reference to the flowchart of FIG. This processing starts when the application (10901) issues a print request to the printing system (109041) in response to a print request from the user. In step S401, the printing system (109041) displays a UI (not shown) showing a list of printable printers (20) on the display (107) based on information of the currently installed printer driver (10903). . In step S402, in response to the user's selection of the output printer (20) on the UI showing the list of printers (20), the printing system (109041) transfers the corresponding printer driver (10903) from the external memory (108) to the RAM (108). 103), which is executed by the CPU (101). In step S403, a request is made to the printer driver (10903) to generate PrintCapabilities (310) and PrintTicket (311) via the printing system (109041). The prohibition processing module (320) of the print setting block (109030) reads out the GPD file (321) and generates PrintCapabilities (310) and PrintTicket (311). Based on the generated PrintCapabilities (310) and PrintTicket (311), the printing system (109041) configures the print setting screen (501) in FIG. 5 and displays it on the display (107).

  Next, in step S404, an operation from the user on the print setting screen (501) is accepted. In step S405, the printing system (109041) determines whether the "More Settings" link (502) on the print setting screen (501) has been pressed. If it is determined that the “More Settings” link (502) has been pressed, in step S406, the printing system (109041) calls the device application (10902). The processing in step S406 at this time will be described later. If it is determined that the “More Settings” link (502) has not been pressed, the process advances to step S407.

  In step S407, the printing system (109041) transfers the current PrintTicket (311) to the printer driver (10903) in response to the pressing of the return button (503) on the print setting screen (501). In step S408, the prohibition processing module (320) is called to check whether the print settings are valid. This is an important part of this embodiment, and will be described later in detail. In step S409, it is determined whether all the setting values are valid based on the verification result. If the setting values are valid, the print setting screen (501) is closed, and the process proceeds to step S410. If all the settings are not valid, the process moves to step S404, and the operation of the user is accepted. In step S410, the printing system (109041) adds the valid PrintTicket (311) of the current setting to the XPS file (312), and outputs the XPS file (312) to the graphics filter (109031) in step S411. I do. The data is converted into the PDL (314) by the graphics filter (109031). Step S411 is a process of calling the graphics filter (109031). Details will be described later with reference to FIG. In step S411, it is delivered to the system spooler (109042), which is a subsystem of the OS (10904), and transmitted to the printer (20). The printing process is executed by performing the above processes.

  Next, the processing of the graphics filter (109031) will be described with reference to FIG. In step S1501, the graphics filter (109031) analyzes the received XPS file (312) and extracts the PrintTicket (311). In step S1502, the prohibition processing module (320) is called, and the generated PrintTicket (311) is subjected to conflict processing. The process moves to step S1503. In step S1503, a PDL (314) is generated from the XPS file (312), and the process ends. Next, the detailed setting screen (600) will be described with reference to FIG. The detailed setting screen (600) is a print setting screen for performing settings that cannot be set on the print setting screen (501). This screen is displayed when the “More Settings” link (502) in FIG. 5 is pressed. A return button 601 shown in the figure transits to a print setting screen (501) and a print setting screen (501) when the user taps the button. Reference numeral 602 denotes a paper size control box for setting the paper size in the print settings. A list of paper sizes is displayed when the user taps, and the paper size is controlled by releasing the tapping finger at the paper size to be selected. The size can be changed.

  In this drawing, “postcard” is set as the paper size. Reference numeral 603 denotes a single-sided double-sided selection control box for performing a single-sided or double-sided print setting. When the user taps, a list of one-sided, short-sided, and long-sided is displayed. , The print settings can be changed. In this drawing, “one side” is selected.

  The calling process of the device application (10902) will be described with reference to the flowchart in FIG. Unless otherwise specified, the main part of the flowchart of this embodiment is the device application (10902). In step S801, a PrintTicket (311) including the paper size is acquired from the printer driver (10903) via the printing system (109041). In step S802, a detailed setting screen (600) is displayed based on the acquired PrintTicket (311).

  In step S803, an operation from the user is accepted. If a return button (601) event has occurred by the user, the process proceeds from the determination processing of the return button (601) event in step S804 to step S810. If no print setting has been changed by the user operation, the process proceeds from the print setting change determination processing of the detailed setting screen (600) in step S805 to step S803, and the user operation is accepted again. If the print setting item on the detailed setting screen (600) has been changed in step S805, the process advances to step S806 to change the setting value of the PrintTicket (311) referred to by the UI. After that, the processing makes a transition to Step S807, and calls the prohibition processing module (307). Since this content occupies an important position in the present embodiment, it will be described later.

  In step S808, it is confirmed whether or not the setting value of PrintTicket (311) has been changed by the conflict process. If a conflict process has been performed, the process moves to step S809 to notify the user at the time of a conflict. The conflict notification will be described later. Step S810 is performed when the return button (601) is tapped, and before the screen transitions to the print setting screen (501), the processing is passed to the printing system (109041), and the printing system (109041) is controlled by the prohibition processing module (109041). 320) Perform a calling process and perform a conflict process on the PrintTicket (311). Thus, when returning to the print setting screen (501), the setting value of the PrintTicket (311) is a printable setting.

  Next, means for notifying the user at the time of a conflict will be described with reference to FIG. The illustrated reference numeral 700 is a conflict pop-up screen. When the device application (10902) has performed the conflict processing, it is displayed to notify the user that the conflict has been performed. Next, a specific example will be described. When "Postcard" is set in the paper size control box (602) while "Single-sided long side" is set in the single-sided double-sided selection control box (603), the single-sided double-sided selection control box (603) is set to "Duplex long side". Is changed to “single-sided”. This depends on the priority described in the GPD file, as described above. At this time, the user is notified by displaying that the conflict process has been performed on the conflict popup (700) and which setting is the conflict. Although the present embodiment is described using a pop-up, other notification means may be used. The same processing is performed when the setting value of another PrintTicket (311) is changed by the conflict processing.

  Next, a process of calling the prohibition processing module (307) will be described with reference to FIG. In step S1000, the prohibition processing module (307) receives the PrintTicket (311) from the caller. In step S1001, the prohibition processing module (307) reads the GPD file (315) of the driver property bag and grasps the prohibition rules. In step S1002, it is determined whether the PrintTicket (311) is valid. If it is invalid, the process proceeds to step S1003, and a conflict process is performed. In step S1004, the prohibition processing module (307) passes the PrintTicket (311) subjected to the conflict processing to the caller. As described above, since the prohibition processing module (307) uses a file having the same contents as the GPD file (321) and does not call the interpreter language, the conflict processing module (307) can perform conflict processing at high speed while maintaining maintainability.

  In the first embodiment, the maintainability of applying a real-time conflict on the UI is referred to. However, when a real-time conflict is applied on the UI, the prohibition processing module calling process in step S810 in FIG. In addition, since the prohibition processing module (320) using the interpreted language is used, there is a problem that the processing is slow. However, if the processing in step S810 is not performed, a PrintTicket (311) that does not perform any conflict processing will be generated when the user does not change the print settings on the detailed setting screen (600). This cannot guarantee that PrintTicket (311) is a valid setting value.

  Therefore, in the second embodiment, when the conflict processing is performed on the UI, the calling processing (step S809) of the prohibition processing module (320) is skipped, and when the conflict processing is not performed on the UI, the return button is pressed. (601) A method of calling the prohibition processing module (307) when an event occurs will be described with reference to FIG. Unless otherwise specified, the main part of the flowchart of this embodiment is the device application (10902). Steps S1101 to S1106 are the same as steps S801 to S806, and a description thereof will be omitted.

  In step S1107, if the user has changed the PrintTicket (311) even once, a Changed flag indicating that the change has been made is set. The Changed flag is a flag held in the device application (10902). Steps S1108 to S1110 are the same as steps S807 to S809, and a description thereof will be omitted.

  In step S1109, it is determined whether the user has changed PrintTicket (311) even once. If the Changed flag is not set, the process proceeds to step S1110, and the prohibition processing module (307) performs a conflict process. As a result, the conflict processing can be always performed without using the prohibition processing module (320) using the interpreter language, and the conflict processing is not performed. Therefore, the entire call processing of the device application (10902) is performed. Thus, the speed of the conflict process can be increased.

  In the second embodiment, a method has been described in which when the conflict processing is performed on the UI, the prohibition processing module calling processing (S810) can be skipped. Exists. For example, some printer drivers (10903) supported by the device application (10902) do not hold the GPD file (315) in the driver property bag (331). In that case, the conflict processing on the UI as in the first embodiment cannot be performed.

  In this embodiment, a means for displaying a UI that does not need to be subjected to a conflict process on the UI to the printer driver (10903) that does not hold the GPD file (315) will be described. FIG. 11 illustrates a non-conflict screen. A non-conflict screen 1200 is displayed when the GPD file (315) does not exist. Reference numeral 1201 denotes a return button, which, like the return button (601) on the detailed setting screen (600), activates an event to be changed to the print setting screen (501) when the user taps the print setting screen (501). Transitions to. Reference numeral 1202 denotes a paper size control box for setting the size of paper used for printing in the same manner as the paper size control box (602), and the user can change the paper size by tapping. 12 and 13 are flowcharts for displaying the non-conflict screen (1200). Unless otherwise specified, the subject in FIGS. 12 and 13 is the device application (10902).

  In step S1301, it is checked whether the GPD file (315) exists in the driver property bag (331). If it exists, it means that the prohibition processing module (307) can be called. Therefore, the processing transits to step S1303 to perform processing for displaying the detailed setting screen (600). Steps S1303 to S1314 are the same as steps S1101 to S1112, and a description thereof will be omitted. If the GPD file (315) does not exist, it means that the prohibition processing module (307) cannot be called, so the flow shifts to step S1302 to perform a processing flow for displaying a non-conflict screen.

  Next, a processing flow for displaying a non-conflict screen will be described with reference to FIG. A step S1401 acquires the PrintTicket (311). In step S1402, the setting value of the PrintTicket (311) is reflected on the non-conflict screen (1200) and display is performed. In step S1403, a user operation is accepted.

  In step S1404, occurrence of a return button (1201) event is confirmed. If the user transits to step S1404 without tapping the return button and changes the print setting of the non-conflict screen (1200), the print ticket (311) is changed in step S1405, and the conflict setting is changed in step S1402. The PrintTicket (311) is displayed on the non-conflict screen (1200) without confirmation. If the print settings have not been changed, the process moves to step S1403, and the user operation is accepted again. In step S1404, when the return button (1201) is pressed, a return button event occurs. At this time, as in step S1407, the OS (10904) performs a conflict process on the non-conflict screen (1200), and sets the PrintTicket (311) to a printable setting. After that, the screen transits to the print setting screen (501). Accordingly, the fastest and most accurate conflict processing can be performed in a situation where the GPD file (315) exists and in a situation where it does not exist.

  In the first embodiment, the conflict performance on the UI has been described, but the same processing can be performed by the graphics filter (109031). Fourth Embodiment In a fourth embodiment, a unit that uses the prohibition processing module (307) of the device application (10902) from the graphics filter (109031) will be described with reference to FIG. Unless otherwise specified, the main part of the flowchart of this embodiment is the graphics filter (109031).

  In step S1601, the graphics filter (109031) analyzes the XPS file (312) and takes out the PrintTicket (311). In step S1602, the graphics filter (109031) checks whether the GPD file (315) exists. If the GPD file (315) exists, the process transits to step S1603, and calls the prohibition processing module (307) of the device application (10902). If the GPD file (315) does not exist, the process transits to step S1604 to call the prohibition processing module (320) of the printer driver (10903). Thereafter, the graphics filter (109031) generates a PDL (314) from the XPS file (312). Thus, the graphics filter (109031) can call the prohibition processing module (307) and perform the conflict processing at high speed in the situation where the GPD file (315) exists.

  1 LAN, 10 PC, 20 printer

Claims (5)

A computer having an operating system, a display control step and a setting change step, an application program for executing,
In the display control step, when a predetermined user operation is received via a first print setting screen provided by a program different from the application program, the display control step is performed by the output destination printer specified by the operating system. Displaying a second print setting screen when the corresponding printer driver is the first printer driver;
In the case where the predetermined user operation is received on the first print setting screen provided by a program different from the application program, the printer driver specified by the operating system is a second printer driver In such a case, controlling to display a third print setting screen different from the second print setting screen,
In the setting change step, a print setting used when printing is performed using the specified printer driver in accordance with a change in the print setting via the second print setting screen or the third print setting screen. and control to change the,
When the specified printer driver is the first printer driver, every time a print setting is changed via the second print setting screen, a prohibition process for eliminating print setting values that cannot be combined is performed. Causing the computer to further execute processing steps;
The computer further executes a second display control step of displaying a pop-up screen at least indicating that the prohibition elimination processing has been performed, in accordance with the removal of the print setting values that cannot be combined by the processing step,
Wherein the first printer driver and the second printer driver application program characterized Rukoto printer output destination of the print data is not common to each other.   2. The application program according to claim 1, wherein print setting items that can be set are different between the second print setting screen and the third print setting screen.   The application program according to claim 1, wherein the predetermined user operation is a user operation of selecting a display item for performing detailed print settings displayed on the first print setting screen. .   4. The application program according to claim 1, wherein a screen layout of the second print setting screen is different from a screen layout of the third print setting screen. 5.   The first printer driver is a printer driver in which a file in which a prohibition rule is described exists in a storage area, and the second printer driver is a printer driver in which the file in which the prohibition rule is described does not exist in the storage area. The application program according to any one of claims 1 to 4, wherein