Correct, by your say so, or not if the timers don't drive the program it just sits there and does nothing. Human intervention is required to configure it or cause it to quit.
On Jul 5, 2012, at 8:24 PM, Graham Cox wrote: > > On 06/07/2012, at 5:57 AM, Charlie Dickman wrote: > >> I have a demonstration app that is basically operating on a 0.15 second >> timer loop. The problem I am having is that even with a periodic timer going >> off it is very difficult to get menu events and mouse clicks in window >> controls through to be processed. I have tried setting up an additional flow >> of events using >> (NSEvent) + >> (void)startPeriodicEventsAfterDelay:(NSTimeInterval)delaySecondswithPeriod:(NSTimeInterval)periodSeconds >> >> as well as >> >> [[NSRunLoop currentRunLoop] runUntilDate: [NSDate >> dateWithTimeIntervalSinceNow: t != 0. ? t * 1.01 : .01]] >> >> (where t can be set arbitrarily but is typically called with a value of >> 0.15) but none of this improves response. Is there anything else to try? > > > Well, you could try writing your app correctly, rather than polling and > running the event loop manually. > > What are you trying to do? Why can't you let the event loop run normally? > > > --Graham Charlie Dickman 3tothe...@comcast.net _______________________________________________ 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
