Hey guys, I am pretty darn sure this is a bug with 3.0 but I wanted to run it past you guys before I reported it to Apple.
In all other firmware versions, if you used a number keyboard, the way to release the keyboard was to create an invisible button on the background that when "clicked" would resignFirstResponder on the UITextField. I am coming to a situation, when calling resignFirstResponder on a diff UITextField is causing the number keybard text field to revert back to the standard keyboard.
If you are unclear, here are the steps to reproduce:
1. Create 2 text fields, one with a normal keyboard and one with a number pad keyboard
2. Create your textFieldDoneEditing action method so when the user clicks Done in the 1st textField (the one with the standard keyboard), the keyboard goes away.
3. Create your invisible background button so when it clicked, you resignFirstResponder on the number textField.
Run the app in the 2.2.1 simulator and all is well. Now run the app in 3.0 simulator. Enter some text in the name textfield, select Done then change focus to the numberTextField and see the keyboard. Did something change in 3.0 that I am not aware of or should this bug be filed with Apple?
Thanks guys!
In all other firmware versions, if you used a number keyboard, the way to release the keyboard was to create an invisible button on the background that when "clicked" would resignFirstResponder on the UITextField. I am coming to a situation, when calling resignFirstResponder on a diff UITextField is causing the number keybard text field to revert back to the standard keyboard.
If you are unclear, here are the steps to reproduce:
1. Create 2 text fields, one with a normal keyboard and one with a number pad keyboard
2. Create your textFieldDoneEditing action method so when the user clicks Done in the 1st textField (the one with the standard keyboard), the keyboard goes away.
3. Create your invisible background button so when it clicked, you resignFirstResponder on the number textField.
Run the app in the 2.2.1 simulator and all is well. Now run the app in 3.0 simulator. Enter some text in the name textfield, select Done then change focus to the numberTextField and see the keyboard. Did something change in 3.0 that I am not aware of or should this bug be filed with Apple?
Thanks guys!