L Lennart Nielsen Jul 20, 2007 #1 Is that possible? The control in question is the ErrorProvider. Lennart
B Bernd Schend Jul 21, 2007 #2 Hi Lennart, just declare a new class MyErrorProvider, which inherits from ErrorProvider. Then you can define additional events. After compiling the MyErrorProvider will appear in the toolbox. Regards Bernd Public Class MyErrorProvider Inherits ErrorProvider End Class
Hi Lennart, just declare a new class MyErrorProvider, which inherits from ErrorProvider. Then you can define additional events. After compiling the MyErrorProvider will appear in the toolbox. Regards Bernd Public Class MyErrorProvider Inherits ErrorProvider End Class
L Lennart Nielsen Jul 23, 2007 #3 Hi Bernd, Yes I know that I will have to do this; it is however creating or capturing the click event I have trouble with. If you have an example or can guide me towards a source, I'd be grateful. Lennart
Hi Bernd, Yes I know that I will have to do this; it is however creating or capturing the click event I have trouble with. If you have an example or can guide me towards a source, I'd be grateful. Lennart
P Phill W. Jul 24, 2007 #4 Lennart said: Is that possible? The control in question is the ErrorProvider. Click to expand... If the base control really doesn't support "Click" then you'll have to subclass (inherit from) it, override the WndProc method and catch the individual Windows-level Message(s) associated with clicking. HTH, Phill W.
Lennart said: Is that possible? The control in question is the ErrorProvider. Click to expand... If the base control really doesn't support "Click" then you'll have to subclass (inherit from) it, override the WndProc method and catch the individual Windows-level Message(s) associated with clicking. HTH, Phill W.
