Build 1149 busts Elastic Behaviour

Working on a bug report, but simply put, as of 1149 you can no longer scroll past the top or bottom row item. The “elastic” stretch where you might, say, put a refresh function is gone entirely, and the widget just locks the scrolling at the row bottom/top (depending if you scroll down or up). 

Default height/width also appear to be busted…filing…

Filed as #24411, highly recommend anyone using this particular widget to consider rolling back, maybe even prior to all the widget fixes as clearly something broke.

Hi @richard9,

This is actually a new boolean feature as of 1149 called “isBounceEnabled”. This feature will be documented in the daily build docs probably today at some time.

Thanks,

Brent

Er…why not set a bounce friction then? I mean, the widget already has some bounce variance compared to most iOS apps, so having a tweak able strength (where 1 == no bounce) might work out better overall?

Also; any idea why that has been set to off by default?

EDIT: Just fueling my own thread at this point, but in general it would make sense to set defaults to match iOS typical functionality, no?

Not that I want to beat a dead horse…but isBounceEnabled is not an active boolean in builds 1149 and 1150.

This is probably why I received an email confirming knowledge of the problem. :slight_smile:

Same thing is being discussed here (end of thread): http://forums.coronalabs.com/topic/36268-tableview-scrolling-backwards/

Thanks jon, posted in that thread, still busted as of 1153

Default height/width also appear to be busted…filing…

Filed as #24411, highly recommend anyone using this particular widget to consider rolling back, maybe even prior to all the widget fixes as clearly something broke.

Hi @richard9,

This is actually a new boolean feature as of 1149 called “isBounceEnabled”. This feature will be documented in the daily build docs probably today at some time.

Thanks,

Brent

Er…why not set a bounce friction then? I mean, the widget already has some bounce variance compared to most iOS apps, so having a tweak able strength (where 1 == no bounce) might work out better overall?

Also; any idea why that has been set to off by default?

EDIT: Just fueling my own thread at this point, but in general it would make sense to set defaults to match iOS typical functionality, no?

Not that I want to beat a dead horse…but isBounceEnabled is not an active boolean in builds 1149 and 1150.

This is probably why I received an email confirming knowledge of the problem. :slight_smile:

Same thing is being discussed here (end of thread): http://forums.coronalabs.com/topic/36268-tableview-scrolling-backwards/

Thanks jon, posted in that thread, still busted as of 1153