TiUITableView only fires the \"scroll\" event when the underlying\nscrollView is being dragged. There is actually a check for\nscrollView.isDragging in the scrollViewDidScroll delegate method\naround line 2020. We actually need to be notified at all times that\nthe tableview is scrolling, regardless of whether or not it's being\ndragged. This is standard functionality that is available in native\niOS and allows us to do much more with the UI. It also allows us to\ndeal with the content inset issues when using headerPullview.
\nWhen you listen to a ScrollView's \"scroll\" event you get a\nboolean called \"dragging\" on the event, this should also be\navailable on the TableView's \"scroll\" event. We already modified\nthe Titanium code-base to support this in our project. We removed 3\nlines of code and added one line. The required changes are outlined\nbedlow. Also the documentation for a TableView's \"scroll\" event\nwould need to be updated to show the new boolean \"dragging\".
\nTiUITableView.m
\nGoto line 2020 and into the method -\n(void)scrollViewDidScroll:(UIScrollView *)scrollView
\nRemove the scrollView.isDragging check
\nAdd the following to the event NSMutableDictionary:
\n[event setObject:NUMBOOL([scrollView isDragging])\nforKey:@\"dragging\"];
Best,
\nBrian
I went ahead and made the changes...here is the pull\nrequest:
\nhttps://github.com/appcelerator/titanium_mobile/pull/85
\nThanks,
\nBrian
Hi Brian, I have some problems too with pull to refresh solution\nwith iphone <= 3G, as you mentioned.
\nI implemented your fix and still have some delay on scrollend to\nset some control variables.
Well, I would like to know how you fixed pull to refresh issues\nwith your fix.
\nThanks.
@Thiago,
\nOn your tableView's scroll event you have to check for dragging\nand if it's not dragging but is reloading then you force the\nheaderPullView to show. Here is an example:
\n\ntableView.addEventListener('scroll', function(e) {\n var offset = e.contentOffset.y;\n\n if (e.dragging && !reloading) {\n if (!pulling && offset <= -65.0) {\n pulling = true;\n var t = Ti.UI.create2DMatrix();\n t = t.rotate(-180);\n arrow.animate({transform:t,duration:100});\n statusLabel.text = \"Release to update...\";\n }\n else if (pulling && offset > -65.0 && offset < 0) {\n pulling = false;\n var t = Ti.UI.create2DMatrix();\n arrow.animate({transform:t,duration:100});\n statusLabel.text = \"Pull down to update...\";\n }\n }\n if (!e.dragging && reloading) {\n tableView.scrollToTop(-65, {animated:true});\n }\n});\nOhh, I was doing everything right, except using scrollToTop. I\nwas using the bugged setContentInsets instead of scrollToTop (by\nthe way, if you set animated to true, it goes to the top and then\nthe scroll goes to the desired position - is there a way to fix\nthis [the best solution I found was setting animated to\nfalse]?).
\nThanks! And I hope they can fix all this weird code and all\ndevelopers like us can sleep better in the end of the day.
Ya setting animated to false is probably the best way...glad you\nwere able to get everything working :)