Skip to main content

WPF Routing

WPF (3.5) introduced the concept of Routing that made the event routing easies in the scenarios where it was tedious to handle events. Consider a scenario where there are a number of Hyperlinks in a Panel that direct to separate locations on Click. Now if this is done in normal programming, each hyperlink will have to have code for execution. It would be easier and cleaner if we could handle the hyperlinks in the container (the Panel) that handles the click and redirects to appropriate location.

WPF handles the events with the following 3 strategies.

  • Direct events are like ordinary .NET events. They originate in one element and don’t pass to any other. For example, MouseEnter is a direct event.

  • Bubbling events are events that travel up the containment hierarchy. For example, MouseDown is a bubbling event. It is raised first by the element that is clicked. Next, it is raised by that element’s parent, and then by that element’s parent, and so on, until WPF reaches the top of the element tree.

  • Tunneling events are events that travel down the containment hierarchy. They give you the chance to preview (and possible stop) an event before it reaches the appropriate control. For example, PreviewKeyDown allows you to intercept a key press, first at the window level, and then in increasingly more specific containers until you reach the element that had focus when the key was pressed.


RoutedEventArgs Class:

  • Source indicates what object raised the event.

  • OriginalSource indicates what object originally raised the event. Usually the OriginalSource is the same the Source. But in some cases they could be different. For example, if you click close to the border of a window, you will get a Window object for the Source but a Border object for the OriginalSource.

  • RoutedEvent provides the RoutedEvent object for the event triggered by your event handler.

  • Handled allows you to halt the event bubbling or tunneling process.


Here is a simple example of when you might use a bubbling event:

<StackPanel Hyperlink.Click="StackPanel_Click">

        <TextBlock>

        <Hyperlink NavigateUri="http://www.google.com">Google</Hyperlink>

        </TextBlock>

        <TextBlock>

       <Hyperlink NavigateUri=http://gmail.com>Gmail</Hyperlink>

        </TextBlock>

        <TextBlock>

       <Hyperlink NavigateUri=http://facebook.com>FaceBook</Hyperlink>

        </TextBlock>

    </StackPanel>

And to handle the HyperLinks..

private void StackPanel_Click(object sender, RoutedEventArgs e)

        {

            Process.Start(((Hyperlink)e.Source).NavigateUri.ToString());

        }

So instead of having to create an event handler for each hyperlink, or creating a single event handler and pointing each hyperlink to the same event handler, one event handler on the parent element can be used.

This article just covered the Routing Basics and can serve as a base material to get started, However there is still lot that needs to be learnt and the who else, other than MSDN can teach it better.

Hope this was helpful,

Till Next we Connect…….

Happy Learning.

The Source Code can be downloaded from here

Comments

Popular posts from this blog

Authentication using Social Networking portals(Facebook, Gmail, and Yahoo)

There are tons of sites, which offer sign on using the social networking site credentials (Facebook, gtalk, twitter and the list continues).It can be termed a “SINGLE SIGNON” and offers a lot of benefits compared to traditional database authentication approach. However, not storing user credentials in the DB imposes an additional risk. How to track who all logged into the system. Now the question is, which approach to follow. The best approach is to use inbuilt asp.net users for storing the logging info about user activities and using single signon technique for authentication. This article will explore the approach and provide the details of implementation using some third party libraries and customizing it to the requirements. The Authentication will be done using the following networking portals Yahoo  Gmail Facebook    Special thanks to my friend Sumit Khandelwal, for implementation of Facebook part (in fact he did it all!!) Except Facebook, all other ca...

Interview Queations-A Quick Recap

Today one of my friends, got his first blog entry published. I find it cool enough to get started and it can come up as an excellent reource for quick review of concepts prior to interview. Here is the link. Quick Review Hope this is helpful! Till next we Connect........ Happy Learning.

C# Partial Feature:Classes and Methods

C# Partial Classes and Methods: One of the unique features of C# is the concept of Partial, extendable to definition of a Class or a Struct, an Interface or a method. Using this, the definition of any class, struct, interface of method can exist in two or more source files. Each source file contains a section of the type or method definition, and all parts are combined when the application is compiled. To split a class definition, partial keyword modifier is used. For Example: public partial class Pradeep { public void OnLeave () { } } public partial class Pradeep { public void InMeeting () { } } Here, it is valid to use the same name for the class and implement desired functionality separately. Finally, when compiled, the code is auto merged , giving a Final class named Pradeep, with the two methods that were defined separately. The partial keyword indicates that other parts of the class, struct, or interface can be defined in the namespace. Following are...