The scrolling backwards seems to be fixed. Thanks. However the behavior of the tableview seems to be a little bit wonky. We are still trying to figure it out and will report back soon.
Thanks,
Mike
It seems that the new isBounceEnabled property implementation in 1149 seems to be causing problems. The first time you load a tabelview object the bounce does not work, when that object gets refreshed it may work… Sometimes it does, sometimes it does not. This is a significant problem for us since we do a pull down to refresh on our home scene and this no longer works reliably. This happens across all platforms…
Corona, do you see this? Anyone else?
Mike
No bounce for me.
@mike: Just tried recreating, seems to work. Are you using the isBounceEnabled in the initializer set to a value, or are you letting it out? Can i see some code, please? Maybe fill in a quick bug report?
Thanks,
Alex
I tried it both with and without .isBounceEnabled set ( and with it set to false as well as true… The behavior seems to be the same regardless. I tried it on the another table view and whether it is set to true or false I got bounce… What is the expected behavior, and is it implemented correctly below?
tableView = Widget.newTableView{
top = SCENE_TOP,
width = Screen.width(),
height = height,
hideBackground = true,
listener = tableViewListener,
friction = 0.92,
noLines = true,
onRowRender = onRowRender,
onRowTouch = onRowTouch
}
tableView:toBack()
tableView.isBounceEnabled = true
Hi Mike,
Please try to set this property “inline” (within the widget declaration, like the other properties) instead of doing it post-creation. That should effect the change you desire. This will be documented in the daily docs in the next couple days.
Thanks,
Brent
I put the property inline and it still does not seem to effect the outcome at all… Same Thing… The first time the object is loaded it appears that bounce is FALSE… If the object is refreshed it sometimes behaves like bounce is True or bounce is False… I have not divined a pattern. On other tableView objects we have, I inserted this parameter and it seems to have no effect at all.
Such as:
tableView = Widget.newTableView{
top = SCENE_TOP + FILTER_TEXTBOX_HEIGHT + TABBAR_HEIGHT,
width = Screen.width(),
height = height,
isBounceEnabled = true,
hideBackground = true,
onRowRender = onRowRender
}
Mike
We implemented a word around that reloads the whole scene which seems to be working for now.
Mike
Hi Mike,
I did some changes in the way that property gets instantiated internally, with a forced check. The modified code should be available in one of the next two daily builds. I think that will fix the issue for good.
Alex
Thanks Alex, I will give it a try as soon as its available.
Mike
Alex, this seems to be completely fixed, thanks so much for taking care of this quickly. Now if you can just get someone from Corona to respond to my post “Android 2.2 HTTP Errors” that has been sitting there for a couple of weeks, I might be able to release my app on time next week.
Thanks,
Mike
Hi Mike,
Glad i could help.
Link of the respective post?
Thanks,
Alex
Err…the elastic table effect is sadly still broken as of 1153.
Good : By default it seems that isBounceEnabled works
Bad : The elastic effect only works while your finger is moving. The moment your finger stops, the row reverts, even though your finger has not lifted from the screen.
(1) This is counter to Apple table functionality where you can stretch indefinitely or even cancel an intended refresh by moving the table back to its original position before lifting.
(2) This causes a constant “judder” effect because on any given frame where movement is not detected, the table row is attempting to slide up. Touch movement constantly varies in speed so it seems to judder up and down as you drag.
Hi Richard,
Looking at this.
Alex
Alex; just worth noting that in my current project, what seems to be happening is that Corona is returning phase == “cancelled” if the user attempts to move their finger while touching a row (constantly)
Alex… Another really bad bug that has cropped up with the this build is that the touch handler is dying on the Tableview after the phone has been asleep. It is happening on iOS as well as Android. Has anyone else seen this… The tableview in question is the same one that was having problems above…
Mike
Hey Mike,
Please post a bug report. I’ll look at it ASAP. I’m already looking into the existing issue on the thread.
Thanks!
Alex
mike, I’m not seeing the touch handler dying (iOS), works the same before or after phone sleep. (Of course, it still has the same bug though)
Alex I submitted a Bug. We are going to try a couple of workarounds and will get back to you. Thanks,
Mike