Search

So, we’ve created some basic functionality for iterating through an ordered list of interesting actions whenever a property value changes.  Based on the logic inside BindableType, if the property values are equal we would stop processing subsequent Property Change Behaviors for this instance by returning false from NotifyPropertyBehavior.

In the next article we’ll start adding more useful and interesting features using the IPropertyChangedBehavior approach.

Consequently, projects targeting Silverlight 4 are free to hook the Resized event without worrying that their browser zoom behavior will be compromised. Yay!

This question on Stack Overflow referring to an error when using the new WPF behavior TranslateZoomRotate.

First of all, its nice to see the new behavior included with Expression Blend 4 in use.  

The TranslateZoomRotate behavior provides support for gesture-based rotating, scaling and position translation just by dropping the behavior onto an element.

In this case the effect provided is a “companion effect” for the Project 3D to Mouse, this, enables us to slide horizontally and vertically a FrameworkElement regarding the calculated X & Y Angle variation based in a determined X & Y axis amplitude. Simply said moves a UIElement accordingly to how is it turning towards the mouse using the other effect.

He creates several demonstrations using the new DataStore and conditional behavior features in concert with several new behaviors including ChangePropertyAction, ControlStoryBoardAction, SetDataStoreValueAction, and the custom Mouse3DBehavior. Adam also shows how to create a custom behavior using code. Don't miss this episode as Adam discusses how behaviors can make the UI developer's job much easier.

Well working on a few WCF RIA Services projects a need for the UI to update based on what roles the current user belongs to came up with each project. To make this easier for all of us working on these projects I created some behaviors that accepts a list of roles and updates the UI accordingly. I decided to include this in an open source library that is available at the associated OpenLight Group Common CodePlex project site. In this article we will discuss the base class used for all of the role based behaviors and look at the RoleBasedEnabledBehavior as an example of how to implement the base class.

Basically if you have situation where you need to either show or hide a visual element, you need to know what State you are in. As you can’t attach 2 different Triggers (Behaviours) to the same element, & expect to activate/fire them in an alternating manner with the same action (i.e. a mouse click). Blend will only ever fire one & continue to fire the same one. (The closest in the Z order i presume…) And my first thought was, that i needed some code to determine what state I was in. But you don’t!

Storyboards are one of the primary ways you create animations in Silverlight, WPF, and Windows Phone using Expression Blend. Creating a storyboard is fairly easy, but actually using a storyboard such as having it play is not. To help with this, you have the ControlStoryboardAction.