On Wed, May 20, 2015, at 12:59 PM, Jens Alfke wrote:
>
> > On May 20, 2015, at 10:18 AM, Richard Charles wrote:
> >
> > This works but the problem is that there are undesirable side effects to
> > running the runloop once when this call is made.
>
> Yup. Manually spinning the runloop in any no
> I have a bit of code that posts notifications to coalescing notification
> queue.
> [...]
> In another place I need to force the notification queue to issue a did change
> notification.
>
> This works but the problem is that there are undesirable side effects to
> running the runloop once whe
> On May 20, 2015, at 10:18 AM, Richard Charles wrote:
>
> This works but the problem is that there are undesirable side effects to
> running the runloop once when this call is made.
Yup. Manually spinning the runloop in any non-custom mode is generally a bad
idea.
> What I would like to do
I have a bit of code that posts notifications to coalescing notification queue.
// Post did change notifications to a coalescing notification queue.
// Notifications are coalesced that match both the notification name and
// object. The notification is posted at the end of the current notification
