Re: Tight loop processing
Re: Tight loop processing
- Subject: Re: Tight loop processing
- From: "Mike R. Manzano" <email@hidden>
- Date: Thu, 10 Apr 2008 15:16:02 -0700
Depending on the nature of your simulation, and if you don't mind
being Leopard-only, you might break it down into a series of
NSOperations and let Cocoa handle the rest for you.
Mike
On Apr 10, 2008, at 11:00 AM, Don Arnel wrote:
Hey all...
This is my first time posting to this list. I've been a Windows
developer for many many years and have just recently started to play
around with Macs. I feel like a beginner all over again! Anyway....
I've got a Cocoa application which runs a simulation loop 1000s of
times. Of course, this prevents any user interaction with the rest
of the program while the simulation is running. When I was
programming for Windows there was a call in Visual Basic
(app.DoEvents()) which would process any pending events. You could
put DoEvents() inside long loops to prevent blocking user input. Is
there a similar way to handle this in Cocoa?
Thanks for any help!
- Don
_______________________________________________
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
_______________________________________________
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