StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2641294
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-04-14T21:48:47.120
FavoriteCount
0
LastActivityDate
2010-04-14T21:54:03.803
LastEditDate
2010-04-14T21:54:03.803
LastEditorUserId
199245
OwnerUserId
199245
ParentId
2631648
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
A different solution I use a very different solution for this situation that I think is much cleaner. Using a couple of utility classes I created I can bind the SelectedOptions directly without having to write application code to deal with commands, collection updates, etc. EnumExpansion class I created a simple class with the following signature: <pre><code>public class EnumExpansion : DependencyObject, IList, INotifyCollectionChanged { public object EnumValue { ... // DependencyProperty ... // IList & INotifyCollectionChanged implementation } </code></pre> EnumValue can be set to any enum type. When EnumValue is set, the internal ObservableCollection is updated by removing all flags not in the current EnumValue and adding all flags in the current EnumValue. Whenever the internal collection is changed, EnumValue is updated. BindableSelectedItems property I also created a simple attached property that allows ListBox to bind its SelectedItems property. It is used like this: <pre><code><ListBox ItemsSource="{Binding Options}" edf:ListBoxHelper.BindableSelectedItems="{Binding SelectedOptionsExpansion}" /> </code></pre> The attached property is implemented by subscribing to SelectionChanged on the ListBox and CollectionChanged on the property value (which is of type INotifyCollectionChanged). Initializing SelectedOptionsExpansion You can do this in XAML but it is quite easy in code: <pre><code>public EnumExpansion SelectedOptionsExpansion { get; set; } ... SelectedOptionsExpansion = new EnumExpansion(); BindingOperations.SetBinding(SelectedOptionsExpansion, EnumExpansion.EnumValueProperty, new Binding { Path = "SelectedOptions", Source = this }); ... </code></pre> How it works Enum to ListBox: <ol> <li>SelectedOptions changes, either via code or data binding</li> <li>The SelectedOptionsExpansion's EnumValue property is updated by the binding, which causes the EnumExpansion's collection to change.</li> <li>The CollectionChange event is picked up by the ListBoxHelper code which updates the selection in the ListBox.</li> </ol> ListBox to Enum: <ol> <li>An item is selected or deselect in the ListBox</li> <li>ListBoxHelper picks it up and updates the EnumExpansion collection, which causes the EnumValue property to update.</li> <li>Since EnumValue is BindsTwoWayByDefault, the SelectedOptions value is updated.</li> </ol> Why I prefer this solution Once the two utility classes are created, the rest of the binding process is straightforward data binding. There is no need to handle commands or update collections in your application code - it is all hidden within the utility classes.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to deal with calculated values with Dependency Properties on a custom WPF control
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRay Burns
UserOwnerUserId
1. USRay Burns
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.