🚀 go-pugleaf

On Fri, 17 Nov 2000 19:27:03 +0000, Bob Moore
<bob@mooremvp.freeserve.co.uk> wrote:

>On Fri, 17 Nov 2000 15:25:15 GMT, SNOW CRASH wrote:
>
>>Just a guess, but try and (instead) do an 
>>InvalidateRect(hwndTrayWnd, NULL);
>
>I also came upon this problem some time ago. I tried Invalidating, and
>that doesn't work. I've tried enumerating the children of the tray and
>repainting them, and that doesn't work either. I suspect (unless
>someone else knows better) that Ians suggestion of inserting and
>removing a dummy icon may the only surefire way of doing this.
>
>--
>Bob Moore [WinSDK MVP]
>http://www.mooremvp.freeserve.co.uk/
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Posted via news://msnews.microsoft.com
>Do not reply via email unless specifically requested to do so.
>Unsolicited email is NOT welcome and will go unanswered.
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Actually, now that I think about it, invalidating the window won't do
anything; it already have the ICON handle itself so it will just
repaint it.

The act of moving the mouse over the icon causes notification messages
to be sent to the owner of the icon (I believe, but if not at least
the tray does _something_).  What is probably happening is that it
gets the "owner" of the tray icon and does a "IsWindow(hWnd)" check on
the handle -- If that comes back as FALSE, then it just kills the
icon.  

Question is, is there a way to get the tray to do this check.. Perhaps
some sort of update message (WM_PAINT is a good try but obviously
doesn't do the trick.)

Unfortunately, I don't have a solution, but I would be interested to
see any results.  If I have time this weekend I will try sending
various messages to the tray and see if any work.

// CHRIS