StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8769944
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-01-07T13:11:44.480
FavoriteCount
0
LastActivityDate
2012-01-07T13:11:44.480
LastEditDate
LastEditorUserId
0
OwnerUserId
389966
ParentId
8551865
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<p>I ended up with two ways to do this. Both ways use a class that wraps the image and implements <code>INotifyPropertyChanged</code>:</p> <pre><code>class ImageSourceWrapper : ObservableObject { private ImageSource _image; public ImageSource Image { get { return _image; } set { if (value != _image) { _image = value; RaiseOnPropertyChanged("Image"); } } } public ImageSourceWrapper(ImageSource image) { Image = image; } } </code></pre> <h2>First Approach</h2> <p>Once I have this, I can have my markup extension return an <code>ImageSourceWrapper</code> object and bind to it, like so</p> <pre><code><Image Source="{Binding Source={my:ImageProvider ImageName=myImageName}, Path=Image}" /> </code></pre> <p>I didn't really like this way, since it's pretty messy and involves having to know the <code>ImageSourceWrapper</code> class rather than working simply with <code>ImageSource</code>. Then I came up with the second approach.</p> <h2>Second Approach</h2> <p>In this approach I still use the <code>ImageSourceWrapper</code> class, but instead of having my markup extension return an <code>ImageSourceWrapper</code> object, I return a binding object which I set up to be bound to an <code>ImageSourceWrapper</code> object.</p> <p>The markup extension looks something like this:</p> <pre><code>private ImageSourceWrapper _imageSourceWrapper; public override object ProvideValue(IServiceProvider serviceProvider) { // Get the object and the property to be bound. IProvideValueTarget service = IProvideValueTarget)provider.GetService(typeof(IProvideValueTarget)); DependencyObject targetObject = service.TargetObject as DependencyObject; DependencyProperty targetProperty = service.TargetProperty as DependencyProperty; // Set up the binding with the default image. _imageSourceWrapper = new ImageSourceWrapper(DefaultImage); Binding binding = new Binding("Image"); binding.Source = _imageSourceWrapper; BindingOperations.SetBinding(targetObject, targetProperty, binding); // Retrieve the actual image asynchronously. GetImageAsync(); return binding.ProvideValue(serviceProvider); } private void GetImageAsync() { // Get the image asynchronously. // Freeze the image so it could be accessed from all threads regardless // of which thread it was created on. newImage.Freeze(); // Got the image - update the _imageSourceWrapper object. _imageSourceWrapper = newImage; } </code></pre> <p>Then I can use it in XAML like this</p> <pre><code><Image Source="{my:ImageProvider ImageName=myImageName}" /> </code></pre> <p>This way the default image is displayed first, and once the requested image is retrieved, it will be displayed instead.</p> <p><em>Sorry if the code here isn't entirely correct, I'm not near the code at the moment. Hopefully this is enough at the moment to express the main idea.</em></p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODisplaying a default image and changing it once the actual image finished loading
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAdi Lester
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODisplaying a default image and changing it once the actual image finished loading
  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
  VTAcceptedByOriginator
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.