Hi Rob (and Lionel),
While debugging a game where there is the same problem, I did exactly
the same fix.
However, although this works, it is horribly slow. Do you have the same
issue?
Maybe this is the reason this was commented out.
I wonder if SYNC_UPDATE and OWN_WINDOW stuff has been written
Robert Shearman <[EMAIL PROTECTED]> writes:
> I'm pretty sure Windows NT doesn't allow you to have direct access to
> the video memory so surely Windows must be doing it like this too?
> How do you suggest to fix the problem?
Windows will certainly let you access the video memory, but since we
ca
On Wed, Jul 27, 2005 at 04:33:29PM +0100, Robert Shearman wrote:
> I'm pretty sure Windows NT doesn't allow you to have direct access to
> the video memory so surely Windows must be doing it like this too?
> How do you suggest to fix the problem?
The only way I could think of would be to lock the
Alexandre Julliard wrote:
Robert Shearman <[EMAIL PROTECTED]> writes:
Previously, using ddraw to write to a small area of the desktop (or
even none at all) would cause the screen to go black because the
contents of the screen wasn't copied to the surface before the surface
was copied back t
Robert Shearman <[EMAIL PROTECTED]> writes:
> Previously, using ddraw to write to a small area of the desktop (or
> even none at all) would cause the screen to go black because the
> contents of the screen wasn't copied to the surface before the surface
> was copied back to the screen. This patch
