Win7 Pro x64

With the DisplayFusion icon set to Show Notifications Only, clicking the down arrow to open the tray icon window, and then right-clicking the DisplayFusion icon and selecting Multi-monitor Taskbar to toggle the taskbar off, causes the tray window to go into a funny state.

After this, the tray window does not automatically close when it loses focus, but does close when an icon is left-clicked that opens a new window (like the DisplayFusion icon). Note this is backwards from normal operation, where it closes on clicking the desktop, but remains open after clicking an icon.

Using an immediate menu action on the context menu of the Outlook icon does not change the tray window's behavior.

Hi Jon,

The auto-closing of the notification area depends on the application; more specifically, it appears to be the first application icon you select.

For example:

1] If you have an Action Center notification and click it then click 'show message' the notification area closes.
2] If you click on the 'Safely Remove Hardware and Eject Devices' item, it pops up a new menu and then this and the notification area close if you click away or eject a device
3] If you click on 'Catalyst Control Center' (if you have an ATI card) and right-click, then select 'About...' an about dialog pops up. Nothing closes at this point. If you then click OK on this dialog the notification area closes too.

I had a look on MSDN but I couldn't find any specific API references to closing the notification area, but judging from the behaviours above I would say that is what ATI are doing. I don't have Spy++ installed atm either, but it might just be a simple WM_CLOSE or similar... (probably non-trivial to find the hWnd of that window too)

Most other 3rd party applications behave the same way a Display Fusion, but it would be nice if you could close it once someone has selected an action off the DF menu.

Cheers,

Darren

I have to confirm this behavior too. For me it also only happens with DF. Any other application does let met close the dialog after giving another window focus.
Maybe it could have something to do with the different contextmenu DF has in contrary to other applications.