Hi,
Yegappan Lakshmanan schrieb am 26.08.2015 um 23:33:
>
> Based on the following posts:
>
> http://blogs.msdn.com/b/oldnewthing/archive/2011/09/26/10216420.aspx
> http://blogs.msdn.com/b/oldnewthing/archive/2005/07/27/443824.aspx
>
> sending a WM_CLOSE and WM_NCDESTROY message to a window is not
> the same as calling DestroyWindow(). So I think the original fix (patch 829)
> for the crash is not correct.
if I understand the first post correctly it would be sufficient to only
send a WM_CLOSE message. For a test I removed the second and third calls
of PostMessage() and re-compiled. All balloon hints were cleanly removed
from the screen, but I could not check if there is a memory or resource
leak.
Patch attached.
Regards,
Jürgen
--
Sometimes I think the surest sign that intelligent life exists elsewhere
in the universe is that none of it has tried to contact us. (Calvin)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/gui_w32.c b/src/gui_w32.c
index 30fd04c..624393e 100644
--- a/src/gui_w32.c
+++ b/src/gui_w32.c
@@ -4851,8 +4851,6 @@ delete_tooltip(beval)
BalloonEval *beval;
{
PostMessage(beval->balloon, WM_CLOSE, 0, 0);
- PostMessage(beval->balloon, WM_DESTROY, 0, 0);
- PostMessage(beval->balloon, WM_NCDESTROY, 0, 0);
}
/*ARGSUSED*/
