The user would select my print driver from the application's Print Dialog
box. On my print property page(s) the user would indicate the parameters for
the overlay AND, still within my property pages, select from a nested Print
Dialog the actual printer to receive the finished pages.
Then when the application goes through its normal printing sequence, my
driver would get control. My driver would pass through most actions to the
'actual printer driver' and act only on end of page actions. At end of page
actions, my driver would create an overlay on top of the page formatted by
the 'actual printer driver' and then call the end of page action of the
'actual printer driver'.
I have been looking through the Windows DDK printer examples and see that
routines exist in the UniDriver user interface and rendering functions to
allow customized logic.
I am interested to see from the newsgroup if there is opinion that what I
seek to do is doable OR not doable. If doable is there an available
example. My current problems in continuing my investigation are: (1)how to
pass the PRINTDLG info of the 'actual printer driver' (inside my print
property page) out to the user's application Print Dialog box return; (2)
how to access the device context written to by the user's application in my
driver's rendering routine.
Thanks for any guidance you may be able to provide.
Ed