On Apr 3, 2016, at 11:27 PM, Luther Baker wrote:
> Disconnected, the keyboard seems to come right up.
I will note that - when connected to Xcode, the first modal presentation takes
forever, device or simulator.
YES.
This is EXACTLY the same problem I had when trying to bring up the keyboard
Hi Alex,
I am using an iPhone. Disconnected, the keyboard seems to come right up.
I'm triggering actions to the first responder using viewWillAppear and
viewWillDisappear and they seem to look fine on the device. Specifically,
the keyboard comes up right along with the presented view controller -
Luther, please try this.
Unplug your app from your Mac and don’t launch it from Xcode.
Tell me how long it takes to display the keyboard.
Also, please tell me if you are using an iPhone or an iPad.
I ran into this about 6 months ago and want to see if it is the same thing.
Cheers.
Alex Zavaton
I am having better luck with viewWillAppear and viewWillDisappear on the
device proper as opposed to the simulator. It seems to work reasonably well
for what I want.
On Sun, Apr 3, 2016 at 9:53 AM, Luther Baker wrote:
> More information
>
> As an experiment, if I tie the DISMISS button solely
More information
As an experiment, if I tie the DISMISS button solely to resigning first
responder ... and wait some amount of time before tapping SAVE to simply
dismiss the view controller, the KEYBOARD pops back up while the view
controller is dismissing!
There must be a problem passing becomeF
I am presenting a newly instantiated modal view controller (iOS, shows up
from the bottom) and I'd like to have one of the text fields immediately
becomeFirstResponder.
*Approach #1:*
If I invoke this directly in the presented view controller's
viewWillAppear, I see some presentation animation ar
