Data from thread to NSView, efficiently
Data from thread to NSView, efficiently
- Subject: Data from thread to NSView, efficiently
- From: "William Zumwalt" <email@hidden>
- Date: Fri, 6 Jul 2007 22:12:32 -0500
I would just like to know if I'm going about this idea correctly. I have a
thread that's constantly passing back status and measurement data via DO
calls to my main process. The bigger the problem, the more data that gets
sent back, tens of thousands of loops easily.
The measurement data is just a few primitive types that, once they reach my
main controller in my apps parent process, I then pass into another
controller (via [recv msg]'s) so that a graph view gets updated where I draw
the results in Quartz.
Where I'm questioning my process is ... there's just so many method calls.
In my child thread it's a continuous loop of calculations where data is
passed back to the main thread. That's a whole bunch of method calls ...
err, or messages to the receiver and I don't know if there's not a better
way in cocoa that I'm not aware of or how to tell if I'm overloading through
DO and not bottlenecking something along the way if there's really a lot of
overhead here.
It works, but it just doesn't seem right. Is there a better way, or is that
wrong?
_______________________________________________
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