OK, maybe this is my opinion, maybe these are bugs.
Given the folowing:
I have a NotifyIcon on my Form, a Context menu associated with the
NotifyIcon, and a MenuItem on the ContextMenu set as default. When the
default MenuItem is clicked, there is code to no longer show the NotifyIcon.
What I feel should happen is when I double-click the NotifyIcon in the
system tray, it should perform the default menu item's Click event.
Heres what DOES happen:
When I double-click, I get squat by default. So I wire up some code to
handle the DoubleClick event from the NotifyIcon. It executes the same code
as clicking the default menu item (which turns the NotifyIcon to invisible).
My opinion is that I shouldn't have to do this.
But wait, there's more! Here's where it gets buggy.
Not only did I have to manually wire up the code to perform the default, but
now since the NotifyIcon disappears on double-click, The message is still
pased to windows!!!! Meaning that after my NotifyIcon disappears, the NEXT
icon in the system tray catches the message and shows ITS context menu.
Arrrgh!!! :S
Does anyone have a quick way to avoid this? Can I halt the message somehow?
Do I need to write my own version which would include bubble support?
--
Any help is appreciated.
Thanks in advance.
WALDO