StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUsing Interface Builder to place UIGestureRecognizer in several views in Tabbed application
text
Body
copied!<p>I have created an application where I try to utilize the new features in Interface Builder (Storyboard, GestureRecognizers etc.) I start off by choosing that Tabbed Application template . I then add a SwipeGestureRecognizer to each view in their corresponding view controller. The SwipeGesture is connected to a method that calls resignFirstResponder on each text input.</p> <p>The SwipeGesture works as expected in the first view but when I try to press a tab to switch view the app crashes. The error that I get is SIGBART or EXC_BAD_ACCESS. If I remove the GestureRecognizers from the second view the second view loads without any problems. </p> <p>This problem does not occur if I for example choose to use UtilityApplication template and add the gesture recognizers in the same way as I did in the Tabbed Application template.</p> <p>Can anyone give me any pointers on how I can solve this problem. I'm afraid that I can't provide much code since the only code that I have added is an IBOutlet to the UITextField and the method called when the gesture has occurred</p> <pre><code>- (IBAction) hideKeyBoard:(id)sender{ [textField resignFirstResponder]; } </code></pre> <p><img src="https://i.stack.imgur.com/ZU4Rh.png" alt="This is an image of my setup in Interface Builder. The view called ViewController is working but when I try to load the SettingsViewController the app crashes."></p> <p>This is an image of my setup in Interface Builder. The view called ViewController is working but when I try to load the SettingsViewController the app crashes.</p> <p>Update: If i added the gesture recognizers programmatically instead the above problem didn't occur.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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