[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: David Duncan <email@hidden>
Date: Fri, 29 Aug 2003 22:27:06 -0400

On Aug 29, 2003, at 03:35 PM, Eric Schlegel wrote:

On Aug 29, 2003, at 12:28 PM, Pietrzak, Bryan wrote:

But, here's a question Eric. And tell me if it's too skanky...

Couldn't I set that attribute today. And then if my app is running on 10.3
or later, I my command handlers just ignore menu items with that command,
letting the OS do the work. But, if on 10.2 or earlier, check that attribute
and disable the command.

Yes, you could probably do that.

Except for the fact that IBCarbonRuntime on 10.2 or earlier would ignore the flag would it not?
--
Reality is what, when you stop believing in it, doesn't go away.
Failure is not an option. It is a privilege reserved for those who try.

David Duncan
_______________________________________________
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.

References:
	>RE: Correct way to handle kEventCommandUpdateStatus? (From: "Pietrzak, Bryan" <email@hidden>)
	>Re: Correct way to handle kEventCommandUpdateStatus? (From: Eric Schlegel <email@hidden>)

Prev by Date: PB Debugger and Virtual Bases Problem
Next by Date: Re: [OT] Commenting source code
Previous by thread: Re: Correct way to handle kEventCommandUpdateStatus?
Next by thread: Re: Correct way to handle kEventCommandUpdateStatus?
Index(es):
- Date
- Thread

Home