Re: NSProgressIndicator (CallBacks)
Re: NSProgressIndicator (CallBacks)
- Subject: Re: NSProgressIndicator (CallBacks)
- From: Alastair Houghton <email@hidden>
- Date: Thu, 19 Jul 2007 09:19:47 +0100
On 19 Jul 2007, at 08:37, Barry wrote:
Thanks for this
My app is doing some heavy matrix maths on images - could be busy
for many minutes depending on image size etc..
Since you mention that, have you looked at Apple's Accelerate
framework? It includes lots of routines you can use for this type of
work, and they've spent a lot of time optimizing them to make them go
fast on the various different CPUs you might be running on.
I guess the CPU is so busy with this it cannot update the display.
No, that's not the problem. It's that you aren't handling events.
I may have to attempt to break the maths into small units & use
multi-threading but this will not be easy !
One or the other; you don't need to do both. The point of threading
is that you can write your code the same way you would normally,
except for the fact that any communication with another thread
requires locking or thread-safe queues or similar. (In Cocoa,
there's a very convenient -
performSelector:onMainThread:withObject:waitUntilDone: method that
you can call to send a message to your main thread.)
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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