[Bug 885] - Screen Corruption in riven

[wine-bugs at winehq.com]

http://bugs.winehq.com/show_bug.cgi?id=885





------- Additional Comments From tony_lambregts at telusplanet.net  2002-07-24 18:42 -------
I've had several days to think about this one and I have come up with the
following conclusions

1. The problem is not with the source and destination drawables being the same.
This is pretty rock stable stuff that has been tested in X11 for years. Also
while  Debuging Bug 792 I noticed that when scrolling in the file dialog that
the source and destination were the same with no screen corruption. (I had put a
fixme in the code to detect this.) So it isn't this.

2. Timing is a factor because slowing down the execution of same drawables
clears up the problem somewhat.

3. If I move forward and then turn. at the begining of the trace there is this
fixme.

> fixme:bitblt:X11DRV_BitBlt potential optimization - client-side DIB copy

This does not occure if I am turning around in circles. What brought my
attention to this is that another program that has screen corruption (Bug 911)
displays this fixme a lot.

All that means is that I understand the problem a little better and have a hint
of where to look next I suppose. My burning question at this point is what does
the somewhat cryptic fixme really mean?


DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=885>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.