RE: OTEnterNotifier
RE: OTEnterNotifier
- Subject: RE: OTEnterNotifier
- From: Quinn <email@hidden>
- Date: Mon, 20 Mar 2006 11:22:35 +0000
At 20:14 -0800 19/3/06, Tim Dorcey wrote:
Thanks for any advice. I know I'm a bit behind the curve here.
I'm a little confused by your question, but I can give you some facts
and let you draw your own conclusions (-:
OTEnterNotifier does not block waiting for notification routines to
complete, or anything like that. It simply sets a flag that prevents
further notifications from being delivered. These queued events are
deferred until you call OTLeaveNotifier.
I saw some code somewhere where the user had explicitly bracketed their
Notifier callback code with OTEnterNotifier/OTLeaveNotifier. I take it this
is redundant, but causes no harm?
It causes no harm /if/ you follow the rule that you must only call
OTLeaveNotifier if OTEnterNotifier returned true. It can be a useful
technique if you have common code that can be called from various
environments (notifier, non-notifier deferred task, system task, and
so on).
S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden