Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Unless I misunderstood your application structure, it seems like you're over complicating things with all those resignFirstResponder and becomeFirstResponder for UIAlertView dismiss.</p> <p>Essentially you got a UIAlertView with Username and Password fields yeah?</p> <p>Add a UIToolBar with a "Done" button that has a callback method like so:</p> <pre><code>// ------------------------------------------ // Setup keyboard done button as input // accessory view for your two fields // ------------------------------------------ UIToolbar *toolBar = [[UIToolbar alloc] initWithFrame:CGRectMake(0, 0, 320, 44)]; [toolBar setBarStyle:UIBarStyleBlackTranslucent]; UIButton *btnDone = [[UIButton alloc] initWithFrame:CGRectMake(230, 4, 66, 35)]; [btnDone setImage:[UIImage imageNamed:@"btnDoneOff.png"] forState:UIControlStateNormal]; [btnDone setImage:[UIImage imageNamed:@"btnDoneOn.png"] forState:UIControlStateHighlighted]; // ------------------------------------------ // Done button calls hideKeyboard method // when tapped, this is the only place you // need to call resign first responder // ------------------------------------------ [btnDone addTarget:self action:@selector(hideKeyboard) forControlEvents:UIControlEventTouchUpInside]; [toolBar addSubview:btnDone]; [btnDone release]; fldUsername.inputAccessoryView = toolBar; fldPassword.inputAccessoryView = toolBar; ... // ------------------------------------------ // Resigns first responder for the two fields // ------------------------------------------ -(void)hideKeyboard { [fldUsername resignFirstResponder]; [fldPassword resignFirstResponder]; } </code></pre> <p>Doing it like this, you can tap either the username field or the password field, the keyboard should not dismiss. When you're done entering username and password, pressing the "Done" button in your keyboard input accessory view will hide the keyboard without causing the keyboard to slide in and out.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to prevent the UIKeyboard from animating away and back after dismissing a UIAlertView
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USZhang
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSorry, I think I might have confused you. All those resignFirstResponder/becomeFirstResponder calles are there to illustrate the problem I'm trying to overcome. The order of events should be: Tap textView -> keyboard launches -> tap button on accessory view -> UIAlertView appears -> dismiss UIAlertView -> textfield becomes firstResponder avoiding the keyboard animating away and back. Its the last step in this sequence that I'm asking for advice sorting out. I'm looking for away to return firstResponder to the textView in a way that avoids the keyboard animating away and back.
      singulars
      1. PO
      1. USaerych
    2. COHave you tried using the UIAlertView didClickButtonAtIndex delegate method and in there, if([alertView.title isEqualToString:@"myAlertView"]) { [desiredField becomeFirstResponder]; } ?
      singulars
      1. PO
      1. USZhang
    3. COYep yep. I've tried that but still no luck.
      singulars
      1. PO
      1. USaerych
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload