Comments on: Parts & States Model with VisualStateManager (Part 4 of 4) http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/ karen corby's fabulous blog Tue, 16 Feb 2010 20:10:26 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Anonymous http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-798 Anonymous Fri, 26 Sep 2008 18:02:52 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-798 I found a work around. The storyboard for each individual VisualState must be declared within the VisualState explicitly, not as a reference to a resource. I found a work around. The storyboard for each individual VisualState must be declared within the VisualState explicitly, not as a reference to a resource.

]]> By: Anonymous http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-797 Anonymous Fri, 26 Sep 2008 17:45:18 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-797 This sample no longer seems to work with the Silverlight 2 Release Candidate. The GoToState(bool useTransitions) helper method now throws an InvalidOperationException - Element is already the child of another element. Will you be posting an update on how to get this to work with RC0? This sample no longer seems to work with the Silverlight 2 Release Candidate. The GoToState(bool useTransitions) helper method now throws an InvalidOperationException – Element is already the child of another element.

Will you be posting an update on how to get this to work with RC0?

]]> By: Anonymous http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-794 Anonymous Wed, 17 Sep 2008 19:00:51 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-794 Looks like your comment area doesn't like XML input, but I was trying to enter: < GoToState State="Pressed" UseTransitions="false" / > Looks like your comment area doesn’t like XML input, but I was trying to enter:

< GoToState State=”Pressed” UseTransitions=”false” / >

]]> By: Morten http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-799 Morten Wed, 17 Sep 2008 18:59:13 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-799 Thanks for a great set of posts. Just a comment on the future trigger support. Please consider adding a UseTransitions property as well, similar to your GotoState method: Thanks for a great set of posts.

Just a comment on the future trigger support. Please consider adding a UseTransitions property as well, similar to your GotoState method:

]]> By: Patrice Lafond http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-792 Patrice Lafond Thu, 10 Jul 2008 15:04:36 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-792 Wow! Exactly what I was looking for! Most of tutorials use Blend (not that is bad, but I understand better with source code). Wow! Exactly what I was looking for! Most of tutorials use Blend (not that is bad, but I understand better with source code).

]]> By: Dr. YSG http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-789 Dr. YSG Thu, 03 Jul 2008 13:57:35 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-789 It was an excellent series, well written, and very informative (at least to me). But I am still left with a question. It seems to me that the example could have been accomplished much easer with templating a UserControl. I think I could easily capture hover, disable, and mouse events and use the VSM in blend to rapdily create the same effects. I must be missing something. Why would I go to the work of building the custom control from scratch. It seems there is something I am still not understanding where method gives some power I would not mormally have. It was an excellent series, well written, and very informative (at least to me).

But I am still left with a question.

It seems to me that the example could have been accomplished much easer with templating a UserControl. I think I could easily capture hover, disable, and mouse events and use the VSM in blend to rapdily create the same effects.

I must be missing something. Why would I go to the work of building the custom control from scratch. It seems there is something I am still not understanding where method gives some power I would not mormally have.

]]> By: John "Z-Bo" Zabroski http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-790 John "Z-Bo" Zabroski Tue, 01 Jul 2008 16:19:01 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-790 The major problem with the current GoToState is that it is fully encapsulated in the ancestor class. Adding a new state to a state group requires breaking encapsulation, or rather unencapsulating things that were given too fine-grained encapsulation... triggers are a good idea and I like how the overall architecture of WPF is selectively open and exposes states through statechart-like analysis patterns. The major problem with the current GoToState is that it is fully encapsulated in the ancestor class. Adding a new state to a state group requires breaking encapsulation, or rather unencapsulating things that were given too fine-grained encapsulation… triggers are a good idea and I like how the overall architecture of WPF is selectively open and exposes states through statechart-like analysis patterns.

]]> By: Bruce Denham http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-795 Bruce Denham Sat, 28 Jun 2008 23:45:33 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-795 Excellent series. You mentioned that the Parts & States Model could also be used with User Controls. I'm having trouble conceptualizing that, but I guess you would just leave the XAML of the UserControl relatively empty, then access the ControlTemplate from the UserControl's resources (or the Application.Resources). It would be good to know why you'd want to do all this for a UserControl, instead of just declaring the UI in it's XAML. Maybe for UserControls, you build your Parts into the XAML while keeping your Visual States and Transitions separate elsewhere? Wondering... Excellent series. You mentioned that the Parts & States Model could also be used with User Controls. I’m having trouble conceptualizing that, but I guess you would just leave the XAML of the UserControl relatively empty, then access the ControlTemplate from the UserControl’s resources (or the Application.Resources). It would be good to know why you’d want to do all this for a UserControl, instead of just declaring the UI in it’s XAML. Maybe for UserControls, you build your Parts into the XAML while keeping your Visual States and Transitions separate elsewhere? Wondering…

]]> By: Keith Woods http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-791 Keith Woods Thu, 26 Jun 2008 15:19:21 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-791 Great series, thanks :) Great series, thanks :)

]]> By: Nostromo http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/comment-page-1/#comment-793 Nostromo Thu, 26 Jun 2008 09:35:18 +0000 http://scorbs.com/2008/06/25/parts-states-model-with-visualstatemanager-part-4-of-4/#comment-793 the second choice: the designer can add new states :D the second choice: the designer can add new states :D

]]>