http://bugs.winehq.org/show_bug.cgi?id=22948
--- Comment #8 from Jörg Höhle hoehle@users.sourceforge.net 2010-06-06 01:26:19 --- To answer my question myself, it seems that the regression that commit 914c8cb8ea1e5cbcfa18558961185dd94313b26d introduced in 1.1.41 is the unability to recover from a resolution change by pressing F6 once or twice.
Remember that F6 is supposed to toggle window mode in Caesar 3, Pharaoh, Cleopatra and Emperor. This regression also affects those apps.
After starting with wine explorer /desktop=Imperium,1024x768 c3.exe, switching to a smaller resolution causes a black screen. Prior to that commit, pressing F6
- once yields a pink&green window of size the desired resolution inside the virtual desktop, displaying 2 tiny views of the game side by side -- independent on this commit;
- twice resizes Wine's desktop to the desired size, graphics now ok (mouse lag still present at 1024x768). Since this commit, the screen remains black.
It is also this commit that causes a black screen when using Wine in fullscreen mode with a monitor whose initial resolution is > 1024x768.
I don't understand why different apps in Wine appear to have different ways of switching to full screen. I'd have naively expected all to be mapped by winex11 to a unique behaviour. Caesar3 etc. initially draws an almost black screen, except the Gnome panels are still present in Ubuntu Intrepid while the app displays the still pictures prior to the animations. Most other apps cause no such behaviour, the Gnome panels disappear immediately. A race condition?
In summary, several distinct regressions affect the Caesar3/Pharaoh/Emperor games. It would be interesting to analyse whether another one causes the inability to use windowed mode (cf. the pink&purple window).