Anyone have trouble clicking the rows in a tableView?

Getting Started Newbie Questions
#1

Hello,

I will write a basic tableView with rows added and add some text to the rows. I have some people with the same phone as me (Samsung Galaxy S4) have trouble clicking the rows. They say they have to click it 5 or 6 times till it reacts. I have had this trouble too but have learned to almost hold my finger down a touch longer so it registers.

Does it matter where you click such as in the empty area compared to over the text added to a row? Anyone have this happen before?

Thanks,

Warren

#2

I have also observed this on two apps of mine that use a tableView for top-level navigation.  I have tried fooling around with the tableView listener, but cannot seem to get the tableView to reliably react to the first tap or touch.

#3

Did you find any result to fix this? It happened for me before so I ended up creating my own tableView with a scrollView widget. I made each row in it the same space with a line separating them and calculated which row was touched by the y value divided by the row height.

I hate to have to do this every time for an app I write. I can’t see how some people has an issue and others do not.

Warren

#4

Hi @warrenwsav, @llc,

By default, there is a slight “delay” for tableView rows, before they register as a touch/tap. This is to prevent an inadvertent selection of the row when the user may desire to scroll the tableView instead.

For some, this delay may seem just a slight amount too long. Fortunately, this property can be adjusted with the “rowTouchDelay” parameter within the tableView constructor. You can experiment which value feels right for your app.

It’s documented here:

http://docs.coronalabs.com/api/library/widget/newTableView.html

Best regards,

Brent

#5

I have also observed this on two apps of mine that use a tableView for top-level navigation.  I have tried fooling around with the tableView listener, but cannot seem to get the tableView to reliably react to the first tap or touch.

#6

Did you find any result to fix this? It happened for me before so I ended up creating my own tableView with a scrollView widget. I made each row in it the same space with a line separating them and calculated which row was touched by the y value divided by the row height.

I hate to have to do this every time for an app I write. I can’t see how some people has an issue and others do not.

Warren

#7

Hi @warrenwsav, @llc,

By default, there is a slight “delay” for tableView rows, before they register as a touch/tap. This is to prevent an inadvertent selection of the row when the user may desire to scroll the tableView instead.

For some, this delay may seem just a slight amount too long. Fortunately, this property can be adjusted with the “rowTouchDelay” parameter within the tableView constructor. You can experiment which value feels right for your app.

It’s documented here:

http://docs.coronalabs.com/api/library/widget/newTableView.html

Best regards,

Brent