Re: Access to events in tight loop?
Re: Access to events in tight loop?
- Subject: Re: Access to events in tight loop?
- From: Scott Anguish <email@hidden>
- Date: Mon, 28 Jul 2008 15:55:56 -0400
do you have to use the tight loop approach? The view documentation
discusses the pros and cons of this approach and other options.
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaViewsGuide/SubclassingNSView/chapter_6_section_4.html#/
/apple_ref/doc/uid/TP40002978-CH7-SW27
On 28-Jul-08, at 11:53 AM, Scott Squires wrote:
If I handle a mouse event and am processing it in a time consuming
method which includes display, what's the cleanest way to peek at
events
during this time (to get updated mouse info,etc ) or to allow the
run loop to continue enough to make another pass?
Is there a clean way to allow the main thread to update?
I know I could create another thread for the routine but with issues
of events, drawing and handling mutable arrays I thought I'd see if
there was a simpler method I was overlooking.
Thanks.
_______________________________________________
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