How to implement DrvCopyBits for mirror driver?
in [Device Drivers]
|
Prev: USB Flash memory Drive.
Next: DTM "INF Syntax Test" and INFGate.exe... how does '/N' command line switch work?
From: Gen700 on 1 Apr 2007 20:30 How to implement DrvCopyBits for mirror driver? I am trying to create a mirror driver by referring MicroSoft DDK. I found out that when I create Device-Managed surfaces, I have to implement DrvCopyBits, DrvTextOut, DrvStrokePath. But in the DDK sample, these methods only return FALSE. I modified the mirror driver sample application (WINDDK\3790.1830\src\video\displays\mirror\app) of DDK so that it can save Bitmap. It successfully rendered. Don't I need to implement the content of these methods? Returning FALSE is enough to render ? If so, why?? I don't understand the difference between returning FALSE and returning TRUE. Could you please help me! Thank you.
From: Tim Roberts on 4 Apr 2007 01:13 Gen700 <Gen700(a)discussions.microsoft.com> wrote: >How to implement DrvCopyBits for mirror driver? > >I am trying to create a mirror driver by referring MicroSoft DDK. >I found out that when I create Device-Managed surfaces, >I have to implement DrvCopyBits, DrvTextOut, DrvStrokePath. >But in the DDK sample, these methods only return FALSE. > >I modified the mirror driver sample application >(WINDDK\3790.1830\src\video\displays\mirror\app) of DDK >so that it can save Bitmap. >It successfully rendered. > >Don't I need to implement the content of these methods? >Returning FALSE is enough to render ? >If so, why?? >I don't understand the difference between >returning FALSE and returning TRUE. > >Could you please help me! I answered your question last week. Did you read it? -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
From: Gen700 on 6 Apr 2007 05:10 Hi, Tim. Thank you for you reply !!!!!! > That's because the mirror driver sample doesn't use a device-managed > surface. It uses a GDI-managed surface, so GDI can do basically all of the > drawing. In my DDK sample driver, the surface is created by using EngCreateDeviceSurface in DrvEnableSurface. Isn't this the method to create device-managed surface? > Not unless there are things you can do better than GDI's code. Now, I create the engine-managed surface by EngCreateBitmap. I call EngAssociateSurface for that I need to hook DrvCopyBits. How can I implement to leave everything up to GDI in DrvCopyBits? I found some samples and they return TRUE or return FALSE or return EngCopyBits..etc. I tried them and they worked. Do you mind to explain the difference between them? Thank you. Gen700
From: Gen700 on 6 Apr 2007 05:16 Hi, Tim. Thank you for you reply !!!!!! I replied to forrow URL . Please Check this. http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?&guid=&sloc=en-us&dg=microsoft.public.development.device.drivers&p=1&tid=bb6f0d49-9966-4862-becd-1e9072c590f3
From: Gen700 on 6 Apr 2007 05:16
Hi, Tim. Thank you for you reply !!!!!! I replied to this URL. Please Check it. http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?&guid=&sloc=en-us&dg=microsoft.public.development.device.drivers&p=1&tid=bb6f0d49-9966-4862-becd-1e9072c590f3 |