A long while back it seemed like the new cool app thing to do was to represent people/avatars in circles instead of the squares (or squares with rounded corners). I made a snarky comment about this myself almost exactly 2 years ago when I noticed that some apps I was using at the time switched to this:
Seeing a trend that the new avatar shape in apps is a circle and no longer square— Tim Heuer (@timheuer) March 23, 2013
Now since this seems to be a popular trend and people are doing it I’ve thought XAML folks have figured it out. However I’ve seen enough questions and some people trying to do a few things that make it more complex that I thought I’d drop a quick blog post about it. I’ve seen people trying to do profile pic upload algorithms that clip the actual bitmap and save on disk before displaying it to people stacking transparent PNG ‘masking’ techniques. None of this is needed for the simplest display. Here you go:
<Ellipse Width="250" Height="250"> <Ellipse.Fill> <ImageBrush ImageSource="ms-appx:///highfive.jpg" /> </Ellipse.Fill> </Ellipse>
That’s it. You’ll see that Line 3 shows us using an ImageBrush as the fill for an Ellipse. Using an Ellipse helps you get the precise circular drawing clip without having pixelated edges or anything like that. The above would render to this image as the example in my app:
Now while this is great, using an ImageBrush doesn’t give you the automatic decode-to-render-size capability that was added in the framework in Windows 8.1.
NOTE: This auto decode-to-render-size feature basically only decodes an Image to the render size even if the image is larger. So if you had a 2000x2000px image but only displayed it in 100x100px then we would only decode the image to 100x100px size saving a lot of memory. The standard Image element does this for you.
For most apps that control your image sources, you probably are already saving images that are only at the size you are displaying them so it may be okay. However for apps like social apps or where you don’t know where the source is coming from or your app is NOT resizing the image on upload, etc. then you will want to ensure you save memory by specifying the decode size for the ImageBrush’s source specifically. This is easily done in markup using a slightly more verbose image source syntax. Using the above example it would be modified to be:
<Ellipse Width="250" Height="250"> <Ellipse.Fill> <ImageBrush> <ImageBrush.ImageSource> <BitmapImage DecodePixelHeight="250" DecodePixelWidth="250" UriSource="ms-appx:///highfive.jpg" /> </ImageBrush.ImageSource> </ImageBrush> </Ellipse.Fill> </Ellipse>
No real change other than telling the framework what the decode size should be in Line 5 using DecodePixelHeight and DecodePixelWidth. The rendering would be the same in my case. This tip is very helpful to when you are most likely going to be displaying a smaller image than the source and not the other way around.
So there you go. Go crazy with your circular people representations! Hope this helps.