iOS Delay Keyboard pop up

[larswik]

I was wondering if there is anyway to delay the keyboard popping up when you click on a UITextView? I have a UITextView at the bottom of the screen. When they user clicks on it The delegate method is called that brings forward the keyboard. I created an animation that moves the UITextView to the top of the screen but the keyboard comes on so quickly that the animation of the textView is not smooth.

If I could delay the pop up until the animation finishes that would be a great look. Since it is a delegate method that brings forward the keyboard I don't know if I could delay it 1/2 a second. Here is the code

- (void)textViewDidBeginEditing:(UITextView *)textView{
    fadeBlackTimer= [NSTimer scheduledTimerWithTimeInterval:.01 target:self selector:@selector(fadeToBlack) userInfo:nil repeats:YES];
    NSLog(@"Time for update");
    self.navigationItem.rightBarButtonItem.enabled = YES;
}

-(void)fadeToBlack{
    fadeToBlackView.alpha += fadeBlack;
    notesTextView.center = CGPointMake(self.view.center.x, self.view.center.y - moveTextView); 
    if (moveTextView < 99) {
        moveTextView += 2;
    }
    NSLog(@"move: %d",moveTextView);
    if (fadeToBlackView.alpha > 1.4) { // 1.4 allows extra time for animation of TextView.
        [fadeBlackTimer invalidate];
        fadeToBlackView.alpha = 1.0;
        moveTextView = 2;
    }

}

 

[ppilone]

If you're just looking to adjust the text view for the keyboard I'd suggest registering for keyboard notifications as opposed to using the text view's delegate.

Specifically:

UIKeyboardWillShowNotification
UIKeyboardDidShowNotification
UIKeyboardWillHideNotification
UIKeyboardDidHideNotification

Check the UIWindow class reference for detailed descriptions of the notifications.

 

[larswik]

This is why I like asking questions here, I didn't even know those existed. I will read up on those tonight. Thank you!

 

[ArtOfWarfare]

Those notifications are also really useful because they can also tell you what the frame of the keyboard is going to be. Thus you can make sure your text field's frame won't be covered up, even if the user is on a device where the keyboard is a different size (say iPhone vs. iPad,) or Apple decides to modify the keyboard in the future (maybe they'll finally add numbers above the letters so you can access those without having to hit the number key each time? Wishful thinking, but, still, write your code properly now so you don't have to rewrite it later.)

 

[dejo]

(maybe they'll finally add numbers above the letters so you can access those without having to hit the number key each time?

Please, no. The keyboard already takes up plenty of scarce screen real-estate on the iPhone / iPod touch.

 

[MattInOz]

Those notifications are also really useful because they can also tell you what the frame of the keyboard is going to be. Thus you can make sure your text field's frame won't be covered up, even if the user is on a device where the keyboard is a different size (say iPhone vs. iPad,) or Apple decides to modify the keyboard in the future (maybe they'll finally add numbers above the letters so you can access those without having to hit the number key each time? Wishful thinking, but, still, write your code properly now so you don't have to rewrite it later.)

You forgot to mention Accessory Views.

Apple doesn't need to change the base keyboards at all. You can use an accessory view to add the numbers if you really want them. As they are tied to the input field you only need them when they make sense, but that means they are the thing most likely to change the area of keyboard during run time and change how much you need to scroll to make the input visible.

 

[ppilone]

You forgot to mention Accessory Views.

Apple doesn't need to change the base keyboards at all. You can use an accessory view to add the numbers if you really want them. As they are tied to the input field you only need them when they make sense, but that means they are the thing most likely to change the area of keyboard during run time and change how much you need to scroll to make the input visible.

IIRC the Japanese keyboard is slightly taller than English keyboards. A good example of why you should use the keyboard notifications.

 

[ArtOfWarfare]

You forgot to mention Accessory Views.

Apple doesn't need to change the base keyboards at all. You can use an accessory view to add the numbers if you really want them. As they are tied to the input field you only need them when they make sense, but that means they are the thing most likely to change the area of keyboard during run time and change how much you need to scroll to make the input visible.

This wouldn't add the number row to built-in apps like Notes or iMessages.

Please, no. The keyboard already takes up plenty of scarce screen real-estate on the iPhone / iPod touch.

Make the screen 4" and add in a row of numbers, roughly half as tall as the letter keys all are.

At least on the iPad they wouldn't take up too much space... just look at the HP TouchPad... it includes a number row without taking up too much screen space. (Not that the screen space is worth anything. The built in apps suck and apps on their store aren't much better.)

 

[jnoxx]

Also have u tried using ANimation blocks, for smoothing out the transition?

 

[dejo]

Make the screen 4" and add in a row of numbers, roughly half as tall as the letter keys all are.

Why not just make all the keys half as tall? Or better yet, add a hardware keyboard to the iPhone. </sarcasm>

 

[larswik]

Also have u tried using ANimation blocks, for smoothing out the transition?

I have not tried Animation Blocks. I have heard of Blocks in passing but don't know what they are. It sounds like grouped code or something. This might be a good weekend project to learn something new.

 

[jnoxx]

I have not tried Animation Blocks. I have heard of Blocks in passing but don't know what they are. It sounds like grouped code or something. This might be a good weekend project to learn something new.

You have worked with ANimations?
(in style of)

[UIView viewWithAnimations:blallaal moreblallala];

Just look for animation blocks on google