http://bugs.winehq.org/show_bug.cgi?id=2398
------- Additional Comments From phil@ldex.terica.net 2005-29-09 21:24 ------- Ouch. That's really unfortunate (to put it kindly). I *really* wish that the new window management system had been implemented alongside the older system, possibly with a command line switch or environment variable to set the mode to be used. At least that way those with apps affected by this change wouldn't now be completely blocked from using newer wine releases.
This genuinely sucks and the wiki 'solutions' don't seem particularly ideal. Is there no hope of getting the old WM code put back in for legacy support until the new WM code is working for these affected apps? This impacts CXO/Codeweavers as well, making everything after their 3.0.1 release unusable for apps affected by this issue. That's a lot of breakage to be shipping in Wine 1.0 and commercial products based on Wine (which pay some of the developers to work on Wine, let's not forget).
If nothing can be done with the current code (or by simply having two wine versions - one with the new window manager code and the other with the old implementation), could packagers be encouraged to provide working legacy packages based on the last-known-good January source (e.g. wine-legacy) for current distributions? That would allow for easy side-installation of the new Wine and the old Wine without too much hassle for end-users.
-
Wine Bugs