Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could easily do it in the UIAlertView delegate method, called once an alert view is dismissed. So, UIAlertViewDelegate defines the following delegate method:</p> <pre><code>– alertView:didDismissWithButtonIndex: </code></pre> <p>Implement that method, and make sure your class is the delegate of the UIAlertViews you create. This method is the perfect place to then show the <em>next</em> alert based on the one being dismissed by the user.</p> <p>If your requirement is "Display up to three alerts, sequentially, but not always in the same order" i'd probably put the alerts in to an array, and then in the delegate method get the next alert out of the array to show. It doesn't have to be any more complex than that really; the key thing is that the delegate method implementation is the best place to <em>show the next</em> alert.</p> <p><strong>Pseudo Code Example:</strong></p> <p>Define an array; NSMutableArray * alerts_;</p> <pre><code>- (void)showAlertSequence { if ( !alerts_ ) { alerts_ = [[NSMutableArray alloc] init]; } [alerts_ addObjects;&lt;My alerts&gt;]; [self showSequencedAlertFrom:nil]; } - (BOOL)showSequencedAlertFrom:(UIAlertView *)sourceAlertView { if ( !sourceAlertView ) { [[alerts_ objectAtIndex:0] show]; } else { NSInteger index = [alerts_ indexOfObject:sourceAlertView]; if ( index &lt; [alerts_ count] ) { [[alerts_ objectAtIndex:index++] show]; } } return NO; } – alertView:(UIAlertView *)alertView didDismissWithButtonIndex:(NSInteger)index { // Show the next alert or clean up if we're at the end of the sequence. if ( ![self showSequencedAlertFrom:alertView] ) { [alerts_ removeAllObjects]; } } </code></pre> <p>As an aside; three sequential alerts will really annoy you users ;)</p>
    singulars
    1. This table or related slice is empty.
    1. PODisplaying UIAlertViews Sequentially
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdannywartnaby
    1. USdannywartnaby
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODisplaying UIAlertViews Sequentially
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COthanks @dannywartnaby This is similar to something that ive already tried. The issue is that here you assuming that all alertViews exist. What if only alertView 1 and 3 exist? You Pseudo code would skip alert3 if that was the case. Or am I missing something obvious?
      singulars
      1. PO
      1. USgrezza
    2. COAnother issue with this approach is that alert 1 wont always exist, which means that none of the other alerts will ever show. This is why I was contemplating using a different approach to the delegate method. Thanks for your response
      singulars
      1. PO
      1. USgrezza
    3. COOK, I see. Well i've updated my answer a little; the bottom line is that the delegate method is, IMO, the best place to decide when to show the next alert. If you can't consistently know which alerts are being displayed and in what order, then it makes sense IMO that put the alerts you want to display into a collection and then essentially iterate over that collection in the delegate method, getting the "next" based on the current.
      singulars
      1. PO
      1. USdannywartnaby
 

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