http://bugs.winehq.com/show_bug.cgi?id=1265
------- Additional Comments From dclark@akamail.com 2003-02-10 13:03 ------- This is being caused because this sequence of events is taking place. Early on the app creates two DCs for the tooltip with a default size of 66x20 pixels. One is an offscreen DC for working in (ends up being 0xa18 on my system), and the other is the DC that is used to actually display the tooltip on the screen (0xa14). When it comes time to show the tooltip, the app moves and resizes both DCs, and paints and writes in the text to the offscreen DC. It then copies this into the screen DC and sends a signal to make it visible. Up to this point everything is fine.
When the window is made visible, some events are received from the X queue, which "catch up" the app. It sends two resize events to the offscreen DC, the first resizes back to 66x20, which effectively clips the rest of the tooltip, and the second resizes it back to the correct size. Unfortunately the contents are now corrupted, but the app is assuming the offscreen DC is ok. The corrupted offscreen DC is then copied to the screen DC.
When the tooltip is hidden and redisplayed, the same sequence of events occurs. Except this time, the DCs were already at the correct size for the tooltip, so no resizing back to 66x20 occurs, and the offscreen DC is not corrupted this time. Even when the window is closed and reopened, it continues to use the DCs it has already created, so no problem occurs.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://bugs.winehq.com/show_bug.cgi?id=1265. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
-
wine-bugs＠winehq.com