iphone - Why calling [self becomeFirstResponder] caused so many problems? -


for past few extremely frustrating days of life, i've been trying figure out what's wrong me code. in page, if put uitextviews or uitextfields or mfmailcomposer or messagecomposer or fields require editing, fields wouldn't respond touches. couldn't edit when ran app. couldn't edit text views or email fields or anything. tried everything, nothing worked. turns out on main page (mainvc) leads page fields don't respond (giftvc), in viewdidappear method (in mainvc), say: [self becomefirstresponder];.

now i'm not sure why put there, turns out commenting line out fixes , makes fields , textviews , email composers , work fine again.

i have in mainvc page:

-(bool)canbecomefirstresponder {     return yes; } 

and commenting out fixes problem well.

the weird part [self becomefirstresponder] line, worked fine in new ios 5 (simulator , device), in ios 4 (simulator , device), wouldn't work @ line. i've removed it, works fine in both cases.

check if mainvc has method called canresignfirstresponder returns no (at least sometimes). if so, once becomes first responder, won't let else become first responder, until returns yes method. (all uitextviews, etc. have become first responder edited.)

actually everywhere in code canresignfirstresponder, in case it's in superclass or something.

otherwise thing stop text fields , views being editable if got set userinteractionenabled = no, since hinges on becomefirstresponder statement, more canresignfirstresponder.


Comments

Popular posts from this blog

objective c - Change font of selected text in UITextView -

php - Accessing POST data in Facebook cavas app -

c# - Getting control value when switching a view as part of a multiview -