
Signature
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/
Thanks for your post. I understand that my initial post was sligthly
misleading.
Anyway now I know how to access my "own events". But, what I really want to
access is the list of AddHandler-connections on standard (!) events.
Lets illustrate with an example. I would like to programmatically check if
following AddHandler has been done earlier (if so I do not want do duplicate
the AddHandler):
AddHandler button.Click, AddressOf button_Click
("button" is a standard System.Windows.Forms.Button)
Herfried K. Wagner [MVP] - 22 Dec 2004 14:18 GMT
"Benjamin" <benjamin.tengelin@nospam.nospam> schrieb:
> Thanks for your post. I understand that my initial post was sligthly
> misleading.
[quoted text clipped - 10 lines]
>
> ("button" is a standard System.Windows.Forms.Button)
IIRC that's not possible. You'll have to keep track of what handlers you
added yourself.

Signature
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/
"Jeffrey Tan[MSFT]" - 23 Dec 2004 01:11 GMT
Hi Benjamin,
Yes, I agree with Herfried that outside of the event definition class, we
can not use a method or property to get the hooked event chain.
Actually, because we use this class, we add the event handler to the
class's certain event, we should "know" of if the event handler is added.
Also, if we want to get the hooked event handler list, we can use an inner
list to store the hooked event handler list.
Hope this makes sense to you.
At last, I think this is more a language related issue than Winform issue,
I suggest you post this issue in "dotnet.languages.vb", then you will get
more useful feedback and help. Thanks
==========================================
Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.
Best regards,
Jeffrey Tan
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.