Re: Connecting actions to menu
Re: Connecting actions to menu
- Subject: Re: Connecting actions to menu
- From: David P Henderson <email@hidden>
- Date: Sat, 16 Jun 2001 08:58:53 -0400
On Friday, June 15, 2001, at 05:38 , jgo wrote:
If something is done in IB, it would be "static", defined
before compile, but what is the first responder is a
dynamic, execution time issue... or so I am led to believe.
Please, expostulate & clarify.
Objects contained in a nib are just that objects. I'm not sure that
"static" is a good way to describe objects in a nib. Upon saving the
object instances in a nib are archived. Upon loading the object
instances in the nib are un-archived and connected to the loading
class(es). Any object in the nib may be replaced by an external object
after it is un-archived.
As I understand it, both the File's Owner and First Responder in a nib
are just proxies for objects outside the nib to which actions and
targets are connected at run time. By connecting actions to First
Responder in a nib you are making them nil targeted actions which causes
the responder chain to be searched for an object to handle it. The
responder chain starts with the Key window's first responder and moves
up the chain from there or graphically
key window first responder -> next responder in view hierarchy ->
window -> window delegate -> main window (if not same as key and repeat
key window search sequence) -> nsapplication global instance -> nsapp
delegate -> oblivion
Dave
--
Chaos Assembly Werks
"Nothing is too good to be true, except, perhaps, the morality of a
bishop."
- Israel Zangwill