Re: video mirror driver by Lev
Lev
Fri May 28 12:19:47 CDT 2004
Dear Pierluigi,
In fact, there are several DDIs that you have to implement.
At least DrvBitBlt, DrvTextOut and DrvStrokePath.
Update regions from any DDIs you have are important.
Particularly for DrvBitBlt the update region is bounded by
prclTrg. More precisely it is defined by pco, if any.
IOCTL or ReadFile will not do because user-mode application
have no access to video FDO. It is exclusive and managed
solely by Windows graphics engine. There is DDI for custom
functions named DrvEscape (respective API call - ExtEscape).
Look at this. You can define any own control codes (except for
reserved ones with predefined semantics). Some IPC based on
shared memory also will do.
Actually, we have come a long way with video drivers and
already have a solution that exactly matches your problem.
If you want to discuss this topic in more details please feel free
to contact me.
--
Sincerely,
Lev Kazarkin
Mirror drivers. Consulting and custom development.
www.demoforge.com
> Hi,
> I need to modify the mirror driver to get a simple information: whatever
> is the application that modify the desktop i need to know what is the region
> that Windows draw and/or update (RECT).
> I'm sure that this information is in the struct SURFOBJ of DrvBitBlt and
> DrvCopyBits so hooking this call I can grab such information.
> The question is: how can I send this information to UserMode Application?
> Can I use a IOCTL or a ReadFile ?
> Thanks,
> Pierluigi M.