StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9063105
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-01-30T11:26:51.863
FavoriteCount
0
LastActivityDate
2013-02-28T14:12:00.327
LastEditDate
2013-02-28T14:12:00.327
LastEditorUserId
966656
OwnerUserId
966656
ParentId
9035320
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I have discovered a solution to my problem. Its a bit dirty, (and I''ll probably get shot down in flames for it) but works very well under tests and is very quick to implement. Here's how I did it. In my app I have a Singleton class called GlobalVars (I use this for storing various global settings). This class holds a boolean called home_pressed and associated accessors (via synthesise). You could also store this value in the application delegate if you wish. In every view controller with a main menu button, I wire the button to the homePressed IBAction method as follows. First setting the global homePressed boolean to YES, then dismissing the view controller in the usual way, but with NO animation. <pre><code>-(IBAction) homePressed: (id) sender { [GlobalVars _instance].homePressed = YES; [self dismissModalViewControllerAnimated: NO]; }//end homePressed </code></pre> In every view controller except the main menu I implement the viewDidAppear method (which gets called when a view re-appears) as follows. <pre><code>-(void) viewDidAppear: (Bool) animated { if ([GlobalVars _instance].homePressed == YES) { [self dismissModalViewController: NO]; } else { //put normal view did appear code here/ } }//end viewDidAppead </code></pre> In the mainMenu view controller which is the root of the app, I set the global homePressed boolean to NO in its view did appear method as follows <pre><code>-(void) viewDidAppear: (Bool) animated { if ([GlobalVars _instance].homePressed == YES) { [GlobalVars _instance].homePressed == NO; } else { //put normal view did appear code here/ } }//end viewDidAppear </code></pre> There, this enables me to go back to the root main menu of my app from any view further down the chain. I was hoping to avoid this method, but its better than re-implementing my app which is what I'd have to do if I wanted use the UINavigationController solution. Simple, took me 10 minutes to code in my 9 view app. :) One final question I do have, would my solution be OK with the HIG?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POReturn to root view in IOS
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAndrew S
UserOwnerUserId
1. USAndrew S
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POReturn to root view in IOS
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.