Re: Changing order of views dynamically
Re: Changing order of views dynamically
- Subject: Re: Changing order of views dynamically
- From: Sergey Shapovalov <email@hidden>
- Date: Tue, 20 Mar 2007 19:45:44 +0300
On Mar 20, 2007, at 7:36 PM, Michael Watson wrote:
What on Earth is not precise about:
"Note: For performance reasons, Cocoa does not enforce clipping
among sibling views or guarantee correct invalidation and drawing
behavior when sibling views overlap. If you want a view to be drawn
in front of another view, you should make the front view a subview
(or descendant) of the rear view."
There are things in IB and NSView that appear to be planning for
future additions, but in the end, the documentation says not to
overlap views.
I think you filed a bug that should not have been filed.
There are 2 possibilities.
1. The documentation is 100% precise. Then the API is misleading. If
it appears "to be planning for future additions", then I want to have
a clear comment, "Do not use this method prior to Leopard (or
whatever) because it won't work".
2. The API does what it promises to do (and the current comment is
clear enough, and for addSubview:positioned:relativeTo: it says,
"Inserts a view among the receiver’s subviews so it’s displayed
immediately above or below another view"). Then the documentation is
not precise.
Isn't this is simple logical dilemma? And whenever 1 or 2 is true,
there is a bug. So, why should it not have been filed?
Best regards,
Sergey._______________________________________________
Cocoa-dev mailing list (email@hidden)
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