> On 1 May 2015, at 19:13, Uli Kusterer <witness.of.teacht...@gmx.net> wrote: > > On 01 May 2015, at 04:15, Graham Cox <graham....@bigpond.com> wrote: >> When the calculation for a tile is finished, it calls its delegate to tell >> it it has finished. The delegate is the original view. I use >> -performSelectorOnMainThread: to notify the delegate. > > Idea: Have you tried using > performSelectorOnMainThread:withObject:waitUntilDone:modes: and making sure > to not just pass NSDefaultRunLoopMode but also NSEventTrackingRunLoopMode > (and maybe even NSModalPanelRunLoopMode)? > > The run loop that runs while the menus are pulled down is the tracking mode, > so your messages may not fire because of that, and maybe you have an issue > where, after a while, somehow they don’t fire at all even after tracking?
I don’t think that theory fits the observations, not as I understand them. I didn’t see any comment that Graham had issues with his messages not firing back to the main thread when the menu was up, or in fact at all, but just that the progress indicator stopped spinning when menus were opened, indicating not progress but a jammed main thread; and the stack trace seems to indicate that the main thread is indeed blocked on a synchronous call to launch services during the opening of the menu item, not running the event loop in any mode, in fact not running anything at all. _______________________________________________ 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
