Re: ddex3 and CETK for direcdraw fails while allocating surface.

On May 30, 7:14 pm, Sheetal <Shee...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Ajay,

It fails because ddex3 tries to use more surfaces. When you create the
Node2D object for your driver, you need to make provision for the offscreen
surfaces too, if you are planning for DirectDraw support. Look in the samples
given.

Moreover, they say you should prefer using SurfaceHeap over Node2D -
wherever possible. Have a look at that too.

Regards,
-Sheetal.



"Ajay" wrote:
Hi,

 I can run ddex1, ddex2 successfully but ddex3 does not execute.
I am using NODE2D class for managing surfaces.
I allocated buffer for 1080 *1920 images this is 32bpp.
When ddi.dll executes it uses this buffer and I can see the desktop.
When ddex3 executes it again try to allocate buffer from NODE2D class
for GPE_REQUIRE_VIDEO_MEMORY.
This memory already use by desktop so without calling free it again
try to allocate  , hence it does not work.
I run CETK too for directdraw but these test cases also fail.
Can anyone let me know how to resolve this issue?
Timely help would be appreciated.

Thanks & Regards
Ajay- Hide quoted text -

- Show quoted text -

Hi ***,
Thanks for reply ,
ddex3 ask memory allocation from onscreen surface , not from
offscreen .in my implementation there are seprate buffer for offscreen
and onscreen surfaces.
at this time of execution yes memory is availabe in offscreen pool but
not in onscreen pool , and it ask memory from onscreen.
this is the issue i m facing .

Regards
Ajay
.