[Bug 1347] Screen is wiped/blanked on usage of DirectDraw (black screen/desktop)

http://bugs.winehq.org/show_bug.cgi?id=1347

Avery Lee  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #42 from Avery Lee   2009-01-06 04:11:20 ---
Hi, I'm the author of VirtualDub.

The particular case that I'm concerned about is the case of using DirectDraw to
 blit from an off-screen surface to a subrect of the primary. That's a case
that's supported on both XP and Vista, and IMO should be supported properly by
Wine, because it's the fastest widely-compatible way to get images onto the
screen. This used to blank the entire screen just like the lock-entire-primary
case. Current alpha versions of Wine do appear to behave much better in this
regard and don't blank the entire screen anymore in that case, although there
still appear to be issues with clipping and stretching.

In the more general case, I'd say that blanking the screen is a very serious
bug, because it has a good chance of making the application unusable as well as
making other applications unusable as well. If the readback hack is not
acceptable and no other correct ways of emulating a primary surface lock are
available, then I'd suggest at least implementing a default that limits the
damage, such as limiting the synchronization blits to the client areas of the
windows owned by the current thread.