|
2012-06-30
, 21:18
|
Posts: 435 |
Thanked: 769 times |
Joined on Apr 2010
|
#2
|
The Following User Says Thank You to gionni88 For This Useful Post: | ||
|
2012-07-01
, 04:39
|
Posts: 650 |
Thanked: 619 times |
Joined on Nov 2009
|
#3
|
Check flicking bool property: http://doc.qt.nokia.com/4.7-snapshot...#flicking-prop
|
2012-07-01
, 07:12
|
Posts: 435 |
Thanked: 769 times |
Joined on Apr 2010
|
#4
|
onVerticalVelocityChanged: console.debug(verticalVelocity)
The Following User Says Thank You to gionni88 For This Useful Post: | ||
|
2012-07-01
, 09:52
|
Posts: 456 |
Thanked: 1,580 times |
Joined on Dec 2009
|
#5
|
The Following User Says Thank You to Wonko For This Useful Post: | ||
|
2012-07-01
, 16:37
|
Posts: 650 |
Thanked: 619 times |
Joined on Nov 2009
|
#6
|
|
2012-07-03
, 07:18
|
Posts: 650 |
Thanked: 619 times |
Joined on Nov 2009
|
#7
|
Page { property bool bannerStart: false ListView { onContentYChanged: { if (bannerStart && (contentY <= params.bannerMargin)) showPullDownItem(); } onMovementStart: { if (contentY==0) bannerStart = true; else bannerStart = false; } onVerticalVelocityChanged: { // Prevent triggering pulldown item when rebound from top boundary. if (verticalVelocity>0) bannerStart = false; } onMovementEnded: { bannerStart = false; // trigger timer to hide pull-down item timer.restart(); } } }
I have googled and saw some pull-down implementations are triggered by "onMovementEnded". However, I don't like the solution because there is a significant delay before the pull-down item is invoked.