Out of curiosity, why hasn't Oliver's swapchains and stateblocks patch been merged? I saw that in wine-patches about 10 days ago, but it hasn't been merged, and there's no comments at all.
=====
On an unrelated note, what is causing this bug:
http://bugs.winehq.org/show_bug.cgi?id=2082
As I understand, this is a regression, since Diablo used to work a long time ago, and then some patch broke it. The bug was opened sometime in March...
On 5/16/05, Ivan Gyurdiev ivg2@cornell.edu wrote:
Out of curiosity, why hasn't Oliver's swapchains and stateblocks patch been merged? I saw that in wine-patches about 10 days ago, but it hasn't been merged, and there's no comments at all.
I could not get the 4 patches to work.
=====
On an unrelated note, what is causing this bug:
http://bugs.winehq.org/show_bug.cgi?id=2082
As I understand, this is a regression, since Diablo used to work a long time ago, and then some patch broke it. The bug was opened sometime in March...
Yes, that broke long ago. I wonder if there is any relation to another game I have with a black screen with circa '97 ddraw.
* On Mon, 16 May 2005, Ivan Gyurdiev wrote:
On an unrelated note, what is causing this bug:
IMHO this is related to heavy usage of window messaging and directdraw stuff mixed in this game.
And I at least can easily see some corrupted bitmap at the start of each new user screen (while out of game). When mouse is moved over the logo bitmap, the bitmap gets redrawn OK.
With one WM rewrite patch [1] the case got worse. Now the main screen isn't redrawable anymore (but user still can navigate through graphic buttons blindly).
There are at least ~3 alive bugs left and crossed under one game here, I guess. IIRC, 2 another critical bugs were eliminated already.
As I understand, this is a regression, since Diablo used to work a long time ago, and then some patch broke it. The bug was opened sometime in March...
Can you tell us exact date, please, at which the game worked? If I would knew this, I would already was doing several-years-wide regression test.
[1] http://www.winehq.org/hypermail/wine-cvs/2005/03/0404.html
As I understand, this is a regression, since Diablo used to work a long time ago, and then some patch broke it. The bug was opened sometime in March...
Can you tell us exact date, please, at which the game worked? If I would knew this, I would already was doing several-years-wide regression test.
When I say it used to work, I am basing this on what you've written in the bug - I hadn't personally tested Diablo until recently, at which point I confirmed your bug, since I am experiencing the same behavior.