Re: UISplitViewController some of the time
Re: UISplitViewController some of the time
- Subject: Re: UISplitViewController some of the time
- From: Conrad Shultz <email@hidden>
- Date: Thu, 03 Nov 2011 13:55:43 -0700
On 11/3/11 1:04 PM, Eric E. Dolecki wrote:
> I am not using nibs. Per Apple's guidelines, a splitviewcontroller must
> be the root. My "home" view controller needs to fill the whole screen,
> over top of the splitviewcontroller, which I've done.
As I said, I have _never_ used storyboards, so this could probably
benefit from someone who actually knows about this.
That said, I glanced over what I could find about UIStoryboard and the
like. I couldn't find anything about UISplitViewController needing to
be at storyboard root.
Now, I know that the HIG tell you (and, I believe, the framework
expects) that UISplitViewController's view should not be a subview -
that is, it expects to take over the screen. Fine. Is that what you
were referring to? If so, that's not an issue here - presenting a
UISplitViewController modally, either in code or by setting the seque
transition style (reminder: I've never done this!) to modal should work.
> Right now I am trying to get the storyboard scene for my
> HomeUIViewController to be used instead of just calling up my class and
> having to do all the UI with code. I'd like to use the scene instead.
> This is happening in the app delegate FYI.
To be clear: storyboard or no, you can ALWAYS use a nib to encapsulate
UI that you hook up in code, getting the best of both worlds (potentially).
UINib is just another class. If you want to get access to pre-built UI
for use in code, try something like (typed in email):
UINib *nib = [UINib nibWithNibName:@"MyNib" bundle:nil];
NSArray *topLevelObjects = [nib instantiateWithOwner:foo options:nil];
Then pull out whatever objects you please from topLevelObjects and
manipulate them. If you have IBOutlets in the file where you are doing
this, and set owner to self, you might even be done.
As I indicated above, though, I seriously doubt this is necessary for
what you are trying to accomplish. If you could clarify where you are
getting this information about UISplitViewController needing to be root,
and if I could maybe spend some time writing a test app to familiarize
myself with storyboarding, we could get to the bottom of this.
But I can't believe there is no one on the list who has experience with
this new technology - please chime in!
--
Conrad Shultz
Synthetiq Solutions
www.synthetiqsolutions.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden