> On Sep 26, 2015, at 10:55 AM, Programmingkid <programmingk...@gmail.com> > wrote: > > I think the reasoning for this is the user interface is expected to be > responsive and if other processes are running, then the interface will be > sluggish.
Not at all. All processes are always running — the OS has pre-emptive scheduling. And the hardware is capable of playing Call Of Duty at 60fps so it’s not like rendering a few menus is much work for it :) > Would you have additional documentation or sample code I could look at? The > event loop timer info looks interesting. The Cocoa Event Handling guide is probably where you want to start. You could also read the API docs on NSRunloop and NSTimer. —Jens _______________________________________________ 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
