http://bugs.winehq.org/show_bug.cgi?id=23745
--- Comment #26 from Roman m01brv@mail.ru 2011-01-27 03:35:57 CST --- I could not find where the window gets the maximized state except during its creation - WIN_CreateWindowEx is called with WS_MAXIMIZE flag. However, a bit later (still during the initialization) I see the log message "window is no longer maximized" from X11DRV_ConfigureNotify. No further messages, which could indicate that it is being re-maximized. I noted that when the window is being minimized to the taskbar, it is no longer marked as fullscreen by the WM (as shown in the right-click taskbar menu). The "maximized" box is ticked only in this minimized state. When the window is in fullscreen, the "maximized" box is unticked and even disabled. Since I could not find anything in the debug log that could indicate that the window gets "maximized" during the minimization, my only guess is that KWin or Xorg may have somehow remembered this maximized state from the very window creation (wine did not notify them to remove this flag at some point?). This is probably ignored when the window is in fullscreen, but is recalled each time the window looses the fullscreen state.
By the way, I found that it is sufficient to force only the "fullscreen" property in the KWin configuration for war3.exe. In that case, the window just never attains the "maximized" state - the respective menu checkbox remains always disabled.