Quote:
Originally Posted by nacho4d
Ok...
My app is using this "trick" and personally I don't think there is someone who has been warned by Apple for using this "trick"
Actually we are not using any private API (not directly) .
I mean, we don't have any private API object reference in our code.
(We have an casted UIKeyboard into UIView, and UIView is public so, we are good right?)
I have received some messages from apple warning me for using other APIs (in other apps) but my app was never rejected.
So. I think the easiest way is to do this trick.
When you use this "trick" you don't have to worry about keyboard animations your keyboard will show and hide the same way as apple's keyboard does. (since your keyboard is attached to apples's keyboard, like a super layer)
If you have a custom toolbar, you probably want to make it dissapear or appear (with an animation or not) when you get a keyboardWillHide or keyboardWillAppear notification.
With 3.0 OS you can get the animation curve the keyboard and you can use it to implement your own animation that should look like the original iPhone keyboard. Or maybe just a fade effect is enough.
I have to say that In first place I actually implemented my own keyboard but is really such a pain!! because:
You have to handle appear and dissappear animations.
And the most difficult part you have to find a way to show a cursor!, finding the cursor position is not easy!
Not showing the original keyboard implies that text will never become first responder. So you will never get Notifications when the keyboard is about to come out and etc. And you won't get a cursor. So you really are at your own.
But... (And this is a BIG BUT)
We all should start looking at new APIs
I cannot say further since 3.2 is still beta and I think there is a NDA.
But maybe we should start looking at new UITextField and UITextView and UITextTraits UITextInput ... etc
3.2 API diffs is a good place to start.
I would like to start a new thread but I am afraid we cannot yet. can we?
Regards Ignacio
|
So I have been playing around with the 3.2 SDK some, and guess what, the View hierarchy has changed and this technique no longer works.
I also have apps released with a decimal point in the number pad. Works quite well despite some usability issues I noticed in testing.
