i see theres this NSAppleEventManager, and that with that you can "suspend" an event and resume it later. i think this is what i want.
but how do I get my app to force all these events to get sent (and therefore handled) on demand (before i go thru loading all the startup stuff)? i can only suspend an event if it's being handled. the problem is my app never gets to handle them.
On Nov 30, 2009, at 5:33 PM, David M. Cotter wrote:
> Coca64 only:
> recently our app has stopped responding to "odoc" apple events on startup. that is, if the user double clicks a document of our app, and this causes the app to launch, then the document is not opened. (cnr when app is already launched). same story dropping the doc icon onto the app icon (same code path).
> this functionality stopped working just recently. it was working before, now it's not. our suspicion is a new component during startup is eating the events (presume for the sake of this question that this can not be changed)
> in the olden days of Carbon, we had a similar problem, maybe the exact same problem. to solve it then, right at the very start of app init we would manually forcibly loop GetNextEvent(highLevelEvent) and store them all off in a vector. then do our (lengthy) startup procedure (which could suck up events), then when we're all done, loop over the vector and handle all the high level events. this worked like a charm. strange, but it worked.
> now i think we may need to do this again, but in Cocoa land.
> how do i manually pull these events out of the que? sincse there is no GetNextEvent().
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden