![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 66%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
I use DocumentProperties function to modify the DEVMODE structure，and the use SetPrinter function to update printer setting. The DEVMODE structure seems to be changed correctly, but the printer always prints the same way.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXY%3C/text%3E%3C/svg%3E)
DocumentProperties makes changes to print settings that are local to an application. while SetPrinter modifies the default DEVMODE structure for a printer (globally setting the printer defaults). You must first call the DocumentProperties function to validate the DEVMODE structure.
Check the question https://learn.microsoft.com/en-us/answers/questions/748446/controle-printer-setting-using-vb-net where @Castorix31 does it successfully.
Hi @Xiaopo Yang - MSFT, thank you for responding!I have called the DocumentProperties function before call the SetPrinter function. My code is as follows：
I checked the printer settings, and it seems to change correctly, but the printer parameters seem to have no effect, the printer always prints the same way.
Hello @dia l,
but the printer parameters seem to have no effect, the printer always prints the same way.
You can set and print from GUI to check if the printer supports these settings or try other printer settings. The APIs all work. You need to consult the printer manufacturer and we have no printers to follow up.
Thank you.
Hi @Xiaopo Yang - MSFT,
I have verified that the printer supports these settings, and I can successfully set parameters and print from GUI.
I send raw data to the printer by calling the following API,
ranther than send the GDI+ out to the printer (as shown in the following figure)
I want to know if this has any impact
According to CreateDC,
The pdm parameter must be NULL if the device driver is to use the default initialization (if any) specified by the user.
so, the code uses the default initialization (if any) specified by the user not the printer global setting or the setting local to an application.
You need to specify the DEVMODE in CreateDC as DocumentProperties says.
To make changes to print settings that are local to an application, an application should follow these steps:
- Get the number of bytes required for the full DEVMODE structure by calling DocumentProperties and specifying zero in the fMode parameter.
- Allocate memory for the full DEVMODE structure.
- Get the current printer settings by calling DocumentProperties. Pass a pointer to the DEVMODE structure allocated in Step 2 as the pDevModeOutput parameter and specify the DM_OUT_BUFFER value.
- Modify the appropriate members of the returned DEVMODE structure and indicate which members were changed by setting the corresponding bits in the dmFields member of the DEVMODE.
- Call DocumentProperties and pass the modified DEVMODE structure back as both the pDevModeInput and pDevModeOutput parameters and specify both the DM_IN_BUFFER and DM_OUT_BUFFER values (which are combined using the OR operator).The DEVMODE structure returned by the third call to DocumentProperties can be used as an argument in a call to the CreateDC function.
Hi @Xiaopo Yang - MSFT,
I'm sorry for my unclear description, and I would like to clarify my issue again.
I executed the printting operation by sending raw data to the printer, followed the steps below:
In this operation, I didn't need to call CreatDC function to get a device context for the printer. I want to know if I must follow the steps below to perform the printing operation and specify DEVMODE in CreateDC, then the print settings can take effect.
Hi @Xiaopo Yang - MSFT,
I’m sorry for my unclear description, I want to clarify my issue again.
I executed the printing operation by following the steps below:
In this operation, I didn't need to call CreatDC function to get a device context for the printer. I want to know if I must follow the steps below to perform the printing operation and specify DEVMODE in CreateDC, then the print settings can take effect.
@dia l, OpenPrinter also takes a DEVMODE structure in the third parameter pDefault. You can try to specify this firstly.