Comments on: Preloading the UIKeyboard

By: kamilk

kamilk — Mon, 28 Jun 2010 12:16:12 +0000

Unfortunately, the trick does not work in iOS 4 anymore, because the UIKeyboard view is not available at UIKeyboardWillShowNotification but on the next run loop pass. You can access it to hide it, for example using performSelector: afterDelay:0, but then the keyboard is already visible, so it’s too late… I’ll try to find another solution and I count on You all too

By: kevin

kevin — Mon, 21 Jun 2010 14:14:44 +0000

@Matt — see “A Developer’s” comment above on the addition of an extra container view under iOS 4.0

By: Matt

Matt — Sun, 20 Jun 2010 07:06:58 +0000

Hi, Thanks for your example but I can get it working with iOS 4.0. Any ideas why?

By: A Developer

A Developer — Fri, 04 Jun 2010 22:36:38 +0000

jonk,

In the latest betas there’s an extra container view, probably used to manage pixel doubling. Add in another for loop, and you’ll find the keyboard.

The name remains the same UIKeyboard, luckily…

best wishes, thanks for the post Kevin!

By: rick

rick — Thu, 20 May 2010 17:12:53 +0000

@jonk: we haven’t tested this technique in the 4.0 beta. Do you have it working in 3.x?

By: jonk

jonk — Sat, 15 May 2010 15:30:26 +0000

I’ve put in several layers of “subviews” in your code, and not once has one come up with the “UIkeyboard”?

the keyboard is coming up, and dismissing, but you can see it come up at launch of the app… so i went in to see if that subview code was working, and basically none of the subviews are the UIkeyboard?

anyone have any ideas why i can’t see this subview? (using latest iphone beta as of this date)

By: Tweets that mention Preloading the UIKeyboard at Uproar Blog -- Topsy.com

Tweets that mention Preloading the UIKeyboard at Uproar Blog -- Topsy.com — Mon, 29 Mar 2010 15:58:59 +0000

[...] This post was mentioned on Twitter by Dave Mitchell, Tak Fung. Tak Fung said: For iPhone devs who want to preload the keyboard so it appears quickly – this is useful: http://tinyurl.com/ykdxptf [...]

By: Petr Dvorak

Petr Dvorak — Fri, 26 Mar 2010 14:36:44 +0000

Thank you! This is very practical blog post. I had my application and it was almost done, worked great. Just the small cosmetic issue – the first keyboard loading took too much time, which was not desired since it was a social app requiring quick comment posting. This how-to solved this problem.

By: Chris Miles

Chris Miles — Tue, 27 Oct 2009 05:20:39 +0000

Thanks for the tip, it worked great. My client wasn’t happy with the initial keyboard delay, and neither was I. Strange that Apple haven’t addressed it.

I simplified the solution by using the existing UITextField rather than creating a dummy/hidden one.

By: kevin

kevin — Mon, 26 Oct 2009 03:07:45 +0000

@danny

This solution isn’t using any undocumented APIs so it shouldn’t be at risk for rejection by Apple. However, this solution does rely on the class name of the stock keyboard so if Apple decided to change that then this code would no longer work.

Something I just thought of but it may be possible to modify this solution such that instead of looping for the first view named UIKeyboard you could instead check to see if the view equals the reference of the dummy keyboard. If this works, it would make this solution more robust.