http://bugs.winehq.org/show_bug.cgi?id=31381
--- Comment #13 from Goblinstomper@gmail.com 2012-08-03 17:15:13 CDT --- (In reply to comment #12)
(In reply to comment #11)
So, I took a shot at the kde bugtracker (https://bugs.kde.org/show_bug.cgi?id=304469) and Martin Lubking there was most helpful, if I understand it correctly his conclusion was that ToEE was trying to use an old way of establishing a full-screen window, failing and only using a canvas which kwin can't or don't manage.
Frankly, what's written in that bug report doesn't make a lot of sense to me. Just so I'm sure I'm understanding this correctly, the application window in http://bugs.winehq.org/attachment.cgi?id=41229 is supposed to be 1280x1024, but actually stays something like 800x600.
It's 1024x768, the same resolution as at least one of the movies played at the start of the game, and after which the window isn't resized again. I found out the dimensions when I mucked about with forcing kwin to keep windows certain sizes, but yes that is correct.
That e.g. _NET_WM_STATE_FULLSCREEN wouldn't be set in that case isn't all that surprising, it doesn't get set if the resize failed.
One thing I did notice in that screenshot is that the size is actually 1279x1019 instead of 1280x1024. Is that because you cropped the screenshot, or does fglrx actually give you that resolution if you ask for 1280x1024? Either way, if it works with the free driver it's probably not worth worrying too much about.
that is due to my cropping yes, fglrx has always had the right size of the screen (but not the "game-window") and if I understood Martin correctly that wouldn't have been a problem if the "game-window" had had the right properties letting the panel know it was supposed to get out of it's way. If I hadn't cropped it it would have looked like the game always ran as a window in the upper left corner on a huge desktop as the application I used to take the screen shots somehow manage to get everything.
Frankly it has become apparent that my lacking knowledge of graphics and the terminology involved makes this at least twice as hard to describe as it ought to be. Thank you for your patience.
and yes, as far as I'm concerned this is not a wine bug and will probably get corrected in fglrx one way or another eventually.