http://bugs.winehq.org/show_bug.cgi?id=20865
Daniel Stiefe1maier caliga@arcor.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |caliga@arcor.de
--- Comment #12 from Daniel Stiefe1maier caliga@arcor.de 2010-02-19 11:42:04 --- TeamViewer 5 is affected by the same problem in at least two ways:
a) The connection window that shows your partner's desktop, is resized a few times directly after creation. Sometimes it then stays at a wrong size (about 100x50 pixel, which is rather silly...)
b) Widgets. (Select 'Chat' or 'Conference call' from the audio/video menu for example) They don't have a 'native' window title bar and use SetWindowPos when dragged. On my system, they jump arround like crazy.
Things to increase probability of unwanted behaviour: - stress (like cat /dev/zero > /dev/null) - having compositing enabled (and some crazy compositing-toys - allow window manager to control the window (winecfg)
On KDE at least, allowing the window manager to control the window leads to more WM_SIZE messages, when the connection window is initially created and resized. Is that because of what Vincent explained, or is it an additional KDE oddity?
I'll try the patch from bug 9802 next week and report...
So, in general, all applications that often do SetWindowPos in a short time, are affected by this problem.
Suggestion: Would it be possible to have a list with pending ConfigureNotify events? (Or more exactly: a list of coords, for which we did configure requests, but did not receive ConfigureNotify events so far) Then it should be possible to distinguish between Wine's own configure requests and others!?