The other day I was working on a Windows Phone app. I wanted to add a “pull down to refresh” panel to a large list of images. Just like the Facebook and Twitter apps have. As Microsoft does not provide this functionality in their default controls I started searching the web if somebody else has build something like this already.
I found a blog post by Jason Ginchereau where he provided this functionality for Windows Phone 7.
In my app I use an ItemsControl with a VirtualizingStackPanel to prevent memory issues. After I added the PullDownToRefreshPanel control to my list and started testing it on my phone, I ran into some issues.
Adding the control to my page was easy. But I noticed two things.
- Performance, it’s taking up a lot of processing power, resulting in visual lag. Specially when using a low powered phone.
- Scrolling, when scrolling through the list with a quick flicking motion the same images kept scrolling by, making the list scroll endlessly until I stopped flicking
In this blog post I will describe my contributions to fix these 2 issues and I will supply the source code for you to use.
1. Improving performance
Looking at the code, the first thing I noticed was that the control subscribes to the LayoutUpdated event. The code in the event handler tries to find the ScrollViewer control to attach to. After the ScrollViewer is successfully found, the event is never unsubscribed and keeps firing quite often. When you add a debug message to the method you’ll see the event fires constantly during the actual scrolling, but also fires when the control is not even on the screen. So the first fix was to unregister the event if the ScrollViewer is found. There is no need to fire unnecessary code.
private void PullDownToRefreshPanel_LayoutUpdated(object sender, EventArgs e)
if (this.targetScrollViewer == null)
if (this.targetScrollViewer != null)
this.LayoutUpdated -= PullDownToRefreshPanel_LayoutUpdated;
The second thing I observed were the NegativeValueConverters. The ValueConvertor adds negative space at the bottom to keep the ScrollViewer positioned on the same location if the PullDownToRefreshPanel was growing in height.
Inside the convertor there is an unnecessary Convert from Object to Double. When resizing the control this conversion was called a lot of times. So this could be written a bit simpler as the value is already of the type Double.
//double doubleValue = -System.Convert.ToDouble(value);
double doubleValue = -(double)value; // No System.Convert needed
When looking at the original example project by Jason, the negative space was needed because the control and the list are in separate rows in a grid. By changing the XAML to put both controls in the same grid cell there is no need for this negative space because the controls are now floating on top of each other. Eliminating the ValueConvertors all together made the process much lighter.
My XAML looks a bit like this:
<VirtualizingStackPanel Orientation="Vertical" />
2. Fixing the scrolling
To make the pull-to-refresh list work, it’s mandatory to change the ManipulationMode property of the ScrollViewer to “Control“. This allows you to catch the MouseMove event and the MouseLeftButtonUp event. With these events you can detect the change of the position of the content inside the ScrollViewer by monitoring the TranslateY property which changes when the compression happens.
Because I noticed the same images kept scrolling by, I was suspecting the VirtualizingStackPanel was not receiving the correct signals and was recycling the same placeholders (and images) over and over without getting fresh data as it should.
Searching the web again I came across a blog post by Matthijs Krempel describing that the Mango update added some new candy that would allow you to detect the compression using VisualStates and therefore you can leave the ManipulationMode on “System”. Resulting in a better performance and in a correctly functioning VirtualizingStackPanel. This does not work out-of-the-box, you need to add a specific template to the ScrollViewer.
Matthijs added this to his own “PullToRefreshPanel” control.
However, the VisualStates let you only know if compression has started or ended. It doesn’t let you know how much compression is applied. Without the mouse events I needed another way to detect the amount of compression. Which led me to build my own version of the control.
Building a new Pull-Down-To-Refresh Panel
Windows Phone provides the Touch class which is an application-level service that processes touch input from the operating system and raises the FrameReported event. Inside this event you can read what kind of interaction is happening between the fingers and the screen.
private void TouchFrameReported(object sender, TouchFrameEventArgs e)
var primaryTouchPoint = e.GetPrimaryTouchPoint(this);
this.initialPoint = primaryTouchPoint.Position;
// Only update if the finger moves up/down the screen
if (this.currentPosition.Y != primaryTouchPoint.Position.Y)
this.currentPosition = primaryTouchPoint.Position;
this.initialPoint = primaryTouchPoint.Position;
So I combined the control Jason originally wrote with the extensions Matthijs made to detect compression. Then I replaced the mouse events with touch actions. Resulting in a faster control that also works with virtualized controls like an ItemsControl with a VirtualizingStackPanel or the ListBox.
I’ll have to note that the PullDownToRefreshPanel control will not work with the LongListSelector as that control does not expose a ScrollViewer.
You can download my Windows Phone 8 example project on GitHub.