• 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: Info window scenario
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Info window scenario


  • Subject: Re: Info window scenario
  • From: "e.sammer" <email@hidden>
  • Date: Wed, 07 Nov 2001 03:13:24 -0500

Erik M. Buck wrote:

> The solution is the responder chain. Send
> state changing messages up the responder
> chain.
>
> Even if you want the "current" document
> directly, you don't need to keep track
> yourself. NSDocument controller already
> knows the "current" document.
>

this is the way i'd like to do it, but i'm still having some difficulty. i am not subclassing NSWindowController, but can. i don't need any additional functionality from WindowController, but if i have to subclass it to get pushed into the responder chain, i will.

i did try subclassing NSWindowController, returning YES from acceptsFirstResponder and implementing a method to update the document, but it seems that it never gets called. i tried initiating the call up the responder chain with tryToPerform:with: and sendAction:to:from but to no avail. is there something i'm missing, or am i still going at it all wrong?

thanks very much for the answers thus far...
--
e.sammer
email@hidden


References: 
 >Info window scenario (From: "e.sammer" <email@hidden>)
 >Re: Info window scenario (From: "Erik M. Buck" <email@hidden>)

  • Prev by Date: Re: Authorization.h
  • Next by Date: Cocoa Equivalent to BufferedStreamReader?
  • Previous by thread: Re: Info window scenario
  • Next by thread: mouseMoved messages (modifying DotView)
  • Index(es):
    • Date
    • Thread