Looks like it on the surface Larry, but if you've seen my reply to
John Stiles, you will have noticed that my ulterior motive is to have
Carbon events, HIToolbox and CF objects scriptable. If you'd like to
rephrase this portion of your reply to include that ability, and can
suggest a cleaner faster way, I'm all ears.
Then I'm redefining the meaning of Carbon events and keeping all
you Apple engineers gainfully employed for years to come.
What you're suggesting is that they muddy the waters.
Nope, I'm suggesting an evolution.
GetApplicationEventTarget(), GetWindowEventTarget(), and
GetControlEventTarget() exist today. I don't see any difference if
there was to be a GetResourceManagerEventTarget(),
GetFileManagerEventTarget(), or a GetNavManagerEventTarget(). I
see usefulness.
You're missing the whole point of Carbon Events.
I'm redefining purpose by subsumption and merge so as to clarify and
simplify.
If you had that you could store all those things you're storing as
parameters in the CE above as values in a dictionary which could be
saved directly to a resource with something like AddCFResource.
That might be a reasonable enhancement to request, but your CE
approach is not well conceived.
AddCFResource() was implicit in my illustration. Once again, let's
see you script it.
Cheers,
Philip Aker
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
