Open ttencate opened 13 years ago
Submitted by ttencate
Shell_NotifyIcon may give ERROR_TIMEOUT sometimes. http://msdn.microsoft.com/en-us/library/bb762159%28VS.85%29.aspx This possibly happens during Explorer startup. Responding to WM_TASKBARCREATED and not displaying the ERROR_TIMEOUT might also resolve that issue.
Converted from SourceForge issue 2887983, submitted by ttencate
Copying from http://syedgakbar.wordpress.com/2008/07/14/restore-notification-area-icon-after-explorer-crash/
"If you are writing any application which adds an icon to the Taskbar notification area, it’s recommend to handle the “WM_TASKBARCREATED†the message sent by explorer. This message is sent by explorer when it’s creating the taskbar. As after crash explorer doesn’t remember the original notification icons, you should handle this message and then re-register your application notification icon.
To capture this message, you must first register it like this:
const static UINT WM_TASKBARCREATED = ::RegisterWindowMessage(__T(“TaskbarCreatedâ€));
Once it’s registered, you should handle this in your Windows Callback Procedure to re-add the icon for your application in the notification area. Something like this:
// Check if the Taskbar is just being created. This message is broadcast by the Explorer // when it’s launched (after any crash) if (message == WM_TASKBARCREATED) { // Add the code to re-add your application in the notification area. }
Simple, but yet effective. What do you think?"