StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6572891
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2011-07-04T14:37:39.123
FavoriteCount
0
LastActivityDate
2011-07-04T14:47:43.243
LastEditDate
2011-07-04T14:47:43.243
LastEditorUserId
604613
OwnerUserId
604613
ParentId
6571092
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Build your own custom filter control. First, get rid of the enum, use a custom class instead, that defines your available filter options. I choose a class named "FilterOption", which has a property named "ColumnCriteriaName". You would create a list of those somewhere in your application. <pre><code>public class FilterOption { public string ColumnNameCriteria { get; set; } } </code></pre> Now its time to create your custom silverlight control. The purpose of this control is the accept a list of FilterOptions and display a set of Radiobuttons. Each button will be a FilterOption value. When the user selects a value, you will get notified. This control will use the Commanding techniques i tried to describe. Add a new control, name it "FilterOptionControl.xaml". The Xaml Code is as follows: <pre><code><UserControl x:Class="SilverlightApplication1.FilterOptionControl" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" mc:Ignorable="d" d:DesignHeight="300" d:DesignWidth="400"> <Grid x:Name="LayoutRoot" Background="White"> <StackPanel x:Name="stacker" /> </Grid> </UserControl> </code></pre> Its just an empty control with a Stackpanel which will hold our RadioButtons which we will create at runtime. Also please note that i will not use MVVM for this custom control, because in this case it would be over-engineering. Of course, feel free to add MVVM to this control if you want to, but i really dont recommend it. You should however use MVVM in your more domain specific controls. Enought talk, lets just paste in the .cs code for your custom control <pre><code>public partial class FilterOptionControl : UserControl { public IEnumerable<FilterOption> AvailableOptions { get { return (IEnumerable<FilterOption>)GetValue(AvailableOptionsProperty); } set { SetValue(AvailableOptionsProperty, value); } } public static readonly DependencyProperty AvailableOptionsProperty = DependencyProperty.Register( "AvailableOptions", typeof(IEnumerable<FilterOption>), typeof(FilterOptionControl), new PropertyMetadata(OnPropertyChangedCallback)); public FilterOption SelectedOption { get { return (FilterOption)GetValue(SelectedOptionProperty); } set { SetValue(SelectedOptionProperty, value); } } public static readonly DependencyProperty SelectedOptionProperty = DependencyProperty.Register( "SelectedOption", typeof(FilterOption), typeof(FilterOptionControl), new PropertyMetadata(OnPropertyChangedCallback)); protected static void OnPropertyChangedCallback(DependencyObject sender, DependencyPropertyChangedEventArgs args) { if (sender is FilterOptionControl) ((FilterOptionControl)sender).OnPropertyChanged(args); } private void OnPropertyChanged(DependencyPropertyChangedEventArgs args) { if (args.Property == AvailableOptionsProperty) { RebuildFilterOptions(); } } public FilterOptionControl() { InitializeComponent(); SelectedValueChangedCommand = new RelayCommand( new Action<object>(this.ChangeSelectedValue)); } RelayCommand SelectedValueChangedCommand; void ChangeSelectedValue(object option) { SelectedOption = option as FilterOption; } private void RebuildFilterOptions() { stacker.Children.Clear(); if (AvailableOptions != null) { foreach (FilterOption option in AvailableOptions) { RadioButton btt = new RadioButton(); btt.Content = option.ColumnNameCriteria; btt.Command = SelectedValueChangedCommand; btt.CommandParameter = option; stacker.Children.Add(btt); } } } } </code></pre> As you can see we have two dependency properties which are both wired up with changed events so we get notified when they get set (this way you could set an initial value for the filter options - however i didnt implement it straight away, youll have to do this yourself). If we get set any FilterOptions on the AvailableOptions Property, we will trigger our build mechanism. We clear the StackPanel and add a new RadioButton for every FilterOption. Additionally we wire up a RelayCommand with this RadioButtons (see <a href="http://msdn.microsoft.com/en-us/magazine/dd419663.aspx#id0090051" rel="nofollow">http://msdn.microsoft.com/en-us/magazine/dd419663.aspx#id0090051</a> for command explanation) and set the CommandParameter to the respective FilterOption. So if a RadioButton gets clicked, this command gets fired with the corresponding FilterOption set as the CommandParameter. We now set the SelectedOption of our control to this new value. The code for the RelayCommand is here, but is taken (and slightly modified) from the msdn link i posted above <pre><code>public class RelayCommand : ICommand { readonly Action<object> _execute; readonly Predicate<object> _canExecute; public RelayCommand(Action<object> execute) : this(execute, null) { } public RelayCommand(Action<object> execute, Predicate<object> canExecute) { if (execute == null) throw new ArgumentNullException("execute"); _execute = execute; _canExecute = canExecute; } public bool CanExecute(object parameter) { return _canExecute == null ? true : _canExecute(parameter); } public event EventHandler CanExecuteChanged; public void Execute(object parameter) { _execute(parameter); } } </code></pre> Now you are ready to use this control on a page as you like. I did it like so in the main page of my test app: <pre><code><UserControl x:Class="SilverlightApplication1.MainPage" *snip* x:Name="me"> <Grid x:Name="LayoutRoot" Background="White"> <StackPanel> <TextBlock Text="{Binding ElementName=filter, Path=SelectedOption.ColumnNameCriteria, FallbackValue='none'}"/> <this:FilterOptionControl x:Name="filter" AvailableOptions="{Binding ElementName=me, Path=MyFilterOptions}" /> </StackPanel> </Grid> </UserControl> </code></pre> and the code behind looks like this: <pre><code>public partial class MainPage : UserControl { public IEnumerable<FilterOption> MyFilterOptions { get { return (IEnumerable<FilterOption>)GetValue(MyFilterOptionsProperty); } set { SetValue(MyFilterOptionsProperty, value); } } public static readonly DependencyProperty MyFilterOptionsProperty = DependencyProperty.Register( "MyFilterOptions", typeof(IEnumerable<FilterOption>), typeof(MainPage), new PropertyMetadata(null)); public MainPage() { InitializeComponent(); MyFilterOptions = new List<FilterOption> { new FilterOption() { ColumnNameCriteria = "One"}, new FilterOption() { ColumnNameCriteria = "Two"}, new FilterOption() { ColumnNameCriteria = "Three"} }; } } </code></pre> I hope that helped. it: Of course, if you still want to use your enums, you can do so too using the FilterOption class, but this code should be a good start for your i hope.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAccessing string value of Enum bound using EnumBoolConverter : IValueConverter
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USUrbanEsc
UserOwnerUserId
1. USUrbanEsc
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.