Reroute Child events to parent

Question

2.00/5 (1 vote)

See more:

I'm making a user control that acts as an icon.

I would like the control to have the same basic behavior regardless of what child control is being triggered.
For example. If a user clicks on a child control -- any child control-- i want to raise the parent controls Clicked event.

is there a was of doing this without manually raising the events?

if the mouse hovers anywhere over the control or any of its children, i want the same tool tip to activate. Must i configure each child control with this behavior, or is there a simpler solution?

Posted 3-Nov-13 8:48am

Mr.TMG

Updated 3-Nov-13 9:47am

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 3-Nov-13 15:19pm

So, VB or VB.NET? Is it System.Windows.Forms, WPF or something else?
You always need to tag your UI library/framework or application type when UI is concerned.
Yes, there is a simpler solution, and this is not a re-routing (why?!). This is previewing events on the form/window. You should understand that events are always reach the form/window, you just need to handle them on this level.
—SA

Mr.TMG 3-Nov-13 15:58pm

Fixed the tag to reflect vb.net.
On my userControl, I basically want to raise events like Me.DoubleClicked as the usercontrol which houses the objects (Like textbox) that are actually being double clicked.

currently, what i'm doing is this
Sub textBox_DoubleClicked(Sender,E as eventargs)Handles TextBox.doubleClicked
Me.Icon_DoubleClick(Me, E)
end sub

Sergey Alexandrovich Kryukov 3-Nov-13 16:37pm

Which "TextBox"? Do you think there is one? Full type name, please.
—SA

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)