Prev: IoGetDmaAdapter() fails with Win2003 Server with 4GB RAM
Next: Link Data User-Mode <--> Kernel-Mode. Please Help !
From: Alan Stewart on 20 Oct 2009 14:11 Hello, We actually have functioning rendering plug-in to the Microsoft PS printer driver, but I need to improve it. I'm using DDK version 3790.1830. Our code is based on the oemps sample. Our current plug-in simply recognizes some custom escapes and inserts custom Postscript into the output stream. However, we're unhappy with the way the Microsoft driver handles GDI+ transparency. GDI+ objects drawn with colors that have alpha values are being rasterized. We have a better way of handling such graphics and would like to eliminate the rasterization. In an effort to understand what is happening and what I can do about it, I've been examining logged calls to all the OEM*() functions. I'm surprised to find that calls are not being made that I would expect. For example, OEMStrokePath() does not get called every time a path is stroked. When the GDI+ rasterization of transparent objects occurs no calls to any of the OEM*Blt() functions are made. What do I need to do to intercept drawing when transparent colors are being used? Any insight, advice or help would be greatly appreciated. Alan -- Alan Stewart TerraGo Technologies |