Re: Visiblity
Re: Visiblity
- Subject: Re: Visiblity
- From: SA Dev <email@hidden>
- Date: Thu, 7 Jul 2005 16:58:32 -0400
Available only in 10.3 and above. If you want backward
compatibility, you could easily just retain it, remove it from its
superview, then add it back in later, releasing when done (the
superview retains its subviews when they're added, then releases them
when they're removed, so remember to *retain* first ) ... ;-)
Also, this is an area of religious debate, so be warned. Many
think it's not a good thing to remove / hide controls. One school of
thought is that it's better to simply disable them so the user knows
they're there (available) but can't be used at the moment. I tend to
agree with this philosophy, though there are *always* exceptions.
On Jul 7, 2005, at 4:38 PM, Lee Morgan wrote:
What about NSView's setHidden: method?
- Lee
On Jul 7, 2005, at 4:28 PM, Theodore H. Smith wrote:
How do you make a control invisible in Cocoa? Is it not actually
possible? Or do I just set it's origin off the side of the window,
and disable it?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40silentalcove.net
This email sent to email@hidden
_______________________________________________
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
| References: | |
| | >Visiblity (From: "Theodore H. Smith" <email@hidden>) |
| | >Re: Visiblity (From: Lee Morgan <email@hidden>) |