In a few previous tutorials, you learned all about Behaviors and how to use a behavior that is provided out of the box by Expression Blend. You find a behavior in your Assets Library, drag/drop it onto something, tweak a few properties, and (like magic!) you are done and everything just works. There will be times, though, where you will not find a built-in behavior to suit what you are trying to do:
In those dark, uncertain times, you will basically need to write your own behavior. Fortunately, as you will see shortly, that isn't something that is too difficult. The Behaviors functionality is made up of three components - Behavior, Action, and Trigger. Each component does something pretty unique, so this tutorial is focused on the most common of them, the Action. What is an Action?
Mundane things you face in in real life and mundane things your applications face, in many ways, are not that much different. They all revolve around cause and effect. When I flip on a light switch, the light turns on. When I click on a button, a sound plays. When my application hits a certain time, it needs to close. Read more: kirupa.com
In those dark, uncertain times, you will basically need to write your own behavior. Fortunately, as you will see shortly, that isn't something that is too difficult. The Behaviors functionality is made up of three components - Behavior, Action, and Trigger. Each component does something pretty unique, so this tutorial is focused on the most common of them, the Action. What is an Action?
Mundane things you face in in real life and mundane things your applications face, in many ways, are not that much different. They all revolve around cause and effect. When I flip on a light switch, the light turns on. When I click on a button, a sound plays. When my application hits a certain time, it needs to close. Read more: kirupa.com
Posts
0 comments:
Post a Comment