I’m not sure if this question is legitimate to begin with, so feel free to move or remove.
I’m at a point in development where I have to choose between pausing Unity from XCode (and using the PlayerPrefs hack) or implement my own in-game solution for keyboard input on the iPhone.
My question to the Unity Devs would be the following:
Is it fair for me to “bet” that the great Unity Dev team will have released its next 2.x.x branch with an official solution to the problem in the near future?
My question to the community:
Would anyone who implemented the iPhone API “hack/solution” elaborate on the disadvantages of using this solution?
So far as I can foretell, that solution cannot be tested unless the code is compiled on the device, as the keyboard will work on the simulator but Unity will not, and Unity will work on the remote, but the keyboard will not. Is this a fair assumption?
Finally, since this thread relates to previous ones on the subject, would you guys mind posting some of your XCode/other implementations, as many in the community would certainly be incommensurately grateful.
No, Unity iPhone is on version 1.0.1, not 2.x. Unity 2.5 is coming soon but won’t offer any iPhone updates. After that (post-U2.5) we’ll be releasing another iPhone update but there are no dates/time lines to share yet. Clearly a native input option with the keyboard would be sweet, but in the meantime others have various tool to help (see the sprite manager thread as I’m sure that will help with making your own keyboard, then separately there’s another thread with an iPhone PSD “skin” file for the keys).
Arggh :!: I got mixed up in the numbers. I did mean the next iteration of unity iPhone (1.x.x)
Thank you for the reply, Tom. I’m not going to press for a more definite answer. I’m fairly certain you wouldn’t keep this info for yourself unless you had to … Right??
I’ll probably use an in-game implementation, then.
