http://bugs.winehq.org/show_bug.cgi?id=2467
--- Comment #139 from Joel Pichette jpichette@hotmail.com 2011-08-17 15:12:29 CDT --- (In reply to comment #129)
Cut the chatter, please. It just makes it hard for anyone who wants to work on this bug to sort out the useful information (Comment #111) from the rest (everything else on this bug).
The reason this hasn't been fixed yet is that, while ddraw in exclusive mode on Windows will happily draw directly to the screen, this has negative consequences that we don't want in Wine. It won't work when a compositing window manager is being used. Even without a compositing window manager, any UI drawn by another program (such as the window you see when you press alt+tab) will be drawn over by any fullscreen ddraw program. Alexandre has made the decision that being a good X citizen, and thus avoiding this sort of problem, is more important than being fully correct.
I think that if someone can find a way to allow ddraw to draw over any Wine window, but not just any X window, (without hurting performance too much) then we could avoid the problems with drawing to the screen, and that change would have a chance of being accepted. I don't know how we could do that, though.
Let's discuss how to implement this into wine then. We understand that windows 1.0, 2.0, 3.0, 3.1, 95, 98, 2000, and xp uses direct rendering without compositing window manager.
We also undertand that microsoft decided that window manager was the new default for windows vista & 7... and that a normal user could not disable it... unless he terminates explorer.exe while he plays his game (starcraft)...
I'm thinking we should consider an approach like a dosbox frontend for old school programs (games mostly)...
Maybe we should implement a hack in winecfg only for diablo 1 / warcraft2 & starcraft (enabling the patch every time the game is started)
or
Maybe we should implement a hack in winecfg for ignoring Alexandre who is a good X citizen ?!?
-
wine-bugs＠winehq.org