Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

iOS Next Keyboard Button

ArtOfWarfare

macrumors G3
Nov 26, 2007
8,924
4,778
Is it completely necessary to have a next keyboard button on a keyboard designed purely for in app use?

https://developer.apple.com/library...eral/Conceptual/ExtensibilityPG/Keyboard.html

This seems to suggest it is, but yet there are apple specific keyboard (e.g. number pad), that don't conform to this requirement.

Several apps I have seen also don't do this.

This is about adding new systemwide keyboards. The number pad is not a systemwide keyboard. A few apps use it. It's not one that you can use in every app by tapping on the globe key in the lower left corner (if you only have a single keyboard enabled on your device, you don't see the globe key . Many people in the U.S. have the English and Emoji keyboards enabled systemwide, for example.)
 
Comment

danielowenuk

macrumors 6502
Original poster
Mar 18, 2011
262
25
Cool, so assuming it's an app specific keyboard, I don't need the globe icon.
 
Comment

danielowenuk

macrumors 6502
Original poster
Mar 18, 2011
262
25
Ok, so I figured out why you need the next keyboard button.

Long story short the method for adding a custom keyboard on Xcode is not what I thought it was.

Adding custom keyboard should really be called "Adding Custom System Wide Keyboard".

The keyboard on my app works great, but needs to be installed as a keyboard, as a result it then becomes the system wide keyboard, and when you aren't in my app the lack of a next keyboard royally screws you (it's only got numbers on it!).

I think I just need to call the UIView that I have created, rather than doing it specifically as a custom keyboard.
 
Comment

1458279

Suspended
May 1, 2010
1,601
1,521
California
If I understand your problem, I had the same problem. The numeric keyboard doesn't have a next or any key to end the input process.

I've seen one solution that added a button on top of the keyboard, but it didn't look right.

Does Apple have a solution to this? It seems like having a next button on a different view other than the keyboard is inconsistent because the other keyboard have buttons that end the input.

Maybe I'm missing something, but don't all keyboards except the numeric have a "end the input" type button?
 
Comment

danielowenuk

macrumors 6502
Original poster
Mar 18, 2011
262
25
That's not really the issue, the issue is instead of calling my app specific keyboard when you tap a textfield, you get the default keyboard...

You can then switch to my keyboard as long as you have it installed in the keyboard section. I don't want to have to do this.

Anyone got an example project with a UIView called as keyboard? Could do with plagerising something.
 
Comment

ArtOfWarfare

macrumors G3
Nov 26, 2007
8,924
4,778
That's not really the issue, the issue is instead of calling my app specific keyboard when you tap a textfield, you get the default keyboard...

You can then switch to my keyboard as long as you have it installed in the keyboard section. I don't want to have to do this.

Anyone got an example project with a UIView called as keyboard? Could do with plagerising something.

It's just a UIView with UIButtons on it. When the user taps something that should invoke your custom keyboard, animate it onto the screen. When the user does something to dismiss it, animate it off of the screen. When the user taps a button on the "keyboard", connect that event to the appropriate method that should run.
 
Comment

danielowenuk

macrumors 6502
Original poster
Mar 18, 2011
262
25
Haha, yeah dead easy, did I tell you I have been doing this about a week :p

I will have a read around and see if I can work it out.
 
Comment
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.