On Jan 31, 2012, at 11:29 PM, Ken Thomases wrote: > On Feb 1, 2012, at 1:20 AM, Gerriet M. Denkmann wrote: > >> >> Although the name of the notification is applicationWillBecomeActive it acts >> more like >> applicationIsAlreadySomehowActiveAndWIllBecomeFullyActiveRealSoonNow. > > Well, remember that this is Cocoa responding to an event delivered from the > system. Events are delivered asynchronously. The system can't afford to > wait for an app to respond to an event before moving on. > > There is bound to be an interval of time between when the system changed > which app is active and when Cocoa actually acts on the event it received > because of that change. > > Regards, > Ken
It would be nice if it were one of the notifications that tells you what's losing the state that you're gaining. I suppose it's worth filing a bug requesting that; the last active app is a useful thing to know. I dug into this because when I put up a dialog saying that an inter-app operation failed, I wanted the activation to go back to the app that started the operation when the dialog was dismissed. Glad to hear it was helpful anyway. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
