Visual State Manager tips for design and authoring

re: Visual State Manager tips for design and authoring

Hotel — Thu, 10 Mar 2011 20:29:46 GMT

yeah - well worth the effort I think. The tips are stunning and of real value

re: Visual State Manager tips for design and authoring

Steven Charles White — Mon, 31 Jan 2011 23:28:32 GMT

This is a response to Francisco's question. The right (IMO) way of doing this is to nest the child control's (view)model inside the parent control's (view)model. That way the state-change in the parent vm can trigger the state-change in the child vm and the view will respond to the GoToState call in the usual way. A less correct but more expedient solution is to define a dependency property (dp) of type string on the child UserControl to represent the state name. One property per state group is best. Then declare the same set of visual states on both parent and child controls. Define the child states as normal; define the parent states by setting the value of the dp on the child control to the same-named state. HTH. Steve

re: Visual State Manager tips for design and authoring

Francsico — Mon, 31 Jan 2011 16:55:36 GMT

How can I define a visual state of a child element(user control) on the parent's visual state? I have a main window with some buttons that are user controls inside. I need to define the visual state of the button on the main window's visual state...

re: Visual State Manager tips for design and authoring

print my emotions — Wed, 18 Aug 2010 05:53:06 GMT

The way you've described it paints a picture in my mind that is quite clear and informative. I will be spending more time with visual state in the near future and I appreciate the clarity you bring to the concepts.

re: Visual State Manager tips for design and authoring

portable staging — Tue, 04 May 2010 06:23:22 GMT

The tips for design and authoring you have shared here are amazing and worth to be worked.

re: Visual State Manager tips for design and authoring

southpawcg — Wed, 02 Dec 2009 20:11:17 GMT

Are there any more accessibly-written blogs on MSDN to which I could refer in order to learn Blend?

This is a global Microsoft malady (and one that we are not supposed to mention, lest we be branded as non-technical) but this blog is so jargon-heavy that unless I am a hard-core dev, it is virtually indecipherable.

It is not a matter of not clearly elucidating the concepts (which is well-done here) but rather a matter of writing simply and without the use of extraneous and over-complicated technical language.

I am probably barking up the wrong tree, but wouldn't it be wonderful if we could talk about "making buttons" rather than "managing XAML-based state groups"?

re: Visual State Manager tips for design and authoring

Steve White — Thu, 15 Oct 2009 19:24:42 GMT

> Is there a way to completely remove the VSM after you have selected a state, and return to "base"?

Currently the way to make a state look like Base again is to select the state then expand the object tree to find every object that is changed in that state (the red circle icons tell you this) and delete the animations from the object tree. You don't need to open the Timeline to do this.

re: Visual State Manager tips for design and authoring

Jack Ukleja — Thu, 15 Oct 2009 01:17:01 GMT

Is there a way to completely remove the VSM after you have selected a state, and return to "base"?

Also I agree with some other comments ... pictures make a blog much more accessible!

re: Visual State Manager tips for design and authoring

Chris — Mon, 05 Oct 2009 15:44:29 GMT

Thank you for the quick tutorial on state management. The way you've described it paints a picture in my mind that is quite clear and informative. I will be spending more time with visual state in the near future and I appreciate the clarity you bring to the concepts.

re: Visual State Manager tips for design and authoring

Here, not there — Mon, 05 Oct 2009 11:40:40 GMT

I agree. This article is dense and not useful without some images or samples.