Its great that the pull-down refresh is working. ...please don't shoot me when I tell you that it 'refreshes' too easily... I see two small problems with the pull-down refresh: While you are scrolling up and down through your CONTACTS or INBOX; you do not know that you have reached the top until you scroll into the blank area. Which means you have a good chance of triggering the refresh. Doing a flicking action, scrolling continues after the user has stopped touching it, and this can also accidentally cause a refresh. For the first, we need some kind of TOP-OF-LIST marker. For the second, I'm hoping 'Flickable.DragOverBounds' is the answer. I did some Googling and found:The boundsBehavior can be one of:Flickable.StopAtBounds - the contents can not be dragged beyond the boundary of the flickable, and flicks will not overshoot. Flickable.DragOverBounds - the contents can be dragged beyond the boundary of the Flickable, but flicks will not overshoot. Flickable.DragAndOvershootBounds (default) - the contents can be dragged beyond the boundary of the Flickable, and can overshoot the boundary when flicked.
The boundsBehavior can be one of:Flickable.StopAtBounds - the contents can not be dragged beyond the boundary of the flickable, and flicks will not overshoot. Flickable.DragOverBounds - the contents can be dragged beyond the boundary of the Flickable, but flicks will not overshoot. Flickable.DragAndOvershootBounds (default) - the contents can be dragged beyond the boundary of the Flickable, and can overshoot the boundary when flicked.