Thread with 8 posts
jump to expanded post
it extremely annoys me that you can have event-driven systems where you trigger an event and set up the event handler after the fact, hoping the event hasn’t actually happened yet
yes multiple early iPhone OS apps do this, why do you ask,
@hikari …in the same runloop iteration, or a subsequent one?
@saagar same runloop iteration… usually. ah, are you going to tell me there’s some guarantee about this? :)
@saagar something I’m not sure about is how NSNotificationCenter interacts with run loops.
@hikari I haven’t looked at this closely but I think the default is enqueuing but IIRC NSNotificationQueue lets you bypass that
@saagar ahh okay. touchHLE currently has an ad-hoc notification queue inside the “movie player”, simply because it never worked when I posted the notification immediately, but maybe I actually should put that queueing inside NSNotificationCenter itself…
