Comments on: Control Visibility with triggers http://joel.neubeck.net/2009/08/control-visibility-with-triggers/ Simplifing structure without changing results Fri, 05 Mar 2010 07:33:38 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Michael Washington http://joel.neubeck.net/2009/08/control-visibility-with-triggers/comment-page-1/#comment-821 Michael Washington Wed, 12 Aug 2009 13:49:30 +0000 http://joel.neubeck.net/2009/08/control-visibility-with-triggers/#comment-821 This works for me. I have used the Visual States before, but at this point they are not easy to use. Using your code was easy to use, simply set the properties and the control works. For SketchFlow it is all about fast and easy so this works. This works for me. I have used the Visual States before, but at this point they are not easy to use. Using your code was easy to use, simply set the properties and the control works. For SketchFlow it is all about fast and easy so this works.

]]> By: Rob Eisenberg http://joel.neubeck.net/2009/08/control-visibility-with-triggers/comment-page-1/#comment-819 Rob Eisenberg Tue, 11 Aug 2009 14:56:41 +0000 http://joel.neubeck.net/2009/08/control-visibility-with-triggers/#comment-819 I think it's on Control in Silverlight; UIElement in WPF. For prototyping, I wouldn't hesitate to use the approach you mention. However, when you move to an actual implementation, its easy for this to get out of hand. It's something to be continually evaluating because you can very easily find that you've put a lot of "code" in the Xaml without realizing it. I think it’s on Control in Silverlight; UIElement in WPF. For prototyping, I wouldn’t hesitate to use the approach you mention. However, when you move to an actual implementation, its easy for this to get out of hand. It’s something to be continually evaluating because you can very easily find that you’ve put a lot of “code” in the Xaml without realizing it.

]]> By: joel http://joel.neubeck.net/2009/08/control-visibility-with-triggers/comment-page-1/#comment-818 joel Tue, 11 Aug 2009 05:11:51 +0000 http://joel.neubeck.net/2009/08/control-visibility-with-triggers/#comment-818 Rob thanks for your comment. I hear what you are saying, but I am not sure I would classify it as abuse. What I like about the trigger is its ease of implementation (drag and drop). Just yesterday I was mocking a few screens in Sketchflow and found the trigger very valuable for rapid prototyping. I had a part of a screen where I needed a checkbox to acknowledge a user was a member of AAA?. Checking the box displayed a group of fields to capture the AAA information. My trigger was easier then constructing a ViewModel and adding a few properties. Quick question about your approach….I did not think that UIElement.IsVisible had a setter, nor did I think it existed in Silverlight 3? Rob thanks for your comment. I hear what you are saying, but I am not sure I would classify it as abuse. What I like about the trigger is its ease of implementation (drag and drop). Just yesterday I was mocking a few screens in Sketchflow and found the trigger very valuable for rapid prototyping. I had a part of a screen where I needed a checkbox to acknowledge a user was a member of AAA?. Checking the box displayed a group of fields to capture the AAA information. My trigger was easier then constructing a ViewModel and adding a few properties.

Quick question about your approach….I did not think that UIElement.IsVisible had a setter, nor did I think it existed in Silverlight 3?

]]> By: Control Visibility with triggers | Silverlight Travel http://joel.neubeck.net/2009/08/control-visibility-with-triggers/comment-page-1/#comment-817 Control Visibility with triggers | Silverlight Travel Tue, 11 Aug 2009 05:03:50 +0000 http://joel.neubeck.net/2009/08/control-visibility-with-triggers/#comment-817 [...] more here [...] [...] more here [...]

]]> By: joel http://joel.neubeck.net/2009/08/control-visibility-with-triggers/comment-page-1/#comment-816 joel Tue, 11 Aug 2009 04:50:52 +0000 http://joel.neubeck.net/2009/08/control-visibility-with-triggers/#comment-816 To bind the IsChecked from one element to the visibility of another, you would need to use a converter to go from a nullable bool to the System.Windows.Visibility enum. It's how many of us did it in Silverlight 2. To bind the IsChecked from one element to the visibility of another, you would need to use a converter to go from a nullable bool to the System.Windows.Visibility enum. It’s how many of us did it in Silverlight 2.

]]> By: Foster http://joel.neubeck.net/2009/08/control-visibility-with-triggers/comment-page-1/#comment-815 Foster Tue, 11 Aug 2009 00:48:30 +0000 http://joel.neubeck.net/2009/08/control-visibility-with-triggers/#comment-815 Triggers are cool, but I wonder if your first one can be achieved with element binding? Triggers are cool, but I wonder if your first one can be achieved with element binding?

]]> By: Rob Eisenberg http://joel.neubeck.net/2009/08/control-visibility-with-triggers/comment-page-1/#comment-814 Rob Eisenberg Mon, 10 Aug 2009 22:24:20 +0000 http://joel.neubeck.net/2009/08/control-visibility-with-triggers/#comment-814 Triggers are an extremely powerful construct and very easily abused. This type of usage puts too much behavior in the Xaml, where it doesn't belong. A better approach would be to use a ViewModel and bind interested elements to the same property. So, the RadioButton.IsChecked is bound to the same property as the UIElement.IsVisible. Doing it this way even requires significantly less code as well. Triggers are an extremely powerful construct and very easily abused. This type of usage puts too much behavior in the Xaml, where it doesn’t belong. A better approach would be to use a ViewModel and bind interested elements to the same property. So, the RadioButton.IsChecked is bound to the same property as the UIElement.IsVisible. Doing it this way even requires significantly less code as well.

]]>