Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-2622] Android: Add scroll end event to scroll views

GitHub Issuen/a
TypeNew Feature
PriorityMedium
StatusClosed
ResolutionNeeds more info
Resolution Date2011-04-15T03:25:07.000+0000
Affected Version/sn/a
Fix Version/sBacklog
ComponentsAndroid
Labelsandroid, feature, rplist, scrollview
ReporterBill Dawson
AssigneeBill Dawson
Created2011-04-15T03:25:06.000+0000
Updated2017-03-16T20:41:47.000+0000

Description

cf #2422 re iOS, feature request from customer

Comments

  1. Bill Dawson 2011-04-15

    Unless I'm missing something really hacky and tricky that we could do, I don't see any way to implement this in Android. We get the scroll event easily thanks to Android View.onScrollChanged. For our TableView, we can get scrollEnd easily thanks to Android ListView.setOnScrollListener, the listener for which contains onScrollStateChanged, which can be checked for SCROLL_STATE_IDLE. But for non-ListView scrollers such as the ScrollView, this doesn't exist.

    Hacky solutions like maybe checking for the first touch UP event after a onScrollChanged event -- meaning the user has lifted their finger after a scroll -- wouldn't take into account that the view still may be flinging, and also wouldn't account for a scroll caused by the trackpad.

    In short, I can't think of any way to do this. Any ideas out there in Donland?

  2. Don Thorp 2011-04-15

    Moving to M05 to see if I can find away around it.

  3. Don Thorp 2011-04-15

    There is some discrepancy about what this event is suppose to do. It appears that it was put in iOS to deal with pull for refresh. Android doesn't have "overscroll" until API 9. Moving to TBS until we can resolve what the event is suppose to do on both platforms.

  4. Rick Blalock 2011-04-15

    iOS ticket can be tracked here: https://appcelerator.lighthouseapp.com/projects/32238-titanium-mobile/tickets/2975-ios-scroll-end-view-consistency-parity-with-android"> https://appcelerator.lighthouseapp.com/projects/32238-titanium-mobi...

  5. Lee Morris 2017-03-16

    Closing ticket as the information that was requested was never provided.

JSON Source