New daily build breaks ScrollView widget’s getContentPosition()

Solar2D Widgets
#1

Astute Corona developers will have noticed that yesterday’s daily build 2014.2481 includes a *lot* of changes and fixes to the widget library, especially scrollviews. One of those changes is listed as fixing a getContentPosition() bug, casenum 34675.

Unfortunately those changes have broken the scrollview widget in a different way. Previously when a user pulled down the scrollview from the top — the standard app refresh gesture — the content position returned would be a positive number. Now the content position returned is always 0.

Here is the output of pull-down-to-refresh from a daily build a week ago:

Version 2014.2472 (2014.10.23) 2014-10-30 14:45:02.441 Corona Simulator[60376:507] debug: y position is: 322| y contentPosition is: 36.5 2014-10-30 14:45:02.458 Corona Simulator[60376:507] debug: y position is: 324| y contentPosition is: 37.5 2014-10-30 14:45:02.475 Corona Simulator[60376:507] debug: y position is: 328| y contentPosition is: 39.5 2014-10-30 14:45:02.492 Corona Simulator[60376:507] debug: y position is: 331| y contentPosition is: 41 2014-10-30 14:45:02.510 Corona Simulator[60376:507] debug: y position is: 332| y contentPosition is: 41.5 2014-10-30 14:45:02.526 Corona Simulator[60376:507] debug: y position is: 335| y contentPosition is: 43

Here is the output of pull-down-to-refresh from the latest broken daily build:

Version 2014.2482 (2014.10.30) 2014-10-30 14:37:14.543 Corona Simulator[59951:507] debug: y position is: 325| y contentPosition is: 0 2014-10-30 14:37:14.560 Corona Simulator[59951:507] debug: y position is: 328| y contentPosition is: 0 2014-10-30 14:37:14.577 Corona Simulator[59951:507] debug: y position is: 330| y contentPosition is: 0 2014-10-30 14:37:14.593 Corona Simulator[59951:507] debug: y position is: 332| y contentPosition is: 0 2014-10-30 14:37:14.611 Corona Simulator[59951:507] debug: y position is: 335| y contentPosition is: 0 2014-10-30 14:37:14.628 Corona Simulator[59951:507] debug: y position is: 337| y contentPosition is: 0 2014-10-30 14:37:14.644 Corona Simulator[59951:507] debug: y position is: 338| y contentPosition is: 0

I’m grateful to the Corona folks for addressing some of these long-standing widget issues, and it seems as though the scrollview is smoother in terms of performance. But it would sure be nice if a daily build later this week would fix this newly-introduced content position bug.

While I’m at it, can we have the mysteriously disappeared endedScroll event restored? It’s approaching a year: http://forums.coronalabs.com/topic/43778-restoring-deleted-scrollview-feature-endedscroll-event/ Thanks in advance. :slight_smile:

#2

PS: Also posted to the daily build forum here: http://forums.coronalabs.com/topic/52326-new-daily-build-breaks-scrollview-widget%E2%80%99s-getcontentposition/

#3

Fixes to the widget library are always welcome but it seems like this one is a bummer. Hope it does not take another 3 months to undo the new bug. 

Also +1 on bringing back the mysteriously disappeared endedScroll event before the anniversary of its disappearance. 

#4

Engineering is working on it. 

#5

Thanks, Rob. The two daily builds since my post on Thursday have not yet included a fix, so hopefully it’ll happen soon…

#6

You have to give engineering time.  You reported it on Thursday, I alerted Engineering on Friday.  Its now the weekend. 

Rob

#7

Rob: Much obliged for your reply. It’s been a week and a half and you’ve released 8 daily builds since this thread began. The scrollView doesn’t seem to be fixed in the latest, 2014.2496. Can I trouble you to give us a hint as to when this bug will be fixed? Thanks!

#8

Aha!

https://developer.coronalabs.com/corona-daily-builds/summary

"Widget 2.0: Fixing a regression issue affecting the pull to refresh functionality on scrollviews. No casenum. "

#9

I’m on daily build 2511 and getContentPosition() still doesn’t seem to be working.  Is this just me or are people still having issues with this?  

#10

I found that this works for me in place of the getContentPosition function 

object._view.y

object._view.x

(object being the name of your scrollview)

Should return the current position of the scroll view…at least it does for me.  So while getposition is down you can substitute that in your code.

#11

PS: Also posted to the daily build forum here: http://forums.coronalabs.com/topic/52326-new-daily-build-breaks-scrollview-widget%E2%80%99s-getcontentposition/

#12

Fixes to the widget library are always welcome but it seems like this one is a bummer. Hope it does not take another 3 months to undo the new bug. 

Also +1 on bringing back the mysteriously disappeared endedScroll event before the anniversary of its disappearance. 

#13

Engineering is working on it. 

#14

Thanks, Rob. The two daily builds since my post on Thursday have not yet included a fix, so hopefully it’ll happen soon…

#15

You have to give engineering time.  You reported it on Thursday, I alerted Engineering on Friday.  Its now the weekend. 

Rob

#16

Rob: Much obliged for your reply. It’s been a week and a half and you’ve released 8 daily builds since this thread began. The scrollView doesn’t seem to be fixed in the latest, 2014.2496. Can I trouble you to give us a hint as to when this bug will be fixed? Thanks!

#17

Aha!

https://developer.coronalabs.com/corona-daily-builds/summary

"Widget 2.0: Fixing a regression issue affecting the pull to refresh functionality on scrollviews. No casenum. "

#18

I’m on daily build 2511 and getContentPosition() still doesn’t seem to be working.  Is this just me or are people still having issues with this?  

#19

I found that this works for me in place of the getContentPosition function 

object._view.y

object._view.x

(object being the name of your scrollview)

Should return the current position of the scroll view…at least it does for me.  So while getposition is down you can substitute that in your code.

#20

Inductiveldeas, thanks man! :slight_smile:

GetContentPosition still not working on Version 2015.2551 (2015.2.5)

Thanks again :slight_smile: