Author Topic: Big bug with iOS and keyboard (UIInput)  (Read 2953 times)

masterprompt

  • Guest
Big bug with iOS and keyboard (UIInput)
« on: August 27, 2013, 10:51:06 PM »
Having buttons on screen and one input text field.  On android, I can enter text, hit enter, keyboard disappears, and everything functions normally.

On iOS, after keyboard goes away, I can no longer click buttons....  It's like none of the ui responds.

I've tried putting the buttons in upper and lower areas of the screen.  Only thing I can do is click on the text field again to bring back up keyboard.

I even tried tying the event receiver to one of the button objects with the OnClick string as the event name, nothing happens when i hit done or return on ios keyboard.

This bug is killing me here......

ENAY

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 248
    • View Profile
Re: Big bug with iOS and keyboard (UIInput)
« Reply #1 on: August 28, 2013, 02:02:33 AM »
Does this bug happen on the UIInput examples that came with NGUI?
I suggest you double check those examples first, just to make sure if this is a bug or not or something you have done with UIInput that currently isn't obvious to see.

Which version of Unity are you using, and which version of iOs and which version of NGUI?

masterprompt

  • Guest
Re: Big bug with iOS and keyboard (UIInput)
« Reply #2 on: September 04, 2013, 09:40:48 PM »
ENAY, from the blitz community.

I can assure you, it's nothing I am doing wrong. I'm no newb to NGUI. It works on android fine, doesn't work on iOS.

NGUI version: current
IOS version: anything 5.0+
Unity version: current

ENAY

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 248
    • View Profile
Re: Big bug with iOS and keyboard (UIInput)
« Reply #3 on: September 05, 2013, 03:12:44 AM »
But did you check the example source code like I asked, just to be sure?

I have no idea what you trying to do in your code, it might be a bug in what you are doing. But if you are sure it is nothing you are doing wrong, what I suggest you do is create a separate UIText window and then debug to the screen of the Android around where you are doing all your UI Stuff to see if there is anything suspicious. If the debug window stops working, it might give you a hint to where things are getting stuck.

That is what I would do anyway.