[TIMOB-16837] TiAPI: Add property to support Inverted ListView (similar to Skype)
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | Low |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | Release 3.2.2 |
| Fix Version/s | n/a |
| Components | TiAPI |
| Labels | n/a |
| Reporter | Lev |
| Assignee | Unknown |
| Created | 2014-04-04T10:21:07.000+0000 |
| Updated | 2018-02-28T20:04:11.000+0000 |
Please take a look at TIMOB-16244 and let us know if that would suffice for your use case.
Having scroll in listview would help me to trigger LoadMore, but still one problem remains - with appending/deleting items from list. When I scroll up and LoadMore is triggered, I add some items to the top. Here the problem is that after items are added, list automatically jumps to the top of block I've added (i.e. scroll position remains constant, relatively to top). Then I need to scroll back down (scrollToItem). That jumping looks weird though.
If you use InsertItemAt() method to add the item to the end of the ListView (similar to Skype) then the list should not jump to the top. Do you have a test case to demonstrate this issue?
Anything what adds/removes items/sections from list could work in 2 different ways - remain scroll position of count from Top, or from Bottom (or somewhere in the middle - also possible). Now it's always Top. Here's code:
listSections = getListSections(); // sections, which I'm going to add to the top of the list, total height is about 2000 _lv.insertSectionAt(0, listSections, {animated: false}); // when I do that, the top item I see is the one which is section == 0, index == 0. However as my list grows from bottom to top, I expect to stay at the same position, not to miss anything what was added // To compensate that, I scroll it back down _lv.scrollToItem(listSections.length, 0, {animated: false});setTimeout(function() {_lv.scrollToItem(listSections.length, 0, {animated: false}); }, 0);Moving this improvement request to engineering for further evaluation and prioritization.
This feature would be very useful for our app - we have implemented 2 "iMessage" style pages. Just to add to this, the documented Android bug that stops "scroll to item" working makes it impossible to add a new item and guarantee that it has been scrolled into view. http://docs.appcelerator.com/titanium/3.0/#!/api/Titanium.UI.ListView-method-scrollToItem "On Android 4.x, the list does not stop at the correct position. This is a known bug in Android. (Android Issue #37278)"