So far I’ve found two different ways to access what I believe are equivalent versions of the Printer DevMode from a wxPython User Interface:
window = wx.GetTopLevelWindows()[0].GetHandle()
name = self.itemMap['device'].GetValue() # returns a valid printer name.
handle = win32print.OpenPrinter(name)
dmin = None
dmout = pywintypes.DEVMODEType()
mode = DM_IN_BUFFER | DM_OUT_BUFFER | DM_IN_PROMPT
res = win32print.DocumentProperties(window, handle, name, dmout, dmin, mode)
if res == 1:
print dmout.DriverData
and also
dlg = wx.PrintDialog(self, dgData)
res = dlg.ShowModal()
if res == wx.ID_OK:
print dlg.GetPrintDialogData().PrintData.GetPrivData()
These to binary structures appear to contain the necessary information to control the device output behavior. This is fine and well, except that it can’t be directly used to reload the PrintSetup dialogs with this stored devmode data. In the first case the PyDEVMODE object contains dozens of individual properties that need to be manually set (PyDEVMODE Reference). In the second case there are a handful of Getter / Setter methods that control some of the properties, but not all of them (wxPrintData Reference). Is anyone aware of a way to create a Python Devmode Object (I’ll take either approach, the differences are trivial) from the actual DevMode (the binary data)? I’d like to avoid having to manually store / reset each individual attribute in order for the dialogs to re-open in the correct state every time.
It appears that at this point there’s no elegant way to achieve this directly in Python. The closest I was able to come up with was a dll written in c++ that I’m able to call into. I end up with the full binary DevMode Structure, and can reload from it. The code for that c++ dll looks like this:
In Python, it’s called into like so: