-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
indexPath in didSelectRowAtIndexPath #30
Comments
The way to "solve" the issue is adding [tableView reloadData] at the end of didSelectRowAtIndexPath. |
That doesn't sound right. You really don't want to be reloading the table data after making a selection. Have you looked at the demo project to see how to use it in a table. I can't imagine why using KILabel would affect selection of table cells. |
Yes, I know it doesn't sound right but it was the only way to get KILabel working. I looked at the demo project and all the examples available and all looks right. The thing is, if it was my mistake, why with the reloadData worked? |
I have exactly the same problem. It seems like a bug. |
I ran into this same issue. It has to do with the way touchesBegan/Moved/Ended/Cancelled have been implemented. I was able to resolve the issue by using a UITapGestureRecognizer in lieu of overriding the touch event methods. |
@nyeu @vgolovnev @dayj |
Thanks @dayj |
I have a tableview where cells display a KILabel, when I tapped a cell (not the kilabel link), I get the wrong indexpath, I get the previous indexPath selected.
If I remove the kilabel, everything works like a charm.
The text was updated successfully, but these errors were encountered: