Re: XC & IB 3.2 overlapping siblings
Re: XC & IB 3.2 overlapping siblings
- Subject: Re: XC & IB 3.2 overlapping siblings
- From: Andreas Grosam <email@hidden>
- Date: Fri, 11 Sep 2009 10:26:35 +0200
On Sep 10, 2009, at 8:40 PM, Erik Buck wrote:
Don't overlap sibling views. Even though it works reliably now, it
is still a poor practice for controls and has a definite user
interface "smell."
Do you mean sibling *views* shall not overlap, or do you mean
*controls* shall not overlap?
Apart from user interface design, is there a strong reason not to do
so in general?
If you must use the same area of the user interface for different
purposes at different times, consider using a tab view with no
visible tabs and programmatically changing which subview of the
tabview is visible.
How would you solve this problem:
There is a view which shows a movie. If you click (or tap) inside the
view, a control appears within the movie view.
(The control view and the movie view may share the same super view,
and the control view may not be a sub view of the movie view. If this
is the case, the movie view and the control inevitable overlap.)
Regards
Andreas
_______________________________________________
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