http://bugs.winehq.org/show_bug.cgi?id=13843
Summary: tooltips not working properly - message problems Product: Wine Version: 1.0-rc4 Platform: Other URL: http://mrhx.ucoz.com/load/0-0-0-27-20 OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: comctl32 AssignedTo: wine-bugs@winehq.org ReportedBy: hramrach@centrum.cz
In the VISG editor (see url) the tooltips aren't resized and painted properly. Works on windows.
Developer explanation (copied below without screenshots):
http://www.reactos.org/forum/viewtopic.php?p=36824&sid=9c02654b3b5b22544...
As you may see, the button tooltip has the same size as in winxp. This is correct, but it is not painted. I think, it's because ROS paints the tooltips not via WM_PAINT.
And the second: the window tooltip with little screenshot... It is not painted and has wrong size. I think, it's because this tooltip didn't have LPSTR_TEXTCALLBACK as its caption (in other words, it has direct caption). I resize the tooltip on TTN_SHOW message. But, as I see, there is no such message for the window tooltip. But the winapi documentation says TTN_SHOW is sent when the tooltip is about to be shown. And no matter, has it LPSTR_TEXTCALLBACK or not. The button tooltip has LPSTR_TEXTCALLBACK instead of its caption, and it's resized correctly.
So, I think, there are two bugs: 1) painting tooltips not via WM_PAINT. 2) not sending TTN_SHOW, if the tooltip did not have LPSTR_TEXTCALLBACK.
http://bugs.winehq.org/show_bug.cgi?id=13843
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-11 05:09:20 --- What OS is that?
http://bugs.winehq.org/show_bug.cgi?id=13843
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-11 06:05:54 --- Judging from the description, url and discussion this has nothing to do with Wine.
Feel free to reopen if the problem is reproduced running under Wine.
http://bugs.winehq.org/show_bug.cgi?id=13843
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-11 06:06:14 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=13843
Michal Suchanek hramrach@centrum.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #4 from Michal Suchanek hramrach@centrum.cz 2008-06-11 10:57:13 --- I report here exactly because I experience the problem under Wine, and if you really read the description you would notice that in an earlier post it is mantioned that it happens under ReactOS *and* Wine.
http://bugs.winehq.org/show_bug.cgi?id=13843
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-12 05:34:22 --- (Thanks for pointing out to my mistake in closing this in a hurry)
That's a problem with our tooltip control. It does send the TTN_SHOW notification, but 1. in response to TTN_SHOW the application sends TTM_GETCURRENTTOOL to the tooltip, and tooltip doesn't fill some vital fields in TTTOOLINFO structure the app relies upon (hwnd, uId, lpszText) 2. in response to TTN_SHOW the application resizes the tooltip to draw a custom image on it, unfortunately right after TTN_SHOW was sent the tooltip control resizes itself, and the size the app set get lost.
http://bugs.winehq.org/show_bug.cgi?id=13843
--- Comment #6 from Austin English austinenglish@gmail.com 2008-12-11 11:04:25 --- Is this still an issue in current (1.1.10 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=13843
--- Comment #7 from Austin English austinenglish@gmail.com 2009-06-10 11:34:25 --- Abandoned. If this is still an issue in current wine and you can provide the needed information, feel free to reopen.
http://bugs.winehq.org/show_bug.cgi?id=13843
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |ABANDONED
--- Comment #8 from Austin English austinenglish@gmail.com 2009-06-10 11:36:33 --- For real this time.
http://bugs.winehq.org/show_bug.cgi?id=13843
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Austin English austinenglish@gmail.com 2009-06-10 11:38:19 --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=13843
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED Fixed by SHA1| |b48f394e4f3ee73eb2f974d1977 | |0d411d13f3e62 Resolution|ABANDONED |FIXED
--- Comment #10 from Nikolay Sivov bunglehead@gmail.com --- This was fixed with http://source.winehq.org/git/wine.git/commit/b48f394e4f3ee73eb2f974d19770d41....
https://bugs.winehq.org/show_bug.cgi?id=13843
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.9.10.
-
wine-bugs＠winehq.org