Note that there are some explanatory texts on larger screens.

plurals
  1. POext_bad_access when trying to show a tableView
    primarykey
    data
    text
    <p>I'm having the following issue: </p> <p>I have a tab-style app. Eacht tab has its own viewcontroller and xip. Within the first tab-view, I try to display a button which load a next view, showing a grouped tableView. Everything works as expected, the numberofSectionsInTableView is called, and then I get an ext_bad_access error. </p> <p>I try to explain my setup:</p> <p>First (by the click of a button), I load the nip of the view: </p> <pre><code>FiltersViewController *filtersViewController = [[FiltersViewController alloc] initWithNibName:@"Filters" bundle:[NSBundle mainBundle]]; [self.navigationController pushViewController:filtersViewController animated:YES]; [filtersViewController release]; </code></pre> <p>In the NIB, the File's-Owner is set to the FiltersViewController class. The view-outlet is connected to the tableView, which is of class UITableView. The TableView itself is sitting in the FiltersViewController object. </p> <p>The FiltersViewController has the following interface: </p> <pre><code>@interface FiltersViewController : UITableViewController &lt;UITableViewDelegate, UITableViewDataSource&gt; {} </code></pre> <p>The tableView's delegate and dataSource is connected to the File's-Owner. I implemented the required methods for table-setup...</p> <p>What am I missing? I've read that ext_bad_access has to to with accessing pointers / objects that are no longer existing. I followed the basic rules for memory management, and cannot find an error in the code.</p> <p>Help is really appreciated. pawi</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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