[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Correct way to handle kEventCommandUpdateStatus?

Subject: Re: Correct way to handle kEventCommandUpdateStatus?
From: Eric Schlegel <email@hidden>
Date: Fri, 29 Aug 2003 15:20:15 -0700

On Aug 29, 2003, at 2:54 PM, Laurence Harris wrote:

One option is install a kEventMenuEnableItems handler on the application. In
it you can disable an entire menu and enable selected commands and then
return eventNotHandledErr. After that the commands in the menu will get
passed to the chain of kEventCommandUpdateStatus handlers, and if none of
them enable a command, it will stay disabled. This may not be appropriate
for every menu, but it works well for some.

That's an excellent suggestion for menus that are entirely managed by your application (which, in practice, is just about every menu that your app provides).

-eric
_______________________________________________
carbon-development mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/carbon-development
Do not post admin requests to the list. They will be ignored.

Follow-Ups:
- Re: Correct way to handle kEventCommandUpdateStatus?
  - From: Laurence Harris <email@hidden>

References:
	>Re: Correct way to handle kEventCommandUpdateStatus? (From: Laurence Harris <email@hidden>)

Prev by Date: Using SCNetworkCheckReachabilityByName from CodeWarrior
Next by Date: Re: Correct way to handle kEventCommandUpdateStatus?
Previous by thread: Re: Correct way to handle kEventCommandUpdateStatus?
Next by thread: Re: Correct way to handle kEventCommandUpdateStatus?
Index(es):
- Date
- Thread

Home