StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14246367
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-09T20:59:44.937
FavoriteCount
0
LastActivityDate
2013-01-09T20:59:44.937
LastEditDate
LastEditorUserId
0
OwnerUserId
9664
ParentId
2668987
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
This is a bit of an old question, but it could use some explanation. From the <a href="http://msdn.microsoft.com/en-us/library/system.windows.data.bindingbase.fallbackvalue.aspx">FallbackValue documentation</a>: <blockquote> A binding returns a value successfully if: <ol> <li>The path to the binding source resolves successfully.</li> <li>The value converter, if any, is able to convert the resulting value.</li> <li>The resulting value is valid for the binding target (target) property.</li> </ol> If 1 and 2 return DependencyProperty.UnsetValue, the target property is set to the value of the FallbackValue, if one is available. If there is no FallbackValue, the default value of the target property is used. </blockquote> In the example provided, the binding successfully resolves to the <code>Hurr</code> and <code>Durr</code> properties. Null is valid value for a string which means the binding is valid. In other words, the FallbackValue is used when the binding is unable to return a value and in the example provided, the binding does provide a valid value. Take for example each of the following snippets that are based off the original example: Example 1 The Hurr and Durr properties are bound correctly; null is a valid value and the FallbackValue will never be seen. <pre><code><TextBlock> <TextBlock.Text> <MultiBinding FallbackValue="Binding is valid. I will never be seen." StringFormat="{}{0} to the {1}"> <Binding Path="Hurr" /> <Binding Path="Durr" /> </MultiBinding> </TextBlock.Text> </TextBlock> </code></pre> Example 2 The Hurr and Durr properties are not bound correctly; the FallbackValue will be seen. <pre><code><TextBlock> <TextBlock.Text> <MultiBinding FallbackValue="Binding paths are invalid. Look at me." StringFormat="{}{0} to the {1}"> <Binding Path="xHurr" /> <Binding Path="xDurr" /> </MultiBinding> </TextBlock.Text> </TextBlock> </code></pre> Example 3 If one binding path is invalid, then the FallbackValue will be seen. <pre><code><TextBlock> <TextBlock.Text> <MultiBinding FallbackValue="One binding path is invalid. Look at me." StringFormat="{}{0} to the {1}"> <Binding Path="xHurr" /> <Binding Path="Durr" /> </MultiBinding> </TextBlock.Text> </TextBlock> </code></pre> Example 4 As with previous examples, the binding is correct, so the FallbackValue will not be used. Further, the FallbackValue for each of the child <code>Binding</code> properties of the <code>MultiBinding</code> parent should refer to a FallbackValue to be used for the target property of the MultiBinding, not for the child Bindings. <pre><code><TextBlock xmlns:base="clr-namespace:System.Windows;assembly=WindowsBase"> <TextBlock.Text> <MultiBinding FallbackValue="Binding is valid. I will never be seen." StringFormat="{}{0} to the {1}"> <Binding FallbackValue="{x:Static base:DependencyProperty.UnsetValue}" Path="Hurr" /> <Binding FallbackValue="{x:Static base:DependencyProperty.UnsetValue}" Path="Durr" /> </MultiBinding> </TextBlock.Text> </TextBlock> </code></pre> Example 5 The binding is still valid even though a path is not provided in <code>Binding</code> properties since the binding will use whatever object it is bound to. <pre><code><TextBlock xmlns:base="clr-namespace:System.Windows;assembly=WindowsBase"> <TextBlock.Text> <MultiBinding FallbackValue="Binding is still valid. I will never be seen." StringFormat="{}{0} to the {1}"> <Binding FallbackValue="{x:Static base:DependencyProperty.UnsetValue}" /> <Binding FallbackValue="{x:Static base:DependencyProperty.UnsetValue}" /> </MultiBinding> </TextBlock.Text> </TextBlock> </code></pre> Example 6 Finally, if a converter is added to any of the Binding properties to force an UnsetValue, then the MultiBinding FallbackValue will be seen: Converter <pre><code>internal class ForceUnsetValueConverter : IValueConverter { #region Implementation of IValueConverter public object Convert( object value, Type targetType, object parameter, CultureInfo culture ) { return DependencyProperty.UnsetValue; } public object ConvertBack( object value, Type targetType, object parameter, CultureInfo culture ) { throw new NotImplementedException(); } #endregion } </code></pre> XAML <pre><code><TextBlock> <TextBlock.Text> <MultiBinding FallbackValue="Binding is valid, but look at me. I'm an UnsetValue." StringFormat="{}{0} to the {1}"> <Binding Converter="{StaticResource ForceUnset}" Path="Hurr" /> <Binding Path="Durr" /> </MultiBinding> </TextBlock.Text> </TextBlock> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow does FallbackValue work with a MultiBinding?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMetro Smurf
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow does FallbackValue work with a MultiBinding?
 singulars
 PostTypePostTypeId
 PTQuestion
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. 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.