StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2458943
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-03-16T23:32:00.180
FavoriteCount
0
LastActivityDate
2010-03-17T10:23:19.867
LastEditDate
2010-03-17T10:23:19.867
LastEditorUserId
281678
OwnerUserId
281678
ParentId
2451326
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
It's worth pointing out that the converter the other posts reference already exists, which is why you can do <code><Ellipse Fill="red"></code> in xaml in the first place. The converter is <code>System.Windows.Media.BrushConverter</code>: <pre><code> BrushConverter bc = new BrushConverter(); Brush brush = (Brush) bc.ConvertFrom("Red"); </code></pre> The more efficient way is to use the full syntax: <pre><code>myEllipse.Fill = new SolidColorBrush(Colors.Red); </code></pre> EDIT in response to -1 and comments: The code above works perfectly fine in code, which is what the original question was asking about. You also don't want an <code>IValueConverter</code> - these are typically used for binding scenarios. A <code>TypeConverter</code> is the right solution here (because you're one-way converting a string to a brush). See <a href="http://bryantlikes.com/SilverlightIValueConverterVsTypeConverter.aspx" rel="noreferrer">this article</a> for details. Further edit (having reread Aviad's comment): you don't need to explicitly use the <code>TypeConverter</code> in Xaml - it's used for you. If I write this in Xaml: <pre><code><Ellipse Fill="red"> </code></pre> ... then the runtime automagically uses a <code>BrushConverter</code> to turn the string literal into a brush. That Xaml is essentially converted into the equivalent longhand: <pre><code><Ellipse> <Ellipse.Fill> <SolidColorBrush Color="#FFFF0000" /> </Ellipse.Fill> </Ellipse> </code></pre> So you're right - you can't use it in Xaml - but you don't need to. Even if you had a string value that you wanted to bind in as the fill, you don't need to specify the converter manually. This test from Kaxaml: <pre><code><Page xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:s="clr-namespace:System;assembly=mscorlib"> <Page.Resources> <s:String x:Key="col">Red</s:String> </Page.Resources> <StackPanel> <Ellipse Width="20" Height="20" Fill="{Binding Source={StaticResource col}}" /> </StackPanel> </Page> </code></pre> Strangely, you can't just use the <code>StaticResource col</code> and still have this work - but with the binding it and automatically uses the <code>ValueConverter</code> to turn the string into a brush.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWPF Binding to change fill color of ellipse
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDan Puzey
UserOwnerUserId
1. USDan Puzey
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThis does not answer the question, the `BrushConverter` does not implement `IValueConverter` so you cannot use it in XAML.
 singulars
 PostPostId
 PO
 UserUserId
 USAviad P.
2. COEdited my answer rather than replying here because I think it's worth pointing out why I'm right in detail...
 singulars
 PostPostId
 PO
 UserUserId
 USDan Puzey

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.