• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: clicking through
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: clicking through


  • Subject: Re: clicking through
  • From: Mailing list subscriptions <email@hidden>
  • Date: Mon, 11 Sep 2006 18:55:55 +0200

El 11/09/2006, a las 18:29, Michael Ash escribió:

Suggested course of action: file a bug report against the documentation.

Why? As far as I can tell, the documentation is *correct*. Overlapping views are supported in Cocoa, subject to the limitations outlined in the documentation. The documentation isn't what I'm worried about. My point is that everyone says "Cocoa doesn't support overlapping views", but neither the documentation nor the implementation seem to actually support this position.

Scott Anguish is a respected author ("Cocoa Programming", http:// www.cocoaprogramming.net/), was one (and maybe still is) one of the key people behind Stepwise (http://stepwise.com/), has been a Mac developer for the last 22 years, and a NeXT developer since 1992. Most importantly of all, he works for Apple as a Senior Technical Writer in their Cocoa & Xcode Tools group (bio: http:// conferences.oreillynet.com/cs/macosx2004/view/e_spkr/1322). He just quoted a section from Apple's documentation that says:


"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."

Without getting bogged down in the semantics of the word, "should", this seems clear enough to me; NSView was not designed to support overlapping views, other than the subview-superview case. Just because it's possible to hack around this doesn't mean that it's "supported".

As I said in my last email, if you think it's the documentation is not clear enough then file a bug report against the documentation. Trying to prove that you're right on this list won't help.

_______________________________________________
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


  • Follow-Ups:
    • Re: Re: clicking through
      • From: "Michael Ash" <email@hidden>
References: 
 >clicking through (From: Hans van der Meer <email@hidden>)
 >Re: clicking through (From: Mailing list subscriptions <email@hidden>)
 >Re: Re: clicking through (From: "Michael Ash" <email@hidden>)
 >Re: clicking through (From: Scott Anguish <email@hidden>)
 >Re: Re: clicking through (From: "Michael Ash" <email@hidden>)
 >Re: clicking through (From: Mailing list subscriptions <email@hidden>)
 >Re: Re: clicking through (From: "Michael Ash" <email@hidden>)

  • Prev by Date: NSSavePanel default name and prepareSavePanel:
  • Next by Date: NSTextView/NSLayoutManager bug?
  • Previous by thread: Re: Re: clicking through
  • Next by thread: Re: Re: clicking through
  • Index(es):
    • Date
    • Thread