Re: -NSView setHidden: in 10.2
Re: -NSView setHidden: in 10.2
- Subject: Re: -NSView setHidden: in 10.2
- From: Glenn Andreas <email@hidden>
- Date: Mon, 20 Sep 2004 10:14:48 -0500
At 10:06 AM -0500 9/20/04, Darrin Cardani wrote:
At 10:52 AM -0400 9/20/04, J Nozzi wrote:
There are plenty of discussions on the matter and it's up to you,
Darrin, to decide which way best fits your app's design. If it's
not something that is needed all the time, try a tab view, a sheet,
or even a drawer (though for some reason there's great hostility
toward drawers in some camps; I see no problem with them if they're
used properly).
This is an iMovie plugin. Or more accurately, it's 2 different
iMovie plugins that share a lot of code and have very similar UI's.
When the user chooses the first plugin, they get the window with all
the controls. When the user chooses the other plugin they get the
window without a couple of controls. It's not a situation where
doing something within the window shows or hides the UI elements.
But it makes the size of the code and resources smaller to do it
this way. I don't believe that breaks the design guidelines you
speak of.
Thanks for all your help,
Darrin
Can you just have two different nibs? That way you can also
re-layout the one without the extra elements and not have any ugly
"big missing gap space".
(Granted, this will require making sure that you keep the two in sync
when you make other changes, but I'd think that providing a different
nib name string is a whole lot easier than going through and hiding a
bunch of elements).
--
Glenn Andreas email@hidden
<http://www.gandreas.com/> oh my!
Mad, Bad, and Dangerous to Know
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden