[1/5] WineD3D: Initialize surfaces at creation

[Stefan Dösinger]

This patch can theoretically lead to higher memory usage, but only if apps 
create loads of surfaces in the default pool without ever using them(which 
allows surfaces up to the amount of emulated vidmem). Normally there will be 
no differences because the memory will be allocated on the first use of the 
surface. Allocating and initializing at creation time is much simpler than 
checking for this in LockRect and LoadTexture.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-WineD3D-Initialize-surfaces-at-creation.patch
Type: text/x-diff
Size: 1463 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20070709/4f578636/0001-WineD3D-Initialize-surfaces-at-creation.bin