uiresponder

How would you allow a UIGestureRecognizer of a UIView to receive a touch event but also make sure that another, underlaying/overlaying UIView also receives that very same touch event? Lets say I have got the following view-hierachie: Views A (blue) and B (red) are both subviews of the same superview (gray). In other words, they are both siblings and the order decides on which of them covers the other. Option 1: View B (red) has a regular UIButton as its subview. Option 2: View A (blue) has a regular UIButton as its subview. Given Option 1 for the sake of explanations: View A (blue) has a

This is what the documentation says: If the first responder [to an event or action message] cannot handle an event or action message, it forwards it to the “next responder” in a linked series called the responder chain. The responder chain allows responder objects to transfer responsibility for handling an event or action message to other objects in the application. If an object in the responder chain cannot handle the event or action, it resends the message to the next responder in the chain. The message travels up the chain, toward higher-level objects, until it is handled. If it isn't

When the keyboard is showing on the iPhone's Messages app, if the user begins a swipe down from the messages tableview and continues into the keyboard area, the keyboard will begin to dismiss. If they move their finger up and down during this process, the keyboard moves with it. Are Apple doing this with private APIs, or is there a way to control the keyboard like this from (I presume) a gesture recognizer? I created a UIView category that provides the desired functionality: https://github.com/danielamitay/DAKeyboardControl Edit: It has indeed been used on the app store. ma11hew28 The simplest

I have a class ASTextField which extends after UITextField and I want to define textFieldResponder. Is any solution to write below line in Swift ?? UIResponder* nextResponder = [textField.superview viewWithTag:nextTag]; which has been written in Objective-C below? -(BOOL)textFieldShouldReturn:(UITextField*)textField; { NSInteger nextTag = textField.tag + 1; // Try to find next responder UIResponder* nextResponder = [textField.superview viewWithTag:nextTag]; if (nextResponder) { // Found next responder, so set it. [nextResponder becomeFirstResponder]; } else { // Not found, so remove keyboard.

I'd like to make a UIKeyCommand that uses only the [return] key. So far I've tried: UIKeyCommand *selectCommand = [UIKeyCommand keyCommandWithInput:@"\n" modifierFlags:0 action:@selector(chooseSelection:)]; There's no global constant for the enter key, like there is for up, down, left, right, and escape (from UIResponder.h ): // These are pre-defined constants for use with the input property of UIKeyCommand objects. UIKIT_EXTERN NSString *const UIKeyInputUpArrow NS_AVAILABLE_IOS(7_0); UIKIT_EXTERN NSString *const UIKeyInputDownArrow NS_AVAILABLE_IOS(7_0); UIKIT_EXTERN NSString *const

I have a view with keyboard notifications such as keyboardWillShow and keyboardWillHide All the codes handles with the notification I use is taken from Apple's sample code "KeyboardAccessory" When I first enter this view, everything works fine. But when I return to this view from its subviews, every time I tap a button that says: [myTextField becomeFirstResponder]; the keyboardWillShow and keyboardWillHide methods will be called twice every time. It's really confusing, Could anyone helps me with this? really appreciate! You might want to post your code. If your methods are being called twice,

I'm attempting to trigger an event in a subview of a UITableViewCell , and let it bubble up the responder chain and be handled by a custom UITableViewCell subclass. Basically: SomeView.m (which is a subview of the UITableViewCell ) [self.button addTarget:nil action:@selector(someAction:) events:UIControlEventTouchUpInside] SomeCustomCell.m - (void)someAction:(id)sender { NSLog(@"cool, the event bubbled up to the cell"); } And to test why this wasn't working, I've added the someAction: method on the ViewController and the ViewController is the one that ends up handling the event that bubbles up