Databases
StackOverflow2013
Postsdbo
POdidSelectRowAtIndexPath: not being called
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POdidSelectRowAtIndexPath: not being called
    primarykey
    data
    text
    <p>I have a <code>UITableView</code> as a subview of my <code>UIScrollVIew</code>, which is the main view controlled by my <code>MainViewController</code>. </p> <p>In MainViewController.h</p> <pre><code>@interface MainViewController : UIViewController &lt;UIGestureRecognizerDelegate, UITableViewDelegate, UITableViewDataSource&gt; // other stuff here... @property (weak, nonatomic) IBOutlet UITableView *myTableView; </code></pre> <p>In MainViewController.m</p> <pre><code>@synthesize myTableView; // other stuff here... - (void)viewDidLoad { myTableView.delegate = self; myTableView.datasource = self; } // other stuff here... -(void)tableView:(UITableView *)tableView didSelectRowAtIndexPath: (NSIndexPath *)indexPath { [self performSegueWithIdentifier:@"listAttributesSegue" sender:self]; } </code></pre> <p>I know that <code>didSelectRowAtIndexPath</code> is not being called because I have set breakpoints on both the method itself and the line of code inside it, and neither is being called. I also know that the datasource is working correctly because I have other functions which modify the cells at runtime and they are working perfectly fine. I am using the latest Xcode with iOS 5.0 set as the development target. I have searched and searched for an answer. Anyone have any ideas?</p> <p><strong>Edit:</strong> I have found the answer. I had a <code>UITapGestureRecognizer</code> set for myTableView's superView. This overrode the selection call. Credit to whoever suggested that that might be it. Your answer was deleted before I could mark it correct.</p> <p><strong>Edit 2:</strong> A lot of people have been commenting about this, so I though I would share it. If you are experiencing this problem, simply set <code>myGestureRecognizer.cancelsTouchInView</code> to <code>false</code> and everything should work fine.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGarrett
    1. USGarrett
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POdidSelectRowAtIndexPath: not being called
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POdidSelectRowAtIndexPath: not being called
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POdidSelectRowAtIndexPath: not being called
      1. USmeggy.meng
      1. VTFavorite
    1. CODid you implement `tableView:willSelectRowAtIndexPath:`? Maybe it's returning nil thus preventing `didSelectRowAtIndexPath:` from calling?
      singulars
      1. POdidSelectRowAtIndexPath: not being called
      1. USKyr Dunenkoff
    2. COyes I tried that too
      singulars
      1. POdidSelectRowAtIndexPath: not being called
      1. USGarrett
    3. COThank you for returning with your solution. I think it could be better to put the edit as an answer.
      singulars
      1. POdidSelectRowAtIndexPath: not being called
      1. USLorenzo B
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload